Small steps.
Better products.

Why use it: Find the work that needs attention without rebuilding a status report.

1. Open the home dashboard after saving a product and initiative.
2. Read attention items and follow a record link to inspect the underlying facts.
3. Use the workspace search to find saved records; choose a result to open that record.

Keep in mind: An empty dashboard means nothing is recorded here; it does not prove everything is healthy.

Open this area ↗

Why use it: Get from a blank page to a useful first product and initiative.

1. Enter a new product name and optionally select a domain starting point.
2. Enter the desired outcome, first initiative, first action and optional responsible person.
3. Inspect the preview, then create the connected records together. Open the initiative and download a backup.

Keep in mind: Setup does not add sample evidence. Domain starting records are prompts to complete, not verified facts.

Open this area ↗

Why use it: Keep the problem, owner, scope and intended result together.

1. Save a product with its audience, context and constraints.
2. Choose Initiatives, link the product and record the problem, outcome, non-goals, owner and success measures.
3. Connect an originating opportunity where appropriate. Filter active or archived records and open the initiative overview.

Keep in mind: Archiving keeps records. A parent archive can make its linked records inactive; inspect archive explanations before restoring.

Open this area ↗

Why use it: Turn a busy day into a small set of accountable next actions.

1. Select the product and initiative focus, review attention items, and use quick capture for new work.
2. In the weekly planner, select actions and commit them to the week. Edit owners, dates or status; preview bulk changes before applying.
3. Use available undo before the affected fields change. At week end, record what happened, why work slipped and the next action.

Keep in mind: Saved commitments are planning records, not proof of completion. Confirming a focus change discards an unsaved capture; cancel keeps it.

Open this area ↗

Why use it: Connect goals, evidence, decisions, delivery and results in one place.

1. Choose an initiative or open its overview from its product card.
2. Read the factual gaps, then follow a direct link to fix the source record. Expand archived records only when needed.
3. Use scoped actions to add work, open a playbook, prepare an update or make a review pack.

Keep in mind: Counts describe linked records. Missing evidence is unknown; completing tasks never proves an outcome improved.

Open this area ↗

Why use it: Explain why a problem deserves attention using traceable observations.

1. Save the original observation or quote with its source, date and context.
2. Keep observations, interpretations and assumptions distinct; add themes and any contradictory evidence.
3. Create an opportunity and link relevant evidence before linking an initiative.

Keep in mind: A theme or interpretation is not a verified fact about all users.

Open this area ↗

Why use it: Review many observations consistently and spot coverage gaps.

1. Choose the research product and optional initiative. Upload a CSV up to 1 MB with 1 to 1,000 rows; map title, observation text and source plus available context fields.
2. Preview new, duplicate and invalid rows. Dates use YYYY-MM-DD. Select the new rows to retain and apply only after checking their sources; duplicates include archived evidence.
3. Filter evidence by segment or theme, manually code themes and retain conflicting feedback. Follow record links to edit observations.
4. Use theme coverage and opportunity links to investigate the original evidence before proposing a solution.

Keep in mind: Theme counts describe your recorded sample, not market prevalence or statistical sentiment.

Open this area ↗

Why use it: Keep the reason for an initiative visible during prioritization.

1. Select an opportunity.
2. Read linked evidence, assumptions and open questions, including archive warnings.
3. Follow the linked initiatives or open Choices to prepare a decision.

Keep in mind: No linked evidence means a gap, not confirmation that the idea is correct.

Open this area ↗

Why use it: Make priorities and timing assumptions visible.

1. Review initiatives in Planning and roadmap.
2. Record reach, impact, confidence and effort where known, then set the appropriate planning horizon.
3. Discuss the score alongside dependencies and evidence; use Choices for alternative assumptions.

Keep in mind: A roadmap horizon is not a delivery commitment; a RICE score is a discussion aid.

Open this area ↗

Why use it: Preserve the assumptions behind a priority decision.

