Why My Long Proposals Closed Slower
For a while I believed a thorough proposal signaled a thorough professional. So my AI project proposals ran long - background, methodology, a technical approach section, phases, contingencies. They looked impressive. They also closed slower than the quick one-pagers I sometimes threw together when I was short on time. That pattern nagged at me until I finally admitted what was happening: the long proposals gave the client more places to hesitate.
Every extra section was another thing to question, another paragraph where the client's eyes glazed, another opening for 'let me think about it.' A long proposal doesn't read as thorough to a busy client. It reads as work - work to get through, and work to figure out what they're actually saying yes to. The one-pager wins because it removes that work. There's nothing to wade through and nowhere to get lost.
The Five Things That Go on the Page
A closing one-pager is not a shrunken long proposal. It's a different document with a specific job: confirm what you both already agreed to and make saying yes the easy next move. Five parts, in this order.
- The outcome, in their words. Open with the result they told you they want, phrased the way they phrased it. Not 'build an AI pipeline' but 'cut the time your team spends sorting inbound emails from hours to minutes.' They should read the first line and think, yes, that's the thing.
- What's included - and what's not. A short, concrete list of what they get, plus a line or two of what's explicitly out of scope. The exclusions protect you and, counterintuitively, build trust: it shows you've thought about the edges.
- The price. One number, stated plainly, tied to the outcome rather than hours. No menu, no tiers unless they asked. A single price is a single decision.
- The timeline. When it starts, when they see the result. Simple and realistic. Vague timelines read as risk.
- One next step. Exactly one action to move forward - reply to approve, sign here, book the kickoff. Never a fork with three options. One door.
What Stays Off the Page
The discipline of the one-pager is mostly about what you leave out. Everything that serves you rather than the client's decision comes off.
- The technical approach. The client is buying the outcome, not your architecture. How you'll build it is your business - keep it off the page unless they specifically asked.
- Your company background and credentials. If they're reading your proposal, you already earned the meeting. Re-selling yourself here just adds length.
- Contingencies and caveats beyond the scope line. A wall of what-ifs reads as nervousness. State the scope cleanly and handle edge cases in conversation.
- Options and tiers they didn't request. Every extra choice is a delay. If they need to choose, that's a conversation, not three columns on a page.
The Proposal Comes After the Conversation
A one-pager only closes because of the work that happens before it. The page is not where you discover what the client needs - it's where you confirm it. That understanding comes from the discovery call, where you get them to describe the outcome, the constraints, and what a win looks like in their own words. If you've written about running a proper discovery call, this is the artifact that call produces.
This is why the one-pager can be short. You're not using the document to figure anything out or to cover for a conversation you didn't have. You already know what they want because you asked. The page just hands it back to them, cleanly, with a price and a next step. Skip the call and no proposal length will save you - you'll be guessing on paper. Have the call and one page is plenty.
A Quick Before-and-After
The same deal, two ways to propose it
| Long proposal | One-page proposal |
|---|---|
| Opens with your company background | Opens with the client's desired outcome in their words |
| A methodology section explaining the build | A short list of what's included and what's not |
| A price buried on page four with three tiers | One price, stated plainly, tied to the outcome |
| Ends with 'let us know if you have questions' | Ends with one clear next step to approve |
The right column isn't less professional. It's more confident. It says: I understood you, here's the result, here's what it costs, here's how we start. That confidence is what closes.
Build Your Own One-Pager This Week
Take your next opportunity and force it onto one page. Write the outcome in their words at the top, list what's in and out, state one price, give a timeline, and end with a single next step. If something doesn't fit, ask whether it's helping the client decide or just making you feel thorough. The page gets shorter and the yes gets faster.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
Why does a one-page proposal close AI projects faster than a long one?
Because a long proposal gives the client more places to hesitate. Every extra section is another thing to question and another opening for 'let me think about it.' A one-pager removes that work - there's nothing to wade through and nowhere to get lost. It reads as confidence rather than nervousness: you understood them, here's the result, here's the price, here's how you start.
What goes on a one-page AI proposal?
Five things, in order: the outcome in the client's own words, a short list of what's included and what's explicitly not, one price tied to the outcome rather than hours, a simple realistic timeline, and exactly one clear next step. Everything that serves you rather than the client's decision - technical approach, company background, extra tiers - stays off the page.
Should I include my technical approach in the proposal?
No, unless the client specifically asked. They're buying the outcome, not your architecture. A detailed methodology section is where more deals stall than close, because it invites the client to evaluate decisions they're not equipped to judge. Keep how you'll build it off the page and handle any technical questions in conversation.
Does the one-page proposal replace a discovery call?
No. The proposal is the artifact you write after the discovery call, not a replacement for it. The call is where you learn the outcome, constraints, and what a win looks like in the client's own words. The page just confirms that understanding with a price and a next step. Skip the call and no proposal length saves you - you'll be guessing on paper.
How do I price on a one-pager?
State one number plainly, tied to the outcome rather than to hours, with no menu or tiers unless the client asked for options. A single price is a single decision. If the client genuinely needs to choose between scopes, that's a conversation, not three columns on the page - keep the page to one clear thing to say yes to.
Last reviewed by Duncan Rogoff on July 28, 2026
