You just got off a good call, and they ask you to send something over before they lose the thread. That is the moment a sales sheet has to perform in: not introducing your business, but confirming what someone already heard and giving them something to forward to a colleague who wasn’t on the call.

It does not need to convince a stranger from zero. It needs to hold up under a second, colder reading, from someone who was not in the room.

A capability statement and a sales sheet get confused often, so it is worth being precise: a capability statement is built for a formal evaluation, procurement, an RFP, a partner vetting you against a list of criteria. A sales sheet is built for a warmer moment, right after a real conversation, when the reader already has some context and just needs it confirmed.

The sections that earn their place

  • One clear headline. What you do and who it is for, in a single line. If a reader has to work to figure out what you sell, the page has already failed.
  • The offer. Your core services, described in the customer’s language, not your internal names for them. Three to five items, not fifteen.
  • Proof. One real result or a short case study beats five vague claims. Specific numbers, specific situations.
  • A way in. Pricing if you can state it plainly, or a clear next step if you cannot: a call, a quote, a free preview.
  • Contact, once. A direct person and a direct way to reach them, not a form buried behind a QR code.

Format: one page, both formats

Keep it to a single page. If it needs a second page to make its case, the case is not tight enough yet. Build it to work two ways: attached to an email as a PDF, and printed if someone needs a physical copy at a meeting or a trade show table. Design for the PDF first; a page that only looks right on screen usually still prints fine, but the reverse is not always true.

What to leave off

Every service you have ever sold, a paragraph of company history, generic stock photography, and any claim you could not defend if someone asked you to. A sales sheet that tries to say everything ends up saying nothing memorably. Cut until only the parts that would change a reader’s mind are left.

A worked example

Here is how that looks with a demonstration company. Harbor Fleet Maintenance is a fictional example built to show the mapping from confirmed business facts to a finished sales sheet, not a real Frontsheet customer.

Their business page inside Frontsheet holds facts at different stages:

  • ConfirmedCore service: scheduled fleet maintenance for regional delivery operators.
  • ConfirmedProof point: cut one client’s unplanned downtime by a documented, named amount.
  • Needs reviewStarting price, imported from the website and awaiting a founder check.

Only the confirmed facts make it onto the sales sheet. The price stays out until it is reviewed, because a sales sheet built from an unverified number is worse than one with a gap. Once the founder confirms it, it is eligible to appear.

Six months later, Harbor Fleet raises that price. The confirmed fact gets updated once. The sales sheet that was built from it does not silently keep showing the old number: it picks up a plain flag.

Needs refreshSales sheet: last exported before the price change.

That is the difference between a document and a page built from a source that stays current: the sales sheet does not know it is wrong until you tell it what changed, and once you do, it tells you back.

Creating and editing a sales sheet inside Frontsheet is unlimited. The first time you export a finished version is the one action that counts against your plan, and re-downloading anything you have already paid for is always free.

Where Frontsheet fits

Frontsheet reads your website from a single URL and drafts your services, proof points, and pricing as a starting set of facts. You confirm what is right and correct what is not, the same way you would review any first draft. A sales sheet built from those confirmed facts pulls from the current version every time you export it, and if a fact it depends on changes later, the sheet shows a needs-refresh flag instead of drifting quietly out of date.

That matters most in the exact moment a sales sheet gets used: right after a good conversation, when someone asks you to send something over before they lose the thread. You want the answer to be an export, not a scramble to check whether the numbers are still right.