Automation Proposal Template
For automation specialists quoting a small business drowning in manual steps between tools it already pays for.
- Who it is for
- Automation specialists
- Ideal client
- A business losing hours to manual steps between tools
- Category
- AI & Automation
- Packages
- 3
Automation work is quoted by the hour far more often than it should be, and hourly is the wrong unit for it. The client cannot tell whether six hours is reasonable, and you cannot tell in advance, because the time goes wherever the APIs are awkward rather than wherever the logic is complicated.
What the client reads
The scope
This is the wording the template arrives with. Yours replaces it.
The packages
3 to choose from
The client picks one, and the one they pick is the one they approve and pay on.
Single Workflow
1 automation
A$300
1-2 days
- 1 workflow (up to 5 steps)
- 2 app connections
- Testing & QA
- Documentation
- 7-day support
Automation Suite
5 workflows
A$1,000
1-2 weeks
- 5 workflows
- Multi-app integration
- Error handling
- Documentation
- Training video
- 30-day support
Full Business Automation
Complete system
A$3,000
3-4 weeks
- Unlimited workflows
- Complex logic
- Database integration
- Custom webhooks
- Monitoring setup
- Team training
- 60-day support
The whole thing, live
The page your client opens
Not a screenshot. This is the real client page running on an invented deal. Pick a package and press approve to see what your client would see; nothing is sent or charged.
How it gets paid
Deposit, then balance
50% is due when the client approves, and the balance when you mark the work delivered. Both payments happen on the same link the proposal is on.
Card or bank transfer, and you choose which per deal. If you want a package to bill every month instead of once, you set that on the package itself when you build the deal, and the client can cancel it from their own link.
Prices are a starting point in Australian dollars. Change the figures, the inclusions and the number of packages to suit what you sell.
The starting terms
What approving the page records
These sit above the approve button. The client reads them, and approving records that they accepted them.
These terms cover the package you approve on this page.
- Scope. The work is the package described above. Anything outside it is quoted separately before it starts.
- Payment. The deposit shown on this page is paid on approval and the balance when the work is delivered.
- Third party costs. Model usage, API credits, software subscriptions and platform fees are yours and are not included in this price. You keep the accounts in your own name.
- What automated output can do. Generated output is reviewed before handover, and no particular accuracy, ranking, conversion or saving is promised. You stay responsible for checking output before you rely on it.
- Access. You provide the accounts, data and permissions the work needs. Time lost waiting on access moves the delivery date.
- Ownership. Prompts, workflows and configuration built for you are yours once the balance is paid. Tools and libraries keep their own licences.
- Changes and cancellation. A change in scope is quoted as a new deal. If you cancel, you are charged for the work already done and the deposit is applied to it.
Approving this page records that you accepted this scope, this price and these terms.
Starting terms, not legal advice. Read them, change what does not match how you work, and have a lawyer look at them if the work is large enough to warrant it. Your own default terms in Settings replace these automatically.
Pricing it well
What decides whether this job is profitable
This template prices by workflow instead, with the step count named. One workflow of up to five steps connecting two apps is a known quantity. Five workflows with error handling is a known quantity. Both can be quoted honestly before you have seen the client's stack, which hourly cannot.
Each tier includes a support window after handover, from a week to sixty days. That is deliberate and it is the part most quotes leave out: an automation that breaks three weeks later is the client's emergency and your unpaid afternoon unless the proposal already said which it is.
Before you send it
What to change first
The parts of this template most likely to be wrong for you.
- The step counts, which are what define a workflow here
- Who pays for the platform subscription and any per-task charges
- The support window, which is the clause that protects your evenings
- Whether documentation and a training video are included at every tier
Related
Ready to close deals faster?
Create your first deal page in minutes. No credit card required.
Get started free