One project record with two faces: a page stakeholders read, and a workspace the collaborators and agents work from. Built for the case where an agent is doing the building and a person is steering, and the record goes stale between check-ins.
When an agent is doing the building and a person is steering, the project record goes stale between check-ins. The agent knows what shipped. The stakeholder does not. Somebody writes an update three days later from memory, or nobody does.
What it does
Ticulate keeps one record with two faces. Stakeholders get a status page: what the project is, where it stands, what is next, what people have asked for. Collaborators and agents get a workspace behind it — decisions, architecture notes, open issues, the roadmap.
An agent finishing a piece of work posts the update itself, through MCP, at the moment it finishes. The page a stakeholder loads is the same record the agent just wrote to.
What the site had to prove
The strongest argument available was the product. Ticulate’s own project page runs on Ticulate — not a mockup of one, the actual page, updated the way any customer’s would be.
Around that: a how-it-works walkthrough, the agent and MCP integration docs, pricing, an FAQ, and beta positioning that says plainly what is and is not finished yet.