Technical strategy
- The roadmap, in the order the business can fund it
- Stack decisions written down, with the alternative rejected
- Build versus buy, before a vendor presentation decides it
01Weekly decision meeting02Async review between sessions03Principal on the engagement
Retainer
What the month covers.
Architecture
- Design review on the systems that will hurt later
- Standards the current team can keep
- Scale discussed against real traffic, not a diagram
Hiring
- The role written so the right engineer recognises it
- Technical interviews run by someone who still writes code
- The first weeks of onboarding, not a welcome doc
Hands-on
- The feature that is blocking the company
- The bug the team has been circling
- Code review that teaches, not just approves
Tooling
- Infrastructure, data and deployment chosen for this stage
- Monitoring you will actually look at
- What not to buy yet
Investors
- A technical narrative that matches the product
- Due-diligence answers prepared before they are asked
- Architecture explained without a performance
Fit
Who this is for.
A good fit
- A founder who can sell the company and needs someone to own the technology
- One to three engineers who need a senior in the room
- A product past the demo, not yet ready for a full-time CTO
- A raise coming, and a technical story that has to hold up
Not this
- A team that needs ten engineers hired this quarter
- A body-shop brief with a fixed feature list and no decisions
- A company looking for a name on the deck and nothing else
Need it built as well? App development · technology consulting · consultancy