AI Agent Proposal Template

For automation and AI freelancers quoting a business that wants an assistant trained on its own material and its own rules.

Use this template freeA$500 to A$5,000, 50% on approval
Who it is for
AI and automation freelancers
Ideal client
A business wanting an assistant trained on its own material
Packages
3

This is the fastest moving category on the whole list, and the risk in quoting it is not technical. It is that the platform changes underneath you between the proposal and the delivery.

What the client reads

The scope

This is the wording the template arrives with. Yours replaces it.

Build a custom GPT or AI agent tailored to your business needs.

The packages

3 to choose from

The client picks one, and the one they pick is the one they approve and pay on.

Simple GPT

Basic custom GPT

A$500

2-3 days

  • Custom instructions
  • Knowledge base upload
  • Action configuration
  • Testing
  • Usage guide
Most picked

Advanced Agent

Multi-capability agent

A$2,000

1-2 weeks

  • Complex instructions
  • API integrations
  • Multiple actions
  • Error handling
  • Analytics
  • Documentation
  • 30-day support

Enterprise Agent

Production-grade

A$5,000

3-4 weeks

  • Custom API backend
  • Multi-agent system
  • Database integration
  • Authentication
  • Rate limiting
  • Monitoring
  • SLA
  • 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.

vytdeal.com/d/sample

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

Both packages are scoped on capabilities rather than on a named product for exactly that reason: instructions, a knowledge base, actions, integrations. A scope written around what the thing does rather than around a vendor's current menu survives the next release, and the client still knows what they are getting.

The documentation in the larger tier matters more here than in most builds. An agent nobody can explain is an agent nobody will maintain, and the first time it does something unexpected the client needs to be able to read the instructions rather than ring you at nine on a Sunday.

Before you send it

What to change first

The parts of this template most likely to be wrong for you.

  • Which platform, and what happens if it changes before you deliver
  • Who pays for usage, which with an agent can be substantial and ongoing
  • What the agent is explicitly not permitted to do, which belongs in writing
  • Whether you maintain it afterwards, and on what arrangement

Related

Ready to close deals faster?

Create your first deal page in minutes. No credit card required.

Get started free