Preparing for expansion
New customers, sites or markets on the way. Architecture, integration interfaces and delivery made ready before the load arrives, not after.
Qualification
Worth checking before we speak
This engagement suits a particular situation. Being direct about it saves you a call and protects the results for the companies it does suit.
Fit and not fit
Neither list is a judgement. They describe what these engagements can and cannot do, across every service line.
A good fit
- A technology company, or an established business whose products or operations depend on software
- An executive sponsor willing to participate personally
- Problems in technology, delivery, team performance, brand or product experience
- An internal or partner team able to carry the work forward: engineering, product, design or leadership
- A willingness to act on what the work finds
- A planned change you want to get right, not only a problem to fix
- For retained work, the ability to engage for six to twelve months
- For workshops, a team that can attend together
Not a fit
- An idea-stage project with no product, team or funding
- A fixed-price quote for a specification handed over without discussion
- One isolated bug, a few development hours, or a single workshop slot filled by whoever is free
- An hours bank or staff augmentation requirement
- No executive sponsor, or no willingness to change priorities
- A search for a full-time employee
Already have a CTO or VP R&D?
Good. We work alongside them on architecture, modernization, delivery improvement, and changes that need additional senior experience. The decisions stay with your leadership; the engagement adds a second experienced view and hands-on help carrying the change through.
Planned change
You do not need to be in trouble
Experienced technology leaders often call before a change rather than after a failure, when a second senior view is cheapest.
Integrating an acquisition
Two products and two teams that need one technical roadmap, a migration sequence and clear ownership while both keep serving customers.
Introducing AI-assisted development
Review, testing and guardrails rebuilt for a higher rate of change, measured against a baseline so the gain is real.
Modernizing before it hurts
A system that still works but is getting harder to change. A risk map and a staged plan while there is still time to choose the order.
Why the boundaries
What each one is protecting
These apply to retained leadership work. Workshops are booked on their own and need a team that can attend together, not a six-month commitment; software R&D is scoped to the piece of work. Every boundary exists because ignoring it produces a bad engagement for both sides.
An existing product
The work is diagnosis and leadership of a system that already exists and already has users. With no product there is nothing to diagnose, and what you actually need is a build team.
An existing team
Kendoo leads; your team builds. Without a team there is no delivery capacity for any decision to act on, and leadership alone changes nothing.
An executive sponsor
Diagnosis usually shows that some current commitments were never achievable. Only an executive can change that, so an engagement without one stalls at the first real finding.
Six to twelve months
Changing how technical decisions get made takes longer than a quarter to hold. A shorter engagement creates pressure to show visible activity fast, which is how expensive mistakes get made.
Leadership, not capacity
If the plan is sound and you simply need more hands, this is an expensive way to buy them. Contract development is the right purchase, and a cheaper one.
Not a full-time hire
If you need a permanent executive with equity and a long horizon, hire one. Kendoo can help you define the role and assess candidates, but it is not a substitute for it.
Self-check
Six questions before you book
If you can answer yes to most of these, the call will be useful. These are the same questions the booking form asks.
- Do you have something already live: a product, a service, or a team doing the work?
- Can you name the problem, even roughly, whether it sits in technology, delivery, the team, the brand or the experience?
- Is there an executive who will take part personally rather than delegate it?
- Are the people it concerns available: engineering, product, design, or whoever actually holds it?
- Do you need senior judgement rather than more hands?
- Could you commit to the shape the work needs, whether that is six months, a scoped build, or a team in a room for a day?
If it is not a fit
You will be told on the call, with the reason. Where possible you will also get a view on what would help instead, whether that is a build partner, a permanent hire, or simply a different order of work.
That costs thirty minutes and is more useful than a proposal for an engagement that was never going to work.
Find out on the call, not in month three
If the criteria above describe your situation, this is the next step.