Founders tend to frame this as a hiring question. It is usually a sequencing question. A fractional CTO, a consultant and a first senior technical hire buy different things: part-time ongoing ownership, a scoped decision, and full-time ownership with the engineering culture that comes with it. The common mistake is not picking the wrong one. It is giving one of them a job that belongs to another.
A six-person company that has not shipped a product does not need a CTO on the cap table yet. A 30-person company heading into a funding round with a codebase nobody fully understands does not need another adviser's opinion; it needs someone accountable. Between those two points the right answer changes more than once.
What follows is written for founders of 3- to 50-person companies, technical or not.
What is the difference between a fractional CTO and a technology consultant?
A fractional CTO owns your technology on an ongoing, part-time basis: they sit in leadership meetings, make architecture calls as they come up, manage developers or an agency, and stay accountable over months. A technology consultant is engaged for a defined question or deliverable, such as an architecture decision, a vendor choice or a pre-diligence review, and leaves once it is answered. One buys continuity, the other buys a specific answer.
The third option, a first senior hire, buys full-time ownership and something neither outsider can provide: culture. The first technical leader decides how code is reviewed, how incidents are handled and who gets hired next. That is the reason to make the hire, and the reason not to make it too early.
| Option | What you get | Commitment | Best stage | Main risk |
|---|---|---|---|---|
| Consultant | One decision or deliverable, with the reasoning written down | Scoped in advance, usually weeks | Before an expensive technical commitment or due diligence | Dependency, if every decision goes back to them |
| Fractional CTO | Ongoing technical ownership, part-time | Commonly one or two days a week, over months | Pre-product to early post-funding, with an agency or a small team | Too little time left for hiring and team building |
| First senior hire | Full-time ownership, hiring, engineering culture | Permanent, often with equity | Product in market and developers to lead | Hiring too senior, too early |
Which option fits which stage of a startup?
The deciding factor is whether there is a team to lead. Before a product exists, a consultant is usually enough for the few decisions that are expensive to reverse. After a first funding round, a fractional CTO can own the roadmap and run hiring. Once a product is in market and several developers need daily leadership, a full-time technical lead earns the cost. Before due diligence, an independent consultant gives investors a view the founders cannot.
Pre-product. The decisions that matter are few: what to build and what to buy, which cloud provider and stack, and what not to build yet. A non-technical founder is most exposed here, because an agency's recommendation is also its sales pitch. A short review from someone with no stake in the build is cheap insurance. The scarce input at this stage is the founder's attention, the same constraint behind algorithmic brand positioning for early-stage projects.
Post-funding. Now there is money to hire and a roadmap promised to investors. This is the natural home for a fractional CTO: someone who owns the plan, interviews candidates and keeps the agency honest while the team forms.
Scaling. Once several developers report to someone, part-time leadership shows its limits. Code review, on-call rotas, career conversations and hiring all need a person who is there every day.
Preparing due diligence. Investors and acquirers will ask about architecture, security, ownership of code written by contractors, and what happens if one engineer leaves. Better to find those answers yourself, before the other side's reviewer does.
Should a startup build, buy or wait on AI features?
In most cases, buy or wait. A startup should build only the part of an AI feature that encodes something proprietary, such as its own data or a workflow competitors cannot copy, and use an existing model through an API for the rest. If no customer is asking for the feature and no deal depends on it, waiting a few months usually costs little, because the underlying tools keep getting easier to use.
Cloud architecture follows the same logic. Start with managed services on one provider and defer anything designed for a scale you do not have. A 12-person SaaS startup running infrastructure built for a hundred engineers pays for it every week in time nobody budgeted.
Both are questions a consultant answers well: a written recommendation with the trade-offs and a date to revisit it, typically at the next funding round.
Where each option goes wrong
Consultant dependency. If every technical decision goes back to the same outside adviser, you have a CTO without the accountability. The test is simple: after the engagement, can someone inside the company explain the decision and its trade-offs? If not, the deliverable was the wrong one. Make written reasoning and a handover part of the scope, a point we cover in what Swiss companies pay for consulting.
A fractional CTO with no time to hire. One or two days a week fill quickly with firefighting. Hiring, the most valuable thing they could do, slips every week because nothing forces it. Put hiring into their objectives with named roles and dates.
Hiring too senior, too early. A technology executive from a 500-person company is used to managing managers, budgets and process. In a seven-person startup the job is writing code, choosing tools and recruiting the second engineer. A senior hire who no longer wants to build will either leave or start building the organisation they left, and early equity given to the wrong person is hard to recover.
How do you combine a consultant, a fractional CTO and a first hire?
In sequence, with a handover written into each step. A common pattern is a consultant who makes the architecture decision and writes the hiring brief, a fractional CTO or the founder who runs the search, and a first senior hire who takes ownership with the decision record in hand. Each step leaves a document behind, so the next person inherits reasons rather than opinions.
A useful hiring brief is short. It lists the decisions already made and why, the ones deliberately left open for the hire, the profile the stage needs, builder or manager, and what the first ninety days should produce. A non-technical founder should also bring an independent technical interviewer into the final round.
On choosing the adviser itself, see choosing a strategy consultant as a startup or SME and how to choose a management consulting firm in Zurich.
Public help before paid help
Swiss founders have public starting points worth checking before paying anyone. Innosuisse, the Swiss Innovation Agency, is the federal agency supporting science-based innovation and start-ups. The SECO SME portal covers the practical side of founding and running a company in Switzerland. Neither will make an architecture decision for you.
Our work with technology startups is mostly the consultant role described here: a scoped decision, written down, handed over. When the question is wider than technology, such as how the company should operate as it grows, it belongs to digital transformation.
Related reading
- What Swiss companies pay for consulting
- How to choose a management consulting firm in Zurich
- Algorithmic brand positioning for early-stage projects
- Technology and startups
Working on this right now?
Tell us where you are in two questions. A consulting partner reviews every enquiry within 2 business days.