Reporting

Reporting: Rep Production, the Customer Book, and the Audit Trail

Every platform has reports. The ones worth having answer a question somebody in your office was already arguing about.

7 min read 5 screensPublished

Rep production

Sold work against quota, per rep and per trade, with the sales activity (calls, appointments, bids out) folded into the same screen instead of living on a separate scoreboard nobody opens.

The rep production screen showing booked revenue against quota per rep, per trade, with a monthly chart and sales activity figures.
Sold against quota, by rep and by trade, with the activity behind it.

Two monthly numbers on this page can legitimately disagree, and the page says so out loud instead of quietly picking one. One counts a job in the month the work lands. The other counts it in the month it was sold. A job sold in July and scheduled into August is counted by both, in different months, and both are right: they are answers to different questions.

Forcing those into one number makes both of them wrong. This codebase tried it once and reverted it, and there is now a test that fails if anybody tries again. A small line under each figure says which rule it is using, so nobody has to relitigate it in a meeting.

Who you work for

Accounts are the builders. Contacts are the people at them. They are two screens because they are two different questions, and running them together is why so many CRMs are unusable for a subcontractor.

The accounts screen listing builder companies with their job counts and values.
Every builder you work for, with their book of work beside them.

The contacts screen answers the question an office actually asks at 8am: who do I email about this invoice, and is that address any good. One row per person, with the company beside them, what they do there, and when anybody last heard from them. Every email and phone number on it is a link: tap and it dials.

The contacts directory with one row per person, showing their account, role, email, phone and last activity, with search and filters.
One row per person. Everything is tappable, and a contact with no company is called out rather than left blank.

It also names the gaps instead of leaving a blank cell: no email on file, no company attached, nobody marked as the one who pays the bills. Those blanks are why a reminder never got sent, and they are fixable in ten minutes once somebody can see them all in one place.

What happened, and who did it

The record of everything anybody did can be read and added to. It cannot be edited or cleared: not by an administrator, not by the owner, and not by us.

When our support signs into your workspace to help you with something, that is written into your own log too. That is a promise you can check rather than one you have to take our word for, which is the only kind worth making.

The audit log listing actions with the person who performed them, the job affected and the time.
Add-only, permanent, and it includes us.

Settings

Roughly forty cards, sorted into categories, with a search across all of them. The ones that matter change how the software behaves rather than how it looks. Which trades you run. Your invoice terms and numbering. Whether change orders are approved online or by phone. How the reminders escalate and what they say. And which optional parts are switched on at all.

The settings screen with categories down one side and cards for company profile, invoicing, integrations and module switches.
Categories on the left, one card per decision, searchable across all of them.

Every screen on this page is the software running, captured from a demo workspace. The builders, addresses and contacts in it are invented; the plan is one we drew. More at Opulence Built.

See it on your own jobs

Twenty minutes, your pipeline, and whoever on your team would actually be using it.