Do you need a CTO, or something lighter?
Answer questions on your product, team, suppliers, security, funding, delivery and AI plans. You get a leadership need score across eight dimensions and a recommendation between an advisor, a fractional CTO, an interim CTO or a full-time hire, with reasons, risks and next steps.
Do you need a CTO?
Answer honestly, or start from the preset closest to you. Your score and recommendation update with every answer.
- Product complexity50
- Team size and leadership50
- Technical decisions pending63
- Vendor dependence83
- Security and compliance33
- Fundraising and diligence67
- AI strategy and readiness67
- Delivery health33
- Fractional CTO93%
- No CTO yet: use an advisor23%
- Full-time CTO hire12%
- Interim CTO0%
- You rely heavily on outside developers and need someone on your side who can check their work.
- Investors or acquirers will examine your technology and technical leadership closely.
- AI matters to your product or delivery, but lacks a clear strategy or guardrails on quality, data and IP.
- A fractional CTO has limited hours, so priorities must be explicit or the role drifts into firefighting.
- If the team grows past roughly ten engineers, plan for a full-time leader and use the fractional CTO to hire them.
- Heavy dependence on one supplier: secure ownership of code, credentials and documentation before any leadership change.
- Write down the three outcomes the role must deliver in the first 90 days.
- Start with a technical review of architecture, code quality, security and supplier dependence.
- Set an AI-native delivery approach with clear review standards, so the team gets faster without adding risk.
- AI readiness is your weak spot. Whoever leads technology should set a policy on AI-generated code review, customer data in AI tools and model vendor risk within the first month.
- With AI in the product, check that your technical lead can reason about model choice, inference cost, evaluation and data privacy, not only application code.
Indicative only. We will send the inputs above with your message so a senior engineer can sanity-check them.
The question is not whether you need technical leadership. It is how much, and in what form.
Every company that depends on software needs someone accountable for technical decisions. What varies is how many hours that takes, how urgently, and whether you can afford a permanent executive. Founders often jump straight to "we need to hire a CTO" when an advisor would do, or wait far too long while a supplier makes decisions no one on their side can check.
AI has raised the stakes on both sides. Product plans now include AI features with real cost, privacy and quality implications, and engineering teams use AI tools that need clear rules on review and data. Someone has to own those choices, whatever their job title.
How the CTO readiness score is calculated
Each answer adds between zero and three points of leadership need to one of eight dimensions: product complexity, team size and leadership, technical decisions pending, vendor dependence, security and compliance, fundraising, AI strategy and readiness, and delivery health. Dimension scores are normalised to 100, then combined with weights that give slightly more influence to product complexity, team and delivery, because those predict leadership problems most directly.
Two further questions, on budget and leadership transitions, do not change the score. They decide which form of leadership fits. A high need with a small budget points to fractional leadership. A leadership gap happening now points to interim cover. A high need, a real team and a budget for an executive point to a full-time hire.
The result shows how well each of the four options fits rather than a single verdict, because the boundaries are genuinely fuzzy. If two options score closely, that is a signal to talk it through with someone who has seen both work.
Advisor, fractional, interim or full-time CTO
Four ways to get technical leadership, each suited to a different stage and situation.
| Best when | Typical commitment | Watch out for | |
|---|---|---|---|
| Technical advisor | Early stage, few engineers, occasional big decisions | A few hours a month | No one accountable for delivery |
| Fractional CTO | Real product and team, budget for part-time leadership | One to three days a week | Hours spent firefighting instead of direction |
| Interim CTO | Leader has left, rebuild, vendor exit or acquisition | Near full-time for a few months | Becoming permanent by accident |
| Full-time CTO | Technology is core, team growing, funding in place | Permanent executive role | Hiring before there is a team to lead |
Commitments are typical patterns, not rules. Many companies move from advisor to fractional to full-time as they grow.
Signs you need a CTO sooner than you planned
You cannot tell whether your developers are doing a good job
If quality, estimates and progress reports have to be taken on trust, you need someone who can check them.
One supplier holds your code, hosting and knowledge
If changing agencies would mean starting again, your biggest risk is not technical, it is commercial.
Enterprise customers are asking security questions you cannot answer
Security questionnaires and certification requests are a sign the business has outgrown informal practices.
Investor due diligence is on the horizon
Investors look at architecture, code ownership, security and the team. Gaps found late cost time and valuation.
AI is on the roadmap with no one owning the decisions
Choosing models, controlling inference cost, protecting customer data and reviewing AI-written code all need a technical owner.
Deadlines keep slipping and nobody can say why
Persistent delivery problems are rarely about effort. They usually trace back to unclear scope, architecture or leadership.
Questions we often hear
When should a startup hire a CTO?
Typically when technology is core to the product, there is an engineering team of several people to lead, and the company has the funding to support an executive salary. Before that, most startups are better served by a technical co-founder, an advisor or a fractional CTO who can make the key decisions without the cost of a permanent hire.
Do I need a CTO if I outsource development to an agency?
You need someone on your side who can judge the agency’s work, even if it is not a full-time CTO. Without that, you cannot assess estimates, code quality, security or whether you truly own what is being built. A fractional CTO or technical oversight arrangement is a common answer for outsourced products.
What is the difference between a fractional CTO and an interim CTO?
A fractional CTO is ongoing part-time leadership, often for months or years, suited to companies that do not yet need a full-time executive. An interim CTO covers a gap or transition, usually close to full-time, with a planned handover to a permanent leader.
Do I need a CTO to build AI features?
You need someone who owns the technical and risk decisions behind them: which models to use, how to control inference cost, how customer data is handled and how quality is evaluated. For many companies a fractional CTO with AI experience covers this well. A full-time hire makes sense when AI is core to the product and the team is growing.
How accurate is this CTO readiness assessment?
It is a structured starting point, not a diagnosis. The weights reflect common patterns in how companies outgrow informal technical leadership, but your specific supplier contracts, team dynamics and investor expectations can change the answer. Treat a close result between two options as a prompt for a conversation.
Related reading and tools
Get the right technical leadership for your stage.
Send us your result and a little about your company. Irwan has led technology at startups and global enterprises for more than 18 years, and will give you an honest view on what kind of leadership you need, even if the answer is not us.
Working with companies globally · Response within 24 hours