Templates / Proposal

Free Sales Proposal Template

A sales proposal covers the scope being quoted, the work plan, what’s included and not, the pricing options, and the terms for payment and approvals.

Sales Proposal template preview

7-day free trial. No credit card required.

Use this template

Language:

en

Last updated:

October 2026

Share template

The sales conversation gets real when a buyer wants proof, a clear boundary, and a price that won’t turn into an open-ended build. This sales proposal puts the scope and the order of work up front, so the buyer can see what ships, what gets signed off, and what happens if the requirements change. The page uses rose pricing accents with Space Grotesk headings and Inter body text, so the promise reads like a spec, not a pitch.

The Summary states the outcome in plain language, then the proposal introduces the person doing the work in Who you are working with and explains the build sequence in How the order runs. The middle sections answer the questions buyers ask before they commit, including what access is needed, when working software shows up, where the MVP boundary sits, and how bug fixes, approvals, and rework get handled.

  • Summary Defines the MVP outcome, calls out the fundamentals that get built early, and names the workshop that locks scope.
  • Who you are working with Explains who delivers the work and how decisions and handoffs get handled during the build.
  • How the order runs Walks through the sequence from scope lock to prototype to staged build and launch handover, with approvals along the way.
  • Order summary Prices the five line items separately, so the buyer can choose what they want included and you can replace the numbers with your own.
  • Next steps Captures acceptance with a signature and states what happens next, including the booking payment and the access needed to start.

The pricing lives in Order summary, where the five items are broken out so the buyer can take one part or the full package. Once the buyer agrees, the Next steps section collects a signature online and points to a booking invoice, leaving you to swap in your own prices and send the proposal.

We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.

Yazan & Mawaheb
Yazan & MawahebAgency Owners

What to include in a sales proposal

PartWhat it covers

Summary

States the shipped outcome and the boundary-setting approach, then points to a short workshop that pins down the exact MVP scope.

Who you are working with

Introduces the delivery owner and explains how decisions, handoffs, and the core platform basics get handled early.

How the order runs

Explains the path from scope lock to prototype to staged build and launch handover, including where approvals happen.

Product discovery workshop

Describes the scope workshop and the build components that follow, including billing setup and the core app deliverable.

Auth and user roles

Defines the login and permissions work, plus the admin and integration pieces that support day-to-day operations.

Order summary

Carries a priced items table for the five components, with each line item priced separately so you can adjust the package and totals.

Next steps

Carries the signature block and a fee summary, and notes the booking invoice and the access checklist that follow acceptance.

What do you need from us before you start?

Lists the accounts and materials needed to begin and names the person who can answer questions and approve scope and prototype.

What’s included in the MVP and what’s explicitly not?

Defines what counts as in-scope, how changes get priced and scheduled, and how bug fixes are handled right after launch.

Payment

Spells out the 50/50 payment split, invoice timing, start conditions, and how pauses, access, and scope changes affect delivery.

Approvals and rework

Defines written approval points, how reversals are treated, how third-party dependencies affect work, and the liability limit.

Who it is for

Product developers, agencies, and SaaS teams quoting a web app MVP build where the buyer wants the scope locked, the fundamentals covered early, and pricing split into selectable line items.

The proposal in full

Summary

You’ll have a working MVP that customers can sign up for, log into, and pay for, with the right permissions in place and an admin view that lets you run the day-to-day without patching spreadsheets.

I’ll turn that into a web app MVP people can log into, pay for, and use. I lock scope early, show you working software fast, and build the fundamentals first so launch day isn’t a scramble. If you want to move, the next step is a short workshop to nail the flows and the exact MVP boundary.

I start by turning your current demo into a scoped plan that can ship. We’ll agree the exact user roles, the paid path, and the admin work you need to run the product. Then I build in short stages, with a staging link early, so you can click through real screens and confirm the direction before I go deeper.

Who you are working with

I’m Mads Nørrebo, a product developer. I build web apps for founders and small teams who have proof of demand and need the first version to be usable, billable, and supportable. Most of my work starts right where you are now: a clear idea, a waitlist or internal users, and a manual process that is starting to break.

I’m the person writing the scope, building the app, and shipping it. That keeps decisions fast and reduces handoffs. I also build the “boring” parts early, because late-stage billing and permissions work is where schedules slip and products launch with gaps you can’t charge through.

How the order runs

After you sign, I move from scope to working software in a straight line: lock the MVP boundary, confirm the flows with a clickable prototype, then build and iterate in staging until it’s ready to launch and hand over.

  1. Scope lock workshop On order I run a half-day product discovery workshop with you. We leave with a written scope that names what the MVP includes, what it does not include, and the launch checklist. I’ll also confirm the roles, the paid plan structure, and the three third-party APIs we’re integrating.
  2. Clickable prototype Within a week I turn the scope into a clickable prototype for the core flows: signup, login, upgrade, and the main “job to be done” inside the app. You review it like a user would. Your approval here is what I build against, so changes stay cheap and obvious.
  3. MVP build in staging Weeks 1-3 I build the MVP and share a staging link as soon as the first end-to-end slice works. You’ll be able to log in and click through real screens, not just look at designs. I’ll ask for feedback in short batches, and I’ll keep a written list of what is in and what is out.
  4. Launch and handover On delivery I run a launch-day checklist with you: production setup, Stripe live-mode checks, admin access, and basic monitoring. Then I hand over the repo, environment notes, and a short “how to run it” guide. You get a final walk-through call so you can ship with confidence.

