Part-time technical leadership. 16 hours a month of ongoing judgement: architecture decisions, vendor and quote evaluation, hiring and priorities. For companies that need technical leadership and are not big enough for a CTO on payroll.
Companies of 10 to 60 people with a small technical team or an outside vendor, and nobody above them deciding with judgement: what gets built, what gets bought, who gets hired and how much it should cost.
It does not replace a development team: it leads one. If something also needs building, that is contracted as a separate project with its own scope and price.
Spread as each month needs. Sessions with the team or the vendor: priorities, pending decisions, review of what was delivered. And work of our own: architecture, proposal reviews, interviews.
Direct access for what cannot wait. An architecture decision or a vendor quote does not get put off for a month.
A written review of infrastructure and vendor costs for whoever runs the company.
Sprints, metrics, observability and controlled deployments that the team keeps even after the engagement ends.
What it does not include is here, not in the small print.
Anonymised, with the role we played in it.
Sprints and metrics, observability, CI/CD and controlled deployments; tens of thousands of lines refactored and over 3,000 tests; a vendor moved to pay-as-you-go and the cloud right-sized; mobile apps from scratch, the first hire and AI-assisted processes.
Technical leadership without a CTO on payroll: 16 hours a month of judgement on architecture, vendors, hiring and priorities, with direct access for anything that cannot wait.
They are agreed in advance. Hours are never invoiced by surprise.
No. It is monthly, and ending it takes one month's notice from either side.
Five or six questions, under a minute. We send you the tentative budget, the estimated time and how many phases it comes in, and you see it right here.