Features · Revenue operations
Run the revenue on the record that designed the job
The spatial engine wins the work — this is the plane that keeps it. Renewals, orders, invoices, and collections live on the same records the job was designed and installed on, so the money never detaches from the model.
Renewal pipeline
Renewals that never go quiet
Every renewal is a record with an owner, a date, and a status workflow — attached to the project it came from. The design record behind it makes the renewal conversation concrete: what was installed, where, and what it does.
- Pipeline with a status workflow — no renewal lost to a forgotten date
- Value and cost tracked on the record, feeding pipeline metrics directly
- The install history behind each renewal lives on the same project plane
A renewal, on the record
- Status
- workflow with an owner and a date
- Value
- tracked on the record itself
- Pipeline
- computed live from renewals
- Context
- the project it renews
Orders & shipments
Orders in, tracking out
Order management with shipment tracking through delivery — and an import path that turns order confirmations, emails, and PDFs into structured orders instead of retyped ones.
- Document and email import that lands as structured, reviewable orders
- Shipment tracking carried on the order through delivery
- Orders feed revenue metrics and the customer portal from the same records
The order path
- In
- emails and PDFs, parsed
- Tracked
- shipments through delivery
- Out
- revenue metrics and the portal
- Copies
- none — one record
Invoices & collections
AR that names the risk
Invoices, aging, and collections workflows on live balances — with customer risk scored by credit utilization and dollars past due together, not age buckets alone. How much of the credit line is consumed, and how much money is actually late.
- Invoice aging and collections workflows on real open balances
- Risk scoring that weighs credit utilization alongside dollars past due
- Vendor bills, credit memos, payments, and a general ledger on their own plane
The risk inputs
- Utilization
- credit line consumed
- Past due
- dollars actually late
- Aging
- context, not the whole score
- Result
- risk you can act on
Financial dashboard
One dashboard, one writer per metric
Revenue, AR, and pipeline are computed live from orders, invoices, and renewals — the records themselves, never a second copy. Net-new concepts get their own plane: recurring services for MRR and ARR, vendor bills for AP, credit memos, ledger entries.
- Revenue, AR, and pipeline read live from the source records
- MRR and ARR tracked on first-class recurring service items
- No metric is duplicated into a second collection — so no two screens disagree
Source of truth, per metric
- Revenue
- orders, live
- AR
- invoices, live
- Pipeline
- renewals, live
- MRR / ARR
- recurring service items
The structure that keeps the numbers honest
Structural facts about how the records are wired — no invented benchmarks.
- One source
- revenue, AR, and pipeline from live records
- orders · invoices · renewals — never a copy
- Emails → orders
- documents parsed into structured orders
- with shipment tracking through delivery
- Two inputs
- AR risk: credit utilization + dollars past due
- not age buckets alone
- MRR / ARR
- recurring services, first-class
- alongside AP, credits, payments, ledger
Revenue operations questions
Is this a replacement for our accounting system?
It is the operating plane for renewals, orders, invoices, and AR risk — with vendor bills, credit memos, payments, and a general ledger tracked alongside. It complements your books rather than replacing them: the dashboard reads operational truth from the records the work actually runs on.
Where do the dashboard numbers come from?
Revenue, AR, and pipeline are computed live from orders, invoices, and renewals — the records themselves, not copies. Recurring revenue, AP, credit memos, and ledger entries have their own collections. No metric has two writers, so no two screens disagree.
How is AR risk scored?
By credit utilization and dollars past due together, not age buckets alone — how much of the customer’s credit line is consumed, and how much money is actually late. Aging is context; the score is built from the two inputs that predict collection trouble.
Can our customers see their own orders and renewals?
Yes — through the white-label customer portal, which reads the same source records this page describes. Nothing is exported or re-keyed for the portal; it is another window onto the one set of records.
Keep the revenue attached to the work
Renewals, orders, and AR on the same records the job was designed on. Talk to us about your renewal book.