Staffing, cadence and exit, answered in full.

In forward-deployed squads of three: an Agentic Lead who owns the operating model and decision rights, a Forward-Deployed Engineer who builds and ships inside your estate, and an Adoption Lead who owns the part that usually fails, getting people to actually work the new way. Squads are founder-led, with James Rooney personally accountable for every engagement; every associate is someone he has already delivered alongside, and the people on your engagement are not substituted without your written agreement. Tenhaw does not sell work that someone else then delivers, and there is no pyramid of junior consultants.

Engagements are structured around a monthly production increment rather than a distant go-live, so you can judge the work on evidence within the first thirty days, not at a milestone months away. Each month the squad commits to something measurable reaching production and reports against it; a month with nothing in production is reported as a failed month. This is the commitment we ask to be held to from month one, and it is why engagements are retainer-shaped, not milestone-shaped.

Three things: the number of business units in scope, whether prototyping is included, and how many sites or regions require on-the-ground time. A single business unit with one location and no prototyping sits at the bottom of the range. A group-level audit spanning four business units across three countries with live prototyping sits at the top. The exact figure is fixed in writing before the engagement starts and does not move.

Retainer engagements run on 30 days' notice from either side, and the fixed-price audit is a defined deliverable rather than a subscription. You own all work product and documentation produced up to the point of exit, including any code written inside your estate. Tenhaw would rather stop a bad engagement at month two than defend it to month nine.

You own the capability. Recruiting your permanent team is a stated deliverable of the retainer and programme engagements, the exit date is agreed at kickoff rather than negotiated at the end, and the final sixty days are a documented handover with a decreasing-involvement taper. The commercial model is designed so that the engagement ends.

Structurally, in four ways. First, working software is deployed on your infrastructure, in your repositories, under your controls and your organisation's policies, so nothing needs migrating off Tenhaw's estate when the engagement ends. Second, your own permanent people are upskilled by pair-programming with ours for the whole build, and that transfer is measured rather than assumed. Third, the method is published in full and free to adopt without hiring us. Fourth, the exit is contractual: thirty days' notice either way, the exit date and taper agreed at kickoff, and you own all deliverables, documentation and code on payment.