CSV export (contacts + orders)

Get your data out: one-click CSV downloads on the contacts and orders lists, built client-side from the rows the page already holds (RFC 4180 quoting, UTF-8 BOM for Excel, money written as the L-MONEY string — never parsed). The shared helper lib/csv.ts is the pattern for any list page.

If you are building a front end

Your front end calls this over the same-origin `/api/v1` proxy — no backend code to write, no schema to design. Endpoints: none — client-side from list data.

Bring any front end — hand-written, or generated with Lovable, v0, Bolt, Claude, or Cursor. You get auth, a multi-tenant database, payments through your own Stripe, and email/SMS without writing or hosting a backend.

How to turn it on: Always on where the lists render.
Who can use it: inherits the list's read permission (no new surface).
The API behind it: none — client-side from list data
Where it lives: /crm/orders

See it in context

Revenue intelligence — the full walkthrough, step by step: Pipeline health, job margins, forecasts — the numbers, from the system of record.

Machine-readable

This page is generated from our published capability catalog. Point your AI assistant at /features.json (or /llms.txt) and it can read every feature, how to enable it, and the endpoints behind it — then build against them.

CSV export (contacts + orders)

If you are building a front end

Your front end calls this over the same-origin `/api/v1` proxy — no backend code to write, no schema to design. Endpoints: none — client-side from list data.

How to turn it on: Always on where the lists render.
Who can use it: inherits the list's read permission (no new surface).
The API behind it: none — client-side from list data
Where it lives: /crm/orders

See it in context

Revenue intelligence — the full walkthrough, step by step: Pipeline health, job margins, forecasts — the numbers, from the system of record.