Runlog docs

Start building

A plan buys a weekly allowance, sized for steady work.

Start

Run the business

Two lenses that turn the record into a running business: what the company is and should do next, and who it should reach. Both are part of an Enterprise agreement; the lenses are on the rail for everyone, and what they hold opens with the agreement.

01

Business

WebDesktopCLI

EnterprisePart of an Enterprise agreement. Ask

Four sections: ICP, Strategy, Profile, Config. The company brain (the focus company’s derived knowledge), the frameworks derived from it, the sales strategy those frameworks imply, and the guidance you steer it with. Every derived line cites the documents it was read from, so a strategy is a claim on the record rather than a paragraph.

02

People

WebDesktopCLI

EnterprisePart of an Enterprise agreement. Ask

Key Persons, Leads, Outreach. Leads are scored against the ICP with the reasoning shown, refreshed on a schedule; outreach is drafted from what the prospect said and did, and every send waits for your approval; nothing leaves without you. Sending capacity per channel is read before a queue is sized.

03

An Enterprise agreement

Quoted, never published. Beside these two lenses it carries SSO, audit export, invoicing, a BAA where one is needed, a dedicated deployment in your own cloud project, and Runlog under your brand for your own customers. On the API it unlocks the locked nodes the reference marks: the Business lane, outbound sends, category-wide schema migration. Pricing names them; Provision a customer is the white-label walk through the API.