Sales One-Pager for Enterprise SaaS

An enterprise sales one-pager is the single page your champion forwards when they are trying to sell you internally. It is not a smaller sales deck or a company brochure. It is a short argument that someone who missed the meeting can read in a couple of minutes: the problem, what would change, why this is credible, and what you are asking them to do next.

If you just raised, have three to six people and no designer, you probably do not have one. You have a deck, a demo login and a website that tell slightly different stories. After a good call your champion asks for “something I can send around,” and they get a 12-slide file or a homepage link. Neither is easy to forward to a VP with two minutes between meetings.

I was founding designer at Almetra AI from the first prototype through a $19M Series A. Almetra sells AI software to manufacturing companies. The people who signed rarely sat through the full demo. They saw what someone else sent them. That is the job of the one-pager.

The short answer

A good enterprise sales one-pager answers four questions, in this order:

1. Do you understand our problem? In the buyer’s words, not in your category language.
2. What changes for the team? The workflow before and after, shown with one real product screen.
3. Why should we believe you? One piece of proof you can defend, plus a calm note on control and rollout.
4. What happens next? A concrete pilot or next meeting, with scope and what you need from them.

Why the sales deck is not enough

I wrote about how to structure an enterprise sales deck: ten to fourteen slides, built for a champion who forwards it. That deck still matters in the room, and as a send-ahead file for people who will click through.

Most internal forwards are not “please read this deck.” They are a short email to a boss or an IT lead, with one attachment and a line like “this is the company I mentioned.” A twelve-slide file asks for more attention than those readers will give. A homepage asks them to go hunting. Think of the one-pager as the summary slide from the deck, written so it can leave the file and still make sense.

Who you are writing for

You are not writing for the person who already likes you. You are writing for the person they need to convince.

• The champion’s boss. They were not on the call. They want to know the problem, the ask and whether this is a distraction.
• An IT or security lead who got the file in a thread and will scan for data, access and rollout effort.
• A skeptical peer who will look for a reason this does not apply to them.

Design for the least patient of those three. A practical test: give the page to someone who did not join the last sales call and ask them to repeat the problem, the change and the next step. If they hesitate, the page is still written for you, not for a forward.

What goes on the page

There is no perfect layout, but this structure fits most enterprise AI companies on a single A4 or letter page.

1. Header: who you help, in one line. Not your mission. A claim about who it is for and what changes. “AI that helps line leads see the cause of a stoppage while the line is still running” is a header. “The future of industrial intelligence” is not.

2. The problem, in their words. Two or three short sentences using phrases from real calls. When I interviewed manufacturing teams for Almetra AI, people did not say they lacked visibility into production data. They said they found out about problems at the end of the shift, when it was too late. Add the cost of the problem only if you can defend the number.

3. What changes. A simple before and after, without mocking their current tools, plus one cropped screenshot of the real workflow. Caption the action on the screen. Use the same screen you show in the sales demo, so the story stays consistent when they see the product live.

4. How the AI reaches an output. In one short block, show what the system claims, what evidence it shows, and what the user can do next, including correcting it. You do not need model architecture on a one-pager.

5. Proof you can share. One result you can defend: a pilot, a design partner or a measurable change you have permission to mention. If you cannot name the customer, describe the type of company and the outcome. An honest sentence beats a row of vague percentage badges.

6. Why this is safe to try. Three short lines at most: how people stay in control, what the first rollout looks like, and where the longer security or integration detail lives. You are not finishing a security review here. You are stopping that review from being why they never reply.

7. The next step. Write the ask as a small project, not as “let’s keep talking.” Include scope, what success would look like, a rough timeline and who needs to be involved on their side.

Put your name, role and a direct way to reach you in the footer, so the page still works if it is printed or saved as a PDF.

What to leave off

Leave off market size and “the future of AI,” founder bios, feature grids, model diagrams, logos you do not have permission to use, and a price list. For most seed-stage AI teams selling to enterprise, the ask on this page is a scoped pilot, not a rate card. If a buyer has already asked for commercial terms, send those separately.

Security and integration detail should live in a separate appendix the champion can attach when IT asks, not on a second page that turns the one-pager into a short brochure.

