Templates by industry · Web agency

Website proposal template for your web agency

This is a website proposal template for a web agency, which you can read in full below: a fixed-price project, from scoping to going live, with its scope in writing, stages the client approves one after the other and a quote by package. Under each section, what wins a client over; in the text, the zones Cuevr fills in for your client.

14 days · 5 proposals · no credit card

L’équipe Cuevr10 years in sales, sharpened by our clients’ teams.

The proposal and closing, in a few figures.

  • 41%

    That is the closing rate of design trades’ proposals (print, web, mobile) sent with Proposify in 2025.

    Source: proposify.com, 2026

  • +20%

    Closing jumps by 20% when more than one decision maker reads the proposal.

    Source: proposify.com, 2026

  • 25.3 minutes

    That is the average time a buyer spends on a winning proposal, against 15.8 minutes on a losing one.

    Source: proposify.com, 2026

What is at stake in a web agency proposal.

  • Writing the scope before the price What is in, what comes next and what is out of scope.
  • Showing the project before coding it A client who sees screens decides more calmly than a client who reads a list of features.
  • Dating every approval A schedule only holds if the client knows what to approve and when.

For a fixed-price web project, stage by stage.

This template is for owners, project directors and salespeople at web agencies, development agencies and studios that sell a website, an app or a custom tool at a fixed price: a scoping phase, a build in stages that the client approves one after the other, going live, then maintenance. The buyer is often a marketing director, an operations director or a head of IT, who compares several agencies on the same brief. For a scoping workshop sold on its own, keep the situation, the scoping section, the investment and the next steps; for a web design or maintenance job, keep the section that applies and adapt the packages in the quote.

The template, section by section.

The fixed text is what you keep as it is. The passages in square brackets are the ones Cuevr AI writes from what you know about the client, or that you replace with your figures and your prices. Under each section, the reason it is there.

  • […]
    Written by Cuevr AI for each client
  • […]
    Your figures, dates and prices
Wooden desk with two computer screens showing web page mockups, a keyboard and phones

Fictional example · For Supplies Example, a wholesaler of supplies for tradespeople that wants an online ordering portal for its business customers.

Build proposal from [Your agency]Build proposal from Example Agency

[The name of the project, for this client]A portal where your customers order without calling

Prepared for [The client] · [Date sent]Prepared for Supplies Example · sent this week

Your situation

[The client in its own words: its business and since when, its size, its customers, and the tool or website it uses today]

[What brings it here: what its current tool prevents it from doing, what that already costs it]

What we propose you achieve: [The result the tool brings once in service, before its deadline]

You have sold supplies to tradespeople for many years, and they order by phone, by email and on an old website that your team re-enters by hand.

This tool prevents you from letting your customers order whenever they want, and it already costs you order errors and data entry time.

What we propose you achieve: a portal where your business customers order on their own, connected to your stock management, in service before your busiest season.

[A sentence from the client, quoted word for word, that says why it is building this tool]

My customers order at dawn, and nobody is there to take their orders.

[First name, last name and title]Karim, sales director
  • [A figure from its current situation, with its unit]value to take from the brief[What this figure measures]Orders re-entered by hand each week
  • [A second figure, on another subject]value to take from the brief[What this figure measures]Share of orders that still arrive by phone

Your stakes

[Who will use the tool every day, and what the project must bring them, in one sentence]

A tool your tradesperson customers open on their own, even late at night, and that your sales assistants no longer have to re-enter.

  • [The main users, in a few words]Your tradesperson customers

    [What they do today, what the tool must spare them or let them do, with the fact from the brief that shows it]They order between two jobs, on their phone, and want to find their past orders in two taps.

  • [A second stake, on the business side]Your sales assistants

    [This stake in one sentence, with the fact that shows it]They re-enter every order received by email, and that is where errors are born.

  • [A management stake: cost, deadline, risk, fit with what exists]Your management

    [This stake in one sentence, with the fact that shows it]It wants a fixed price, a useful first version before the season, and a tool connected to your stock management without replacing it.

If nothing changes: [Each of the consequences the client foresees, with figures when it gives them]

If nothing changes: your competitors already offer online ordering, and your best customers end up ordering from them.

Our response for [The client]Our response for Supplies Example

We do not build everything at once. We first put into service a useful first version, the one that changes your users’ daily work; the rest comes after, guided by use. The exact scope is settled with you at the end of scoping, in writing, in the fixed price below.

[What this means for the client: what its first version contains and why, tied to its deadline]

