01 · Strategy
The expensive decisions get made before anyone writes code.
Build or buy. Rewrite or refactor. Keep the vendor or replace them. Technical consulting is the work of getting those calls right when the cost of a wrong one is measured in quarters. We sit on your side of the table as senior engineers who have built and operated the kind of systems we advise on. We have no stack to sell and take no referral fees, so the recommendation can be the cheaper option, or doing nothing at all. The output is a decision and the reasoning behind it. If you already know what to build and need the system itself designed, that is platform architecture.
What you walk away with
- A clear recommendation you can act on next Monday, with the reasoning written down.
- The trade-offs we weighed, so the decision is yours to own with full information.
- An independent read on your architecture, codebase or vendor from someone with no stake in the answer.
- A prioritized path through the decisions that are capping your speed or scale.
- For investors and acquirers, a plain-language account of where the risk lives and what the next two years of engineering will cost.
What it covers
- Fractional CTO
- Senior technical leadership without a full-time hire. We set technical direction, make the architecture calls, sit in on hiring and translate between the business and the engineering reality.
- Architecture review
- An independent opinion on whether the system you have is sound for the company you are becoming. We name the decisions quietly capping your speed or scale and give you a prioritized path. Designing the replacement is platform architecture work.
- Build-versus-buy decisions
- The analysis behind an expensive fork in the road: what building costs over three years, what buying constrains, and which one fits the company you intend to be.
- Vendor and agency audits
- A second opinion on the firm building your software: whether the work is sound, the architecture defensible, the pace reasonable and the price fair. We report what we find without trying to win the project by trashing the incumbent.
- Codebase audits
- A structured assessment of code quality, architecture, test coverage and operational risk, written so a founder can act on it. The fixed-scope entry point is our Performance & Architecture Audit.
- Technical due diligence
- For investors and acquirers: what you are actually buying, where the risk lives and what the next two years of engineering will cost. We work for your clarity, not the deal's momentum.
Why we will tell you not to build it
A consultancy paid by the hour has a quiet incentive to find more hours. We work the other way. Some of the most useful recommendations we can make are to buy off the shelf, to keep the system you already have, or to do nothing for now. We would rather be the firm that told you the truth than the one that took the project.
Most technical advice comes from someone with a stake in the answer. The vendor wants you to buy. The framework evangelist wants you on their framework. The contractor wants the bigger build. Even well-meaning advice often comes from someone who has never had to live with being wrong.
One studio means you get a principal, not a pyramid. The person assessing your codebase is a senior engineer who has shipped and operated real systems, not an analyst translating a methodology. The same judgment runs through our platform architecture and performance engineering work: the advice is independent, and the engineering behind it is real.
A good test for whether you need this: if the next technical decision will commit more money or more months than you would comfortably lose, get an independent opinion before you make it.
How the work runs
Every engagement moves through the same five stages, with one team throughout.
Understand
A first conversation and a look at what already exists: your position, your customers’ path, your traffic and your technology.
Define
Positioning, scope and architecture decided deliberately and written down, so everyone knows what is being built and why.
Design
Brand, content and interface designed together, against those decisions rather than the fashion of the month.
Build
Built with speed, accessibility and security as requirements, and reviewed on a staging site before anything goes live.
Improve
Launch is the start. We measure what matters, fix what drifts and report in plain language.
Further reading
- Marketing Systems Architecture: A Five-Year BlueprintThe five layers of a marketing system that compounds over years instead of resetting with every campaign, and what each year of the build looks like.
- How to Measure Marketing ROI Without Lying to YourselfEvery attribution model has blind spots. A three-level framework, plus incrementality tests, for measuring what marketing produces and admitting what it can't.
- Website Redesign vs Rebuild: A Decision FrameworkShould you redesign the site you have or rebuild it from the foundation? Six factors, the running costs people forget, and a five-question check.
- How to Vet a Web AgencyHow to check an agency's claims before you sign: archived history, live portfolio sites, code, contracts, references and the people who will do the work.
Technical consulting: common questions
How is a fractional CTO engagement structured?
Around what you actually need. Some clients want a few days a month of senior direction and architecture oversight; others want hands-on involvement through a critical decision or build. We scope to the problem, not to a fixed retainer template, and we say so when you have outgrown the need for us.
Can you review work another agency is doing?
Yes, and we do it without theatrics. We assess the architecture, code and pace objectively and tell you what we find, good or bad. The goal is an informed read on whether the relationship is serving you, not to win the project by trashing the incumbent.
How is this different from platform architecture?
Consulting answers a question: should we build this, buy it, keep it or replace it, and is the current system sound? Platform architecture is design work: the data model, API contracts and system boundaries your team then builds from. A consulting engagement can end with a decision that leads into architecture work, or you can stop at the decision.
Is this just for startups?
No. We advise funded startups choosing their first real architecture, established companies whose platform has stopped keeping up, and investors doing diligence on a target. The common thread is a high-stakes technical decision and the desire to get it right with someone whose only agenda is accuracy.