Every module, one customer record.

these aren't bolt-ons that almost talk to each other. they're parts of one platform reading from one database. turn on what you need; it's all there when the work grows into it.

CRM

contacts, companies, deals, pipeline. the customer record everything else hangs off.

Proposals

build, send, e-sign. signed copies land on the record and move the deal along.

Portal & website

a customer portal and a public site on your own domain, with your branding.

Helpdesk

tickets, queues, configurable statuses, sla clocks that pause on the customer, saved replies, csat.

Jobs & dispatch

drag-and-drop scheduling, on-site forms, mobile sign-off, time straight to the invoice.

Docs

a knowledge base for runbooks, customer docs and a public faq, with suggest-as-you-type.

Billing

contracts, recurring subscriptions, one-off invoices, stripe payments, credit notes.

Procurement

purchase orders and supplier records tied to the jobs and tickets they're for.

Analytics

crm, helpdesk, billing, sla and csat in one place, one date range, click through to the records.

Vault

customer passwords and secrets, encrypted per tenant, shared only with who you choose.

staff records, leave and the people-admin that usually lives in a spreadsheet.

Claims

log and track claims against the customer and job they relate to.

Audit

a tamper-evident log of every change. how that works →

Arrange any of it the way you think.

the canvas is the workspace that ties the modules together. pull in the panels you need for the job in front of you, click a customer and everything re-scopes to them, save the layout. it's the same engine across every module.

Try the canvas →