Write every heading as a claim

The same rule I use for sales decks applies here, and it matters more because there is no presenter. “Our platform” tells the reader nothing. “Line leads see the cause of a stoppage while the line is still running” tells them what to believe, and the paragraph under it has to prove it. Read only the headings, top to bottom. If that sequence already makes a clear argument, the page will work when someone skims it.

One screen, used everywhere

The product thumbnail is doing more work than it looks. It has to:

• Match the live product, or be clearly labelled if it is designed and not shipped yet
• Use realistic data for the buyer’s industry, not empty states or lorem ipsum
• Be cropped to the part that matters, with one annotation
• Be the same workflow the deck and demo already use

If the one-pager shows a polished screen, the demo shows an older build and the website shows a third version, the buyer notices. They may not mention it. They just trust you a little less. Update the screen in all three places together. If a screen only makes sense when you talk over it, it is not ready for a page that travels without you.

Make it actually forwardable

• Export a clean PDF with a file name they can put in an email: company, audience and date, not “final_v7_USE_THIS”.
• Keep type large enough to read on a phone and on a printed page.
• Assume the page may be printed in grayscale. Do not encode meaning only in a red or green badge.
• Do not lock the file in a tool only a designer can edit. This page will be out of date within a month if your team cannot change a screenshot themselves.
• Match the website. If the homepage says something different, the one-pager starts to feel like marketing.

Design OS is how I keep that loop tight with seed teams: the one-pager, the deck, the demo and the product screens stay one system, and they change together when the positioning or the proof changes.

How it fits with the deck, the demo and the pilot

Asset	Job	Typical reader
Sales one-pager	Get a yes to the next step from someone who was not in the room	Champion’s boss, IT, a peer
Sales deck	Walk a meeting and give the champion a fuller story to present	People in the meeting, plus a careful forward
Sales demo	Prove the workflow live, with real or clearly labelled designed screens	The buying group on the call
Pilot design	Turn a yes into evidence a budget owner can approve	Daily users, champion, IT, budget owner

The one-pager opens the door. The deck and demo carry the meeting. The product has to deliver during the pilot, which I covered in design for enterprise pilots. If the page promises a result the product cannot show in the first sessions, you will win the forward and lose the contract.

A one-day way to draft it

If you need a version this week, start with the words, not the layout.

1. Write the four answers in plain sentences: problem, change, proof, next step.
2. Pull the product screen you already use in the demo. Crop it and write a one-line caption.
3. Add short control and rollout lines, plus your contact details in the footer.
4. Export a PDF and send it to someone who was not in your last sales conversation.
5. Rewrite anything they could not repeat back, then tidy the layout.

A clear argument on a plain page beats a beautiful page that still talks about you.

Common mistakes I see

• Treating it like a brochure. Company history, a stock photo and no ask.
• Compressing the whole deck. Twelve slides at 8-point type is not a one-pager.
• Leading with the product name. The reader still does not know why they should care.
• Vague proof. “Trusted by industry leaders” with no named result you can share.
• No next step. The page informs, then stops, so the champion has nothing to request.
• A different story from the demo. The meeting said one thing. The page says another.

When to bring in a designer

You can draft a useful one-pager yourself with a strict structure, claim headings and one real screen. Bring in a designer when the page still does not look like something an enterprise buyer would forward, when the product screen is the weak part, or when the one-pager, deck, demo and website have drifted apart.

For a single leave-behind, a scoped project is usually enough. If those assets have to stay in sync after a raise, that is founding-designer work: your founding designer, without the hire. I use Design OS for that weekly loop with seed teams.

If that is the gap you are in, book a strategy call and bring the current deck, demo path or leave-behind. We can look at what a champion would actually forward, and what needs to change so the page, the meeting and the product say the same thing. The Almetra AI work shows how those pieces have to hold together from first prototype through a $19M Series A.

Bottom line

An enterprise sales one-pager does the selling after you leave the room. Write it for someone who was not on the call. Give them the problem in their words, one clear change, proof you can defend, and a next step they can approve. Keep it to one page, keep it honest, and keep it aligned with the deck, the demo and the product.