1. Create a scenario for a product and add initiative estimates.
2. Use matching periods, reach units, impact scales and effort units. Apply shared scales only when the numbers mean the same thing.
3. Record the selected option, tradeoffs, confidence and revisit date. Save an alternative scenario or download the decision brief.

Keep in mind: Changing scale labels does not convert numbers. Incompatible scales are not comparable.

Open this area ↗

Why use it: Give follow-up work an owner and a clear completion check.

1. Add manual actions or review actions already extracted from saved drafts; set owner, due date, criteria and status.
2. Record decisions, assumptions, rationale, evidence and open questions.
3. Create or apply readiness checks, inspect the evidence, and record the review before changing readiness status.

Keep in mind: Action status and named reviews are local, self-reported records, not verified signatures.

Open this area ↗

Why use it: Make scope and constraints concrete before handing work to a delivery team.

1. Save stories with acceptance criteria, edge cases, estimates, test references and parent links. Record prerequisites with owners and needed-by dates.
2. Use story refinement to draft smaller slices, preview affected windows and checks, then apply. The original story remains; estimate the new slices explicitly.
3. Create a delivery window with dates, responsibility, capacity and a common estimate unit. Resolve unknown estimates or excess load before committing.
4. Create product checklist templates and apply them to initiatives. Review newly created checks in Execution; inspect downstream dependency impact.

Keep in mind: Changing scope or estimates can reset commitment. Story splitting does not automatically redistribute estimates or prove readiness.

Open this area ↗

Why use it: Transfer reviewed scope without sharing an API key.

1. Choose a product, destination and stories.
2. Map destination fields, inspect exact CSV rows and duplicate-export warnings.
3. Save the local handoff, download CSV and its row manifest, then import through your own destination tool.

Keep in mind: A saved manifest records preparation only. It does not create tickets or verify external IDs.

Open this area ↗

Why use it: Separate delivered work from observed improvement.

1. Create a shared objective and link initiatives. Add metrics as key results with units, meaning, time window, baseline, target and desired direction.
2. Add dated observations with sources, or map a CSV's date, value, source, unit and window columns. Inspect row errors and duplicates before applying.
3. Inspect trend values, freshness and exact sources. If the metric definition changes, confirm the baseline and target for the new definition.
4. Record an experiment hypothesis and plan, pre-register it locally before results, then record the observed result and your decision.

Keep in mind: Blank values are unknown. Future, conflicting or incompatible observations cannot silently establish success. No statistical significance or causality is calculated; correct history by adding observations.

Open this area ↗

Why use it: Explain changes using the same records the team maintains.

1. Choose an initiative, audience and cadence, then build an update snapshot.
2. Review and edit the wording. Inspect differences from the previous saved snapshot for the same scope.
3. Save to Artifacts to establish the next comparison baseline; download and share manually.

Keep in mind: Downloading alone does not save a baseline. Editorial changes do not change source records; rebuild after source changes.

Open this area ↗

Why use it: Bring a bounded, readable evidence summary to a product review.

1. Choose product or initiative scope and audience.
2. Choose whether to include owners, source references and notes. Add exact case-sensitive redaction terms and inspect the complete preview.
3. Download text or HTML. Open the HTML and print or save as PDF using the suggested page settings.

Keep in mind: The compact report counts omissions and shortened entries. Exact-term redaction is not automatic personal-data detection; inspect all free text.

Open this area ↗

Why use it: Start domain work with concrete prompts and completion checks.

1. Choose a product and one of the SaaS, commerce, API, internal operations or regulated-workflow packs. Edit template fields, guidance, criteria and order, then save.
2. Choose an initiative and start or resume its playbook. Open each ordinary record and replace the prompts with your real evidence.
3. Resolve missing checks, then explicitly record your name, review note and confirmation. Pause or disable the pack when needed without deleting work.
4. Re-review steps after source evidence or pack guidance changes. Inspect duplicate record links if an imported template reference is ambiguous.

Keep in mind: A nonempty field is not proof. Self-review is not certification, and a regulated pack does not establish compliance. Advanced JSON editing is optional.

