- Executive summary The essentials on one page, with no jargon.
- System map What parts there are, how they connect and who each one depends on.
- Risks, by priority What can fail, how much it would hurt and what to fix first.
- Costs What you pay today for servers and licences, and what is surplus.
- Team and ways of working How things get delivered today and where time is lost.
- What not to build What we recommend not doing, and why.
- 90-day plan The next steps, in order, and who should take them.
Technology consulting
Technology consulting to decide well before you build.
For those who have to make a technical decision without being technical.
- Software audit
- Architecture
- Technical hiring
- Fractional CTO
If you're reading this, you probably have to decide something technical without technology being your trade. Rebuild a system or fix it. Hire someone or outsource. Accept the quote in front of you or ask for another.
Whoever sells you the solution is rarely the best person to tell you whether you need it. We build software too, which is why we know what it costs to build something that wasn't needed.
Our job here is to look at what you have, understand what you want to achieve and tell you, in writing and in language you can take to your partner or your board, what we would do in your place. Sometimes the answer is a project. Sometimes it's to leave things alone for now.
There are two ways to work with us. A software audit, which is a review of your technology (the code, the servers and how the team works) and ends in a report. And a fractional CTO: someone who leads your technology a few hours a month, without being on the payroll.
TechTraveller Studio
Four questions, four short answers.
-
“Do we rebuild or fix?”
Almost always, fix it in parts. A rewrite from scratch only pays off when what you have stops you changing anything, and even then it's done piece by piece, with the old system still running. That is what legacy system modernization looks like when it works.
-
“Who do I hire first?”
Someone who builds and can explain what they're doing. A large team before you know what to build only takes you faster in the wrong direction.
-
“Should we move to the cloud?”
If you're paying for servers nobody maintains, or you can't grow, yes. If what you have works and nobody complains, it can wait. Migrating because it's fashionable is expensive.
-
“Can AI do this?”
Part of it, sometimes. It depends on whether the task repeats and whether the data lives somewhere it can be read.
Find out in three questions
Every feature you don't build is a feature you don't have to maintain, explain or fix. Before recommending a project we ask three questions, in this order.
A CTO is the person who leads a company's technology. You can hire one in-house or have one for a few hours a month: that is a fractional CTO.
| Aspect | In-house CTO | Fractional CTO |
|---|---|---|
| Cost | An executive salary, all year round. | A monthly fee for the hours you need. |
| Commitment | An employment contract. | A service agreement, with no added headcount. |
| When they start contributing | After recruitment and onboarding. | No recruitment process: they start on signing. |
| What they decide | Everything technical, full time. | What sets the direction: architecture, priorities and who to hire. |
| When it fits | When you already have a large technical team to lead every day. | When the team is small or doesn't exist yet. |
If your company grows to need an in-house one, we help you choose them and hand over.
It isn't a slide deck or a list of jargon. It's a document written for whoever decides, with the conclusions up front and the detail behind.
A software audit usually takes about a week from the day you give us access. The firm timeline goes in the proposal.
How long does a software audit take?
About a week from the day you give us access to the code and the systems. It depends on how much there is to review; the firm timeline goes in the proposal.
What happens after the report?
The report is yours. You can apply it with your team, with your supplier or with us. If you like, we go through it with you and with whoever has to carry it out.
How many hours a month is a fractional CTO?
As many as your company needs. They are agreed in writing before we start and reviewed if the situation changes.
Do you work with our current team or supplier?
Yes. We're not here to replace anyone: we review, propose and, where needed, support whoever is already doing the work.
What if the conclusion is that nothing needs building?
We tell you. It's one of the most common answers, and usually the one that saves the most money.
Five questions, two minutes. We reply within 24 hours.