How It Works
A predictable route from problem to production
Every engagement runs through the same five steps, whether it is one specialist or a managed delivery workstream. Each step has a primary activity, a defined output and a decision or acceptance gate before the next begins. The commercial model changes with the nature of the work; the governance does not. Our intent is that you always know what is being delivered, who owns it, what evidence supports progress and what would have to change for the plan to be revised.
Process
Five steps, five decision points
The gates matter more than the stages. Each one is an opportunity to confirm, adjust or stop before further commitment.
- 01
Discovery
A focused working session on the estate, the constraint and the date that matters. Primary activity is establishing facts rather than presenting credentials. Output is a written understanding of scope, dependencies, data and compliance boundaries and known unknowns. Decision point: whether the problem is understood well enough to shape, or whether a short assessment is needed first.
- 02
Shaping
We propose the engagement construct — specialist capability, managed workstream or Build-Operate-Transfer pod — with named roles, assumptions, exclusions, governance cadence and the acceptance criteria that define done. Output is a proposal you can challenge line by line. Decision point: agreement on scope, model and acceptance before mobilisation.
- 03
Mobilisation
Access, environments, tooling, screening and onboarding dependencies are tracked to a plan with named owners on both sides. Right-to-work and any client security requirements are cleared before start dates are confirmed. Output is a documented readiness position. Decision point: day-one readiness confirmed rather than assumed.
- 04
Delivery and governance
One accountable delivery lead, an agreed reporting cadence, and progress evidenced through reconciliations, test results and decision logs. Risks are raised with options and an owner, including when the news is unwelcome. Decision point: milestone acceptance against the criteria agreed at shaping.
- 05
Transfer
Documentation, runbooks, structured knowledge sessions and handover of configuration and control records. Where a Build-Operate-Transfer model applies, the team and process move into your organisation on agreed terms. Decision point: your team confirms it can operate the outcome without continued dependency.
Commercials
Four ways to contract
We recommend the model that matches how well the scope and dependencies are understood, and we say plainly when a requirement is not yet defined enough to price on a fixed basis.
Time and materials
Suited to work where scope legitimately evolves week to week and you want direct control over priorities. Effort, roles and rates are transparent; we report consumption against plan.
Fixed price
Suited to well-understood scope with stable requirements. Deliverables, exclusions, assumptions and acceptance criteria are defined before commitment, and change is handled through a documented route.
Outcome aligned
Suited to engagements where the result can be defined and measured objectively. We agree the measure, the evidence and the review points with you during shaping rather than after signature.
Build-Operate-Transfer
Suited to capability you intend to own. We establish the function, run it under governance while it stabilises, then transfer people, process and documentation on agreed terms.
Get in touch
Start with a discovery conversation
Bring the constraint, the estate and the deadline. The first session is about establishing facts and giving you a direct view of what is realistic — not a sales presentation.
Prefer email? info@techtranspiresol.co.uk