Why I Stopped Sending Detailed Project Proposals and Started Sending One-Page Briefs

Last quarter I stopped sending the kind of fifteen-page Webflow project proposals I had been writing for two years. The trigger was a conversation with a founder who asked me to skip the proposal and just send him a single page. The result was that he signed faster than any client who got the long version. I ran the experiment with the next four proposals and the pattern held. This is the field note about what changed and why I think the one-page brief beats the detailed proposal for the kind of mid-market work I do.

What Did the Old Detailed Proposal Actually Contain?

The detailed proposal ran fifteen to twenty pages and included a project summary, technical scope across CMS architecture and design system, a phase-by-phase timeline, deliverables list, pricing breakdown, terms and conditions, and a multi-page appendix with case studies and process documentation. Each section had been refined over dozens of proposals. The document looked thorough and professional, which felt like the right signal to send to mid-market clients.

The structural problem was that the document was optimized for the Partner's confidence rather than the client's decision. Fifteen pages of dense content forced the client to read a lot before making a yes-or-no call, which extended the decision timeline and gave more surface area for second-guessing. The proposal looked thorough but functioned as friction. The realization that thoroughness and conversion were trading against each other took longer to internalize than I would have liked.

What Does the One-Page Brief Actually Look Like?

The one-page brief contains six elements. A two-sentence problem statement that names what the client is solving for. Three to five concrete deliverables that describe what the engagement produces. A timeline as a single date range with key milestones inline. A flat price with payment terms in one line. A short paragraph naming what success looks like in the client's terms. And a clear next step (sign or schedule a call) at the bottom. The whole document fits on one page in standard formatting.

The discipline is in what gets cut. The case studies, the process methodology, the technical architecture details, the team biographies, and the boilerplate terms all come out. The brief assumes the client either trusts you enough to engage or does not, and additional documentation rarely tips that decision. Removing the documentation forces the brief to be sharp about scope and price, which is what actually drives the decision. The brief looks slight on paper. It performs better in practice.

Why Did Removing Detail Improve Conversion?

Three reasons. The shorter document gets read in one sitting, which keeps the decision momentum intact. The forced clarity on scope and price removes the ambiguity that long proposals often contain. And the implicit confidence of sending a brief one-pager signals that the Partner does not need to over-justify the engagement, which is the exact signal mid-market clients respond to from senior practitioners.

The third signal matters more than the first two. Long proposals communicate hesitancy, even when the content is strong. Short briefs communicate that the Partner has done this work many times and knows what the engagement contains. The signal is subtle but real, and it shifts how clients perceive the practice's credibility. The shift is most pronounced with founders and senior marketing leaders who pattern-match on what experienced operators do, and short documents are what experienced operators send. I covered the broader practice positioning in what surprised me about charging a flat monthly retainer.

What Happens to All the Detail That Used to Live in the Long Proposal?

It moves out of the proposal and into other artifacts. The technical scope lives in a project plan that is shared after the engagement begins. The case studies live on the website and get linked when relevant. The process methodology lives in client onboarding documentation. The boilerplate terms live in a master services agreement that is signed once and referenced from every subsequent engagement. The detail does not disappear. It is delivered at the right moment in the engagement rather than upfront.

The reorganization actually produces a better client experience because each detail arrives when the client needs it. Sending all the detail upfront forces the client to read information they do not yet care about, which is friction. Sending the detail when the corresponding decision arrives keeps the client engaged because each new artifact maps to a current question they have. The pattern is calmer for the client and more efficient for the Partner. The reorganization is the actual win.

How Do You Handle Clients Who Ask for More Detail Before Signing?

Some clients do ask, and the right answer depends on what they are actually asking for. Often the request for more detail is really a request for one or two specific clarifications, and answering those clarifications inline is more useful than producing a long document that addresses the questions they did not ask. The diagnostic is to ask what specifically they want to know more about, then answer that.

Occasionally a client will insist on a fully detailed proposal as their internal procurement requirement. For these cases, I produce the detailed version as a follow-up document on request. The default is the one-page brief, but the detailed version exists when genuinely needed. The split keeps the brief lean for the majority of conversations while accommodating the minority who require formal procurement processes. Both versions serve their respective contexts. Neither is universally correct.

What Did the Conversion Rate Actually Change To?

The detailed proposal produced about a 20 percent conversion rate from sent proposal to signed engagement, which was respectable for the price point. The one-page brief produced about a 35 percent conversion rate over the same period and led to faster decision timelines. The sample size is small (roughly two dozen proposals across both formats), but the directional improvement was consistent enough that I switched the default and have not gone back.

