How we work
A delivery motion built for the channel, not borrowed from consultancy.
Predictable onboarding, written scopes, partner-safe communication, and an operating rhythm after go-live.
Engagement path
From first conversation to steady state
| Stage | What you send us | What happens | Partner action |
|---|---|---|---|
| 1. Opportunity brief | Platform, estate scale, desired date, constraints | We acknowledge, confirm capacity and flag missing detail | One form or call — no multi-week RFP theatre |
| 2. Scope and commercial | Access route, customer change process | We return effort, assumptions, delivery window and white-label rules | You wrap it in your paper to the customer |
| 3. Kick-off | Named contacts and the agreed brand model | Named contacts, access path, communication rules, success criteria | You introduce us under the agreed brand model |
| 4. Build | Time-bound least-privilege access, change windows | Design, deploy, integrate, validate | You stay the commercial owner; we execute |
| 5. Hypercare | Customer feedback and open issues | Stabilise, tune, document, hand into operations | You receive the pack you will use at QBR |
| 6. Lifecycle | Retainer commitment and escalation owner | Reviews, tuning, reporting, optional retainer | You own renewal; we keep the platform earning it |
After you submit
What happens after you submit a brief
No black box. This is the sequence from the moment the form lands.
| When | Step | What happens |
|---|---|---|
| Day 0 | Brief received | Acknowledgement, capacity position, clarifying questions |
| Day 1 | Scoping call | Estate, constraints, access route, desired date confirmed |
| Day 2-3 | Scope returned | Partner-safe scope, effort against SKUs, delivery window |
| Then | You quote | Licence + services line item on your paper, your margin |
| Then | Mobilisation | Access granted, kick-off booked, delivery starts |
| After | Handover | As-built pack, validation evidence, optional retainer |
Timings assume we have the estate detail and an access route. If either is missing, we say so at acknowledgement rather than letting the date slip quietly.
Example output
What a returned scope looks like
Every scope we return follows the same format, so it is easy to price and easy to wrap into your own paperwork.
| # | Section | What it contains |
|---|---|---|
| 1 | Opportunity summary | Partner, platform, customer scale, desired date |
| 2 | Outcome definition | What “done” means, in the customer's language |
| 3 | Scope of work | Workstreams, phases, environments in scope |
| 4 | Out of scope | Explicit exclusions, so nothing is assumed |
| 5 | Effort and SKU mapping | Packaged SKU(s) plus any overflow block required |
| 6 | Delivery window | Start, key milestones, hypercare period |
| 7 | Dependencies | Access, change windows, customer resources |
| 8 | Assumptions and risks | Written down, not verbal |
| 9 | Brand model | White-label / co-delivery / named partner |
| 10 | Deliverables | As-built pack, validation evidence, handover pack |
Operating principles
Operating principles
- Single throat to choke on delivery — a named Avertory lead per engagement.
- Written assumptions. Scope change is explicit, not absorbed in silence.
- Access is least-privilege and time-bound. We work to UK data protection expectations.
- End-user contact is authorised by the partner, logged, and summarised back to the partner.
- We measure success as time-to-value, stability after go-live, and partner CSAT — not hours billed in isolation.
Handover
What partners typically receive at handover
- As-built summary and policy / configuration baseline.
- Open risks and agreed exceptions.
- Operating cadence and escalation path.
- A customer-facing pack the partner can put their name on.
Send the platform, customer scale and desired date. We return assumptions and a delivery window.
Brief a live opportunity