Product discovery workshop

A half-day working session to define the MVP boundary, user roles, paid path, and launch checklist, ending with a written scope I build against.

Web app mvp build

A working web app MVP delivered with a staging link during development and a production deployment at the end, based on the agreed flows and scope.

Stripe billing setup

Stripe checkout and subscription billing wired into the app, including plan setup, webhook handling, and live-mode validation so you can take payments on launch.

Auth and user roles

Login, signup, password reset, and role-based access rules for the roles agreed in the scope lock, so each user sees and can do the right things.

Admin dashboard

An internal admin area to manage users and subscriptions and to view the operational data you need to support customers without database edits.

3rd-party api integration

Integration with up to three external APIs named in the scope, including error handling and basic retries, with a clear note of any API limits that affect UX.

Order summary

These line items cover the full web app MVP build as described, including the scope lock workshop, prototype, staging MVP, and launch handover.

Next steps

If you want me to hold time for this, sign below and I’ll send the booking invoice and a short checklist for the workshop.

  1. Sign the proposal to confirm the web app MVP build.
  2. Pay the booking invoice for 50% to reserve the start date.
  3. Share access to Figma, Stripe, and the current spreadsheet or tool so I can prep the workshop.

What do you need from us before you start?

Access to your current materials and accounts: the Figma, the spreadsheet or current tool, and the Stripe account you want to use. I’ll also need one person who can answer product questions quickly and sign off on the prototype and scope.

When can we see something working, not just designs?

You’ll see two kinds of “working” early. First is the clickable prototype, which confirms the flows before I build. Then I’ll share a staging link as soon as the first end-to-end slice is running, so you can log in and test real screens.

What’s included in the MVP and what’s explicitly not?

What’s included is the list in “What you are ordering”, plus whatever is written into the scope we lock in the workshop. Anything outside that boundary is treated as a change, priced and scheduled before I start building it.

Who fixes bugs in the first few weeks after launch?

I do. For the first two weeks after launch, I’ll fix bugs that are inside the agreed scope and that prevent normal use of the MVP. New features and new edge-case requirements are handled as follow-on work once the MVP is stable.

Payment

50% is due to book the work when you sign. The remaining 50% is due when I deliver. Invoices are payable within 14 days of the invoice date.

Start and schedule. I start after the booking payment is received and I have the access I need. If feedback or approvals pause, the timeline shifts by the same amount the project is waiting.

What I need from you. Before I start, I need access to your current materials and accounts, including Figma, your spreadsheet or current tool, and the Stripe account you want to use, plus one decision-maker for quick sign-off.

Scope and changes. The web app MVP build is based on the scope I lock with you in the workshop and confirm in the prototype. Anything outside that boundary is a change, priced and scheduled before I build it.

Approvals and rework

I ask for written approval on the scope and on the clickable prototype before I move into the main build. If I build against approved work, later reversals are treated as changes.

Access and third parties. If the MVP depends on third-party services, I can only build and test against what their accounts, APIs, and uptime allow. Time spent diagnosing external outages or account issues is follow-on work.

Bug fixes after launch. For the first two weeks after launch, I fix bugs that are inside the agreed scope and that block normal use of the MVP. New features and new edge-case requirements are follow-on work.

Liability limit. I’m not responsible for lost revenue, lost data, or indirect damages related to use of the MVP. If something goes wrong, my responsibility is limited to the amount you paid for the work.

Questions about this proposal template

What should a sales proposal include?

A sales proposal usually includes a summary of what gets delivered, how the work runs, pricing, and the terms for payment, scope changes, and approvals. This template also includes buyer-facing answers on access needed, timing for working software, and bug fixes after launch.

How do you write a scope that doesn’t turn into an open-ended project?

A proposal needs an explicit boundary that says what’s included and what is not, plus a change process for anything outside that line. This template ties the boundary to a discovery workshop and written approvals before the main build starts.

Should a proposal break pricing into separate line items?

Separate line items let a buyer accept only part of the work or take the full package, and the proposal stays clear about what each piece covers. The Order summary in this template prices five components individually so the package can be adjusted without rewriting the whole document.

When should a buyer see working software during an MVP build?

A buyer usually wants early proof in two forms: a prototype that confirms the flows, and a staging build they can log into and test. This template describes both and puts them in the delivery sequence before launch handover.

What payment terms make sense for a project like this?

Common terms split a booking payment from a final payment tied to delivery, with a stated invoice due period. This template uses a 50% booking amount on signing and the remaining 50% on delivery, with invoices payable within 14 days.

How do approvals and rework usually work in a proposal?

A proposal normally names the approval points and says what happens if approved work gets reversed later. This template asks for written approval on the scope and clickable prototype, and treats later reversals as changes.

Start free today

Your entire business, one login away

No credit card required. No contracts. Just the tools you need to run, grow, and automate your business with Super Work AI.

No credit card required

Plutio - Your entire business, one login away