We do not build everything at once. We first put into service a useful first version, the one that changes your users’ daily work; the rest comes after, guided by use. The exact scope is settled with you at the end of scoping, in writing, in the fixed price below.

Your first version contains online ordering and the follow-up of past orders: that is what frees your assistants before your busiest season.

  • The first version

    [The journeys that go into the first version, in one sentence]The catalog, the basket, the order and each customer’s order history.

  • Next

    [What comes once the first version is in service]Customer-specific prices, one-tap reorder and your salespeople’s dashboard.

  • Not now

    [What we deliberately leave out, to hold the price and the date]Online payment and the mobile app, which wait until we have seen how it is used.

Why custom-built, and why us.

  • The alternative considered[An alternative the client has considered, for example off-the-shelf software, and its limit]an off-the-shelf ordering tool, which does not connect to your stock management without costly development.

    What we do differently[What you do against it]we connect the portal to your stock management from the first version.

  • The alternative considered[A second alternative, for example its in-house team, and its limit]your IT team, already busy with what exists.

    What we do differently[What you do against it]we take the build on, and you keep control of every approval.

  • The alternative considered[A third alternative, for example another provider or a freelancer, and its limit]one freelancer for the design and another for the code, which you would have to coordinate yourself.

    What we do differently[What you do against it]one team, one contact, from the first workshop to go-live.

You see your tool before it is coded

In a few weeks, your needs become screens that your future users have tested. You fix a drawing, not a piece of software.

  • Workshops

    With your business teams and your future users.

  • A clickable prototype

    The key screens, tested before a single line of code.

  • A costed backlog

    Each feature described, estimated and ranked by priority.

Notebook of pencil screen sketches lying on a desk next to a phone

[What this scoping changes for the client: the needs of its business teams to settle between, and who on its side takes part in the workshops]

Your sales team and your assistants do not describe an order the same way: the workshops bring them together, with a few of your tradesperson customers, to settle it before drawing.

  1. [Duration]a few days

    Workshops

    Objectives, journeys, business rules, existing tools.

  2. [Duration]a few weeks

    Mockups

    The key screens drawn, then assembled into a clickable prototype.

  3. [Duration]a few days

    Test with your users

    [Number] of your users test the prototype; we fix what snags.A few of your users test the prototype; we fix what snags.

  4. [Duration]a few days

    Backlog and architecture

    Scope, architecture and acceptance criteria approved with you, in writing.

Built in stages, shown at every stage

Development moves in short cycles. At the end of each one, a demo on a version that runs, and an online test version open to your teams.

  • A demo every cycle

    You see it, you test it, you approve it.

  • An online test version

    Open to your teams from the first cycle.

  • Reviewed and tested code

    Review by a second developer, automated tests.

Two screens showing code, with a keyboard, on a development workstation

[What this way of working changes for the client: who on its side sets the priorities, and what it has already lived through with a project delivered in one block]

Your sales director sets the priorities each cycle, and your assistants try the portal as it goes: you avoid finding out at the end what you would have fixed at the start.

  1. Start of the cycle

    Priorities

    Your product owner and our project manager choose the cycle’s features.

  2. During the cycle

    Development

    Each feature coded, reviewed by a second developer, tested automatically.

  3. End of the cycle

    Demo

    By video call, what is done, what remains, what changes.

  4. The next day

    Online

    The new version is on your test environment.

[A conviction of your project manager about the value of showing the work at every stage]

A demo at every stage is that many chances to correct course before it is too late.

[First name, last name, title at your agency]Sonia, project manager at Example Agency

A go-live without surprises, and a tool that lasts

Your key users run acceptance testing on criteria written during scoping. We put it into production, then we keep the tool up to date and running.

  • Acceptance on written criteria

    A report signed by you.

  • A supported go-live

    Training for your users, help at startup.

  • A warranty, then maintenance

    Hosting, backups, updates and monitoring.

Server rack with blue indicator lights in a hosting room

[What this go-live changes for the client: who on its side runs acceptance, where the tool is hosted, what it expects from maintenance]

Your sales assistants run acceptance on real orders, the tool is hosted in France with a host of your choice, and you expect maintenance to keep the portal available in the middle of the season.

  1. [Duration]a few weeks

    Acceptance

    Your key users test against the written criteria; we fix as we go.

  2. [Duration]a few days

    Go-live

    Putting into service, user training, publication if needed.

  3. [Duration of the warranty]a few months

    Warranty

    Any defect against the acceptance criteria is fixed at no charge.

  4. Afterwards

    Maintenance

    Hosting, backups, security updates.

