We look before we build, and measure every week.

An engagement runs in five steps. Each one ends with something you keep, whether or not you go on to the next.

  1. 01Look
  2. 02Connect
  3. 03Teach
  4. 04Measure
  5. 05Decide
Each step ends with something you keep.

The five steps

  1. Look

    We sit with the people who do the work: a consultant's day, the operations view, the owners' priorities. Then we sample your database through the connector and put real numbers on what we find.

    You keepA written analysis of your data with live figures, and session records of how your desk actually runs.

  2. Connect

    Claude goes into your JobAdder through NativeMCP. Everyone signs in as themselves. In the first fortnight we fix whatever your team runs into.

    You keepA connector pinned to your account, and a list of every fix made from your team's feedback.

  3. Teach

    A handbook in your words, a training session on your real work, and saved skills for the jobs your team repeats. We teach on your database, not a demo one.

    You keepThe handbook, the deck and the skills. They're yours.

  4. Measure

    Every week, a written report on who used it, for what, and what got in the way. A team version too, with nobody ranked. When something narrows or breaks, the report says so first.

    You keepA week-by-week record of who's using it, to show your fellow owners.

  5. Decide what's next

    A short list of what to do next, ranked by effort and impact, built from what the sessions and the weekly numbers showed rather than from a menu.

    You keepItemised scopes and costings, so you can say yes to one piece at a time.

What ‘next’ looked like at one agency.

The top six items on the roadmap we wrote for the agency on our Work page.

IdeaEffortImpact
Record, transcribe and summarise candidate calls into structured JobAdder notesLowHigh
Reporting on demand through the connector, with sensitive data gatedLowHigh
A Claude project loaded with the agency's own policies, for writing new onesLowMedium to high
Surfacing candidate and client crossovers before anyone has to askLow to mediumHigh
A self-service refresh campaign for the candidate databaseMediumHigh
Merge duplicates, link head offices to branches, tidy locations, retire stale recordsMedium to highHigh, and foundational

What we won't do.

You're handing us access to your candidate database. These are the lines. Most are enforced by the software itself, not by good intentions.

  • No shared loginsEvery person connects with their own JobAdder sign-in and sees only what their permissions allow. Every change is attributed to whoever asked for it.
  • No crossed wiresYour workspace is pinned to your JobAdder account. Connecting it to any other account is refused and recorded, every time.
  • No copy of your databaseNo candidate records are stored on our side. Requests pass through to JobAdder and the answers pass back.
  • No deleting by defaultDeleting records is switched off unless you ask for it and understand what you're turning on.
  • No training on your dataWe don't train AI on your data. On Anthropic's Team plan, neither do they.
  • No quiet retriesIf a change might have half-landed, the connector says so and Claude checks before trying again.