Services
Fractional CTO / AI lead
Part-time technology leadership for companies that need a CTO, but not a full-time one. Strategy, team, vendors and AI.
Services · MVP in 14 days
A working first version of your product in 14 days
For founders without their own developers and for companies that want to test an idea quickly with real users.
What you are dealing with
You have had the idea for months, but still no product
An agency wants six months and a budget you do not have. A freelancer makes promises, but the deadline slips and the scope keeps growing.
You pay by the hour and do not know where it ends
Hourly billing means every change and every bug goes on your bill. You find out the final price only at the end.
You want to test the market, not build a finished system
You need something to show customers or investors. Not a perfect product that arrives when it is already too late.
What belongs in an MVP and what does not
An MVP should answer one question: does anyone want this? Anything that does not help answer it is moved to the next version. That is why we cut the scope together at the kick-off workshop.
| Belongs in the MVP | Does not belong in the MVP |
|---|---|
| One main scenario from start to finish | All edge cases and exceptions |
| User login, if necessary | Complex roles and permissions |
| Simple data administration | Advanced reports and dashboards |
| A basic payment or order, if the idea requires it | Integration with several payment gateways and accounting |
| A responsive website that works on mobile | Native mobile apps for iOS and Android |
| A clean, clear look | A custom design system and animations |
The line is not set in stone. If an item from the right-hand column is essential to your idea, we bring it into scope and drop something else. The 14 days do not change; the content does.
A good MVP is narrow rather than wide. One feature that users actually use beats ten features they only try out. If the workshop shows that the idea cannot reasonably fit into 14 days, we tell you straight away and suggest a different approach.
What happens after 14 days
You get a working application on your domain, the code in your repository and documentation. Then it is time to put the MVP in front of users and collect feedback. Once you know what works, we can plan the next version. If the MVP grows into a company with its own team, we can continue as your fractional CTO.
What you get
- Kick-off workshop and a written specification with a clear scope
- Clickable prototype of the main screens for your approval
- Working web application deployed on your domain
- Source code in your repository, including the rights to it
- Basic documentation and an operations guide
- Handover meeting and a list of recommended next steps
How it works
day 1
Kick-off workshop
We go through the idea, the target user and the main scenario. Together we cut everything that does not belong in the first version.
days 2–3
Specification and prototype
You receive a written scope and a clickable prototype. Once you approve it, the scope is locked.
days 4–12
Development
We build with an AI-assisted approach and show you finished parts along the way so you can see progress.
days 13–14
Handover and deployment
Testing, deployment on your domain, handover of code and documentation, and a handover meeting.
Who it is for
- Founders who do not have their own developers
- Companies that want to test a new product or service
- Projects with one clear main use case
- Situations where you need something to show customers or investors
Who it is not for
- Projects whose scope cannot be narrowed to one main scenario
- Systems with demanding regulatory requirements from day one
- Briefs that are expected to keep changing during development
Why work with us
One person from brief to deployment
Michal Czerník manages the full SDLC from analysis to operations. Nothing gets lost in handovers between analyst, designer and developer.
AI-assisted development saves time
We build applications with Claude Code. Routine code is written quickly, leaving time for what matters most, which is scope, quality and testing.
Experience keeping scope under control
Experience leading teams and in the CTO role helps say “not now” at the right moment. That is why 14 days holds in practice.
Frequently asked questions
Is it really possible to build an MVP in 14 days?
Yes, as long as the scope is narrowed to one main use case. That is why we start with a workshop and lock the scope once the prototype is approved.
How much does an MVP cost?
We set a fixed price upfront based on the agreed scope, with no hourly rates. You receive the specific amount after the initial consultation.
Who owns the source code?
The source code belongs to you and we hand it over into your repository. You can keep working on it with anyone you choose.
What if I come up with a new requirement during development?
We add the new requirement to the list for the next version. It goes into the current scope only in exchange for something else, so the deadline holds.
What happens after handover?
After handover, you decide how to continue. We can carry on with further development, or your team or another vendor can take over the code.
Which technology do you use?
We choose common, well-supported technologies so that another developer can work on the code too. We explain the specific choice at the workshop.
Related offers
Services
Excel to app
An internal application instead of shared spreadsheets. Stock, orders, attendance or approvals in one tool, accessible over the web.
Services
Connectors for Pohoda, Money, ABRA
Connecting Pohoda, Money or ABRA accounting with your e-shop, CRM and warehouse. No more retyping orders and invoices by hand.
Free consultation
Tell us what you are working on. We will get back to you and arrange a short call to see whether and how we can help.