From service notes to a clear offer

Make the fit clear before the proposal.

A service overview explains who a service helps, what it delivers, required client inputs and what is excluded.

Make this with my agent

Bring your notes. Review a draft before sharing.

Explore the method

01
A defined starting point
The client brings an existing draft and an authorized source bundle.
02
Three tangible deliverables
One annotated draft, one claim-to-source checklist and one review conversation.
03
Enquiry is not a booking
Dana confirms price, timing and availability after scope review.

THE REAL HTML · FICTIONAL EXAMPLEView on its own

A worked example, not a customer result. September 2026 dates are sample facts.

Now make it about your work

Your service. Your agent. A clearer fit.

Help a prospective client understand the work before starting a scope conversation.

Start with three things

Authorized service scope, intended clients and exclusions.
Concrete deliverables and required client inputs.
Approved commercial conditions and the confirmed enquiry route.

Make this with my agent

You review the facts and access. Nothing is published without your approval.

The method behind the service overviewAsk your agent to make fit, deliverables and boundaries concrete without inventing prices, availability or results.

What should a useful service overview include?

State who the service is for, the problem it addresses, what you actually deliver, what the client must provide and what is excluded. Your agent can turn that approved material into a readable HTML overview. Keep availability, pricing and commitments conditional until they are confirmed through your normal enquiry and proposal process.

What to give your agent

Current service scope, intended audience and situations where it is not suitable.
Concrete deliverables, examples permitted for sharing and client prerequisites.
Approved pricing or timing if supplied, with conditions and exclusions.
The verified enquiry process and who can confirm fit and availability.

Describe fit before listing capabilities
Name the job the prospective client needs done. Include a clear not-for case so the page helps unsuitable enquiries self-select. Do not imply expertise, certifications or industry coverage that the source material does not establish.
Turn services into observable deliverables
Replace 'strategic support' with the actual work supplied: for example, one annotated draft and a review discussion. Separate deliverables from hoped-for business benefits. Include only portfolio examples and client references you have permission to share.
Put prerequisites beside the offer
Explain what the client must supply and what you will not do. Preserve conditions attached to price and timing. If availability or price is unknown, say confirmation happens during enquiry rather than inventing a package to complete the layout.
Offer an honest next step
Use a short HTML page with fit, deliverables, inputs and exclusions. Point to a supplied contact route without creating a booking or payment form. Review before sharing; a capabilities page should not look like a signed scope of work.

Keep creating and revising in the agent you already use. Start with a saved artifact style and learn how to update HTML without changing its link.

Use the full promptReady for your agent and your notes

Use the conversation where you already did the work. Only attach material you are allowed to share.

Get the ready-to-copy creation request →

Create a service overview from my authorized service scope, intended audience, deliverables, prerequisites and exclusions. Ask for missing essentials. Explain fit and not-for situations before capabilities. Distinguish deliverables from unproven business outcomes. Preserve conditions on supplied price, timing and availability; do not invent certifications, customer references, testimonials or commitments. Use only the confirmed enquiry route. Make static HTML with no scripts or forms and my saved style if available. State that specific scope and availability require confirmation in our existing process. Show me the draft. Do not publish or change access without separate explicit approval.

Check before you shareAccuracy, clarity, and permission

Can a prospective client tell whether this is for their situation?
Are deliverables and required client inputs concrete?
Are exclusions and unconfirmed commercial details clear?
Does the next step avoid implying a booking or contract?

When HTML fits

A reusable introduction that can accompany an email and lead to a properly scoped proposal.

When another format fits better

Use your existing proposal, contract, scheduling and payment systems for actual commitments. This is not a checkout, binding quote or proof of current capacity.

What we started withThe same facts, as an email

Fictional project email

Paper Lantern — research-summary editing scope

Thanks for asking about research-summary editing. Here is the scope as of September 7, 2026.

This is for teams with an existing summary draft and a completed research bundle they are authorized to share. The aim is easier review of reasoning and source links, not new research. Deliverables are one annotated draft, one claim-to-source checklist and one review conversation. The checklist maps major claims to supplied sources and flags gaps; it does not verify inaccessible sources.

Please provide the draft, accessible authorized sources, intended audience and quotation or sharing restrictions. You remain responsible for permission to share those materials. New research, inaccessible-source verification, legal or medical advice, graphic brand design and publishing are excluded. No sales or research-accuracy outcome is guaranteed.

I confirm price, timing and availability after reviewing scope; no slot is reserved by reading this. Continue in our existing email conversation. A specific engagement still needs the normal scope and approval process. There are no supplied testimonials, certifications or performance metrics. This is a fictional reading aid, not a contract, payment page or booking system; no actual contact address is included.

Dana

Inspect the HTMLOne self-contained file

The example is sanitized and isolated from this site. No scripts, forms, or live data.

