Get Paid for Automation, workshop 05, with Johnathan Lightfoot
Scope it before you quote it
Turn a vague client request into a written scope with deliverables, exclusions, assumptions and acceptance criteria, so both sides agree what is being built before any work starts. In three hours you also learn to handle the changes that appear once building begins, and you scope a real project of your own.
- When
- Saturday 9 January11:30 AM in Accra
12:30 PM in Lagos - Registration closes
- Saturday 2 January, 11:30 AM in Accra
- Length
- 3 hours, live online
- Fee
- GHS 350MoMo or card, through Paystack
- Places
- 30 people
- For
- Automation practitioners who quote and deliver projects and want the scope agreed before the work starts
Why this workshop
The argument that ends most automation projects is not about the build. It's about what was supposed to be built. A client says connect our forms to our accounting and pictures one thing. You picture another. You are both being reasonable, and you are describing two different projects.
The gap gets filled in during delivery, and the filling is unpaid. An extra system to connect, more users than planned, a report nobody mentioned, a data cleanup that turns out to be three systems. You absorb it to keep the client happy, the margin goes, and the relationship sours anyway.
A written scope settles those questions before any money changes hands. It states what is included, what is not, what you assumed, what the client must provide and how you both agree the work is finished. That protects the client from paying for work they did not ask for, and it protects you from doing work you will not be paid for.
What you will be able to do
- Turn a vague client request into a specific statement of the problem being solved.
- Write deliverables precise enough that both sides know when they are finished.
- List exclusions and assumptions that stop extra work arriving unpaid.
- Set acceptance criteria for an automation, including what counts as working.
- Identify the access, inputs and decisions you need from the client before you start.
- Handle change requests with a written process instead of an argument.
- Recognize the warning signs of a project that is not ready to be quoted.
What you leave with
- A scope document template with the problem, deliverables, exclusions, assumptions, client responsibilities, acceptance criteria and sign-off already laid out.
- A change request form and a short process for pricing and approving changes once work has started.
- An acceptance and handover checklist for an automation project, covering documentation, training and the support period.
- One real project scoped by you in the clinic, in a state you could send to a client.
- The questions to ask before you scope anything, and the vague phrases that should make you stop and ask them.
The 3 hours
- 0:00Where automation projects go wrongIntroduction, and the scope disputes participants bring with them
- 0:15From a vague request to a defined problemWhat the client actually needs, who uses it, what it connects to, and what done looks like
- 0:50Writing the scopeDeliverables, exclusions, assumptions, client responsibilities and acceptance criteria
- 1:30Break15 minutes
- 1:45Changes, handover and sign-offChange requests, what happens when the client adds work, and closing a project cleanly
- 2:20Scoping clinicScope a real project yourself, test it against the group, then questions
Is this for you
Good fit
You already build and deliver automations, in n8n, Make, Zapier, Microsoft Power Automate or Power Apps, or with code. You have taken on a project where the client kept adding things, or quoted work without writing down exactly what was included. Freelancers, independent consultants, small automation service providers and technical professionals who deal with clients directly all fit.
Not a fit
You have not built a working automation yet. This is not an introductory building class, so start there first. It is also not a contract law course: we cover what a scope needs to say, not how to draft an enforceable agreement, and for that you need a lawyer. And if you want a promise of clients or income, no honest workshop can make one.
Bring: A laptop, and a project you have quoted, delivered or are about to quote, with the original client request if you still have it. If you have a scope or statement of work you have used before, bring that too.
Who teaches it

Founder of Bulletproof Automations. Three decades in systems integration and technology leadership as a CTO and CIO, and a former U.S. Navy Operations Specialist.
Questions
Am I ready for this?
If you have built and delivered at least one automation for someone else, or you are quoting your first paid project now, yes. The workshop does not teach building. It assumes you can do the work and teaches you to define it.
Does it matter which automation platform I use?
No. The examples draw on n8n, Make, Zapier, Microsoft Power Automate and Power Apps, custom integrations and AI automation, but a scope is written the same way whichever tool does the work.
Are the examples relevant to Ghana?
Yes. The worked examples and the clinic project come from the kind of work Ghanaian small businesses and service providers commission, with local realities like power, internet and paying for tools written into the assumptions.
Is this a certification?
No. It is a training workshop. It does not award, and does not count towards, any Bulletproof Automations certification.
Do I have to take the whole series?
No. Each workshop in Get Paid for Automation stands alone. Take the ones you need, in any order.
How do I pay?
Register on this page and pay at the secure checkout by mobile money or card. Your place is confirmed when the payment is confirmed, and your confirmation email follows. Any lower price you qualify for is shown on this page.
How do I join?
Live online, by invitation. When you register, give us the Google account you will join with. Once your payment is confirmed, we add that account to the workshop's calendar invitation and the joining details reach you by email. Join signed in to that account, from a laptop if you can.
Part of Get Paid for Automation
Each workshop stands alone. You do not need to take the whole series, or take the workshops in order.
- 01Sat 12 Dec
You know automation. Do you know what to charge?
Cost a project, choose a pricing approach and write a quotation you can explain to a client.
- 02Sat 19 Dec
Who should you sell to?
Define who to sell automation services to, and who to avoid.
- 03Sat 26 Dec
Where are the clients?
Find where your ideal clients are and get meetings with them.
- 04Sat 2 Jan
Discover what clients need
Turn client frustrations into defined automation problems worth paying for.
- 05Sat 9 Jan
Scope it before you quote it
Turn a vague request into a written scope both sides can agree to before work starts.
- 06Sat 16 Jan
Write proposals that win
Write proposals that show you understood the problem and make the next step easy.
- 07Sat 23 Jan
Close the deal
Discuss fees, answer objections, and follow up so proposals get signed.
- 08Sat 30 Jan
Deliver like a professional
Test it, keep the client informed and hand it over so their team can run it without you.
- 09Sat 6 Feb
Turn projects into recurring income
Offer paid support after handover so maintenance work is covered by an agreement.
- 10Sat 13 Feb
Win international clients
Present and price automation services for overseas clients, across currencies and time zones.
Get Paid for Automation is organized and presented solely by Bulletproof Automations, an independent training provider. n8n, Make, Zapier, Microsoft Power Automate and Power Apps are named only to describe the tools participants use; none of their owners sponsors, endorses or is affiliated with this series. The workshops teach business skills and do not guarantee clients, contracts or income.
Attending a webinar or workshop is training. It is not a certification and does not count towards one.