Open this area ↗

Why use it: Get targeted feedback while retaining control of local records.

1. In Backup & sharing, select a scoped review request, write questions and preview the exact file before downloading.
2. The recipient opens Feedback, imports the request, answers questions and downloads a response through their own browser.
3. Return the file manually. The requester previews the response, resolves conflicts and chooses the proposed changes to accept.

Keep in mind: No message is sent automatically. Names are self-reported; stale responses cannot overwrite newer work without review.

Open this area ↗

Why use it: Choose a useful starting point without learning every feature at once.

1. Open Tools and workflows.
2. Choose a product-management tool or browse the workflow catalog below.
3. Open the relevant workspace and try one small real task before expanding its use.

Keep in mind: Tools organize your records; they do not fetch missing evidence from external services.

Open this area ↗

Why use it: Find a suitable draft structure for your notes.

1. Search or filter the workflow library.
2. Inspect the workflow sections and available examples.
3. Open a workflow in Draft studio and supply its requested inputs.

Keep in mind: The 20 structures are local templates, not 20 external AI services.

Open this area ↗

Why use it: Understand what information a workflow needs before writing your own.

1. Open Examples and choose a workflow.
2. Read sample source text or download the local sample output.
3. Load an example in Draft studio, inspect how lines were organized, then replace it with your own facts.

Keep in mind: Sample outputs are demonstrations, not recommendations for your product.

Open this area ↗

Why use it: Start with organized source material and a reviewable structure.

1. Select a workflow and optionally link an initiative; inspect its captured context.
2. Paste text, load a sample, or import TXT, Markdown or field-mapped JSON up to 1 MB. Fill the requested fields.
3. Prepare the local draft and compare every section to its source. Save the draft and continue editing in Artifacts.
4. Save a reusable workflow configuration when helpful, or download the editable prompt bundle for manual use elsewhere.

Keep in mind: The engine groups source lines using rules. It cannot infer missing facts, translate, browse URLs or parse PDF, Word or audio. A prompt download never calls an AI API.

Open this area ↗

Why use it: Keep a draft's evidence, revisions and review decisions together.

1. Find a saved artifact by search, tag, product, initiative, type or lifecycle stage.
2. Edit sections and actions, including owners, dates, criteria and status. Save a revision; inspect previous content and differences.
3. Request review, record a local reviewer and approve the revision after checking it. Content edits reset approval.
4. Add named review comments, resolve or reopen them, and compare revision history. Save content changes before commenting; unresolved review work stays visible.
5. Preview Markdown, JSON, plain text, Jira, Slack or selected-action Jira CSV before exporting. Removal prepares a backup copy first.
6. To continue a process, choose the next workflow from the saved output. The new draft retains a link back to its source output; inspect both before sharing.

Keep in mind: Review names are self-reported. Export formats do not automatically send messages or publish issues.

Open this area ↗

Why use it: Prepare consistent first drafts for repeated work.

1. Choose a workflow and download its CSV sample.
2. Match input column names and preview the rows before processing up to 50 drafts.
3. Keep the tab open, review results and failures, download retry rows if needed, and export the selected format as a ZIP.

Keep in mind: Batch processing is local and foreground-only; it does not run a scheduled background job or verify conclusions.

Open this area ↗

Why use it: Avoid losing important terminology and constraints between drafts.

1. Give a context entry a name and write its product context or operating rules.
2. Save locally, reopen and edit it as the product changes.
3. Use it as reference when drafting; download a text copy when needed.

Keep in mind: Saved context is reference material; it does not automatically establish facts or change other records.

Open this area ↗

Why use it: Reuse a consistent instruction checklist.

1. Name a prompt template and write its instructions.
2. Save, edit or download the template locally.
3. Copy it manually only into a tool you choose and review that tool's data and cost rules separately.

Keep in mind: Saving or downloading a prompt does not execute it or connect to an AI provider.

Open this area ↗

