Write proposals that decide, not dazzle

A proposal is where most of the trust in a project is won or lost, and most of them are built to do the wrong job. They are designed to impress. Glossy mockups, a page about the team’s passion, a vision section, and the price tucked at the very end behind a “let’s hop on a call.” That is a sales brochure pretending to be a decision. The owner reading it does not need to be dazzled. They need to decide, and they are busy. So we build the proposal to do that one job. After we audit before you build, the proposal is where the plan becomes a yes or a no.

The job of a proposal

A small business owner reading a proposal is not shopping for inspiration. They are trying to answer a few hard questions quickly, between everything else they have to do that day. What exactly will I get? What will it cost? When will it be done? What happens if it goes wrong? Can I trust these people with money and time I cannot easily get back?

A good proposal answers those questions so plainly that the owner can decide without a follow up call. That is the bar. If they have to schedule a meeting just to find out the price, the document failed at its only job. Our proposals are written so that a confident yes or a clear no is possible from reading alone. The call, if there is one, is for nuance, not for facts that should have been on the page.

Helping someone decide is not the same as pushing them to buy. A proposal that helps will sometimes lead to a no, and that is fine. A no that comes fast and clear is better for everyone than a yes that came from confusion and falls apart in month two.

What ours always contains

Every proposal we send has the same backbone, because the owner deserves the same answers every time.

The one number. We open by stating the goal the site exists to serve, the number we agreed on at the start. This site is being built to get more calls, or more bookings, or more qualified inquiries. Naming it up top tells the owner we understood the point, and it frames every line that follows.

The scope, in and out. We list what is included, plainly, and just as importantly what is not. The pages, the features, the integrations we will build, and the things people often assume are included but are not. Saying what is out of scope is not a trick to upsell later. It is how we prevent the slow, resentful drift where the owner expected something we never agreed to.

A fixed price. One number, stated clearly, for the work described. No “starting at,” no ranges that quietly climb, no surprise line items at the end. If something would change the price, we say what and by how much.

A timeline. Real dates or real ranges, with the few things we need from the owner to hit them. Most delays come from waiting on content or feedback, so we name those upfront and make the owner a partner in the schedule, not a bystander.

Guarantees. What we stand behind, in plain language. What we will fix without argument, and how to reach us if something breaks.

What happens after launch. The site going live is not the end. We say what support looks like, who owns what, and how changes work once it is built. An owner should never wonder whether they will be stranded the day after launch.

Why we lead with price and process

We put the price and the process near the front, not the back, and we do it on purpose.

Burying the price is a tell. It says the seller is worried the number will scare you off before the pitch can win you over. That is a manipulation, even a polite one, and owners feel it even when they cannot name it. Leading with the price says the opposite. Here is the cost, here is exactly what it buys, decide if it is worth it. That honesty does more for trust than any amount of polish.

Process matters for the same reason. An owner who has been burned before is not afraid of the work, they are afraid of the chaos. Showing the steps, the timeline, and what we need from them turns an unknown into something they can picture. People say yes to things they can picture.

What we leave out

A proposal gets stronger as you remove things, not as you add them.

We leave out filler. The long mission statement, the page about our values, the stock language every agency uses. None of it helps the owner decide, and all of it makes the real answers harder to find.

We leave out jargon. If a word would make the owner feel they need to nod along without understanding, we cut it or we explain it. The proposal should read like a clear person talking, not a contract written to protect us from them.

We leave out fake urgency. No countdown, no “this price expires Friday,” no manufactured scarcity. Pressure tactics insult the reader and poison the start of a relationship that is supposed to last past launch. If the work is worth it, it is worth it next week too.

What is left is short, honest, and easy to act on. The owner can read it, understand it, and decide. That is a proposal that respects the person reading it, and respect is what gets the yes that actually holds.

Once the yes is in hand, the question becomes how to deliver it without the project sprawling into a six month slog, which is why we scope to a month of momentum.