Playbook · The CTO role

Updated

What does a good technology roadmap look like?

A good technology roadmap is one page per quarter that ties each technical piece of work to a business goal, names what you will not do, and says what has to be true before the next step starts. The example below is made up for an imaginary startup, so you can see the format without reading a client’s plan.

Custom software projects reviewed on Clutch average $132,480 and take about 13 months. Most cost $10,000 to $49,999.
Source: Clutch, 21 Sep 2026

From my work

The roadmap is mostly about what to leave out. Itmatched had spent years on their MVP before it reached me. Once the legacy code was fixed, new requests came in: gift cards, promotions, analytics pages. I pushed back. Anything outside the MVP could ship after launch, or they would never leave the MVP loop. They agreed, and we went to production on time.

What every technology roadmap needs

  • The business goal for each quarter, in one sentence.
  • The technical work that serves that goal, and nothing else.
  • A “not now” list, so the team stops arguing about it.
  • Risks: what could stop the plan, like a key person leaving or a vendor changing its price.
  • A gate for each step: what must be true before the next quarter’s work starts.
  • Who owns each item, by name. Work that belongs to everyone waits for someone.

Example: an imaginary booking app

This is a made-up example. The company does not exist and this is not a client’s roadmap. Imagine a seed-stage startup selling class booking software to yoga studios. It has two engineers, a working MVP, 40 paying studios, and a goal of 200 studios in a year.

  • Q1, stop the leaks. Goal: keep the studios we have. Work: error tracking, backups that have been restored once, fix the three bugs behind most support emails. Not now: a mobile app. Gate: support emails down by half.
  • Q2, make sign-up self-serve. Goal: studios can start without a call. Work: onboarding flow, card payments, a staging environment. Not now: a marketplace for students. Gate: one studio fully onboarded without help.
  • Q3, get ready to grow the team. Goal: hire the third engineer. Work: written setup guide, code review rules, tests on the payment flow. Not now: rewriting the front end, however much the two engineers want to. Gate: a new hire ships to production in their first week.
  • Q4, prepare for the round. Goal: a clean technical story for investors. Work: security review, a cost review of the cloud bill, an architecture document. Not now: anything that cannot be finished before the round. Gate: a due diligence checklist with no red items.

Mistakes that make a roadmap useless

  • A list of features with no reason next to them.
  • Dates for work nobody has estimated. That is a wish with a calendar attached.
  • No “not now” list, so every request lands in the next sprint.
  • Written once, praised in one meeting and never opened again. Review it at the start of every quarter.

How I scope it

I start with the story the founder wants to bring to life, so we can find the one feature that has to work. Everything else gets sorted around it. My 14-day Trial starts the same way: a look at the code and the infrastructure, with findings ranked by risk in the first 5 business days. Then I fix what can be fixed in the 14 days, and it ends with a written plan for the rest and a walkthrough call. $995, one time. I sell this, so read it with that in mind.

Read next

Sources

Start

Tell me where the product is stuck.

In 30 minutes we look at where things stand, what you need from a CTO right now, and which option fits. Either way, you leave with a clear next step.

How the call goes

  1. 01You tell me about the product, the team and the next 6 months.
  2. 02I ask about the code, the stack and what keeps breaking.
  3. 03We pick the option that fits, or agree that none does.

09:00 to 20:00 CET

Founding rate: the first 3 clients get 20% off, in return for a named testimonial and a case study. On a monthly plan, the 20% applies to the first month.