Senior builders, working with your people.

No. Engagements are staffed by senior practitioners selected for the work you need to do. A design pair has two practitioners and a build team has three, with partner oversight. Associates come through work James Rooney knows at first hand or referrals from people he has delivered with. Everyone is screened and contracted to written confidentiality and data-handling terms before client access.

On a build, we pair with your engineers throughout. They bring the knowledge of your systems and the awkward cases worth testing; working through those together helps your team learn to run and improve what we build. Associates are engaged for your work, with no bench cost added to the rate.

James Rooney runs the first 30-minute call and remains the accountable partner for your engagement. He leads every audit personally and provides oversight on the other services, including programmes delivered by other suppliers. Your proposal makes his role clear, and he is named from the first email as your escalation route. The first conversation gives you a chance to explore the problem with the person who will take responsibility for the work.

We review the effect on delivery with you and arrange how the work will continue. On team engagements, the other senior practitioners carry the work; if James Rooney is unavailable, oversight transfers to a senior practitioner on the engagement. Code, documentation and credentials are kept in your repositories and accounts from day one, so the team can access what it needs.

Where a replacement is needed, we may substitute someone of equivalent skill and seniority. We tell you before the change, pay for the handover and remain responsible for the work and its quality. The continuity arrangements and any specific requirements belong in the Statement of Work.

Operating-model leads, agentic architects, agentic leads and forward-deployed engineers bill at £1,250 a day, the senior practitioner rate. Adoption leads bill at the associate rate of £950 a day. James Rooney bills at the partner rate of £1,560 a day. All rates exclude VAT.

Monthly service prices use these rates at 20 billable days a month. A design pair has two practitioners and a build team has three, with partner oversight. Your proposal sets out the roles and allocation so you can see how the price is calculated.

£950 a day is our published rate for the adoption role. It is a different specialism within a senior team, and the lower rate does not make its contribution less important. The adoption lead works with the people whose tasks are changing: observing the work, helping them try the new approach and using their feedback to improve it. They report what people are using and what has changed in practice alongside the software delivered that month. That gives you a view of whether the system is becoming useful in everyday work.

Your proposal sets out the team shape and price: how many people, which roles and how their rates contribute to the fee. It names James Rooney as the accountable partner and your escalation route.

Before signature, you can review the Statement of Work, confirmation of BS7858-standard screening, insurance certificates showing the cover levels, and the Data Processing Agreement with its sub-processor annex. The Statement of Work defines the scope, deliverables, timeline, personnel and fees. Bring your procurement requirements into the conversation so we can work through them with you.

During supplier onboarding, alongside the Statement of Work. You receive confirmation of BS7858-standard screening covering identity, right to work, employment history and criminal record checks. Screening is completed before anyone gets access to your systems or data.

Each practitioner has written confidentiality obligations that continue indefinitely after the engagement and works to your data-handling requirements. Access is limited to what the work requires, time-boxed to the engagement and closed through documented offboarding.

Yes, we accept named-competitor restrictions in the Statement of Work. Raise the firm on the first call so we can check existing commitments and confirm the restriction before signature. We do not offer blanket sector exclusivity: our work spans financial services, retail and consumer, industrial and energy, and the public sector.

Your confidential code, prompts, requirements, data and roadmaps are protected and are not transferred between engagements. Your team works inside your systems under your access controls. Confidentiality applies whether or not you request a competitor restriction.

We discuss current availability on the first call. If we are fully committed, we will say so; possible start dates depend on the roles, scope and existing commitments. We confirm the proposed team shape and timing in writing before work begins.

Capacity varies with the work, so we do not publish a maximum number of concurrent engagements. Design pairs have two senior practitioners and build teams have three. James Rooney leads every audit personally and provides oversight on the other services. Availability has to support the agreed team and his involvement.

We can consider it as a Statement of Work term. Bring the required limit and the service it applies to, so we can assess the dependencies and support arrangements before confirming what we can commit to in writing. Other operational resilience requirements can be reviewed in the same conversation.

The Statement of Work records the agreed scope, timing and responsibilities. You own the deliverables, documentation and code created for you on payment of the applicable fees. Retainers can end on 30 days' written notice either way; fixed-price engagements can end on written notice, with fees due for work performed and committed costs incurred up to termination.

We start with the systems you need to build and the constraints your engineer will work within. Associates come through delivery James Rooney knows directly or referrals from people he has delivered with. We look at their work, their judgement about production readiness and how they build with a client's engineers. Being able to explain a decision and learn from your team's feedback matters alongside technical ability. The role bills at £1,250 a day excluding VAT, and BS7858-standard screening is completed before client access.

Our build team works inside your management structure, with reporting lines and decision rights agreed for the engagement. The agentic lead takes responsibility for delivery, the engineer builds in your repositories under your access controls, and the adoption lead works with the people whose tasks are changing. Your team's knowledge and feedback shape the work throughout. James Rooney provides partner oversight and is your escalation route. If you need a different arrangement, we can explore the fit on the first call.

The published examples are a Tenhaw engagement in specialty insurance and his earlier AI Voice Insights work inside HSBC.

On the insurance engagement, James is the embedded agentic lead. Month one was an audit that helped unblock data issues affecting development and testing. In month two, he pair-programmed with the client's engineer to build a working proof of concept on Azure: extracting information from PDFs and turning it into business intelligence. The two-week build covered ground the business had previously spent roughly twelve months on. The published month-three work is productionisation against the client's security standards; the two-week result remains a proof of concept.

At HSBC, James led the Voice Insights proof of concept while working inside the bank. Its projected reduction of 1.5 million administrative hours a year was potential identified by the prototype, not a realised saving. It did not reach production. That is founder experience, separate from work delivered under Tenhaw.

The team combines three responsibilities: leading delivery, building the system and helping people use it. The agentic lead owns delivery and agreed decision rights, the engineer builds and tests, and the adoption lead works with your people to improve the workflow and measure its use. Our engineer pairs with yours throughout the build, so your permanent team contributes and learns as the system takes shape.

If your main need is more engineering capacity, a larger supplier team may fit better. Tenhaw can provide programme management or oversight while another supplier provides that capacity.

By making workload and team feedback part of how we plan and review the change. People need time to learn, room to raise concerns and a say in how their work changes. The adoption lead works alongside the team, observes the tasks they actually handle and uses that knowledge to shape the rollout.

We look at what has become easier, what still needs support and where the change is adding effort. That gives your team and its leaders something concrete to adjust. Adoption reporting sits alongside delivery reporting, so a working system and the experience of using it are both visible.

Yes. Delivery teams are made up of senior practitioners, with James Rooney as the accountable partner. His experience includes advising HSBC's CIO's office on target operating models with 150+ teams and a $102M budget in scope, and running priority programmes for Microsoft's EMEA senior leadership team. Both were roles inside those organisations, separate from Tenhaw contracts.

The relevant questions are what decisions your board needs to make and what experience the engagement requires. We can discuss how the proposed roles support that work and how findings, costs and delivery risks would be presented.