Features Tell, Outcomes Sell: How to Rewrite Your Offer So Price Stops Being the Question

A designer I worked with once sent me a proposal to look over before it went out. It was clean. Well organized. Every phase laid out, every deliverable accounted for.

It also read like a parts list.

“Phase 1: Discovery and site measure. Phase 2: Concept development, two directions. Phase 3: Furniture and finish selection. Phase 4: Procurement and install oversight.”

I asked her one question. “If you handed this to three clients and changed nothing but the price at the bottom, would any of them be able to tell you apart from the other two designers they’re talking to?”

She knew the answer. The proposal described what she would do. It said almost nothing about what the client would get.

That gap is where price takes over. When a client can’t see the value, the number is the only thing left to judge.

Why your proposal reads as a price menu

Here is the uncomfortable mechanic. A proposal is a comparison document. The client is almost always looking at more than one. So they read yours the way they read a menu: scanning for what’s included, then checking the price against it.

If your proposal is a list of tasks, you’ve handed them a menu. And on a menu, the only interesting variable is cost. You’ve trained the client to shop you on price without meaning to.

A list of deliverables answers “what will you do.” It never answers “why does that matter to me.” The second question is the one that closes.

This is not a discounting problem. It’s a language problem. And language is the part you actually control.

It helps to remember what the client is doing while they read. They are not evaluating your taste. They already saw the portfolio, and the portfolio is why you’re in the running. By the time the proposal lands, they’re trying to justify a decision they half want to make. Feature lists give them nothing to justify with except the price. Outcome lines hand them the reason they were looking for.

The fix isn’t to add more deliverables or drop your rate. It’s to translate every line from what you do into what changes because you did it.

Features describe your process. Outcomes describe their life after.

A feature is a fact about your work. A mood board. Three concept directions. A furniture plan. A site measure. These are real and they matter, but they’re about you. They describe your process.

An outcome is what’s different in the client’s world once the feature exists. A home that finally fits a family of five. A living room they stop apologizing for. A kitchen that holds up to four kids and a Tuesday-night dinner party.

The feature is the cause. The outcome is the effect the client actually wanted when they reached out.

Clients don’t lie awake wanting a furniture plan. They lie awake because the room doesn’t work, because they’re embarrassed when people come over, because they’ve rearranged the same space four times and it still feels wrong. The furniture plan is your answer. The fixed room is their reason.

When your proposal names the reason, the client sees themselves in it. When it only names the answer, they’re left translating, and most won’t bother. They’ll just look at the price.

The before/after rewrite

Here’s what the shift looks like in practice. Five lines, written first the way most proposals say them, then rewritten as the outcome underneath. These are illustrative, not pulled from a specific client. The pattern is what matters.

Feature: “Custom furniture plan and space layout.” Outcome: “A layout that fits the way you actually live, so you stop shuffling the same pieces around every few months hoping it’ll click.”

Feature: “Two concept directions to choose from.” Outcome: “Two complete visions of your space, so you make one confident decision instead of second-guessing a hundred small ones for the next year.”

Feature: “Full finish and material selection.” Outcome: “Every finish chosen to work together and hold up to your real life, so you’re not staring at a paint chip at 11pm wondering if it’ll clash with the floor.”

Feature: “Procurement and vendor management.” Outcome: “We handle the ordering, the tracking, and the back-and-forth with vendors, so the project doesn’t quietly become your second job.”

Feature: “Install day oversight.” Outcome: “We’re there when it all comes together, so the day you’ve been waiting for feels like a reveal, not a stress test.”

Notice what didn’t change. The work is the same. The deliverables are the same. You are not promising more or charging differently. You’re describing the same offer in the client’s terms instead of yours.

That’s the whole move. The value was always there. You just stopped hiding it behind the process.

The one question to ask of every line you write

When you’re not sure whether a line is a feature or an outcome, use this test. It’s the same one a good coach uses on any piece of writing: would the client just nod, or would they see it happening?

If you write “we deliver thoughtful, high-quality design,” the client nods. It’s agreeable. It’s also invisible. Every designer says it, so it communicates nothing.

If you write “we design the entryway so the first thing your guests feel is that they’re somewhere, not just inside,” the client can see it. They can picture the door, the light, the moment someone walks in.

If you have to agree with it, it’s weak. If you can see it happening, it’s strong.

Run every line through that filter. Agreeable lines describe a category. Visible lines describe a result. Cut or rewrite anything the client would simply nod along to. This is the same specificity that keeps a studio from sounding like every other studio, applied to the one document where vagueness costs you money directly.

When outcomes go too far

There’s a failure mode on the other side, and it’s worth naming so you don’t trade one problem for a worse one.

Outcome language can tip into overpromising. The moment you write something you can’t actually deliver, you’ve moved from positioning to selling something untrue, and clients can smell it.

Be careful with outcomes you don’t control. You don’t control your client’s resale value. You don’t control whether their in-laws approve of the sofa. You can’t promise a timeline that depends on a backordered vendor. Claims like those read as either naive or dishonest, and both cost trust.

The honest version stays inside what you actually do. “A layout that fits the way you live” is a promise you can keep, because the layout is yours to design. “A home that doubles in value” is not, because the market is not yours to design.

The line to hold: describe the change you create, not the outcome the world might add on top of it. Specific and true beats impressive and shaky. A client who believes one real promise will pay more than a client who half-believes three big ones.

How BVE rewrites features as outcomes in your voice

The reason most designers default to feature language isn’t that they don’t know better. It’s that features are easier to write. They’re already in your head. You know what you do. Translating each one into the client’s life takes a second pass that’s slow when you’re staring at a blank proposal at the end of a long day.

That second pass is exactly what Brand Voice Engine is built to do. You give it your deliverables, the work you already know how to describe. It rewrites each one as the outcome a client actually wants, in your studio’s voice, not generic agency copy. It holds the line on honesty too, so the rewrites stay inside what you can deliver instead of drifting into overpromise.

The compounding part is that you only have to do it once. The outcome language you build for a proposal is the same language that belongs on your services page, in your discovery-call follow-ups, in the email you send when a lead goes quiet. Get the translation right in one place and it travels. The studio that has done this work sounds the same whether a client meets it on the website or across a kitchen table, and that consistency is its own kind of proof.

It’s the same logic that keeps your brand voice consistent across every channel, pointed at the one document where the words decide whether price is the conversation or just a footnote to it.

Your work is already worth the number on the proposal. The only question is whether the language lets the client see it before they get there.

BVE turns your deliverables into outcomes that sell, in your studio’s voice. Start writing for free →