For agency dem and client work
One workflow, thirty clients, thirty different sets of credentials
Agency own problem no be to build the thing once. Na to build am once come run am thirty times, for thirty businesses wey dia accounts, tone, timezones and opinions all small-small different — and still fit explain, at the end of the month, wetin each of dem get.
The three-person agency
Three people, twenty-eight clients, mostly small businesses. The work really dey repeat: monthly campaign, weekly post, lead form wey suppose reach the right inbox within one hour, and report on the first of the month wey go show wetin happen.
The reason dem dey busy no be say any of that one hard. Na because dem dey do am twenty-eight times, and the twenty-eight just different small-small sotay no template fit all of dem. Client twelve want Polish and English. Client nineteen no gree send anything before ten for morning. Client four own inbox belong to person wey never reply once.
So the shape na: one workflow, wey get parameters, run per client, with the differences kept as configuration instead of twenty-eight copies wey don quietly change each on dia own.
Credentials wey belong to the client
Each client accounts na dia own credential set, wey dem store am encrypted, and dem call am by name. The workflow point to the set, no be to the secret, so the same published workflow fit run against twenty-eight different sets of accounts without twenty-eight copies of anything.
E mean say to rotate one key na just one edit for one place. E still mean say client wey comot go carry dia credentials go: delete the set and every workflow wey point to am go stop for that client, sharp sharp and e go show, instead of e go continue to work for six weeks because nobody remember.
One version, or one version per client
When you publish improvement, e push am to every client at once, and na that one be the point of building am once. Where one client really need something different, that difference na branch inside the shared workflow with condition on the client, no be fork — because fork na thing wey dem go fix for one place and forget the other.
Runs wey dey go on no dey affected either way: each run follow the version wey e enter on, so to improve workflow on the twelfth no go scatter client campaign wey start on the tenth.
- ⚡ScheduleOne run for each client. 28 run dem, one version wey dem don publish.
- 2Configuration wey dem readTone, language dem, time to send, approver. For each client.
- 3Copy and pictureDem draft am, come illustrate am from the licensed library.
- ✋ApprovalClient 19 require am come wait. The other 27 continue.
- ✉Dem don send amEach one on the client own accounts, inside the client own window.
- 📄Ripot amSame shape for everybody, so month-to-month get meaning.
28 credential sets1 workflow wey you go maintain
One workflow. Thirty clients. Nobody notice.
Wetin agencies dey build
Six wey pay for demself quick
The monthly report
Dem assemble am from numbers on the first, in the same shape for every client, before anybody ask. The number one reason wey agency dey start here.
Lead routing
Form land on client site, AI step read wetin the person really want, and e reach the right inbox within one minute — with copy to you, so you fit show client wey dey ignore leads say dem dey ignore am.
To onboard a client
Accounts connect, workflows enable, configuration fill, first report schedule. The checklist come turn to workflow, and the fourteenth client get the same start as the first.
Content calendar dem
Post wey dem don draft, illustrate am from di licensed library, queue am make dem approve am, come publish am on di client own schedule.
Dey watch for wahala
Client site don fall, form wey no dey submit again, feed wey quiet for three days. E beta make you notice am before dem notice am.
Offboarding
Delete di credentials, stop di workflows, produce final report. If you do am well e take ten minutes; if you do am from memory e take six months plus one awkward email.
Wetin you fit tell client
Say di work dey happen ontop dia own accounts, so wetin come out na dia own and e go still be dia own when di relationship end. Say every run get log, so if dem ask wetin happen on di fourteenth, answer dey. And say dem simulate di campaign before e go out, wey beta pass say "we check am well well".
Di Team plan dey exist for dis kind work: shared workflow library so di good version na di one everybody dey use, role-based access so junior fit run workflow without fit rewrite am, and enough AI steps to cover portfolio no be just one project. Di numbers dey di pricing page.
Where dis one no good again: if all di twenty-eight clients really need different thing, you no get workflow, you get twenty-eight workflows plus filing wahala. Di technique wey dey up dey work because most agency work na di same job with different name inside. Where e no be so, tell di truth about am before you go build configuration system wey get twenty-eight special case inside.