Write & communicate

Turn product material into a customer one-pager

Condense verified product and customer context into a decision-useful page without unsupported personalization

8 min setupTested with:ChatGPTReviewed: 2026-08-28

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

Product source materialCustomer contextDocument constraints

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Create a customer-facing one-pager using only the supplied product material and confirmed customer context.

Approved capabilities, workflows, limits, implementation, security, price, evidence, and links:
[product]

Confirmed goals, workflow, participants, constraints, questions, priorities, and unknowns:
[customer]

Audience, stage, length, format, voice, sections, claims, CTA, and approvals:
[delivery]

First build a relevance map linking each confirmed customer need to a verified capability, limitation, proof item, and open question. Do not state a hypothesis as the customer's pain, priority, outcome, or commitment. Draft a scannable page with audience-specific heading, confirmed context, relevant workflow, capabilities and boundaries, evidence with sample and timeframe, implementation or fit requirements, open questions, and one proportionate next step. Prefer concrete verbs and decision information over promotional adjectives. Never invent integrations, security status, price, ROI, timeline, customer quote, result, or approval. Keep material exclusions visible when they affect fit. Then provide a claim ledger and layout hierarchy; audit whether the page can stand alone and whether every personalized line was actually confirmed.

Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Product source material: Workflow platform records requester, owner, accepter, acceptance evidence, and escalation. Integrates with Slack and Teams; no email-only workflow or on-premise hosting. SSO is available on Enterprise only. Setup requires a workflow owner and 60-minute mapping session. Case study: one 35-person UK agency reduced overdue handoffs 18% over 10 weeks; no guarantee. Annual price depends on seats; no approved quote yet. Security overview link approved: https://example.com/security.
Customer context: Confirmed on discovery call: Northstar Studio has 42 staff, uses Teams, and wants to evaluate one brand-project handoff because review ownership is inconsistent. Operations Director and Project Lead will map it. They require SSO; hosting requirement and procurement process are unknown. No agreed budget, rollout date, or performance target.
Document constraints: One A4 page for Operations Director to share with IT and Project Lead before a 45-minute workflow review. Plain professional tone. Required: situation, proposed evaluation, relevant capabilities, evidence and limits, requirements, open questions, CTA. No ROI claim. Legal approval needed for case result.

Example output

Northstar Studio: evaluate one brand-project handoff

Confirmed context Northstar Studio uses Microsoft Teams and wants to examine inconsistent review ownership in one brand-project handoff. The Operations Director and Project Lead are available to map the workflow. No budget, rollout date, or performance target has been agreed.

Proposed 45-minute evaluation Map one recurring handoff from request to acceptance. Identify requester, current owner, accepter, acceptance evidence, and escalation path. Record where Teams should display those decisions and which steps remain human decisions. The output is a fit assessment and open-question list, not a rollout commitment.

Relevant capabilities and boundaries The platform records the five handoff fields and integrates with Teams. SSO is available only on Enterprise. Email-only workflows and on-premise hosting are not supported. Setup requires a named workflow owner and a 60-minute mapping session if evaluation proceeds.

Evidence, with limits One 35-person UK agency reported an 18% reduction in overdue handoffs across 10 weeks. This is a single case, does not predict Northstar's result, and must receive legal approval before external use. No ROI or expected improvement is stated.

Questions before fit can be confirmed Is on-premise hosting required? Which SSO requirements apply? Who reviews security and procurement? How many seats would be in scope? What observable evidence would make the evaluation useful? Pricing cannot be stated until seat scope and an approved quote are available.

Next step Confirm the workflow participants, IT attendee, and hosting/SSO questions, then run the 45-minute mapping review. Security overview: https://example.com/security.

Claim ledger: Teams, SSO tier, exclusions, setup needs, and security link map to approved product material; customer size, Teams use, evaluation need, and participants map to confirmed discovery notes; case scope and qualifier are retained.

Why this works

1
A relevance map prevents generic product facts from masquerading as customer-specific value.
2
Visible limitations make the page useful for a real buying decision, not only persuasion.