<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><title>Paper Lantern · Service overview</title><style>
*{box-sizing:border-box}html{color-scheme:light}body{margin:0;background:#f6f8f5;color:#20352f;font:17px/1.65 system-ui,sans-serif}main{max-width:1000px;margin:auto;padding:clamp(20px,5vw,64px)}h1,h2,h3,p{margin:0 0 18px}h1{font:500 clamp(32px,5vw,58px)/1.14 Georgia,serif;letter-spacing:-.025em;overflow-wrap:anywhere}h2{font:500 29px/1.3 Georgia,serif;overflow-wrap:anywhere}h3{font-size:19px;line-height:1.4}.label{font:700 12px/1.6 system-ui,sans-serif;letter-spacing:.08em;text-transform:uppercase}.intro{font-size:20px}.lead{background:#174b40;color:white;padding:24px;margin:28px 0}.lead p:last-child{margin:0}.grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,230px),1fr));gap:20px;margin:24px 0}.card{background:white;border:1px solid #bbc5c4;padding:24px}.metric{font:500 38px/1.2 Georgia,serif;display:block;margin-bottom:12px}section{margin:36px 0}ul,ol{padding-left:22px}li{margin-bottom:12px}.note{font-size:14px}.warning{border-left:5px solid #956118;padding-left:20px}a{color:inherit;text-underline-offset:4px}a:focus-visible,summary:focus-visible{outline:3px solid #956118;outline-offset:4px}table{width:100%;border-collapse:collapse;table-layout:fixed;font-size:15px}th,td{text-align:left;vertical-align:top;border-bottom:1px solid #bbc5c4;padding:12px 8px;overflow-wrap:anywhere}caption{text-align:left;font-weight:700;padding:12px 0}pre,code{white-space:pre-wrap;overflow-wrap:anywhere}footer{border-top:1px solid #bbc5c4;padding-top:24px;margin-top:40px;font-size:14px}@media(max-width:480px){th,td{padding:10px 4px;font-size:14px}}@media print{body{background:white}.card,.lead{break-inside:avoid}h2,h3{break-after:avoid}}
</style></head><body><main><header><p class="label">Paper Lantern / Fictional service / September 7, 2026</p><h1>Make an existing research summary easier to review.</h1><p class="intro">For teams with a draft and an authorized source bundle—not teams seeking a new research project.</p></header><section class="lead"><h2>Three concrete deliverables</h2><ul><li>One annotated draft.</li><li>A claim-to-source checklist.</li><li>One review conversation.</li></ul></section><section><h2>What you bring</h2><p>Your current draft, accessible authorized sources, intended audience, and any restrictions on quotations or sharing. You remain responsible for permission to share the material.</p></section><section><h2>What the checklist means</h2><p>It maps major claims to supplied evidence and flags gaps. It does not claim inaccessible sources were verified.</p></section><section class="warning"><h2>Outside the service</h2><ul><li>New research or inaccessible-source verification.</li><li>Legal or medical advice.</li><li>Graphic brand design.</li><li>Publishing for the client.</li></ul><p>No sales or research-accuracy outcome is guaranteed.</p></section><section class="card"><h2>Confirm the scope with Dana.</h2><p>Use the existing email conversation. Price, timing and availability are confirmed after scope review. No work slot or appointment is reserved here.</p><p class="note">This invented overview is not a live offer, contract, payment page or booking system. No customer references or certifications are claimed.</p></section><footer>Fictional worked example by share/artifacts. Names, dates, figures and records are invented for demonstration. Static snapshot; no live data or automatic updates.</footer></main></body></html>

The original worked scenarioThe source scenario, step by step

An editing service with an explicit boundary

Fictional service notes; not a live offer or booking page.

The original notes

Paper Lantern offers research-summary editing for teams with a completed, authorized source bundle and a draft. It delivers one annotated draft, a claim-to-source checklist and one review conversation. It does not conduct new research, verify inaccessible sources, give legal or medical advice, or publish for the client. Price, timing and availability are confirmed after reviewing scope. Enquire through the existing email conversation with Dana.

For

Teams with a completed authorized source bundle and a draft.

Delivered

One annotated draft, a claim-to-source checklist and one review conversation.

Not included

New research, inaccessible-source verification, legal or medical advice, or publishing for the client.

Next step

Ask Dana in the existing email conversation; price, timing and availability follow scope review.

The client can assess fit without mistaking an overview for a commitment.

Questions, adaptations & sourcesGo deeper when you need to

Is this the same as a project proposal?

No. An overview explains a repeatable service. A proposal describes a specific client's work, resources and approval request after the fit is understood.

Do I have to show a price?

Only if you have an approved price with relevant conditions. Otherwise explain what needs to be reviewed before quoting; do not invent a starting price.

Can it include client examples?

Yes, when the examples and any attribution are approved for this audience. A fictional demonstration must be clearly labeled and never presented as a client result.