Your code, with you.

Your code lives from day one in a repository in your name, and you have access at any time to your environments, your accounts and the documentation.

[The technologies chosen, explained in plain language, and why any competent team will be able to take them over]

Your code lives from day one in a repository in your name, and you have access at any time to your environments, your accounts and the documentation.

Widely used technologies that any competent team will be able to take over: you stay free to change provider without starting from scratch.

Ready for [The client’s deadline]Ready for your busiest season

[The client’s schedule: the start date, its deadline, the number of weeks between the two, and what happens after go-live]

We start as soon as you agree, to put the portal into service a few weeks before your busiest season, with room for acceptance testing; improvements follow after go-live.

Task board on a brick wall with sticky notes arranged in progress columns

The milestones.

  • End of scoping: prototype tested; scope, architecture and acceptance criteria signed.
  • End of the first version: the priority journeys demonstrated, cycle after cycle.
  • End of the integrations: the tool connected to your systems.
  • End of acceptance: report signed.
  • [The go-live date]A few weeks before your season: [What the client will have that day, then the warranty]the portal in service, then the warranty.

Your involvement.

  • A product owner on your side, [Time per week]: they set the priorities and approve at every demo.A product owner on your side, a few hours a week: they set the priorities and approve at every demo.
  • Your users to test the prototype, then your key users for acceptance.
  • Every approval has its date: if an approval or a piece of content arrives after the planned date, go-live moves back by the same amount, and we tell you the same day.
  • What the client must provide: [What the client must provide that is specific to its project: content, data, accounts, and by what date]What the client must provide: your catalog, your prices and access to your stock management, from the start.

Watch point: [The client’s tightest schedule constraint, and how you hold it]

Watch point: your season is a fixed date: we place acceptance early and keep a margin, so that a late approval does not make you miss it.

Your team

A dedicated team of [Number] people follows your project from start to finish. [The owner or partner who stands behind the project before your management]

A dedicated team of a few people follows your project from start to finish. The head of Example Agency stands behind the project before your management, from the first workshop to go-live.

Two developers seen from behind in front of a large screen showing code in an office
  • [First name Last name]Sonia

    Project manager, your main contact

    Runs the schedule, leads the demos and acceptance. [Their experience]Runs the schedule, leads the demos and acceptance. Has led ordering portals for distributors.

  • [First name Last name]Elodie

    UX and design lead

    Leads the workshops, draws the screens and has them tested. [Their references]Leads the workshops, draws the screens and has them tested. Has designed business tools for field teams.

  • [First name Last name]Bastien

    Technical lead

    Builds the tool and its integrations. [Their specialty]Builds the tool and its integrations. Specialist in connecting to management software.

Our commitments.

  • A shared dashboard from day one: progress and budget used, visible to you at any time.
  • A demo at the end of each cycle, and a written summary within [Delay].A demo at the end of each cycle, and a written summary within one working day.
  • An answer within [Delay] to every question, through a direct channel with the team.An answer within one working day to every question, through a direct channel with the team.

A project like yours

Since [Year], we have built [The type of tools you build]: [Number and nature of your projects] to date.

[Why these two cases resemble the client’s project]

Since our beginnings, we have built business tools, ordering portals and field apps for small and mid-sized companies.

These two cases resemble your project: business customers who order by phone and by email, a tool to connect to the existing system, a season not to be missed.

  1. [A client close in size or in the tool, described without naming it]A farm equipment distributor

    [Its situation and its problem]Its customers ordered by phone and by email, and each order was re-entered

    [What you built, in how long]We ran a scoping workshop, then built an ordering portal connected to its management system, in a few months

    [The result with figures, with its period]A growing share of orders placed online over the first months.. [What made it work]Customers involved from the workshop.

  2. [A client close in challenge, described without naming it]A network of training centers

    [Its situation and its problem]Paper attendance sheets re-entered by assistants, and certificates issued late

    [What you built, in how long]We built a tracking app that works offline and its back office, connected to the management system, in a few months

    [The result with figures, with its period]Certificates issued faster, by trainers who use it every day.. [What made it work]The trainers tested the screens before the code.

[What the client of the first case says about it, word for word]

Our trainers saw the screens before the first development. On go-live day, they already knew how to use it.

[First name, last name, title, company]Sandra, operations director, network of training centers (fictional case)

Your investment

A fixed price, by package. Each package is invoiced when you approve it, on a signed report. After go-live, hosting and maintenance are priced separately, with their commitment period.

