Skip to content

All decks

Deck 07 · Jun 2026 · 11 slides

The Pragmatic Automation Blueprint

Built and running

The method behind the recruitment system I built and run at Mankind. Visuals made with NotebookLM.

The visible problem was admin: about four hours a day, and 50 minutes for every candidate profile. I did the job by hand for four weeks before automating anything, and found two problems underneath. “Good” had no written definition, so every recruiter judged candidates slightly differently. And the firm had no memory: candidates who missed one mandate vanished, and were paid for again six months later.

So the first thing I built was a rubric, not code. Then I tested adoption for $27 a month instead of buying a platform: ClickUp as the backbone, custom JavaScript as the bridge, and Claude scoring CVs against the rubric. Nothing is scraped. Profiles went from 50 minutes to 15, and daily admin from four hours to 45 minutes. The full account, including what didn’t work, is in the Mankind Recruitment OS case study.

  1. The Pragmatic Automation Blueprint, slide 1 of 11

    01 / 11

  2. The Pragmatic Automation Blueprint, slide 2 of 11

    02 / 11

  3. The Pragmatic Automation Blueprint, slide 3 of 11

    03 / 11

  4. The Pragmatic Automation Blueprint, slide 4 of 11

    04 / 11

  5. The Pragmatic Automation Blueprint, slide 5 of 11

    05 / 11

  6. The Pragmatic Automation Blueprint, slide 6 of 11

    06 / 11

  7. The Pragmatic Automation Blueprint, slide 7 of 11

    07 / 11

  8. The Pragmatic Automation Blueprint, slide 8 of 11

    08 / 11

  9. The Pragmatic Automation Blueprint, slide 9 of 11

    09 / 11

  10. The Pragmatic Automation Blueprint, slide 10 of 11

    10 / 11

  11. The Pragmatic Automation Blueprint, slide 11 of 11

    11 / 11