Why use it: Keep control when moving devices or collaborating through files.

1. Download a full workspace backup regularly; it includes original sources and private local history. For a protected file, open Password-protected backup, enter and confirm a strong passphrase, then download the encrypted backup. Keep its password separately; lost passwords cannot be recovered.
2. For selective sharing, choose a product or initiative bundle, disclosure options and redactions. Inspect the exact preview and omissions before downloading.
3. To restore an encrypted backup, select the encrypted file, enter its password and choose Unlock and preview backup. Unlocking alone saves nothing. Import a backup or portable bundle and compare changes. Choose additions or replacements explicitly; for returned bundles compare base, local and incoming records and resolve conflicts.
4. Check storage health and backup reminders. Export raw storage for recovery if needed; reset only after keeping a usable backup.
5. Enable the optional offline app while online and wait for readiness. Reopen in the same browser; keep independent backup files.

Keep in mind: There is a 5 MB application limit. Optional encryption protects only the chosen backup file. Browser data, ordinary exports, safety backups and review bundles remain unencrypted, and browser cleanup may erase local work. Selective bundles omit private workflow history; no live synchronization occurs.

Open this area ↗

Why use it: Use existing team channels without granting this app account access.

1. Choose Jira, Slack, Notion, Confluence, email, GitHub, Linear or Asana in the handoff guidance.
2. Export the recommended format from a saved draft or use the delivery CSV handoff.
3. Inspect recipients, assignees, fields and sensitive information, then paste or import using your own external tool.

Keep in mind: Destination tools may need accounts or payment. This app does not connect to them or verify that the import succeeded.

Open this area ↗

Why use it: Know what to trust and what to review before using a draft.

1. Read How it works for supported inputs, local drafting and revision controls.
2. Check storage, sharing and developer-tool boundaries.
3. Use this guide's complete workflow directory to pick your next task.

Keep in mind: Automatic organization is not expert judgment, statistical analysis or identity verification.

Open this area ↗

Why use it: Choose what leaves your browser and understand who can see local work.

1. Read Privacy and control before storing sensitive notes.
2. Use an appropriate browser profile and protect your device; inspect every exported file before sharing.
3. Use disclosure previews for collaboration and keep full backups in a private location.

Keep in mind: There is no app login or cloud workspace. Anyone with access to your browser profile may access local records; having the public web link alone does not expose them.

Open this area ↗

Why use it: Move from a search result to the record that explains it.

1. Search the workspace or follow a direct record link.
2. Inspect the selected record and its context.
3. Use the linked editing area when you need to change it.

Keep in mind: This page needs a record kind and ID from your own workspace. A copied URL cannot share the record's contents.

Open this area through a record link or search result; an empty URL has no record to display.

Why use it: Read comfortably on a phone or desktop.

1. Use the Light or Dark theme control in the workspace.
2. Use Motion to pause decorative animation and parallax; your device's reduced-motion preference takes priority.
3. Navigate using keyboard focus and normal links; every task works without the 3D renderer.

Keep in mind: Decorative 3D objects illustrate the workflow; they are not a data visualization of your records.

Open this area ↗

Why use it: Reuse the same drafting engine in a local technical workflow.

1. From the repository, follow the README to run the CLI for module listing, a single draft or a CSV batch.
2. Developers can run the newline-delimited stdio MCP server; workspace-reading tools require an explicit portable file path. Optionally set PRODUCT_OPS_ALLOWED_ROOT or the CLI --allowed-root flag to restrict file access to a chosen folder. Inputs must be regular files of at most 5 MB; replacing an existing output requires explicit overwrite permission.
3. The repository VS Code extension offers PM Ops: Prepare Local Draft From Selection. Follow its packaging instructions if distributing it separately.

Keep in mind: These require local setup and are not website buttons. They cannot silently read browser storage; a third-party MCP host may have separate costs.

Open this area ↗

