How it works
Five clear steps from “this eats my week” to a working system you own.
What are the steps in an OpenAtoZ project?
There are five: you describe the task, I send a fixed-price scope, I build and test with fictional data, we run a live test together, and I hand over a written guide listing every trigger, permission and how to switch it off. You own everything at the end, with nothing to cancel.
Describe the task
Tell me the job that eats your week. I ask a few sharp questions: which tools you use, how many enquiries or records, who needs alerting.
Fixed-price scope
You get a short written scope: what gets built, what you will own, what is out of scope, the delivery date and the price.
Build and test with fictional data
The build happens in your accounts with the least access needed, tested first with made-up data so no real customer is affected.
Live test together
We run a real test, such as a test enquiry through your own form, and you check the result yourself.
Handover
A written guide, a list of every trigger and permission, how to switch it off, and access handed back.
What you own at the end
Everything: the form, the sheet, the scripts or workflows, the reply templates and the guide. No licence from me, no lock-in.
What I won’t do
- Promise numbers of jobs, bookings or revenue.
- Send cold marketing on your behalf.
- Lock you into a subscription or a tool you can’t leave.
Explore more
Tell me what you need done
Describe the job in a few lines. You get a fixed-price scope, or an honest “not for me”.
How long does it take?
Reply-in-5 is guaranteed live within 48 hours of access. Other jobs have a delivery date in the scope.
What access do you need?
Only what the job needs, granted by you and removed at the end.