The honest caveat is that conversion rate is a single metric and not the only one that matters. The brief does not work as well for very large engagements where formal procurement is required, and it does not handle multi-stakeholder decisions where each reviewer has different concerns. For the bread-and-butter mid-market engagements that make up most of my practice, the brief outperforms cleanly. For genuine enterprise scale, the detailed version is still the right tool. The judgment is about matching the document to the situation.

How Did Pricing Conversations Change After Switching to the Brief?

The brief forced more honest pricing because there was less room to bury caveats and exclusions in dense text. The price has to stand alone on the page, which means the price has to be defensible in a sentence. The discipline produced cleaner pricing across the board, with fewer hidden costs and clearer scope boundaries. Clients responded well to the simplicity.

The second-order effect was that ambiguous pricing situations got resolved upfront rather than later. The detailed proposal had been a place where I would sometimes paper over scope ambiguities with vague language, hoping to negotiate them in execution. The brief format forces those ambiguities to surface during the proposal conversation, which is the right time to resolve them. The pricing conversation is harder upfront and easier later. The total work is the same. The distribution is healthier. I covered the broader screening discipline in how turning down Webflow clients made my solo practice more profitable.

What Mistakes Did I Make in the First Few One-Page Briefs?

Four mistakes. Trying to compress the long proposal into one page rather than rewriting from scratch, which produced cluttered briefs that lost the clarity advantage. Including too many deliverables, which made the scope feel diffuse. Soft pricing language that left the rate ambiguous, which made clients ask follow-up questions that delayed signing. And weak next-step language at the bottom, which left the client unsure what they were committing to.

The fix for each was the same. Cut more aggressively. The brief works because it forces hard choices about what truly matters. Compromising on the discipline by adding back content (out of habit or out of fear that the client will want more) undoes the benefit. The discipline of trusting the format took several iterations to internalize, but once it landed, the briefs got cleaner and the conversion rate stabilized higher. The discipline is the lever. The format is just the artifact that enforces it.

How Does the Brief Format Interact With the Retainer Model I Use?

Cleanly. The brief works especially well for retainer engagements because retainers benefit from short, clear scope statements rather than long deliverable lists. A retainer brief might say six paragraphs covering ongoing platform partnership, monthly check-ins, AEO maintenance, and quarterly strategic reviews, with a single monthly price and clear renewal terms. The retainer is harder to over-document than a project, which is the right shape for the brief format.

The combination of brief plus retainer compounds well. Each retainer engagement gets initiated through a brief that takes 30 minutes to write. The brief frames the relationship as a strategic partnership rather than as a list of hours, which is exactly the framing the retainer model depends on. The two work better together than either does alone. The brief makes the retainer easy to start. The retainer makes the brief feel sustainable across long relationships. I covered the retainer model in detail in what surprised me about charging a flat monthly retainer instead of per-project for Webflow work.

What Should a Partner Do This Week if They Want to Try the Brief Format?

Three steps. First, write a one-page brief for an engagement you are currently quoting, and compare it to the detailed proposal you would have sent. The comparison itself surfaces what the long format was hiding. Second, send the brief to one new prospective client this week as a real test of the format in your specific market. Third, capture the result honestly, including signing speed, follow-up questions, and final outcome. One data point is not statistically meaningful but it builds intuition.

The fourth step is to commit to the format for a defined period, perhaps two months, and run every prospect through the brief by default. The commitment is what produces enough data to know whether the format works in your specific market and price point. Switching back to long proposals occasionally during the test compromises the data. The discipline is to give the new format a real run before deciding. The decision is then based on evidence rather than on the comfort of the old habit. The same principle applies across most practice changes. I covered a related document discipline in how I write Webflow project proposals that win clients.

What Did Not Change Even After Switching Document Formats?

The work that produces engagements is still mostly the conversation that happens before any document gets sent. The brief works because the upstream conversation has already established trust, scope, and price alignment. Sending a brief to a cold prospect would not produce conversions any better than sending a detailed proposal. The document format changes the friction at the close, not the dynamics of the relationship that gets you to the close.

The honest reading is that documents matter less than most Partners think and conversations matter more. The brief is a useful improvement, but it is a small improvement compared to the upstream work of building the relationship and aligning expectations through actual conversation. The lesson, after running the experiment for several months, is that document optimization is real but secondary. The conversational work is primary. Both matter. Sequencing them correctly is the discipline that produces the practice's results over time. I covered the conversational pattern in what surprised me about charging a flat monthly retainer.

If you are running a Webflow practice and trying to decide whether the one-page brief format would fit your sales conversation, drop me a line and tell me what your current proposal looks like. Let's chat.