Pages
The documents, kept current.
Strategy, audience research, the content plan, and every operating doc the engagement needs — written where the work happens, so they do not go stale the week after they are handed over.
This is the real interface, running on made-up data in your browser. Click anything, switch business from the sidebar, or open it full screen.
Your wiki, maintained.
Most engagements produce a strategy document once, in the first month, and never open it again. Pages is the version that stays alive: a tree of documents you can browse, read, and comment on at any hour, kept in sync with the work rather than filed beside it.
It is a real editor, not a viewer. Rich text, images, files, code blocks, and links to other pages and boards. Several people can write in the same document at once and see each other doing it — collaborator avatars, live cursors, and comment threads anchored to the exact text they are about.
Everything is markdown underneath, which is why it exports cleanly and why an AI assistant can read it. That matters more than it sounds: a document a machine can read is a document that can be used by an automation, an audit, or an agent later.
Inside Pages
Write together
Several people in one document, live, with cursors and avatars.
Comment in place
Threads anchored to the exact text they are about.
Organise as a tree
Nest pages under pages, as deep as the work needs.
Embed anything
Images, files, code blocks, and links to boards and cards.
Set who sees it
Client-visible or internal, per page, inherited by children.
Export to markdown
Take any page with you, any time, as plain text.
Open the docs.
Book a 30-minute call. We'll go through what's working, what isn't, and what the first move should be. If we're not the right fit, we'll say so on the call.