A BETTER WAY TO SHARE THE WORK
Help a prospective client see whether your service fits
Explain the work someone can buy before asking them to read a custom proposal.
New to creating with an agent? The request will guide it through the task. Bring your notes; you don’t need to write HTML.
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.
01 / SEE THE DIFFERENCE
An editing service with an explicit boundary
Fictional service notes; not a live offer or booking page.
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.
Open a complete fictional HTML example, with its source notes →
Create my service overview02 / MAKE IT YOURSELF
Start with the evidence. Shape the page around the reader.
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.
03 / TRY THIS PROMPT
Copy this into your agent. Add your source material.
Use the conversation where you already did the work, or start one with your notes. Replace the placeholders and supply any missing context; only attach information you are allowed to share with your agent.
Get the ready-to-copy creation request for guided questions, this task, and a draft review before anything is published.
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.
04 / BEFORE YOU SEND
A polished page still needs your judgment.
- 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.
FROM DRAFT TO A LINK
Make it clear. Make it yours. Then share it.
Keep creating and revising in the agent you already use. With a compatible connection, share/artifacts publishes the reviewed HTML so you do not have to rebuild it in another editor. Ask your agent to use your saved artifact style for headings, color, and tone; review the result before sending it.
Choose who should be able to open the page and verify the returned link. For corrections to the same deliverable, update the existing artifact without changing its link. Publish a separate artifact when the old edition needs to remain available.
These are static pages, not live apps: no scripts, forms, or automatic data refresh. Source collection and scheduling depend on your agent and its available tools, not on share/artifacts.
Make this with my agentQuestions before you start
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.