Anatomy of a Website Proposal: Pricing Against Outcomes

The Flaw of the Line-Item Proposal

Every week, talented designers and developers put together proposals that are dead on arrival. The document is long and thorough: your process, your background, how you work. And at the end, the part that matters:

┌─────────────────────────────────────────────────────────────────────────────┐
│                           THE LINE-ITEM PROPOSAL                            │
│  Discovery and user research                                                │
│  Wireframes and page layout                                                 │
│  Visual design                                                              │
│  Build                                                                      │
│  Testing and fixes                                                          │
├─────────────────────────────────────────────────────────────────────────────┤
│  TOTAL: a number the client can take apart                                  │
│  And nobody can tell what any of it is worth.                               │
└─────────────────────────────────────────────────────────────────────────────┘

You think this demonstrates rigour. In practice, it is a tactical surrender.

The moment a client sees hours and rates, their training compels them to take your proposal apart:

• “Why does discovery need that many hours? Cut it in half.”
• “Can our nephew do the testing to save money?”
• “We found someone cheaper for the build.”

You have handed them a spreadsheet. Their only remaining move is to subtract.

1. From Costs to Outcomes

A proposal that sells hours sells a commodity. A proposal that sells the result sells a decision.

┌──────────────────────────────────────┬───────────────────────────────────────┐
│                  TWO CONVERSATIONS, TWO DIFFERENT OUTCOMES                   │
├──────────────────────────────────────┼───────────────────────────────────────┤
│ WHAT THE PROPOSAL TALKS ABOUT        │ WHAT THE CLIENT IS BUYING             │
├──────────────────────────────────────┼───────────────────────────────────────┤
│ Hours, tasks, line items             │ A business outcome they can point at  │
│ A rate card                          │ One number, and a reason for it       │
│ Your process                         │ Their problem, solved                 │
│ What it will cost them               │ What it will earn them back           │
└──────────────────────────────────────┴───────────────────────────────────────┘

The change is not about inflating your price. It is about changing what the price is compared against.

When a client is choosing between three quotes, they are not really comparing your total against the other two totals. They are comparing what they expect to get back against what they expect to pay. If a proposal leaves the first side blank, there is nothing to weigh, and the cheapest number wins by default.

So build that side, using the client’s numbers rather than yours: the enquiry volume, the margin, the cost of a paid advert.

2. The Four Parts of a Proposal That Sells

Part 1: The Diagnosis (The Mirror)

Open with an honest teardown of what the site does now and what it costs the business. Use their figures where you can: how many enquiries a month, what a new customer is worth, what a paid advert costs per enquiry, how many calls go unanswered.

When the client reads it, they should think: “They understand our business better than the last three who quoted.”

Part 2: The Future State

Do not list generic deliverables like “a modern website”. Describe what changes for the visitor, in terms they can picture.

┌──────────────────────────────────────┬───────────────────────────────────────┐
│                    THE DIAGNOSIS, THEN THE FUTURE STATE                      │
├──────────────────────────────────────┼───────────────────────────────────────┤
│ WHAT THE SITE DOES NOW               │ WHAT IT DOES AFTER                    │
├──────────────────────────────────────┼───────────────────────────────────────┤
│ A visitor cannot tell what you       │ The offer, the price range and the    │
│ do in the first five seconds         │ next step are visible before          │
│                                      │ they scroll                           │
│ Enquiries arrive through a form      │ The enquiry path works on a phone     │
│ that sometimes fails                 │ and the message reaches you           │
│ Search sends people to pages         │ Each page answers one real question   │
│ never written for them               │ someone is typing                     │
│ You find out about a broken page     │ You find out the same day, and fix    │
│ when a customer complains            │ it before anyone notices              │
└──────────────────────────────────────┴───────────────────────────────────────┘

Part 3: The Return

Model the return in the client’s own currency. Take the things the project replaces, and price each one.

┌──────────────────────────────────────┬───────────────────────────────────────┐
│                    THE RETURN, BUILT FROM THEIR NUMBERS                      │
├──────────────────────────────────────┼───────────────────────────────────────┤
│ WHAT THE PROJECT REPLACES            │ WHAT IT IS WORTH TO THEM              │
├──────────────────────────────────────┼───────────────────────────────────────┤
│ A subscription to a tool nobody      │ What that money costs per year        │
│ uses and still pays for              │                                       │
│ The time a new enquiry waits         │ What one enquiry is worth when        │
│ for an answer                        │ it arrives late                       │
│ A paid advert that brings in         │ What the wrong enquiry costs in       │
│ the wrong people                     │ hours and goodwill                    │
│ An hour a day answering the          │ What an hour a day costs, for a       │
│ same question                        │ year, in wages                        │
└──────────────────────────────────────┴───────────────────────────────────────┘

Then set your fee against that. If the project costs the client less than the thing it replaces in its first year, the price stops being the point. Keep the arithmetic easy to check: a client who can verify your numbers trusts the number you are asking for.

Part 4: Three Options, Not One Price

Never present a single take-it-or-leave-it figure. It creates a binary question the client can only answer yes or no. Present three options, with the middle one being the scope you actually recommend:

┌──────────────────────┬───────────────────────────────────────┬────────────────┐
│                       THREE OPTIONS, ONE RECOMMENDED                          │
├──────────────────────┼───────────────────────────────────────┼────────────────┤
│ OPTION               │ SCOPE                                 │ PRICE          │
├──────────────────────┼───────────────────────────────────────┼────────────────┤
│ Option 1             │ A clear site that works on a phone,   │ Lowest         │
│ The basics done right│ a contact path that works, and the    │ option         │
│                      │ messy parts cleaned up                │                │
│ Option 2             │ Everything in option 1, plus the pages│ Middle         │
│ The recommended scope│ that earn money, the fixes to search  │ option         │
│                      │ visibility, and a plan for what       │                │
│                      │ comes next                            │                │
│ Option 3             │ Everything in option 2, plus new      │ Highest        │
│ The full rebuild     │ structure, new content, connections to│ option         │
│                      │ the tools you already run, and        │                │
│                      │ support after launch                  │                │
└──────────────────────┴───────────────────────────────────────┴────────────────┘

The conversation in the client’s head shifts from “Should we hire Aura Logic?” to “Which of these should we do?” — and the middle option, which you have quietly made the sensible one, is where most projects land.

Conclusion: Charge for the Value, Not the Sweat

Your worth is not determined by how many hours you spend or how hard you work. It is determined by the value you unlock and the cost of the problem you remove.

Throw away the hourly spreadsheets. Stop letting a client audit your labour. Anchor the work in what the client gains and structure the proposal so the choice is between good options rather than one number that is either too much or too little.

When you price the outcome, the hours stop being the argument.