Use it when: you have source notes for meeting to execution and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 6 examples to see a sample input.
2. Replace the sample with your own meeting notes; context and objective; preferred output channel. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: executive summary · decisions made · action items · owner mapping · due dates · risks blockers · jira task drafts.

Important: The local engine organizes supplied text; it does not invent missing evidence or verify recommendations. Check the draft with the people responsible.

Try Meeting to Execution ↗

Use it when: you have source notes for prd to stories and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 6 examples to see a sample input.
2. Replace the sample with your own prd or feature brief; delivery constraints; target release or timeframe. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: feature summary · user personas · stories · acceptance criteria · edge cases · dependencies · risks.

Important: The local engine organizes supplied text; it does not invent missing evidence or verify recommendations. Check the draft with the people responsible.

Try PRD to Stories ↗

Use it when: you have source notes for weekly status pack and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 6 examples to see a sample input.
2. Replace the sample with your own project updates; reporting period; audience and tone. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: overall progress · completed · in progress · risks · blockers · next week · leadership summary.

Important: The local engine organizes supplied text; it does not invent missing evidence or verify recommendations. Check the draft with the people responsible.

Try Weekly Status Pack ↗

Use it when: you have source notes for release readiness pack and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 5 examples to see a sample input.
2. Replace the sample with your own release scope; readiness notes; known risks and open approvals. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: release summary · go live criteria · open risks · blocker owners · rollback plan · comms notes · approvals needed.

Important: Open approvals, rollback gaps and unknown criteria require human review; the draft does not authorize release.

Try Release Readiness Pack ↗

Use it when: you have source notes for stakeholder update builder and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 5 examples to see a sample input.
2. Replace the sample with your own project context; key update notes; audience and tone guidance. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: executive summary · key updates · wins · risks · decisions needed · asks · next steps.

Important: The local engine organizes supplied text; it does not invent missing evidence or verify recommendations. Check the draft with the people responsible.

Try Stakeholder Update Builder ↗

Use it when: you have source notes for roadmap decision brief and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 5 examples to see a sample input.
2. Replace the sample with your own decision context; options and tradeoffs; constraints and deadlines. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: decision summary · options reviewed · tradeoffs · recommendation · dependencies · risks · follow up questions.

Important: Recommendations reflect supplied notes; the toolkit does not choose strategy for you.

Try Roadmap Decision Brief ↗

Use it when: you have source notes for sprint retrospective synthesizer and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 6 examples to see a sample input.
2. Replace the sample with your own retro notes or sticky notes dump; sprint context; retro goal or facilitation focus. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: what went well · what to improve · action items · team sentiment · carry forwards.

Important: The local engine organizes supplied text; it does not invent missing evidence or verify recommendations. Check the draft with the people responsible.

Try Sprint Retrospective Synthesizer ↗

Use it when: you have source notes for bug report to root cause brief and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 6 examples to see a sample input.
2. Replace the sample with your own bug description; logs and reproduction notes; impact notes. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: root cause summary · severity · impacted users · fix recommendation · prevention steps · owner.

Important: A root cause or fix is only a source-backed draft. Reproduce and investigate the defect independently.

Try Bug Report to Root Cause Brief ↗

Use it when: you have source notes for customer feedback to product insights and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 6 examples to see a sample input.
2. Replace the sample with your own customer feedback dump; source context; analysis goal. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: top themes · sentiment breakdown · ranked feature requests · quick wins · strategic signals.

Important: Themes, rankings and sentiment headings do not establish a statistically measured breakdown. Inspect source coverage and contrary comments.

Try Customer Feedback to Product Insights ↗

Use it when: you have source notes for okr progress brief and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 6 examples to see a sample input.
2. Replace the sample with your own okr list; progress notes; blockers and context. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: okr health summary · objective status · key result scores · risks · leadership narrative.

Important: Supply verified measurements. A health or score heading is not a calculated aggregate of your objectives.

Try OKR Progress Brief ↗

Use it when: you have source notes for competitive analysis brief and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 1 examples to see a sample input.
2. Replace the sample with your own product context; competitor notes; launch or strategy goal. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: competitor matrix · differentiators · capability gaps · positioning recommendation · gtm implications.

