CTO on Demand
Senior technology leadership, with accountability attached
For companies that have a product in the market, a development team, and technical decisions nobody is currently owning.
Triggers
The situations that lead here
Executives rarely start by searching for a fractional CTO. They start with one of these.
- A technical decision has been open for months and keeps being deferred
- Delivery has slowed and the explanations no longer convince anyone
- A senior engineer left and took the system knowledge with them
- The team wants a rewrite and management cannot judge the proposal
- Reliability problems are reaching customers
- You are about to raise, and technical diligence is coming
- Two credible engineers disagree and there is no one to settle it
- You suspect the plan is wrong but cannot prove it
Scope
What Kendoo is accountable for
Accountability, not attendance. Each of these is owned, with the decision rights agreed in writing at the start.
-
Technical direction
Where the architecture is going, which constraints are real, and which options are actually available given the business position.
-
Architecture decisions
The expensive, hard-to-reverse choices, made explicitly and recorded with the reasoning, so they can be revisited when the facts change.
-
The delivery system
How work is planned, reviewed, tested and released. Most delivery problems are system problems, not effort problems.
-
Team leadership
Working with your leads and managers directly: design review, coaching, unblocking, and escalation when something needs it.
-
Risk and modernization
What is fragile, what it would cost if it failed, and the order in which to address it without stopping delivery.
-
Visible progress
A monthly written report to management covering what moved, what did not, which risks changed and what needs a decision.
Working relationship
How Amir works with your organisation
With founders and executives, the work is about trade-offs and sequencing: what the technical position makes possible, what it rules out, and what each option costs. The aim is that you can make the call with the real constraints in front of you.
With product, the work is about feasibility and order, so the roadmap reflects what can actually be built in the state the system is in.
With engineering, the work is hands-on. Design reviews, architecture decisions, coaching leads, and being available when something needs deciding rather than escalating for a week.
Kendoo does not take over your team's reporting lines. Your managers keep managing; what changes is the quality of the technical decisions and the clarity of the priorities they are working to.
Outcomes
What changes, and how you will know
Measured against the baseline written in the first month, not against impressions.
Decisions get made and recorded
The open architectural questions close, with the reasoning captured so they can be revisited on evidence rather than reopened on opinion.
Delivery becomes predictable before it becomes fast
Predictability first: commitments that hold. Speed follows once the system stops producing surprises.
Risk becomes visible earlier
Problems surface in the monthly report while they are still cheap, rather than as incidents.
Your leads grow
Coaching is part of the engagement, so capability stays in the organisation after it ends.
Why the engagement is six to twelve months
The first month is diagnosis. Changing how technical decisions are made, how work reaches production and how risk is surfaced takes longer than that to hold, and an engagement that ends before the change is embedded leaves the organisation where it started.
It also protects you. A short engagement creates pressure to produce visible activity quickly, which is exactly how the wrong expensive decision gets made.
What this is, and what it is not
What it is
- Ongoing senior leadership with agreed decision rights
- A fixed cadence: weekly leadership, monthly reporting
- Accountability for technical direction and delivery
- Coaching that leaves capability behind
- One named person, Amir, throughout
What it is not
- Full-time employment or an equity role
- Engineers to build, which is Software R&D Services instead
- An hours bank you draw down against
- A one-off code fix or a single audit document
- An agency assigning whoever is available
If what you need is engineers to build rather than someone to own the technical direction, that is a different line of work: Software R&D Services. The call will tell you which one you actually need.
Questions executives ask
How is this different from hiring a full-time CTO?
A full-time CTO is a permanent executive with a salary, equity and a long recruitment cycle. Kendoo is an ongoing retainer with defined decision rights and a fixed cadence, aimed at organisations that need senior judgement now and may not need it permanently.
Will Amir write code?
Occasionally, where a decision needs proving. But implementation capacity is not what is being bought. Kendoo leads the technical direction and the delivery system; your team builds.
Why not just buy a few hours of advice?
Advice without accountability does not change an organisation. The engagement includes decision rights, a cadence and reporting precisely because occasional opinions rarely survive contact with delivery pressure.
What if we already have engineering managers?
Good. The work then focuses on technical direction, architecture and decision quality, and on coaching those managers rather than replacing them.
Can you start next week?
Usually not. Kendoo takes on a limited number of engagements at a time so each one gets the attention it was scoped for.
Results
See how this looks in practice
Real engagements, shared anonymously. The situation, the decisions, and what changed.
Explore the resultsPut the decision in front of someone accountable
Thirty minutes on your situation, and a straight answer about whether this is the right engagement.