[The total set against the client’s budget, what stays outside the price, and why this split into packages suits it]

A fixed price, by package. Each package is invoiced when you approve it, on a signed report. After go-live, hosting and maintenance are priced separately, with their commitment period.

The total stays within the budget you indicated, hosting and maintenance stay outside the price, and the split into packages suits you because you commit to scoping before settling the build budget.

[Title of the project]A portal where your customers order without calling

Package 1

  • Scoping and prototype

    Workshops, mockups, tested prototype, backlog, architecture, acceptance criteria

    [Duration]a few weeks

    [Price of package 1, excl. VAT][Price of package 1, excl. VAT]

Package 2

  • First version

    The priority journeys, demonstrated at every cycle

    [Duration]a few months

    [Price of package 2, excl. VAT][Price of package 2, excl. VAT]

Package 3

  • Integrations and follow-on

    Connections to your systems, back office, tracking

    [Duration]a few weeks

    [Price of package 3, excl. VAT][Price of package 3, excl. VAT]

Package 4

  • Acceptance and go-live

    Acceptance on written criteria, putting into service, training

    [Duration]a few weeks

    [Price of package 4, excl. VAT][Price of package 4, excl. VAT]

Options, outside the total

  • Hosting and maintenance

    Hosting, backups, monitoring, updates and fixes, with [commitment period]Hosting, backups, monitoring, updates and fixes, with a commitment period to set together

    Option

    [Price of the option][Price of the option]

  • Credit for changes

    [Number] days to use within the year, after go-liveSome days to use within the year, after go-live

    Option

    [Price of the option][Price of the option]

Total excl. VAT[Total excl. VAT][Total excl. VAT]

VAT[rate][rate]

Total incl. VAT[Total incl. VAT][Total incl. VAT]

Options available, outside the total[Combined amount of the options][Combined amount of the options]

  • Invoicing: [Your payment schedule: each package invoiced when approved on a signed report, and your payment term]each package is invoiced when approved on a signed report, with payment within [payment term].
  • Changes: on a constant budget, a new feature replaces another of the same weight, at the start of a cycle, with no change order. Beyond that, it is priced within [Delay], and nothing is committed without your written agreement.on a constant budget, a new feature replaces another of the same weight, at the start of a cycle, with no change order. Beyond that, it is priced within [pricing delay], and nothing is committed without your written agreement.
  • Ownership: [What becomes the client’s property, and when: specific code, mockups, accounts, documentation; each assigned right mentioned separately, with its extent, its purpose, its territory and its duration]the specific code and the mockups become your property with each package payment; each assigned right is mentioned separately, with its extent, its purpose, its territory and its duration; the documentation and your accounts are handed over.
  • Validity: [Validity period of the offer] from the date it is sent.offer valid for a few weeks from the date it is sent.

Your questions

What you asked us.

[A fear the client voiced, written as their question]Can the budget run away?
[Your answer in two sentences, with proof]Each package is a fixed price, signed before the start. A new request replaces a feature of the same weight or is priced before any commitment.
[A second fear, written as their question]Will my tradesperson customers really use it?
[Your answer, with proof]They test the prototype before the code, and their feedback changes the screens. The portal is designed for a phone, between two jobs.
[A third fear, written as their question]What happens if we change provider?
[Your answer, with proof]Your code lives in a repository in your name from day one, with its documentation and a planned handover. You do not start from scratch.
[A fourth question from the client]Who looks after the tool after go-live?
[Your answer, with proof]The same team, under the maintenance plan: hosting, backups, updates and fixes, with a fast response in the middle of the season.

[Your agency]Example Agency

[Your agency] is [what it is, where, since when]. [Your team: who works there and how]

Our conviction: [What sets you apart from other web and development agencies]

Example Agency is an independent web and mobile development agency. Designers, developers, testers and project managers work in one team, from the first workshop to maintenance.

Our conviction: before coding, we check that off-the-shelf software is not enough, and we tell you when it is.

  • [Your years in business][Years in business, to be filled in by the agency]
  • [The size of your team][Team size, to be filled in by the agency]
  • [Your references, verifiable][Verifiable references, to be filled in by the agency]

Start [The client’s start]Start at the beginning of next month

  1. [The date the client decides]at the next management meeting

    Decision

    [Who decides, and in which body]The owner decides, with the sales director.

  2. [The planned signature date, or “Right after”]right after

    Signature

    You accept the proposal online; we reserve the team.

  3. [Its date]the week of the start

    First workshop

    A meeting with your product owner and your users: the project starts with them.

  4. [Its planned date]a few weeks before your season

    Go-live

    Your tool in service, then the warranty.

