Webflow Development Proposal Template

In SendScope under Development, as Webflow Development

Webflow is sold on the promise that the client can edit it afterwards, and making that promise true is what you are actually being paid for. A site only you can change is a Webflow site built badly.

So the training session in the larger package is not an extra, it is the deliverable. These packages count pages and CMS collections, because the collections are where the structure really lives, and a client who needs five of them has a different project from one who needs one.

The account question should be settled before anything starts. A site built in your workspace and transferred later is a different arrangement from one built in theirs, and it decides who pays Webflow every month after you have gone. Agree it in the terms rather than discovering it at handover.

Use this template free

What the client reads

The scope

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

Custom website built on Webflow with CMS integration and animations.

The packages

2 to choose from

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

Basic Site

Up to 5 pages

A$1,000

1 week

  • Up to 5 pages
  • Responsive design
  • Basic animations
  • CMS setup
  • Form integration
Most picked

Custom Build

Advanced Webflow

A$3,000

2-3 weeks

  • Up to 15 pages
  • Custom animations
  • CMS collections
  • Integrations
  • SEO setup
  • Client training
  • 2 revisions

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.

sendscope.io/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 build you approve on this page.

  • Scope. The build is the package described above. Anything not listed is a change request, quoted and approved on its own before it is built.
  • Payment. The deposit shown on this page is paid on approval and the balance when the work is delivered and accepted.
  • Acceptance. The work is delivered for you to review. Please raise anything that does not match the scope within seven days, and it is fixed at no charge.
  • Fixes and new features. A defect is behaviour that does not match the scope and is fixed under this price for 30 days after delivery. A new requirement is a change request.
  • Hosting, domains and services. Hosting, domains, licences and third party services are yours, held in your name and billed to you, unless the package above says otherwise.
  • Your part. Content, access, credentials and decisions come from you. Time lost waiting moves the delivery date.
  • Ownership. The code written for you is yours once the balance is paid. Open source and third party components keep their own licences.
  • Cancellation. If you cancel, you are charged for the work completed and handed what has been built to that point.

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.

Before you send it

What to change first

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

  • Whose account the site lives in, and who pays for the plan afterwards
  • How many CMS collections are included, which is the real measure of complexity
  • Whether custom code is in scope, since it changes who is able to maintain it
  • Training, and whether a recording is included for the next person in that seat

Related

Ready to close deals faster?

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

Get started free