The Engagement Model
Mostly remote, with on-site time at the points where it is needed
on site
Hands-on training for your team
Two full days with your engineers, QA and tech lead, covering agentic ways of working and the tooling itself. Your team runs the tools on your own codebase with us present, so the practice starts inside the team rather than being handed over later.
visits
On site at the key points
Stage gates, the pilot kick-off and the rollout handover. These are the points where decisions are made and where being present in person is useful. Dates agreed jointly and in advance.
throughout
Everything else runs remote
Agent build, pipeline work, reviews and working sessions all run remotely.
How We Support Your Team
All of it aimed at the same thing: the programme runs without us afterwards
Working sessions, not slides
- Every engineer runs a real change through the fleet with one of us alongside
- Sessions are recorded and become onboarding material for future hires
- All of it on your own codebase, never an example project
- These run remotely through the rollout, on top of the two on-site days
Internal agent maintainers
- Two or three of your engineers learn to write and change agent definitions
- Agents are software and need maintainers, and those maintainers should work for you
- Trained during the programme, not briefed at the end of it
Runbooks you keep
- Onboarding a new module
- Adding a reference dataset
- Diagnosing an agent that starts producing poor output
- Disabling an agent quickly
- Updating the written conventions when one changes
A steward for every module
- Each module gets a named steward with a written remit
- Keep the written context current, review changes, and never be the sole author
- Stewards meet monthly to share what the agents keep getting wrong
The engagement ends at week 14
By then the duties, the runbooks and the named owners all sit inside Nerve Solutions, and there is no ongoing dependency on us. That is the design, not a limitation: a programme that still needs the consultants in month six has not been handed over. The full plan sets out the operating cadence your team runs from week 13 onward, including what to watch for and how to respond to each signal.
Contents of the Full Plan
Eighteen sections, seven of them stage playbooks. Released once the agreement is signed
Each of those is a full section rather than a heading: the agent specifications, the gate criteria, the measurement set, the stage-by-stage deliverables, the risk register with its stop conditions, and the staffing the schedule assumes. These are released once the agreement is signed.
Next step
If this approach works for you, the next step is the engagement agreement. On signature the full plan is released in the same format as this preview, and week one starts with the baseline measurement.
⚠ PLACEHOLDER — REPLACE WITH CONTACT DETAILS BEFORE SENDING ⚠