What a Fractional CTO Engagement Looks Like

"Fractional CTO" is one of those terms that means different things at different stages of a company. The honest version of the engagement, and the one Varstatt offers, sits at one specific point on the arc: pre-team, pre-product or post-pivot, founder-plus-one.

Fractional CTO = Founding Engineer at the Pre-Team Stage

For an early-stage startup, the fractional CTO and the founding engineer are the same person — the senior developer who builds your first version.

There's no team to lead yet. There's no hiring funnel to run, no engineering org to manage, no board call where someone needs to translate sprint velocity into business risk. There's an idea, a Figma file, and a founder who needs working software. The job at this stage is technical: pick the stack, make the architecture calls, ship the product, watch it in production. A senior person who does that is the CTO of the company while there's only one of them — there isn't a separate "leadership" job to fill on top.

Once you reach the stage where CTO-as-management actually matters, you need a full-time CTO, not a fractional one.

The split a lot of services sell — a fractional CTO who advises a few hours a week while a separate engineer or agency does the work — is unstable past pre-product. Real management of a real engineering team isn't a fractional job. The fractional version becomes a hiring consultant or a coach. Both are useful but neither is what someone usually means by CTO. By the time you have engineers who need leading, the company can afford the full-time hire — and the half-time version becomes a bottleneck instead of a leverage point.

That's why this engagement sits at one end of the arc and a full-time hire sits at the other, with relatively little in between.

The Shape

The fractional-CTO version of the Varstatt weekly retainer is the same retainer as every other shape: $997/week, cancel anytime through Stripe, senior engineer working on your product week after week, no minimum commitment. The "fractional CTO" framing just describes the position the engagement fills — the founding-engineer / first-developer / architect-and-builder role, condensed into one person on a weekly retainer.

If your bottleneck is "I already have engineers and need senior leadership for them," that's the full-time CTO question — and the right time to make the hire is now, not split the role into a fractional version of someone else's job. If your bottleneck is "I have an idea and I need a senior person to actually build it," keep reading.

What This Engagement Covers

The work the retainer does, week after week:

• Architecture decisions — stack, infrastructure, build vs. buy — made by someone who has shipped commercial software since 2011
• Working code, shipped weekly, against priorities you set on a shared task board
• An honest read on technical risk: what is breakable, what is irreversible, what can wait
• Direct, async-first communication — no daily standups, no status meetings
• A codebase you fully own from day one (client owns everything)
• Pause and resume freely through Stripe — the engagement bends with the work, not the calendar

Out of scope, by design:

• Engineer hiring — no resume screening, interviewing, or offer negotiation
• Team management — no 1:1s, performance reviews, or managing other developers
• Board updates, investor decks, fundraising material
• An advisor who only writes documents and never opens the editor

How This Differs From Other Pre-Team Engagement Shapes

A few related shapes occupy the same pre-team slot. Quick read on each so the choice is clear:

• Full-time CTO. The right answer once you have a team to lead. Pre-team it's expensive idle capacity — the salary load is most of a seed round and the role doesn't have enough of its own work to fill the week.
• Traditional fractional / virtual CTO. Advisory hours, strategy work, oversight of someone else's implementation. Right fit when you have engineers who need direction and you don't yet need full-time leadership over them.
• Technical co-founder. Same scope as this engagement, but as equity instead of cash. Right fit when you find one — the supply is small and the matching is hard.
• Development agency. Optimised for delivery throughput against a defined scope. Right fit when the scope is well-defined and the founder doesn't need a partner on the architecture decisions.
• Freelance developer. Cost-efficient for implementation when you have the spec. The fractional CTO / founding engineer role is partly about making the spec, so it sits one rung above this.

The retainer described here is the founding-engineer slot specifically: senior judgment, hands-on implementation, weekly cadence, no agency layer.

Plenty of companies start with this engagement and graduate to a full-time CTO once they have a team that needs leading. That's the expected arc, not a failure of the model.

What the First Six Months Look Like

Month one is product setup and the first features. Stack chosen (the default stack unless there's a strong reason otherwise), repo configured, deploy pipeline live, auth and core data model in place, first user-facing flows shipped.

Months two through four are sustained build. One major capability per month, broken into weekly tasks. Each week ships something reviewable. The product compounds. You stop sending me Loom videos explaining what you want and start sending me task tickets because the shorthand develops.

Months five and six are usually one of three branches. Some founders ramp to a full team and either keep me as the senior IC alongside the new hires, or hand off and graduate. Some hit product-market-fit signal and shift the engagement toward growth features and scale work. Some pivot or pause — and the retainer pauses cleanly with them.

None of those branches require a contract change. The retainer runs the same way regardless of which branch you're on.

Who This Is For

Non-technical founders who built a deck, did discovery, and now need a working product. Technical founders who can code but want a senior partner sharing the architecture load. Operators who acquired a small SaaS and need someone competent running the engineering side without hiring full-time. Solo founders post-pivot who need to rebuild quickly without re-onboarding an agency.

If you are pre-team and pre-traction and you searched "fractional CTO" because you wanted someone to build with you, this is the engagement.

Other Shapes the Retainer Takes

Same retainer, different shapes — pick the one that matches the work in front of you:

• What a 2-Week PoC Looks Like — when the first thing to do is validate one technical assumption
• What a 6-Week MVP Build Looks Like — when the shape is clear and v1 is the next step
• What a Code Audit Looks Like — when there's already a codebase that needs senior eyes first
• All retainer shapes →

How to Start

The path is the same for every shape:

1. Submit a project brief — 2–3 minutes. Within 24 hours, you get an honest read on whether this engagement fits.
2. 15-minute discovery call — confirm scope and timing, no sales pitch.
3. Subscribe to the weekly retainer — work begins the next business day. Cancel anytime through Stripe, no paperwork.

If you have questions before any of that, the project brief form has a free-text field — write whatever you need to.