Key Takeaways
A strong idea can die unread, so make the first page decision-ready.
The unread proposal. In the mid-1980s, Patrick Riley brought investor Adnan Khashoggi a detailed, 50-page business plan for a venture in the Horn of Africa. Khashoggi explained that the length had made it harder, not easier, to consider. He had already passed the document to advisers, moving the idea away from an immediate decision. His proposed remedy was a single page that made the deal and the requested commitment clear.
Respect the reader’s attention. Riley later saw a technology executive’s office stacked with proposals that appeared never to have been read. The problem was not necessarily weak ideas. It was that busy decision-makers must triage. A compact, persuasive proposal is designed to earn a few minutes of attention and give a reader enough to decide whether to engage.
What's striking is that brevity here functions as an interface, not a literary virtue. The proposal reduces the effort required to understand what is being offered and what response is needed. That is especially useful when readers face competing demands. But attention is not the only barrier: a concise page cannot compensate for poor timing, low trust, or an idea that lacks value. Its job is more modest and more useful: make a worthwhile idea easier to evaluate.
Use one page to initiate a decision, not replace due diligence.
A complete first step. Riley defines the One-Page Proposal as a concise document that presents the facts and reasoning behind a project, makes a persuasive case, and asks for a specific action. He recommends about 400 words, which an average reader can review in three or four minutes. The page should stand on its own as an invitation to consider the deal, not as an excerpt that forces the reader to reconstruct the point from a larger document.
Keep the long plan available. A full business plan still has a place when a venture requires detailed analysis, financing, or formal review. The distinction is purpose: a one-page proposal starts a conversation; the longer plan supports deeper scrutiny when requested. Riley argues that an executive summary often reports or abridges information, while a proposal must also persuade and ask.
This distinction resembles staged decision-making: first establish whether a question merits attention, then spend resources on deeper analysis. It protects both sides from investing in a lengthy review before basic interest exists. The limit is important, though. Some decisions are governed by mandated forms, technical standards, or legal disclosure requirements, and a short pitch cannot substitute for them. Used as a doorway rather than a universal document, the format is more credible and more effective.
Research until you can compress the idea without concealing uncertainty.
Know the gaps first. Riley recommends separating what is known from what remains unknown before drafting. A construction family that developed a solar roof understood building and power generation, but lacked information about the solar market, regulatory agencies, and likely corporate partners. They researched those gaps before pitching the technology to Duke Energy. The exercise turns enthusiasm into a case that another person can test.
Verify the foundations. The aim is mastery, not merely collecting enough facts to fill a page. Riley advises checking important claims against at least two independent sources, since bad data can undermine the argument or make its central conclusion false. Research may include company reports, industry publications, government data, and direct knowledge. Compression comes after the writer understands the subject, not instead of understanding it.
The known-and-unknown inventory is a practical form of epistemic humility: it makes missing evidence visible before confident prose can disguise it. This also improves the quality of questions asked during research. A useful safeguard is to distinguish verified facts, estimates, and assumptions, even when the final page has room for only the most decision-relevant details. Concision should remove clutter, not uncertainty that could materially affect the reader’s judgment.
Write for one decision-maker, while preparing for everyone who can block the deal.
Choose the reader deliberately. The intended recipient shapes what belongs on the page and how much explanation is needed. A film financier may already understand distribution economics; an unfamiliar investor may need more context. Riley urges writers to learn the recipient’s interests, past decisions, and likely concerns, then tailor the proposal without resorting to obvious flattery.
Account for resistance. When Riley sought Senator Daniel Patrick Moynihan’s support for a Japanese exhibition of the space shuttle Enterprise, critics might have portrayed the plan as a profit-seeking foreign venture. The proposal addressed that concern directly: Japanese sponsors would cover the costs, and net proceeds would go to the Smithsonian. Moynihan endorsed the project. Anticipating critics helped Riley answer concerns before they became a reason to refuse.
The advice joins audience design with stakeholder analysis. Persuasion improves when the writer models not only the recipient’s preferences but also the pressures surrounding that person. A decision-maker may personally like an idea yet reject it if colleagues, constituents, or risk reviewers raise unanswered objections. Tailoring still has ethical boundaries: understanding someone’s priorities should clarify mutual benefit, not manipulate personal vulnerabilities or bury material facts.
Move the reader from a clear objective to a specific, feasible request.
Build a logical path. The page begins by naming the project and giving it a brief explanation. It then states the main outcome, adds a few supporting benefits, explains why the plan makes sense, addresses its financial implications and present status, and ends with a concrete request. Riley treats this progression as essential because each part prepares the reader for the next.
Make the ask unmistakable. A proposal is not complete if the reader must guess what to do. Riley’s example of philanthropist Murph Slattery shows the value of preparation: she asked Kmart founder S. S. Kresge to fund a teaching auditorium at Detroit Children’s Hospital and named the amount, ten million dollars. Kresge agreed during a brief conversation. The request was clear, connected to a purpose, and within the recipient’s capacity.
The sequence is a compact argument: orientation, desired outcome, justification, feasibility, and choice. It reduces ambiguity about both the project and the recipient’s role. The Slattery story also shows that a direct request can be respectful rather than pushy when its purpose and scale are clear. Still, a polished sequence does not guarantee agreement. It creates a fairer decision by making the proposal’s logic and requested commitment visible.
Put real numbers and current progress where a cautious reader expects them.
Make risk legible. The financial discussion should explain the major costs, expected returns or savings, and relevant funding sources. It should also acknowledge financial risks rather than embellish the case. The current-status account should say what is already arranged, what remains uncertain, and who has committed support. These details help a reader distinguish an early idea from a project with momentum.
Answer the obvious doubts. In the shuttle exhibition proposal, Riley stated that Japanese organizations would cover U.S. costs and that the project was nonprofit, directly addressing concerns about public expense and private gain. He also described existing partners and the proposal’s political opposition. The page gave Senator Moynihan concrete information relevant to his decision instead of relying on broad assurances that the project was worthwhile.
Numbers and status act as credibility signals because they let readers inspect the proposal’s assumptions. They also make uncertainty more specific: an estimate can be questioned, revised, or compared, while a vague promise cannot. The format’s space limit creates a selection problem, however. Writers should include figures that change the decision, not every available metric. If estimates are preliminary, labeling them honestly is more persuasive over time than presenting false precision.
Cut repetition and cleverness before shrinking the type.
Edit for the decision. Riley recommends removing facts that are interesting but unnecessary, repeated claims, explanations the recipient already knows, and wordy or ornate phrasing. A title should identify the subject plainly; a subtitle can add context or appeal. He discarded a punning title for a solar proposal because it felt out of place for a conservative, engineering-focused utility audience.
Keep the page readable. The page limit is real, not an invitation to cram. Riley advises using standard business type at 10 to 12 points, clear section breaks, and comfortable margins rather than shrinking the text until it is difficult to read. The aim is to preserve the information essential to understanding and evaluating the request, not to save every sentence from the draft.
Revision here is a decision test: each sentence must earn the space it occupies by clarifying the offer, evidence, or ask. That principle fits interface design, where removing unnecessary choices can make a core action easier to find. Yet aggressive cutting can erase caveats or context that matter, especially in technical or high-risk proposals. The useful standard is not maximum compression; it is maximum clarity per line without distorting the case.
Let clean, readable production signal care without pretending to be bigger.
Substance over spectacle. Riley rejects the assumption that expensive paper, color, elaborate graphics, or lavish binding make a proposal persuasive. The page’s force should come from the writer’s knowledge and the clarity of the case, making the format accessible to a small business as well as a large one.
Make the document easy to use. He recommends good-quality paper for a printed copy, black ink, a standard typeface, and a clean layout with adequate margins. A polished page can show care, but decorative choices should not compete with the argument. The proposal can later be sent electronically or by fax, but Riley considers a strong printed version useful for a personal meeting or follow-up.
This is a useful correction to status signaling: polish should support comprehension, not impersonate organizational scale. A consistent, readable document lowers friction and communicates attention to detail. At the same time, material expectations vary by industry and institution. In some settings visual design is part of the product; in others, a plain page is the norm. The principle is not austerity for its own sake, but matching presentation to the reader’s context.
Present the page personally, rehearse your case, and move on from maybe.
Pair writing with conversation. Riley advises against sending the proposal as an anonymous document. Whenever possible, introduce it in a meeting; otherwise, speak with the intended reader before sending it. Know the argument well enough to explain it briefly and respond when the conversation begins with a question about money, progress, or implementation rather than following the page’s order.
Treat answers as information. A clear refusal lets the proposer redirect effort while preserving the relationship. An indefinite maybe can leave the project stalled, so Riley recommends following up after a few days and moving on if the reader remains unavailable or undecided. He also recounts inventor Chester Carlson’s persistence: it took more than twenty presentations before a company helped develop his dry-copying machine, later associated with Xerox.
The page and the conversation do different work. Writing stabilizes the case; personal contact establishes context, allows questions, and signals commitment. Carlson’s repeated attempts also distinguish persistence from waiting passively for one gatekeeper. Riley’s treatment of maybe is intentionally brisk, and not every delay is rejection: some decisions require internal review. A useful application is to set a follow-up point, then seek other routes rather than letting uncertainty consume the project.
Analysis
Riley’s method is best understood as a decision interface for a crowded business environment. Its central insight is not simply that short documents are easier to read. It is that a proposal must reduce the recipient’s interpretive work: identify the opportunity, show why it fits, clarify the commitment, and make the next action obvious. The narrative begins with Riley’s own failure to anticipate Khashoggi’s constraints, which gives the method a practical origin rather than presenting brevity as an abstract style preference.
The book’s strongest contribution is the insistence that compression depends on prior depth. A one-page limit forces prioritization, but prioritization is only sound when the writer understands the market, the numbers, the decision-maker, and the project’s vulnerabilities. The proposed page is therefore both an external pitch and an internal test. If the writer cannot state the goal, feasibility, current position, and ask coherently, the underlying thinking may not yet be ready.
The format also makes persuasion unusually accountable. Explicit costs, status, and requests can be checked; they are harder to disguise behind enthusiasm. Its advice to anticipate opposition is most convincing when it means disclosing and answering legitimate concerns, as in the shuttle exhibition example. Tailoring becomes less defensible when it turns into flattery or selective omission, a risk Riley himself warns against. The one-page rule is not universal. Regulated submissions, complex public works, and formal funding processes may require prescribed documents, and serious investors still need detailed diligence. The book acknowledges these limits, though its broad advocacy can understate the role of organizational procedure. The most durable lesson is thus not that every proposal must literally fit one sheet. It is that every ambitious project needs a concise, decision-ready front door, with evidence and deeper documentation available behind it.
Review Summary
The One-Page Proposal receives positive reviews for its practical approach to crafting concise, effective proposals. Readers appreciate the step-by-step guide and examples provided, finding it useful for business and personal applications. Many have successfully implemented the book's principles, noting improved efficiency in proposal writing. Some readers highlight the financial section as particularly valuable. While most reviews are favorable, a few critics find the content obvious or stretched. Overall, reviewers recommend the book for its ability to help distill complex information into a single, impactful page.
People Also Read
Glossary
The One-Page Proposal
A concise decision pitchA self-contained, single-page document that presents the essential facts and reasoning for a project, argues for its approval, and asks a specific recipient to take a specific action. It is designed to initiate consideration efficiently, not to replace detailed plans or formal documents required for later review.
law of easiest decision
Easy choices get decided firstRiley’s description of how people handling many decisions tend to resolve the simplest ones first. Requests that demand more reading, meetings, or information are easily postponed. The concept explains why a long proposal can lose attention even when the underlying idea is promising, and why reducing the effort needed for an initial decision can help.
Secondary Targets
Supporting project benefitsAdditional outcomes that reinforce a proposal’s central objective. They show how a project may create benefits beyond its main purpose, strengthening the case for approval. Riley advises keeping these goals relevant to the primary objective and limiting their number so the list remains credible rather than appearing inflated.
Setting the Stage, Compelling Points, and The Pitch
Three moves in the argumentRiley’s internal structure for the proposal’s main persuasive discussion. The opening establishes the circumstances and stakes, the next movement supports the case with relevant facts, and the close explains what approval will accomplish and why. These are organizing functions within the argument, not separate printed headings.
FAQ
What's "The One-Page Proposal" about?
- Purpose of the Book: "The One-Page Proposal" by Patrick G. Riley is a guide on how to condense a business pitch into a single, persuasive page. It aims to help entrepreneurs and business professionals communicate their ideas effectively and efficiently.
- Origin of the Concept: The concept was inspired by Adnan Khashoggi, who emphasized the importance of brevity in business proposals, especially for decision-makers with limited time.
- Target Audience: The book is intended for anyone who needs to present business ideas, including entrepreneurs, business executives, and even individuals seeking to propose projects within their organizations.
Why should I read "The One-Page Proposal"?
- Efficiency in Communication: The book teaches how to present complex ideas succinctly, which is crucial in today's fast-paced business environment.
- Proven Success: The author shares personal success stories and historical examples, demonstrating the effectiveness of the one-page proposal format.
- Broad Applicability: The techniques can be applied to various fields, from business ventures to community projects, making it a versatile tool for many readers.
What are the key takeaways of "The One-Page Proposal"?
- Brevity is Key: A one-page proposal is more likely to be read and understood by busy decision-makers than lengthy documents.
- Structured Format: The book provides a clear template with specific sections like Title, Target, Rationale, and Action, ensuring all necessary information is included.
- Preparation and Research: Thorough research and understanding of the subject are crucial for crafting a compelling proposal.
How does Patrick G. Riley define a One-Page Proposal?
- Concise Document: It succinctly expresses all facts, reasoning, and conditions surrounding a project within a single page.
- Persuasive Language: The proposal uses persuasive language to build a case for approval and proposes a specific course of action.
- Template and Process: It serves as both a template and a process, requiring comprehensive understanding and clear expression of complex thoughts.
What is the significance of the one-page format according to the book?
- Respect for Time: Decision-makers often have limited time, and a one-page format respects their time by providing all necessary information quickly.
- Easiest Decision Law: People tend to make the easiest decisions first; a concise proposal facilitates quick decision-making.
- Cultural Considerations: In international contexts, a one-page proposal can overcome language and cultural barriers, making it universally effective.
What are the main components of a One-Page Proposal?
- Title and Subtitle: These provide a quick overview and add interest to the proposal.
- Target and Secondary Targets: Clearly state the main goal and additional objectives of the proposal.
- Rationale and Financials: Present the reasoning behind the proposal and outline the financial aspects involved.
- Status and Action: Describe the current status of the project and specify what action you want the reader to take.
How does the book suggest preparing for writing a One-Page Proposal?
- Research Thoroughly: Gather all relevant information and understand the subject comprehensively.
- Organize Information: Sort research into categories like Title, Rationale, and Financials to streamline the writing process.
- Anticipate Questions: Consider potential questions from the reader and address them within the proposal.
What are some historical examples of One-Page Proposals mentioned in the book?
- Declaration of Independence: Cited as a powerful one-page document that effectively communicated a complex and revolutionary idea.
- Magna Carta and Gettysburg Address: These are highlighted as examples of concise, impactful communication.
- Arecibo Interstellar Message: Used as an example of a one-page proposal intended for communication beyond Earth.
What are the benefits of using a One-Page Proposal within an organization?
- Encourages Innovation: Provides a clear format for employees to present new ideas, fostering innovation.
- Saves Time and Resources: Reduces the time and effort required to evaluate proposals, increasing productivity.
- Facilitates Communication: Streamlines the flow of ideas and ensures that proposals are clear and focused.
What advice does the book offer for presenting a One-Page Proposal?
- Personal Connection: Always introduce the proposal with a personal conversation, either in person or by phone.
- Know Your Proposal: Be prepared to discuss any aspect of the proposal in detail and answer questions confidently.
- Follow Up: Use email or fax as intermediates but always follow up with a hard copy for a professional touch.
What are some best practices for writing a One-Page Proposal?
- Use Clear Language: Avoid jargon and complex language; aim for clarity and simplicity.
- Be Positive and Direct: Use positive language and make direct requests in the action section.
- Check Grammar and Spelling: Ensure the proposal is free of errors to maintain professionalism and credibility.
What are the best quotes from "The One-Page Proposal" and what do they mean?
- "The one-page proposal is a time-sensitive document." This emphasizes the importance of brevity and timeliness in business communication.
- "If you don’t ask for something, it’s not a proposal." Highlights the necessity of making a clear request or call to action in any proposal.
- "Throw your heart over the bar, and your body will follow." Encourages readers to commit fully to their proposals, reflecting passion and dedication.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.