Founders ask this question in two ways. Some search for a fractional CTO for their MVP. Others search for a temporary CTO, someone to own the technical side until the product is live and the first engineer is hired. It is the same need: you have something to build, nobody on the team can judge how it should be built, and a full-time CTO is too early and too expensive.
Most of the advice you will find on this comes from build studios, and a lot of it says the same thing: build first, hire the CTO later. That is right if someone on your team can read an estimate and tell a good sprint from a bad one. If nobody can, you are signing the biggest cheque of your first year with no one on your side of the table.
How long a first build takes
Here is how our Build & Ship work lays out a typical MVP:
| Phase | Time | What happens |
|---|---|---|
| Discovery and architecture | Weeks 1 to 2 | Requirements, stack, system design, a plan with milestones, and the detailed cost estimate |
| Build sprints | 6 to 8 weeks | Two-week sprints with a demo of working software every week |
| QA and launch | 1 to 2 weeks | Testing, security review, CI/CD, monitoring and go-live |
Four things stretch it:
- Regulation. A greenfield healthcare product that has to be HIPAA compliant from day one usually takes 10 to 16 weeks, because access control, audit logs and data handling have to be designed in, not bolted on.
- A second kind of user. A product with one type of user is one build. A marketplace or a product with separate patient and clinician sides is closer to two.
- Integrations. Every outside system you connect to, such as payments, an EHR or an ERP, adds work and adds a party you do not control.
- Slow decisions. In a 10-week build, a week spent waiting for the founder to answer a question is a tenth of the schedule. This is the one you control completely.
What it costs
A first build has two cost lines, and it helps to keep them separate even when one firm provides both.
The build. At Kompella, MVP builds typically range from $50,000 to $150,000+, depending on complexity, integrations and platforms. We give a detailed scope and estimate at the end of the 2-week discovery phase, before any build commitment. Be wary of a firm price before anyone has done discovery. Either the scope is vague, or the price is.
The CTO time. Our fractional CTO services page publishes three tiers:
| Tier | Monthly fee | Time |
|---|---|---|
| Advisory | $8,000 | 1 day a week |
| Fractional | $15,000 | 2 days a week |
| Embedded | $25,000 | 3+ days a week |
For context, our fractional CTO cost guide puts a full-time CTO's first year at $350,000 to $550,000+ once salary, benefits and recruiting are counted, before equity, and the search alone often takes 6 to 9 months. That is longer than the whole build.
What the fractional CTO does during the build
The build team writes the code. The fractional CTO makes sure it is the right code, built in a way you can live with. In practice that means:
- Writing the scope with you. The most common first-build failure is not bad code. It is building too much. The CTO's first job is cutting the feature list to the smallest version the first customers will pay for.
- Checking the estimate. A senior person who has shipped similar products can tell you whether a quote is padded, thin, or missing whole pieces like admin tools, billing or monitoring.
- Choosing the stack and architecture. Mainstream, easy to hire for, and cheap to run at your expected usage. A first product rarely needs microservices.
- Accepting each sprint. At the weekly demo, someone on your side has to say "this is done" or "this is not done". That person should not work for the build team.
- Setting up ownership from day one. The code repository, cloud accounts, domain and app store accounts should be in your company's name, with the build team added as users. Fixing this after launch is awkward, and fixing it after a dispute is worse.
- Hiring the first engineer. If the plan is to bring the product in house, the CTO writes the role, runs the technical interviews and hands over.
- Answering investors. Seed investors will ask how the product is built and what the technical risks are. A founder who can answer, with the CTO in the room if needed, raises with fewer follow-up questions.
Match the CTO's days to the shape of the build
This is the part most budgets get wrong. Founders pick a tier at the start and keep it flat for the whole build. But the need for senior judgment is not flat. It peaks twice.
The first peak is discovery and architecture. This is where the decisions that are expensive to reverse get made: what is in scope, which stack, how data is modelled, how users and permissions work, what has to be compliant. Two days a week is about right here.
The middle is quieter. If the build team has a capable lead and runs weekly demos, the CTO's job is to review, accept sprints and catch drift early. One day a week is often enough.
The second peak is launch. Security review, the go-live plan, what happens when something breaks at 2am, and the first real customer feedback all land in the same few weeks. Back to two days.
Worked example using our published tiers: on month-to-month terms, a three-month build planned this way costs $15,000 for the first month, $8,000 for the second and $15,000 for the third, a total of $38,000 against $45,000 at a flat two days a week. The saving matters less than the timing. You are buying the most senior time exactly when the hardest decisions are being made.
One caution. If nobody runs the build day to day, for example because you are hiring freelancers rather than a team with its own lead, do not drop to one day in the middle. Someone has to own the work every week, and if it is not the build lead, it has to be the CTO.
What "temporary CTO" should mean for a first product
A temporary CTO usually means one of two things, and our article on interim CTO vs fractional CTO covers the difference in full. Interim cover is for an empty CTO seat with a team that needs an owner. A first build usually has no team yet, so what you need is a fractional CTO with an end date.
Write that end date down as an end state, not a month:
- The product is live and has paying or active users.
- Your first engineer or tech lead is hired and has been through a handover.
- The code, cloud accounts and documentation, including the reasons behind the main architecture decisions, are in your company's hands.
When you don't need one yet
Not every first product needs a fractional CTO. Skip it if:
- You have a technical co-founder who has shipped real software and is working full time on the company. Adding a second senior voice creates confusion about who decides.
- The product carries little technical risk, such as a store or a content business on standard tools.
- You are still at the idea stage, with no customers to talk to and no decisions in flight. Senior judgment is most useful when there is something to decide. Our piece on when pre-seed founders need a CTO goes into this.
What the work has looked like
At A'alda, a veterinary healthcare company, we served as fractional CTO and CPO and built the technology platform from scratch, then guided the technology due diligence for its IPO in Japan. The platform was designed from the start to support expansion into several countries, and the same architecture later went through IPO due diligence.
For Dr. Morepen we built the ERP system for its pharmacy operations, and the company is expanding its pharmacy presence on it. Business systems like this are a good reminder that the messy real-world parts, such as existing data and the other systems it has to talk to, belong in the discovery estimate rather than being found in sprint four.
Aesthetic Record shows the other end of the timeline. The company already had early traction when we joined, and over 4 years as fractional CTO the work was re-architecting the platform for scale and HIPAA compliance as it grew to more than 4,000 US clinics. Much of that work is easier or harder depending on choices made in the very first build.
The short version
Plan on 8 to 12 weeks to build a first product, longer if it is regulated, and two cost lines: the build at $50,000 to $150,000+ and the CTO at $8,000 to $15,000 a month for most first builds. Put more CTO days at the start and at launch, fewer in the middle. Define the end state before you begin, and keep every account in your company's name.
Need help thinking this through? Book a 30-min call, no pitch. Book a Free 30-Min Strategy Call →
