An international employment agency lives on a flow of applications, and each link in that flow is usually a separate person. Someone runs the Meta campaigns, someone moves leads into a sheet or CRM, someone makes creatives for a new corridor, someone writes landing pages for a new country.
The bottleneck is not any one of those roles — it is the seams between them. A lead that arrives at night waits until morning. A creative for a new route waits for the designer. And once a campaign has run, nobody can say with certainty what in it worked, because no one kept the versions of the copy or the audiences.
Four layers, each sitting on top of a tool that was already in use. Nothing was rewritten from scratch.
Execution layer. One working repository as the single source of truth: campaigns, scripts, creatives, legal pages. All under git, so every campaign change has a history and can be rolled back.
Knowledge layer. Processes written down as instruction scripts rather than kept as verbal agreements. The most valuable one launches a full Lead Gen campaign in Meta — campaign, ad set, lead form and the ad itself, with four ready audience presets. It is not a prompt but a record of the rakes already stepped on: app development mode limits, lead form locales, newly mandatory API fields, the form auto-binding to the wrong default.
Integration layer. Incremental lead pulls from the lead forms on a schedule, mapping a campaign to citizenship and country of interest, prioritisation rules, upsert into the CRM. The CRM holds a formula with a WhatsApp link: the manager clicks and writes without copying the number. A separate track handles candidate applications with deduplication.
Production layer. Video creatives assembled as code rather than as a project in an editor. A clip for a new corridor is a change of parameters, not a new edit.
| Metric | Value |
|---|---|
| Cost per lead, winning combination | $1.63 — men 25–44, India and UAE, Facebook feed only |
| Leads in the system | 115 backfilled in one pass + a continuous flow |
| Corridors fixed on data | 6 (poor-quality routes cut on the numbers, not on a hunch) |
| Candidate campaigns in Ukraine | 3 campaigns → 37 leads |
| Manual work per lead | 0 minutes from Meta to CRM |
| Direct outreach | a separate table; wave two verified 29 employers |
$1.63 is the cost per lead on one winning combination, not an account average. The average is higher, and anyone showing you a single good CPL as an overall result is leaving something out. The combinations that burned budget were cut — see below.
This is the part case studies usually leave out, and it is exactly what you need before commissioning something like it.
One operator. That is the point of the case: not “AI replaced the marketing team”, but “a layer of agents on top of working tools let one person hold a flow that usually takes four”.
On one combination and one corridor, yes, and the figure is verifiable in the ad account. As an account average it would be untrue, which is why we do not present it that way.
Because a chat keeps no priority and does not deduplicate. The manager should start from a card that already shows citizenship, country of interest and priority, with the WhatsApp link ready.
For now yes, because that is where the flow is in these corridors. The integration layer does not depend on the source — the collector changes, the rest stays.
If you have a flow of applications and a person sorting them by hand, yes. If the flow does not exist yet, there is nothing to automate: you need the channel first, and that is the honest answer even though it does not sell.
Start with a short brief — we reply with an estimate.