Steal our proposals. Improve them. Send them back. We publish our actual client proposals and our win rates. Here is what happened when we made them public.
Steal our proposals. Improve them. Send them back.
In March 2026 we published five real client proposals on the Striveloom blog. Real scopes, real pricing frameworks, real timelines. Company names changed with permission. Everything else authentic.
Within 90 days, two things happened. Proposal win rate increased from 41% to 58%. And we started getting inquiries from clients who opened every conversation with "I read your proposal for the e-commerce migration — can we talk about something similar?"
Public proposals are not a gimmick. They are a qualification machine. Clients who have studied your proposals before the first call arrive pre-sold on your approach. They show up to ask about their situation, not to evaluate whether you know what you are doing.
Most agency proposals are bad. Not because agencies are bad at what they do. Because proposals are treated as sales documents rather than as thinking documents.
A sales document tries to impress. It leads with agency credentials, client logos, and award badges. It downplays scope uncertainty. It promises outcomes it cannot guarantee. It is written to get a signature, not to be useful.
A thinking document restates the client's problem in sharper terms than the client used. It maps the scope to the problem. It admits what is uncertain. It gives the client enough information to evaluate whether the proposal matches their actual situation.
Most clients have seen dozens of sales proposals from agencies. Almost none have seen a real thinking document. When they see one, they remember it.
We published the proposals for the same reason we publish our MRR: transparency is the fastest shortcut to trust. A prospect who has read your proposal before the call already knows your pricing philosophy, your scoping approach, and your risk policy. The call becomes a fit conversation, not a credibility audition.
Per First Round Review research on sales process transparency, B2B service providers who publish detailed methodology documents and pricing frameworks reduce average sales cycle length by 30% to 40% because prospects arrive with a higher level of pre-qualification (per First Round Review, 2024). We experienced a 33% reduction in average sales cycle over the six months after publishing.
Here is the structure we use for every proposal. All five published versions follow this template:
Section 1: Problem restatement (not brief summary) We write back the client's situation in more specific terms than they sent us. If they said "we need a new website," we write "your current conversion rate on mobile is 1.2%, which is roughly half the industry average for your category, and the site takes 6.4 seconds to load on mobile. The new site needs to solve those two measurable problems." This section does two things: proves we listened, and raises the standard for what success means.
Section 2: Scope and what is not in scope Every scope section has an explicit "out of scope" list. This is the most important habit we have. Scope creep almost always starts with something that seemed obvious to the client and was never mentioned in the proposal. Listing what is not included prevents the fight before it starts.
Section 3: 90-day milestone breakdown We do not promise outcomes. We promise milestones. Week 2: strategy document delivered and approved. Week 4: wireframes approved. Week 8: development complete, staging review. Week 12: launch and handoff documentation. Clients can evaluate progress against specific deliverables rather than waiting for a big reveal.
Section 4: Investment and payment structure Straight pricing with three-line justification. Monthly retainer or fixed project price. 50% upfront for projects under $20K, 33% upfront for projects over $20K. Monthly billing for retainers, NET 15. No "contact us for pricing" ambiguity.
Section 5: Risk reversal If we miss a milestone without documented cause, the client gets a credit. We have never triggered this clause. But its presence tells the client we have confidence in our process and removes the fear of paying before they see results.
Section 6: Next step One action. Not "let us know if you have questions." Specifically: "If this looks right, please sign the agreement linked below and we will send the kickoff questionnaire within 24 hours." Clear next step, clear timing.
Six months of data before and after publishing the proposals:
The win rate increase was significant. But the deal size increase surprised us more. Clients who arrived having read our proposals came in with bigger problems framed more specifically. They had already mapped their situation against our structure and identified a larger scope. The average deal size increased 16% with no change to our service offerings.
Thirty-one percent of prospects in the post-publication period mentioned the published proposals in their first message or first call. "I read your proposal for the SaaS redesign and I want to talk about something similar." That is the best possible sales context. The prospect has done half the qualification work before the first conversation.
The most common pushback when we mention publishing proposals: "Won't competitors copy your format?"
Yes. Some will.
But here is the thing: a competitor can copy the six-section structure today. They cannot copy the fact that we published it in March 2026 and have been refining it publicly since. The publication history is the moat. If a prospect Googles both agencies and sees that we published our proposal format 8 months ago with public commentary on each revision, and the competitor just launched a similar format last month, the trust signal is clear.
Y Combinator's library on competitive strategy notes that process transparency is a sustainable moat when combined with execution history — the document plus the track record is what competitors cannot replicate (per Y Combinator, 2024).
The second worry: "Won't bad prospects use it to know exactly what to say to manipulate the proposal?" Maybe. But any prospect who studies your published proposals in that level of detail to game the process is also probably a sophisticated buyer who understands what good work looks like. They are unlikely to be the difficult client you fear.
You cannot publish a sales brochure and call it a proposal. The standard agency proposal would embarrass you if it were public. That gap between your current proposals and a document you would be proud to publish is exactly the gap your win rate is paying for.
Start with the problem restatement. Write the client's situation back to them with more specificity than they used. If you cannot do that, you do not understand the problem well enough to propose a solution. The restatement forces clarity.
Add the out-of-scope list. Every proposal needs one. Anything a client might reasonably expect but is not included belongs on the list. It is uncomfortable to write. It is much less uncomfortable than the scope argument at month 3.
Add a risk reversal. One specific, defensible commitment. Not "we guarantee results" — that is unenforceable and unbelievable. "If we miss any of the three milestone dates in this proposal without documented cause, we will apply a 10% credit to the next invoice" is specific, defensible, and tells the client you believe in your own process.
When those three things are solid, consider publishing it. See the current published proposals at Striveloom's services page.
Publishing proposals is uncomfortable at first. It feels like showing your hand. The industry instinct is that proposals are proprietary, competitive intelligence that should never leave the room.
That instinct is wrong. The agencies treating proposals as proprietary are the agencies with 40% win rates. The ones publishing them honestly are converting 58% to 60%.
Transparency in the proposal is a bet on your quality. If the work is good, transparency accelerates trust. If the work is not good, hiding the proposal just delays the moment the client figures that out.
Take the structure above. Write your next proposal using it. See what happens to your close rate. Then consider whether that proposal is good enough to publish.
Industry benchmarks from agency surveys suggest average proposal win rates between 30% and 45% for most digital agencies. Agencies with strong positioning and a defined ICP typically see 50% to 65%. Striveloom's rate went from 41% pre-publication to 58% after publishing proposals publicly, primarily because published proposals improve lead quality — prospects who have studied your proposals arrive more qualified. Win rate is as much a lead quality metric as a sales skill metric.
Yes. Agencies that hide pricing until the proposal stage waste time on leads who cannot afford them. Publishing a pricing framework publicly — even without specific project numbers — pre-qualifies leads before the first call. In the five public Striveloom proposals, pricing ranges are visible. Prospects who reach out after reading them are price-aware and rarely negotiate aggressively. The fear that publishing prices loses deals is mostly unfounded — it mainly filters out leads who would have wasted time anyway.
Six to eight pages for a project proposal. Two to three pages for a retainer proposal. Any longer and you are compensating for unclear thinking with volume. The six sections above — problem restatement, scope, milestones, investment, risk reversal, next step — cover everything a client needs to decide. Agencies that write 30-page proposals are either padding for credibility or do not know what the client actually needs. Shorter, clearer proposals win more often.
Leading with agency credentials instead of client problem. The first thing a prospect reads should be evidence that you understand their situation. Agency awards, years in business, and client logos are credibility signals, not decision drivers. Put them in an appendix. Open the proposal by restating the problem with more precision than the client used. That precision signals more competence than any credential list.
Write an explicit out-of-scope list in every proposal. Anything a client might reasonably assume is included but is not should be listed. This feels uncomfortable to write — it forces direct conversations about what you are not doing. But scope creep almost always starts with something that was obvious to the client and never addressed in the proposal. The list prevents the argument before it starts. Every time you have a scope dispute, add the missing item to the out-of-scope template for future proposals.
Founder & CEO of Striveloom. Software engineer and Harvard graduate student researching software engineering, e-commerce platforms, and customer experience. Builds the agency that ships like software — one team, one pipeline, one platform. Writes on AI agencies, web development, paid advertising, and conversion optimization.
100 days of agency wins, fails, and one near-lawsuit — all posted publicly. What build-in-public actually does to inbound leads and client quality for a digital agency.
One $99 website audit product. 287 sales in 6 months. Here is how a simple productized offer funded Striveloom's runway and converted buyers into retainer clients.
We publish Striveloom's actual MRR, churn rate, and CAC every month. Here is what 18 months of live numbers taught us about trust, clients, and acquisition cost.
Book a free 30-minute call to scope your project. Fixed pricing, transparent timelines.
| Metric | Pre-Publication (6 months) | Post-Publication (6 months) |
|---|
| Proposals sent | 47 | 52 |
| Proposals won | 19 (40.4%) | 30 (57.7%) |
| Average deal size | $7,200 | $8,400 |
| Average sales cycle | 22 days | 15 days |
| Discovery-to-proposal conversion | 54% | 68% |
| Prospects who mentioned proposals in first call | 0% | 31% |
