
Hire a fractional CTO when a technical decision is holding back a business result and nobody in your company can own it. Typical moments: a build that keeps slipping, a vendor you cannot judge, your first engineering hires, or an integration or AI project that touches the core of your operations. A fractional CTO is a senior technology leader who works for you part of the week, so you get the judgment of a CTO without a full-time executive salary. At Ampersand, senior engineers stay on your project from the first conversation to handover, and that continuity is the reason this model works for founders and owners in Switzerland.
TL;DR
- Hire a fractional CTO when technology decisions matter every month but do not yet fill a full-time executive role.
- The strongest triggers are a stalled or over-budget build, vendor confusion, a first engineering hire, a legacy system that blocks growth, and investor or due diligence questions.
- Define the decisions you want owned, the hours per week and the handover before you start. Vague scope is the main reason these engagements disappoint.
- Judge the engagement by decisions made, risks removed and how much less you depend on the CTO over time.
- If you are still too early to need a leader, a short audit or a scoped build is usually the better first step.
What a fractional CTO actually does
A CTO (chief technology officer) is the person accountable for how a company’s technology supports its business: what gets built, with whom, on which platform, at what risk and cost. A fractional CTO does that job for a fixed share of the week, often one to three days, instead of five.
In practice the work falls into a few areas:
- Direction. Turning business goals into a technology roadmap, and deciding what to build, buy or integrate.
- People and partners. Hiring or coaching developers, briefing agencies and freelancers, and checking that what they deliver matches what was agreed.
- Risk. Security, hosting, data protection, dependency on a single vendor or a single developer.
- Translation. Explaining technical trade-offs to a CEO, a board or investors in business terms, and bringing business constraints back to the engineers.
The key word is ownership. An adviser writes a report and leaves. A fractional CTO sits in the decisions and answers for the outcome. That distinction matters when you compare offers, because many people use “part-time CTO,” “fractional CTO” and “consultant” for very different levels of responsibility. Ask which decisions the person will be accountable for, not just how many hours they will spend.
As a Raconteur feature on fractional CTOs puts it, the model suits startups and growth companies, and also firms that are digitally transforming legacy systems and need an outside voice.
Seven signs it is time
The search results for this question list many signals. The ones that matter for a founder or an owner in Switzerland come down to seven.
1. Your product build is stalling or the budget keeps growing
If the same feature has been “almost done” for two months, or each estimate from your developers is larger than the last, you have a leadership problem, not only a coding problem. Someone senior has to look at scope, architecture and team setup and decide what to cut, what to rebuild and what to leave alone.
2. You cannot judge your vendors
You pay an agency or freelancers, and you cannot tell whether the quotes are fair, the architecture is sound or the delivery is on track. That gap is expensive. A fractional CTO reviews proposals, challenges estimates and reads the work you receive, so you stop relying on the vendor’s own account of its progress.
3. You are about to make your first engineering hires
Hiring a developer without technical leadership usually ends in a mismatch: the wrong seniority, the wrong stack, or nobody able to review the code. A fractional CTO defines the role, interviews candidates alongside you and sets the standards the new person will work to. Many teams use the engagement for the first six to twelve months of hiring and then reduce it.
4. A legacy system is slowing the business
An old shop, a custom ERP or a patchwork of spreadsheets and plug-ins can quietly cap growth. Replatforming or migrating is a decision with real consequences for cost, downtime and data. This is where an outside senior voice is most useful, because the person deciding does not have to defend the old design.
5. You want to automate or add AI, and do not know where to start
Most companies have repetitive work: copying orders between systems, answering the same support questions, preparing the same reports. Deciding which workflows are worth automating, and how to connect them safely to your CRM, shop or ERP, is a leadership decision before it is a development task. Getting it wrong means automations nobody trusts.
6. Investors, partners or buyers ask technical questions
A funding round, an acquisition or a large customer will ask about security, scalability, ownership of code and key-person risk. If nobody at your company can answer with confidence, a technical review and a named senior owner for these questions makes the conversation shorter. Technical due diligence from the sell side, done before the buyer’s team does it, also removes surprises.
7. You are the technical bottleneck
If every technical question lands on a non-technical founder, or on one overworked developer, decisions wait and quality varies. A fractional CTO takes the decisions off that person’s desk and leaves them with a clear path.
Fractional, full-time, interim or adviser: which fits
The right model depends on how often technical decisions come up and how much accountability you need.
| Situation | Best fit |
|---|---|
| Decisions come up weekly, but the workload is under a full job | Fractional or part-time CTO |
| You need one answer: which platform, which vendor, is this quote fair | Audit or one-off consulting |
| The CTO has left and you need someone full-time for a few months | Interim CTO |
| Technology is the product, and a team of ten or more developers needs daily leadership | Full-time CTO |
| You have a working team and only need a sounding board once a month | Advisory or coaching |
The tipping point toward a full-time hire usually comes when the technology leader’s job fills the whole week: managing a sizeable engineering team, owning an extensive roadmap and being present for daily decisions. Before that, paying for five days when you need two means paying for idle capacity.
There is also a stage that comes earlier than all of this. If you have an idea and no product, you may need a build partner with senior oversight more than a CTO. That is a different engagement, and a good one blends both: someone who sets direction and also delivers.
Why the Swiss market makes the case stronger
A full-time CTO in Switzerland is among the most expensive technology hires in Europe, and the search for the right person can take months. Swiss startups and small and mid-size companies also tend to need leadership across several areas at once: product, data protection, integration with local systems and, often, multilingual and multi-market requirements. A senior person who works across these for a few days a week is a more proportionate answer than a full-time executive who has to be kept busy.
Time to start is the second factor. A fractional engagement can begin within weeks. A full-time search cannot, and a mis-hire at executive level costs far more than a mis-matched part-time engagement that you can end after a few months.
What to define before you hire
Most disappointing engagements fail on scope, not on talent. Settle these five points in writing before the first week.
- The decisions you want owned. For example: the platform choice, vendor selection, the hiring plan, security posture, the roadmap for the next two quarters. A list of five to eight is enough.
- The time commitment. Days per week, and which of them are fixed (a weekly leadership meeting, a standing review with developers). Unclear availability is the second most common complaint.
- The outcomes for the first 90 days. One technical review delivered, one vendor decision made, one hire made, one risk closed. Concrete and checkable.
- Access and ownership. Code repositories, hosting accounts, domains and documentation belong to your company and are accessible to you from day one. This protects you from dependency on any individual or vendor.
- The exit. How the engagement shrinks or ends: documentation, a handover to a hire or to your team, and a notice period.
The fifth point deserves emphasis. A good fractional CTO works toward making you less dependent on them, not more. Lock-in is a warning sign in any technology engagement.
Questions to ask a candidate
Beyond references and experience, the answers to these tell you how the person works:
- Who will actually do the work, and who will I speak to when something goes wrong?
- What happens if you are unavailable for a week?
- Which decisions will you make and which will you bring to me?
- How do you document decisions, so that someone else can pick up the thread?
- What do you do when you disagree with my plan?
People who answer with specifics, such as a named process, a typical week or an example of a decision they reversed, are usually the ones who deliver. People who answer in generalities rarely do.
How to tell whether the engagement is working
Hours worked are the wrong measure. Look at four things instead.
- Decisions made. Are the open technical questions from your list being closed, with a written reason for each?
- Risks removed. Single points of failure, unmanaged accounts and unreviewed code should be disappearing quarter by quarter.
- Delivery predictability. Estimates from your developers or agency should become more accurate, and surprises rarer.
- Your independence. Your team should be able to explain the architecture and the roadmap without the CTO in the room. If they cannot after six months, something is missing.
Review these every quarter with a short conversation: what was decided, what is still open, what changes for the next 90 days. If the answers are vague twice in a row, adjust the scope or end the engagement.
When a fractional CTO is not yet the next step
Sometimes the honest answer is that your next step is smaller. If you have a clear idea and need it built, a scoped project with senior oversight serves you better than an open-ended advisory. If you have an existing system and doubts about its quality, an audit gives you a fixed-price answer in a few weeks. If you are heading into a funding round, a technical due diligence review is a defined task with a defined result. Each can later grow into a continuing engagement if it proves useful.
How Ampersand works with founders and owners
Ampersand is a small studio in Zurich. We offer senior-led technical consulting, including part-time CTO roles, billed monthly, alongside audits, technical due diligence and product coaching. Because the same senior engineers lead the work from the first consultation to handover, the person who understands your problem is the person who solves it, with no mid-project staff changes or rewritten requirements. We also build: websites, web and mobile apps, platforms, integrations with shops, CRM and ERP systems, AI automation, and migrations of legacy systems. Our clients include UBS and the City of Lugano. We aim to leave you able to run things yourself rather than locked in.
If you are weighing up whether you need advice, a build or both, see the advisory, build and support options or start from Ampersand’s main page.
FAQ
How many hours a week does a fractional CTO work?
One to three days a week is common, often a fixed weekly leadership day plus time on call for urgent decisions. Early in an engagement, such as during a vendor selection or a hiring push, the load is usually higher and then settles. The right figure is the one that covers the decisions on your list, not a standard package.
Is a fractional CTO the same as a part-time CTO?
In everyday use the terms overlap, and both mean senior technology leadership for part of the week. The difference that matters is accountability: some people sell advice and reports, others take ownership of decisions and results. Agree which one you are buying before you sign.
What stage of company hires a fractional CTO?
Most often startups and small to mid-size companies that have a product or an operation running on software but no senior technical leader. Companies modernizing legacy systems also use the model, because it brings an outside, experienced view without a permanent hire.
Does a fractional CTO write code?
Their core value is decisions, direction and oversight, not daily programming. Some engagements combine leadership with hands-on delivery, which suits small teams that have no engineers yet. Decide at the start which you want, and write it into the scope.
When should I move to a full-time CTO?
When the role fills the whole week: a growing engineering team to lead, an extensive roadmap to own and daily decisions that cannot wait. A well-run fractional engagement should leave you with documentation and a hiring profile, so the move is straightforward when the time comes.
Sources
Talk to us
Have a project this touches on?
A free 10-minute call is the fastest way to find out whether we are the right studio for it.
Book a free 10-min callKeep reading
More articles.
Stripe vs Datatrans: Which Fits a Swiss Business?
Stripe vs Datatrans for Swiss businesses: fees in CHF and EUR, TWINT and PostFinance support, onboarding, data location and when each one makes sense.
Read articleHow to Test Business Integrations Before Go-Live
A practical guide to testing integrations between your shop, CRM, ERP and other business systems: what to check, in what order, and a checklist you can reuse.
Read articleSprint Planning for Startups: How to Plan Sprints That Hold
How a startup team can plan a sprint: prepare the backlog, set a goal, size the work to real capacity and avoid the mistakes that break the plan.
Read article