Expertise · Story and content locking

How many pages is just enough for the document?

The question is not 'how many pages', but 'what is each page doing'.

Quick summary

There is no fixed number for every type of document. A funding proposal should be concise, around ten to twenty pages, as investors only spend a few minutes on the first read. Annual reports or capability documents meant for reference should be thicker, but the principle remains: each page must have a reason for existence; unnecessary pages dilute the message and may cause the reader to abandon it midway.

Quick comparison
You should choose this direction when
  • fundraising documentation and concise board slides
  • bidding documentation and annual reports need to be substantial
  • Separate the main content and appendices when depth is needed.
Not needed when.
  • stuffing everything out of fear of missing something
  • Adjust the length of the annual report for fundraising

The question about document length often arises when business owners are preparing funding proposals, capability statements, or annual reports and want to know if they are on the right track. Sinh Vũ does not have a single number to provide, as length depends on the type of document, how the reader engages with it, and the time they actually spend. What needs to be clear beforehand is that length is an editorial decision, not a default.

Why is there no golden number?

The pitch deck and the annual report are both corporate documents, but they serve two completely different situations. One needs investors to grasp the idea within the first few minutes. The other serves shareholders to look up financial data throughout the year. Applying the length of one type to the other is a fundamental mistake.

Data from DocSend, a document sharing tool provider, shows that investors only spend a few minutes on the first read. This is a reference point, not an absolute industry standard, but it reflects reality enough to make decisions: a thirty-page funding document does not automatically persuade more than a well-edited fifteen-page document.

The purpose-based classification framework

Compact, around ten to twenty pages: funding proposals, sales slides, presentation slides for committees. Readers do not have much time and need to grasp the main ideas quickly, deciding whether to continue reading within the first few pages.

Thicker, not rigidly limited: annual reports, capability profiles for bids, internal reference documents. Readers actively seek specific information, rather than reading from start to finish in a linear fashion.

Guy Kawasaki suggests the 10/20/30 rule for funding pitches: about ten slides, presented in twenty minutes, with font size no smaller than thirty. This is a personal rule of thumb, not an industry standard, but the reasoning remains valid: fewer messages at once help readers remember and decide faster.

When to separate the appendix

A document may need to be concise for presentation while also having enough depth for thorough evaluation. These two needs are not contradictory if edited correctly: the main section maintains the flow and message, while the appendix contains tables, sample contracts, or supporting data.

Readers skim through the main content without being interrupted by blocks of data. If they want to delve deeper, the appendix is readily available. This separation addresses the pressure of "fear of missing out" without bloating the main body.

The writing style that places conclusions at the top (inverted pyramid) is often significantly shorter than the conventional lead-in style, and helps readers quickly scan while still grasping the main point.

Nielsen Norman Group, Concise, Scannable, and Objective

Common errors

  • Stuffing everything the business has into documents out of fear that investors or partners might think they lack information. The opposite result occurs: readers drop off midway because they can’t find the main point.
  • Using the length of the annual report as a standard for funding applications, or forcing capability documents for tenders to be as concise as sales slides. These two types serve different situations.
  • Incorporate a thick appendix into the main body, causing the reader to lose track and unable to distinguish between the core message and supporting data.
  • Deciding on length before knowing who will read it, in what context, and what they need to decide after reading.

The viewpoint of Sinh Vũ

Sinh Vũ creates funding proposals with each page conveying a message. Investment funds scan quickly; if a page's role is unclear, it should be cut or merged. For multi-page annual reports, the focus shifts to design: dense data blocks must still be easy to reference, with headings and layouts guiding readers to find the parts they need without reading the entire document.

The specific number, how many pages, can only be finalized after clarifying three things: who will read it, in what context they will read it, and what decision the document needs to help them make. Without clarity on these three points, any numbers provided are mere guesses.

The tool brings back.

Decision checklist

Topic: How many pages should a document be to be sufficient? Sinh Vũ guide, sinhvu.com

0 more than 7 items

Select each item you find appropriate, then print or save as PDF to take with you.

Sign indicating that you should take action
Questions to answer before deciding

If you have marked most of the signs above, this is the time to discuss in more detail. Sinh Vũ can help you review and propose a direction.

References

DocSend, Pitch Deck Metrics. Guy Kawasaki, The 10/20/30 Rule of PowerPoint. Nielsen Norman Group, Concise, Scannable, and Objective. Sinh Vũ's practical experience in creating funding proposals and annual reports.

Frequently asked questions

How many pages should a pitch deck have?

About ten to twenty pages is a common reference level, based on DocSend data and Guy Kawasaki's rule of thumb. This number is not an absolute industry standard, but it reflects reality: investors only spend a few minutes on the first read. Keep the main content concise, pushing detailed data to the appendix if depth is needed for evaluation.

When to separate appendices instead of cramming them into the main body?

When a document needs to be presented quickly to a board while also providing enough data for reviewers to read thoroughly afterward. The main section maintains the flow and message, while the appendix contains tables, sample contracts, or supporting documents. The reader scans the main section without interruption and can choose to delve into the appendix if desired.

Is there a page limit for the annual report?

There are no hard limits, as annual reports serve as references rather than quick presentations. However, a heavy volume of data still needs to be designed for readability, with a clear layout and headings guiding users to specific information without needing to read everything.

← Back to Corporate documents