Important: Supply dated competitor research yourself. This workflow does not browse competitors or verify current capabilities.

Try Competitive Analysis Brief ↗

Use it when: you have source notes for go-to-market strategy pack and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 1 examples to see a sample input.
2. Replace the sample with your own product or launch summary; target market notes; launch constraints and risks. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: target segments · channel plan · messaging pillars · launch timeline · success metrics.

Important: The local engine organizes supplied text; it does not invent missing evidence or verify recommendations. Check the draft with the people responsible.

Try Go-to-Market Strategy Pack ↗

Use it when: you have source notes for feature prioritization matrix and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 1 examples to see a sample input.
2. Replace the sample with your own feature candidates; scoring context; delivery constraints. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: evaluation criteria · rice scores · moscow tags · ranked feature list · recommendation.

Important: The draft does not independently calculate or validate all priority estimates. Use Planning or Choices for explicit numeric RICE comparisons.

Try Feature Prioritization Matrix ↗

Use it when: you have source notes for user interview synthesis and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 1 examples to see a sample input.
2. Replace the sample with your own interview notes or transcript; research goal; audience context. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: key themes · verbatim highlights · pain points · jobs to be done · product implications.

Important: The local engine organizes supplied text; it does not invent missing evidence or verify recommendations. Check the draft with the people responsible.

Try User Interview Synthesis ↗

Use it when: you have source notes for api specification draft and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 1 examples to see a sample input.
2. Replace the sample with your own api goal; entities and operations; security, compliance, or platform constraints. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: endpoint list · request response schemas · auth model · error handling · rate limits.

Important: Review every endpoint, schema, authentication and error-handling section with engineers. This is not a validated or deployed API.

Try API Specification Draft ↗

Use it when: you have source notes for quarterly business review and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 1 examples to see a sample input.
2. Replace the sample with your own quarter summary; kpi snapshot; next quarter context. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: kpi scorecard · wins · misses · next quarter plan · leadership asks.

Important: The local engine organizes supplied text; it does not invent missing evidence or verify recommendations. Check the draft with the people responsible.

Try Quarterly Business Review ↗

Use it when: you have source notes for product hunt launch kit and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 1 examples to see a sample input.
2. Replace the sample with your own product pitch; audience and product hunt category; launch day notes. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: tagline variants · short description · long description · maker comment · upvote strategy.

Important: Write and check the final copy yourself. No launch is published and no votes or promotional activity are automated.

Try Product Hunt Launch Kit ↗

Use it when: you have source notes for a/b test result brief and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 1 examples to see a sample input.
2. Replace the sample with your own experiment context; metrics and results; caveats and constraints. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: hypothesis · winner loser · statistical significance · business impact · decision.

Important: The engine does not calculate statistical significance, infer causality or decide a winner. Supply independently checked results and uncertainty.

Try A/B Test Result Brief ↗

Use it when: you have source notes for user journey map and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 1 examples to see a sample input.
2. Replace the sample with your own persona context; journey notes; business goal. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: persona summary · journey stages · touchpoints · emotional curve · pain points · opportunities.

Important: The local engine organizes supplied text; it does not invent missing evidence or verify recommendations. Check the draft with the people responsible.

Try User Journey Map ↗

Use it when: you have source notes for incident postmortem and need an editable first structure.

1. Open this workflow in Draft studio. Load one of its 1 examples to see a sample input.
2. Replace the sample with your own incident summary; timeline and resolution notes; follow-up context. Keep source references and unknowns visible.
3. Prepare a local draft. Check every section below against your source, fill gaps yourself, then save a revision.
4. Review the artifact and preview your chosen export before sharing it manually.

Sections to review: incident timeline · root cause · impact scope · resolution steps · prevention actions · sign off.

Important: Check the timeline, root-cause evidence and prevention owners. A sign-off section is not an authenticated approval.

Try Incident Postmortem ↗