Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.runwita.com/llms.txt

Use this file to discover all available pages before exploring further.

Sometimes you need a journey out of Runwita and into someone else’s hands. A handover doc for a colleague, a status pack for a manager, a snapshot for a customer review. The PDF export is built for those moments.

​
How to export

1

Open the journey

Click into any journey from the Journeys list, Home, or via ⌘K.
2

Open the Options menu

Top-right of the journey header, click Options ▾.
3

Click 'Export as PDF'

The button changes to Exporting… for a few seconds while Runwita captures the live page and builds the structured layout.
4

Pick a save location

A native macOS save dialog appears with a default filename of Customer - Use case.pdf in your Downloads folder. Adjust if you want, then click Save.
5

The PDF opens in Finder

Runwita reveals the file in Finder once it’s written. Open it with Preview, Acrobat, or whatever you use.

​
What’s in the PDF

The export is two parts: Page 1: a screenshot of the live journey. Exactly what you were looking at when you clicked Export. Same hero, same open threads, same right-rail intelligence. If you want the manuscript-feel cover, this is it. Pages 2 onwards: structured content. Same data as the live view, rendered in a print-styled layout designed for paper:
  • Hero, mirroring the Where we stand header. Active status, customer + use case, engagement count, months in, owner, last touch.
  • Open threads, every non-resolved topic with its full chronological touchpoint history (date, state, note per row). Resolved topics get a brief tail at the end of the section.
  • Engagements, in reverse chronological order. Title, date, summary, sections, decisions per engagement.
  • Open actions, sorted by due date, with owner and due date inline.
  • Footer, journey identity on the left, generated date on the right.

​
Why both formats

The cover screenshot is for vibes. It looks like Runwita, it carries the brand, and it’s instantly recognisable to anyone you’ve shown the app to before. The structured pages are for use. Text is selectable, copy-pasteable, searchable in any PDF reader. Someone reviewing a thirty-page handover doesn’t want to OCR a screenshot to find a name. You get both, because both matter.

​
What’s NOT in the PDF (yet)

  • No customer-shareable mode. Every export today is Internal: it includes intelligence outputs (sentiment, deal health, stakeholders), every internal-flagged action, and every engagement note. If you want to share with a customer, eyeball it first or wait for the customer-shareable mode.
  • No multi-journey export. One journey at a time.
  • No scheduled exports. Trigger manually each time.
  • No branding controls. Logo, footer text, header bar are fixed in v1.
These are deliberate v1 cuts, not bugs. They appear when there’s real demand.

​
When the cover capture fails

Occasionally the live screenshot capture fails (a transient render error, an intelligence panel that’s still mid-fetch, a Mac display in the middle of a resolution change). When that happens, the export degrades gracefully: you get a structured-only PDF with no cover, no error message, no failed save. The data is still there, it’s just less pretty. If you find yourself getting structured-only PDFs reliably, file it as a bug at contact@runwita.com.

​
What’s next

Journeys

What the export captures.

Intelligence

Run intelligence first if you want the deal health score on the cover.