Your consultants work JobAdder by asking.

We connect Claude to your JobAdder, put every consultant on their own login, and train them on their real work. Then every week you get a straight report on who's using it, for what, and what got in the way.

Weekly usage reportWeek 4

Two people use the whole toolkit. Everyone else uses a corner of it.

Requests to JobAdder through Claude
8,036
People in the office using it
7 of 7
Changes written back to JobAdder
67
Requests that failed
0.4%

93% of it was finding and reading records. We said so, and started a weekly ‘one thing to try’.

From a real weekly report, names removed. Every engagement includes one. See the actual page

What it looks like on the desk.

On its own, Claude writes. Connected to JobAdder through NativeMCP, our connector, it does the work as well: it searches your candidates, reads the notes, builds the shortlist and sets the reminders, all under the consultant's own name.

Nobody learns a new system. They ask the way they'd ask a sharp new starter, and check the work the same way. Some examples:

  1. ConsultantsRead this CV and tell me which of our open jobs it fits, and why.
  2. OwnersWhich contractors finish in the next four weeks?
  3. Back officeFind candidates who look like they were entered twice.
  1. Consultant

    Find senior .NET engineers in Brisbane with fintech experience who haven't heard from us this month.

  2. Claude

    I found 12. The best five have between 8 and 15 years in .NET, four of them in payments. Here's why each one fits the Lead Engineer role. Want them on the shortlist?

    Searched candidates and notes in JobAdder
  3. Consultant

    Yes. And remind me to call the top three tomorrow morning.

  4. Claude

    Done. Five added to the shortlist, and three call reminders set for 9am tomorrow.

    Updated the job and created 3 tasks in JobAdder
An example of an everyday request. The names, role and numbers are made up; every step is something the connector really does.

Three things that happened at one agency, and what we did about them.

A recruitment agency of about ten people, on JobAdder, working with us through 2026. We've left their name out. The numbers are real.

91% of 33,820 candidates were marked Active. One had been since 1999.

Nine in ten were still marked Active, the status they were given when they were entered. Only 24 were marked Do Not Contact. So a search for active candidates returned about 30,000 people, many of them likely retired, moved on or entered twice.

The same look had good news in it. Searching CVs for what people have done worked from day one: one search for a specialist skill set found 3,800 matching candidates.

What we proposed: agreed rules for what Active means, a clean-up of the 4,347 client records we'd analysed, and a small website where old candidates update their own details. The rules come first. Cleaning up before they exist just makes a new mess.

One square for every candidate record, in order from the oldest to the newest. The colours match the real status counts from a live sample; where each colour falls is illustrative.

A fault in our connector, and how it was caught.

This one was ours. One of the owners asked Claude for one type of note from the last few months, and got back every note in the system, all 874,560, with no warning. We traced it to a fault in how our connector sent searches to JobAdder. It was quietly ignoring filters in 18 of the 27 areas the connector covers.

Most filtered searches still gave plausible answers, so the fault was easy to miss.

What we did: fixed it that week, added tests so it can't come back, and explained it in plain words in that week's report. A filter JobAdder can't apply is now an error, not a silent pass.

  1. Activities, filter dropped
  2. Applications, filter dropped
  3. Attachments, not affected
  4. Candidates, filter dropped
  5. Categories, not affected
  6. Companies, filter dropped
  7. Contacts, filter dropped
  8. Email compose, not affected
  9. Floats, filter dropped
  10. Folders, filter dropped
  11. Interviews, filter dropped
  12. Job boards, not affected
  13. Jobs, filter dropped
  14. Lookup lists, not affected
  15. Lookups, filter dropped
  16. Notes, filter dropped
  17. Opportunities, filter dropped
  18. Placements, filter dropped
  19. Requisitions, filter dropped
  20. Search, not affected
  21. Sign-in, not affected
  22. SMS, not affected
  23. Submissions, filter dropped
  24. Timesheets, filter dropped
  25. Users, filter dropped
  26. Video, not affected
  27. Webhooks, filter dropped

Filters dropped Not affected

18 of the 27 areas answered every filtered search as if it were unfiltered.

A thousand lookups a morning became one request.