[First name Last name, title · email address · phone number]

Thomas, owner · thomas@example-agency.example · [phone number]

This template, filled in for your next project.

Paste the brief or the workshop notes: Cuevr AI writes the zones from what you know about the client, a complete proposal in under 15 minutes instead of 2 hours.

Use Cuevr

14 days · 5 proposals · no credit card

Five ways to lose a web project.

The client reads your proposal before meeting your team, and compares it with other agencies on the same brief. Here is what loses it, or what makes the project cost more later.

  • A vague scope

    “everything is included” does not say what is. Write what goes into the first version, what comes next and what is left out, before pricing: that is what prevents change orders.

  • Approvals with no date

    The project waits for the client, and the schedule slips. Give each approval its date and say what moves if it arrives late.

  • Content and accounts that arrive late

    Text, data, accounts and access are usually with the client. List what it must provide and by when, in the schedule itself.

  • A single-block quote

    The client can neither adjust it nor commit to a first stage on its own. Split it into packages, with a fixed price for each, and put maintenance and changes in options.

  • Maintenance and code ownership left aside

    The client wonders who will look after the tool after delivery, and who owns the code and the accounts. Answer before it asks.

From this template to your proposal, in three steps.

  1. Start from a template

    Save your best proposal as a template (“Save as template”), keep your build stages and your terms fixed, and place variable zones in the sections that change from one client to the next. When starting a proposal, choose “From a template”.

  2. Cuevr AI fills the zones

    Load the brief or the meeting notes into the qualification; Cuevr sorts everything into four sections and writes each section from your knowledge base and the qualification, in your agency’s brand. You review and edit everything by hand: you check the client, the figures and the commitments.

  3. Share and track reading

    Click “Share”, then “Publish now”, and send the client link. You see who opened the proposal, for how long, and which sections, through to the online signature.

Questions about this template.

What should a web agency proposal contain?

The client’s situation, its stakes, your response with a written scope, scoping, the build in stages, go-live and maintenance, a schedule built around its deadline, the team, cases close to its project, the investment in packages and the next steps. The template above follows that order: the client first, the agency last.

Fixed price, packages or time and materials: how do you present the price of a web project?

A fixed price per package gives the client a commitment it understands, package by package, and lets it commit to scoping before settling the build budget. Time and materials remains a choice when the scope cannot be fixed in advance; in that case, cap it or split it into packages. The template presents four packages and options outside the total.

How do you stop the scope drifting into change orders?

By writing it before the price: what is in the first version, what comes next, what is left out. Then by setting the rule for changes in the proposal: on a constant budget, a new feature replaces another of the same weight; beyond that, it is priced before any commitment.

Who owns the code and the accounts?

Write it before signing: what becomes the client’s property, and when (for example at each package payment), with each assigned right mentioned separately and delimited by its extent, its purpose, its territory and its duration. Also plan for handing over the documentation and the accounts, and have your lawyer review the clause; the template does not set it for you.

Word, Google Docs or PDF?

This template is read here, in full, with no file and no form. To write it by hand, copy the text from the page into Word, Google Docs or the editor you prefer. In Cuevr, the proposal is built in your brand in the editor, then exported to Word (which also opens in Google Docs) or PDF; the client reads it online and signs it.

Is this template free?

Reading is free, with no account. To fill it in with Cuevr, the trial is free: 14 days, 5 proposals, no credit card.

Other industries, other templates.

  • Marketing agency

    Proposal for support from [Your agency]

    The same buyer compares agencies: services in packages and options.

    Services, packages and options13 sections

  • Consulting firm

    Proposal for an engagement by [Your firm]

    Another form: a mission in phases and fees by phase.

    Engagement in phases12 sections

  • SEO agency

    SEO support proposal from [Your agency]

    Services you follow month after month.

    Subscription13 sections

  • IT services and IT consulting

    Fixed-price project proposal from [Your IT services company]

    A fixed-price or time-and-materials project, for a management committee.

    Fixed-price projectTime and materials14 sections

All templates by industry

Your next project deserves this template.

Try Cuevr on a real project: the template, the zones, your agency’s brand and reading tracking.

Use CuevrSee a demo

14 days · 5 proposals · no credit card

Book your demo

Your details first, then the time that suits you.

Step 1 of 2 · no commitment

Why do so many deals fail?

Video hosted by YouTube

The closing problem

Video hosted by YouTube

Why your proposal matters

Video hosted by YouTube