Verified against Perplexity Pages · 2026-07-24
Turn a research thread into a structured Perplexity Page worth sharing publicly
A brief for generating a Perplexity Page that specifies section structure, a target reader who was not part of the original research thread, and a rule against carrying over conversational asides that only made sense in context.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Turn this research into a Perplexity Page — a standalone, structured document meant to be read and shared on its own, not a transcript of how we got here.
TOPIC
How usage-based pricing actually works across the major dev-tool platforms
SOURCE MATERIAL
The full Deep Research thread comparing pricing models across five API platforms, including the evidence table
WHO WILL READ THIS
A product manager at a partner company who asked for "the pricing research" but wasn't in any of the original threads
SECTION STRUCTURE REQUIRED
Summary, How the pricing models differ, Cost comparison at three usage tiers, Open questions, Sources
REWRITING RULES
- The target reader was not part of the original research conversation and has no idea what was asked, refined, or corrected along the way — write for someone seeing this topic fresh, not someone following our back-and-forth.
- Drop any conversational aside, hedge, or self-correction that only made sense in the moment ("actually, let me revise that" or "as I mentioned above") — the Page should read as a finished document, not a cleaned-up chat log.
- Every factual claim carried over from the source material keeps its citation — do not strip citations during the rewrite for readability, and do not introduce a new claim in the Page that wasn't actually established and cited in the source research.
- If the source research contained an unresolved question or a flagged gap, keep that gap visible in the Page rather than smoothing it into confident-sounding prose just because the Page format looks more finished than a thread.
TONE AND LENGTH
Plain, direct, no marketing language — roughly the length of a two-page internal memo
OUTPUT
The finished Page content, organized under the section headers specified above, with a short one-line summary at the top stating what this Page covers and as of what date — since anyone opening a shared link later has no way to know how current it was when written unless it's stated explicitly.Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
A Perplexity Page is meant to stand alone as a shareable artifact, which is a fundamentally different job than a research thread, whose structure — a series of questions, refinements, and corrections — only makes sense to someone who was present for the back-and-forth; asking for the reformatting explicitly, rather than just "turn this into a Page," is what forces the model to actually rebuild the structure for a cold reader instead of lightly editing the conversational log it already has. Naming a specific target reader who wasn't part of the original thread is the concrete mechanism that catches conversational residue a generic "make this readable" instruction would miss — a model reformatting its own prior output has every incentive to preserve phrasing that felt natural in context (self-corrections, references to "as discussed above") because it doesn't have an outside reader's perspective to notice those phrases no longer point to anything the new reader can see. The citation-preservation rule matters specifically because reformatting for readability is exactly the kind of pass where citations get quietly dropped — they add visual clutter to a document being polished for presentation, and a rewrite optimized purely for flow will trim them first unless explicitly told that citations are load-bearing content, not formatting overhead. And keeping unresolved gaps visible rather than smoothed over addresses a specific risk of the Page format itself: a shared, professionally formatted document reads as more authoritative and complete than a thread of typed questions and answers, even when the underlying research has exactly the same open questions in both — the formatting itself creates a false signal of completeness that the content has to actively resist.
Verified against
Perplexity Pages 2026 · 2026-07-24
Changelog
- 2026-07-24 — Initial publish, verified against Perplexity Pages generation.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
