Will it hold up when customers arrive?
I test the workflows your customers need and find where things slow down, fail or stop responding. You learn what to fix now and what can wait.
Hands-on CTO for early-stage startups
It works in the demo. But what happens when your first customers arrive? I find what might break, help fix the important parts and get the product ready to launch. You may not need a rewrite.
You know what is ready to ship and what still needs work.
Services
I test the workflows your customers need and find where things slow down, fail or stop responding. You learn what to fix now and what can wait.
I check whether one customer can see another’s data, who can change key settings and whether you can recover your data if something goes wrong.
I set up automated tests and a release process. If an update breaks a core feature, the team can return to a working version.
AI can draft code, tests and documentation. I set up its working environment (an agent harness): what data and tools it can use, who checks the output and what needs approval.
Not necessarily. I can join for the launch, work directly on critical fixes and help you decide who to hire and what to hand over to the team.
People, agents and control
You don’t need a technical brief to start. Show me the product, tell me who is coming at launch and explain what worries you.
I try the customer journey and look at how the product works under the hood.
I explain what could derail the launch, what it will take to fix and what can wait.
I take on critical fixes or work with your team. We check the changes before customers see them.
Example: launching a pilot
We make sure a new customer can sign up and do the one thing they came for. We repeat it under expected traffic, check that they only see their own data and make sure the team can spot a failure.
You get a list of what passed, what needs fixing by Monday and what can wait.
Your technical partner
I started as a developer and became a team lead and CTO. I’ve led engineering for large organizations and now build products with AI myself. I can explain a technical decision in plain language, work on the code and organize the team.
B2B SaaS architecture and integrations with marketplaces and enterprise systems.
Led development, implementation and support for enterprise systems. Coordinated engineering and integrations in public healthcare.
I build the working Molv Slovo MVP and the separate Molv AI Force platform. My work covers architecture, AI-assisted development, testing and releases.
Frequently asked questions
Yes. I first review what you’ve built and what you have access to. Then we decide what to keep, fix or replace.
Not necessarily. If the problems are limited to a few areas, fix those first. A rewrite only makes sense when the current approach cannot safely take you to launch.
Yes. Show me the demo and tell me the launch plan. I’ll help work out what needs an engineer and what AI can assist with under review.
We don’t send customer data to AI tools by default. If a use case needs it, we agree on which data may be used and where it can go.
A plain-English list of risks, a prioritized list of fixes and clear conditions for launch. Then you can decide whether you want help implementing the changes.
Send a demo link, your launch timing and your biggest concern. No repository access or credentials needed for the first conversation.