Your morning. Ready for recruiting.
CVs in your ATS. Profiles in your agency template. One morning summary of what needs your attention. We build the automation so you can focus on candidates and clients.
For solo recruiters and small agencies · A four-week build
Your morning, already organised.
Senior Java Developer
8 years’ experience · Warsaw · B2B
A scanned CV needs a second look. You stay in control.
From attachment to a client-ready profile.
An example workflow using sample data. Candidate details are extracted, formatted and anonymised, then checked by your team before sharing.
MARTA W. · marta@example.com · [phone number]
senior java developer, 8 yrs exp, warsaw, looking for b2b...
CV_final_v3_NEW(2).docx · 4 fonts · photo included · client sees name, contacts, current employer
Candidate MW-2481 · Senior Java Developer
8 years · Warsaw · availability noted · B2B
Agency template · anonymized · one font · skills mapped to the role spec · ready to send
Four weeks. A connected recruiting desk.
Four connected workflows, delivered week by week and connected to your existing ATS. Scope, integrations and price agreed before work begins.
- 1Week 1
CV intake
Email attachments become parsed, structured ATS records automatically. Works with the inbox you already have.
- 2Week 2
Morning digest
One 7:30 email: what came in overnight, what needs attention, what is on today. Inbox archaeology ends.
- 3Week 3
CV formatting & anonymization
Every CV lands in your template, anonymized for client sending, with a human check before anything goes out.
- 4Week 4
Re-engagement & lead-gen
Your dormant candidate database starts working again: matched, messaged, and routed back to your desk.
Fixed price, agreed in writing before work starts. Delivered in four weeks. Optional monthly support: monitoring, alerts and fixes, not billable hours. One call gets you the exact number.
A connected desk for a solo recruiter in CEE.
Previously, CVs stayed in email while formatting, anonymisation and inbox triage were handled manually. The current system connects Gmail, Google Drive and Manatal through n8n and Claude: CV intake, a 7:30 digest and formatted profiles with human review.
Candidate re-engagement and lead generation remain in development for this case. Quantified results have not yet been published.
Before this: nine years of CRM and automation engineering, including a recruitment ATS we built and shipped on the Salesforce AppExchange.
Less admin between you and the next conversation.
- Open inbox: 40+ emails, CVs buried in threads
- Download each CV, rename the file, upload to the ATS
- Retype candidate data the parser missed
- Reformat two CVs into the agency template by hand
- Delete names and contacts before sending to a client, hope nothing slipped
- Realise at noon a strong candidate applied on Friday
- 7:30, one digest email: what came in, what matters, what is on today
- Every overnight CV already parsed, formatted, in the ATS
- Client-ready anonymized versions waiting for your check
- Candidate follow-ups prepared for your review
- Low-confidence parses flagged for a human, not guessed
- You spend the morning talking to candidates
Start with the recruitment automation checklist.
12 tasks recruiters still do by hand, and the four worth automating first. Enter your email to read the checklist here, or send us a message about your process.
Questions before you get started.
Does this work with Manatal, Bullhorn, Vincere or Recruit CRM?
Yes. The current production build runs on Manatal; the same pattern connects to Bullhorn, Vincere, Recruit CRM, Loxo or JobAdder through their APIs. The workflow is the product, the ATS is a connector.
Is this safe for my LinkedIn account?
Honest answer: mass LinkedIn automation from cloud tools is against LinkedIn’s terms and risks your account. Where LinkedIn is involved we keep actions in your own browser, at human pace, with you pressing the final button. Most of the value here (CV intake, formatting, digest, re-engagement) does not touch LinkedIn at all.
What happens when it breaks at 7am?
Every workflow ships with monitoring and error alerts. A failed step becomes a message to us, not a silent gap in your morning digest. Fixing what breaks is part of the support arrangement, not an hourly invoice.
Who owns the workflows after handover?
You do. Everything runs in accounts you control, documented, with a written spec. If we disappear tomorrow, your system keeps running and any competent automation person can maintain it.
How much does it cost?
Fixed price for the four-week build, agreed in writing before work starts, plus an optional monthly support arrangement for monitoring and fixes. The exact number depends on your stack and volume; you will have it after one call, not after the project.
I’m Stan. I build these myself.
Nine years of automation and CRM engineering, with a background in QA. I scope and build the workflows; a dedicated QA lead tests them. On the call, you speak directly with the person responsible for your project.