/ Platform — Brand & documents

Your look, set once. Carried into every invoice.

Colours, fonts and voice live in one place per brand. Emails, estimates, invoices and posts all draw from it, so changing your look changes everything that goes out next.

Book a walkthrough→All eight areas
Brand & documents, in motion
/ 01 — What it does

Three things it does every day.

01

A brand look per brand

Palette, headline and body fonts, from a library or your own files. One account can run several brands, each with its own look.

02

Estimates and invoices in that look

Start from a layout or upload your current invoice and work from that. Each document gets a private link and a PDF.

03

Paid, without the chasing

Reminders before and after the due date, monthly statements, and an online Pay button once payments are connected.

/ 02 — Under the hood

What a careful buyer checks.

Numbering
Numbered per brand and type, taken atomically, so two invoices never share a number.
Void, never delete
Once a document is sent it can be voided, not deleted. Only drafts are removed.
No double reminders
Every automatic email is claimed once per document before it sends, so a customer is never mailed twice.
Payments
Card, Apple Pay, Google Pay and bank debit, paid out to your own Stripe account. Off until you connect it.
Deposit matching
With your bank connected, deposits are suggested against open invoices. A person confirms; nothing is marked paid on its own.
Fonts in email
Brand fonts load in Apple Mail and on iPhone. Gmail and Outlook show a matched fallback.
/ 03 — Connected to

Reachable from your own code.

API reference and keys
API
  • /documentsdocuments:read · write
  • GET /webhooks/deliverieswebhooks:read
Webhook events
  • document.sentDocument sent
  • document.viewedDocument viewed
  • document.acceptedEstimate accepted
  • document.paidInvoice paid
  • document.voidedDocument voided
MCP tools
  • list_documents
  • get_document
  • create_invoice_draft
  • mark_invoice_paid
/ 04 — In deployment

Where it already runs.

Every deployment
Endurance race serieso Live

Registrations, the newsletter and race-week messages lived in separate tools, so every race started from a spreadsheet.

Registration sync into one customer record per athlete, a brand look per race, and email from the series' own domain that pauses itself if a send goes wrong.

Read the deployment ->
Multi-location custom print shop^ Deploying

School and team stores, quotes and customer email ran on a site builder and an inbox.

A rebuilt store with every school and team store moved over, quotes that become pipeline deals, and the product catalog inside the email builder.

Read the deployment ->

See it on your business. A walkthrough, with your numbers.

Book a walkthrough→