Skip to main content
Engr. Adekunle runs three to five sites at a time across Ibadan. Bricklayers, labourers, painters, tilers. He hires through a foreman he’s worked with for nine years. The foreman is honest enough, mostly, but Adekunle has stopped pretending he doesn’t know that on a job where eight men were supposed to show up, six might have, and the wages for the missing two went into someone’s pocket. He calls this his ghost-worker tax. It runs about ten to fifteen percent of every site’s labour cost. He’s accepted it. Guild is the version of this where the ghost-worker tax goes to zero, because attendance is on the audit ledger and the foreman cannot edit it after the fact. Here’s what you can actually do.

Post a job

Five bricklayers, three days, Bodija, ₦4,000 a day. Submit. Our matching model ranks every plausible candidate in under a hundred milliseconds and pings the top ones across voice, WhatsApp, and SMS.

Link a bank by direct debit

One mandate. One ₦50 confirmation transfer. After that, paying a Job Seeker is one tap from your dashboard. OPay handles the debit, the receipt, and the reconciliation.

Pay Job Seekers

Per-shift, per-job, mid-job. OPay moves money from your bank to their wallet in seconds. The reconcile guard verifies every transaction before crediting. Idempotent end to end.

Escrow

Optional escrow flow for larger jobs. Fund the budget upfront; the funds release per-shift as attendance lands. Refunds for unfilled headcount are automatic.

Workforce reports

Hiring spend, attendance breakdown, workforce composition by trade and location, repeat-hire rates. Downloadable. Auditable. Defensible to your accountant.

​
Why this works

Two things make Guild useful for employers and they’re related. One: attendance is the source of truth, not the foreman. Every shift is marked in real time through the foreman’s dashboard. The Job Seeker’s phone has location and time validation. The audit row writes once and can’t be edited. If a Job Seeker disputes (“I worked four days, he only paid me three”), the ledger settles it — the dispute resolves against whichever side the data doesn’t support. Two: payment is per-attendance, not per-job. You don’t pay a Job Seeker a lump sum and hope they finish. You pay them per shift completed. If they leave after day two of a five-day job, you’ve paid for two days, not five. The remainder rolls back to your wallet (or your linked bank, if you funded by direct debit). Result: the ghost-worker tax goes to zero. The cost of the platform is a fraction of what you used to lose.

​
What you give up

A small thing worth being honest about: you give up the casualness of cash. The foreman who used to hand out daily wages from a Ghana-Must-Go bag is now a foreman who hits Mark Present on a dashboard. Some old-school site contractors don’t like this. Most adjust inside a week — especially after the first Saturday they realize they paid exactly for the headcount that showed up.

​
How employers use Guild

You don’t get voice as an offline phone line (that’s Job Seekers only). You don’t get SMS as a bidirectional rail (transactional SMS still fires to your phone for OTPs and confirmations).

​
Where to start

Link a bank first

Direct debit is the path of least friction. Set it up once and paying becomes one tap forever after.

Then post a job

Once your bank is linked, posting and paying are five minutes of work for a three-day project.