One-pager template
Compress the offer, proof, and next step into something busy people can scan and forward.
A good one-pager does one job: compress the important context into something a busy person can scan. The format matters, but the useful part is the thinking behind it. Readers need the context, the recommendation, the proof, and the next step without having to reverse engineer your intent.
Claude can turn company notes, product details, audience context, proof, pricing, and next steps into a clear first version. Send turns that version into a live page you can share, track, and revise as the conversation changes.
What to include in the one-pager
- Who it is for and what problem it solves.
- What the product, project, or offer does.
- Key proof, examples, metrics, or customer context.
- Pricing, availability, scope, or constraints if relevant.
- Clear next action and contact details.
Prompt to use in Claude
Search the registry for the Send connector. Once connected, use their "send/one-pager" skill.
How to create it with Send
Give Claude company notes, product details, audience context, proof, pricing, and next steps, plus any constraints, examples, or audience notes that matter. Ask it to create the one-pager with the Send connector so the output becomes a page instead of another loose document.
After you share it, Send helps you see whether prospects, partners, and stakeholders open it, come back to it, or share it internally. You can update the same link when details change.
One-pager structure
Snapshot
Audience, problem, offer, and reason to care.
Details
How it works, examples, proof, and constraints.
Fit
Who it is best for and what questions remain.
Next step
CTA, owner, link, or contact path.
Why send a one-pager as a page
A one-pager is supposed to save the reader time. Send gives you a clean link, keeps the page current, and shows whether the recipient actually reads it.