One consultant had Claude building a daily call list the long way: about a thousand separate JobAdder lookups every morning, each one slow and each one a chance to fail. We saved the consultant's rules as a routine on our server. Now the consultant makes one request, our server does the sifting, and the list comes back without anyone who was on it in the last four weeks or from the backgrounds they don't want.

  1. 1,014Wk 1137
  2. 2,889Wk 2152
  3. 5,653Wk 3184
  4. 8,036Wk 467
  5. 2,655Wk 572
  6. 2,421Wk 653
Week 5: the call list moves onto the server, and requests drop by more than half. Requests to JobAdder through Claude each week; the small figure is changes written back. Changes peaked in week 3, when one consultant caught up a backlog, then dipped while that consultant's new routine spent two weeks only flagging changes before it was trusted to make them. Week 5 was four days.

The other findings, and what didn't go to plan

Aaron Thomas

You deal with a technology recruiter, not a software vendor.

Aaron Thomas founded Digital Native in 2016, after leading technology recruitment at Hudson and running Davidson's technology business across Queensland and New South Wales. Twenty years on the desk, recruiting everyone from engineers to CTOs. He built NativeMCP for his own desk first.

Yes, we recruit technology people in Brisbane too. So here's the deal: we use a consultant's JobAdder sign-in only to carry out that consultant's own requests, we keep no copy of what comes back, and you can switch anyone off instantly. Ask for a confidentiality and non-use agreement before you connect anything.

Running more than one brand?

  • Each JobAdder account gets its own workspace, locked to that account. Brands that share one JobAdder account share one workspace.
  • Each workspace has its own switches. Turn off the tools a brand doesn't need, including sending SMS.
  • Each gets its own weekly report, with a team version that ranks nobody.
  • Roll it out one desk or office at a time. Everyone signs in as themselves, so nothing is shared between brands by accident.

What it costs.

  • A Claude Team plan for each person. Paid to Anthropic at their published price. We recommend Team because Anthropic doesn't train its models on Team data.
  • Our work, quoted per piece. After a first call you get an itemised quote, and you can say yes to one piece at a time.
  • A free 14-day trial of the connector on your own data, if you'd rather see it before talking money.

Questions owners ask.

New to all this? Read the plain-English guide.

Why not just use ChatGPT, or hire an AI champion?

ChatGPT, or Claude on its own, is good with words but can't see your database, so the work stops at copy and paste. An AI champion is a good hire, but they'd still need a safe way into JobAdder and a playbook that works on a recruitment desk. That's what we bring.

Why not JobAdder's own AI features?

Use them. JobAdder's AI works inside its own screens, for example refreshing old candidate profiles in the background. NativeMCP is different: your consultants ask Claude for anything across the whole database, in their own words, and the work lands in JobAdder. The two sit side by side.

Could our own AI person just use NativeMCP?

Yes. The connector is available on its own, and the free trial is exactly that. What an engagement adds is the look at your desk and database, the routines, the handbook and the weekly report.

Will it replace my consultants?

No. It does the searching, clicking and typing around the job. The calls, the judgement and the relationships stay with your people, and they get more time for them.

Can it message candidates or clients?

It can send an SMS through JobAdder, but only when a consultant asks it to in the conversation. If you'd rather it never did, we switch messaging off for your agency. Deleting records is off by default.

Is our candidate data safe? You're a recruiter too.

Everyone signs in with their own JobAdder login and sees only what they already could. We keep no copy of your candidates and we don't train AI on your data; on the Claude Team plan, neither does Anthropic. Our records show who used which tool and when, not what they searched or what came back. The full detail is here.

What happens if something breaks, or we stop?

Tell us and we fix it, Monday to Friday, 8:30am to 5:30pm. Keeping the connector working when JobAdder or Anthropic change something is our job, not yours. If you stop, we switch your workspace off and every sign-in with it, and you keep the handbook and the skills.

What do I need already?

JobAdder, and a Claude Team plan for each person who'll use it. Nothing to install, and nothing changes in how JobAdder works.

We don't use JobAdder. Can you still help?

The connector is built for JobAdder. If you're on something else, talk to us and we'll tell you honestly what's possible.