What you can audit
Every Make It Happen engagement includes a dashboard built inside the client's own product. It shows progress and results while the work is happening, from the client's own data, so the numbers can be checked rather than taken on the word of the party being evaluated.
We don't tell you the results. You can audit them yourself. The dashboard goes live during delivery rather than after it, inside your own product and on your own data, and it opens on a phone at eleven at night without a login you have to ask us for. The word that matters is audit: you are not being shown results, you can check them.
The normal agency relationship runs on asymmetry.
The agency knows what happened. The client receives a summary written by the party being evaluated. Nothing in it is verifiable, so the relationship runs on trust, and it degrades the first time a number looks wrong. Then comes the month spent arguing about the report instead of the work: the client asks for the raw export, we explain the methodology, and nothing moves. We invert it. You see the same data we see, in your own product, whenever you want, without asking. A number you can check does not have to be believed. That is why this is a position and not a feature — a feature gets cut from a scope to protect a date, and this does not get cut.
Seven rules the dashboard is held to.
There is no published build specification for this yet: every implementation re-derives the pattern, which is worth admitting and is something we intend to fix. What exists is the standard, and it is not negotiable downward. These seven are what a dashboard has to do before we call it delivered.
Figures reconcile, and it shows
Every number on the screen reconciles to the source it came from — to the cent wherever money is involved — and the reconciliation state is shown openly, including when it fails. Hiding the reconciliation is exactly what makes the rest of the numbers unbelievable, so it sits next to them.
Mobile first, because of when
An owner opens this on a phone, at night, after the operating day is over, standing in a kitchen. So it is designed at phone width first, readable with no training and no legend to decode, and loaded in under three seconds on mobile data rather than on office wifi.
Opens on the latest period
It opens on the most recent period, already loaded. No date range to set, no filter to choose, no saved view to remember: the thing you came to see is the first thing on the screen. Configuration is there for the questions that come after that one, never for that one.
Honest about the data's limits
Where a query is capped, a sample is bounded or a source has not reported yet, the interface says so on the number itself. A dashboard that silently truncates is a dashboard that lies, and one wrong total teaches the owner to distrust every other total on the page.
Private by default
The default view is aggregate. Individual records are not browsable out of curiosity: opening one takes a specific reason and a permission that says so, and the opening is logged. Most operating questions are answered by a total, and the ones that are not should leave a trace.
Role aware
Different people see what is theirs. A salesperson sees their own pipeline, a manager sees the team, an owner sees everything, and a third party outside the company sees only the slice the agreement covers. Roles are edited from a panel rather than from the code, so a new role does not wait for a deploy.
Engineered for cost
Every block on the dashboard has an explicit read budget and a row cap, sized against the real limits of the accounts it runs in. A dashboard that works on demo data and collapses on production data is not delivered, and neither is one that stays up by quietly multiplying reads behind every refresh.
You cannot buy this, and you cannot decline it.
It is in every engagement and it has no line of its own, because the moment it becomes a line it becomes the line that gets cut when a date tightens — and the engagements that most need auditing are exactly the ones under pressure. Charging for visibility would also mean selling you the right to check our work, and that is not for sale. It goes live during delivery, at stage seven of nine, not at handover, so it is watching the work while the work can still change.
Questions buyers actually ask
Is this just another monthly report?
No. A report is a document we write about ourselves; this is a screen in your own product reading your own data, live. You open it at any hour without asking, you see the same figures we see, and each figure shows what it reconciles to. There is no version of it we edit first.
Can I check the numbers myself without asking you?
That is the whole point. Each figure states its source and its reconciliation state, so you can trace a total back to the records behind it. Where a query is capped or a source is late, the screen says so instead of rounding the problem away. The access is yours, in your own accounts.
What happens if your numbers don't match mine?
We reconcile to your source and publish which of the two was wrong. Most mismatches are definitional: a different date boundary, a cancelled order counted another way, a duplicate. The fix is to write the definition down where both sides can read it. The reconciliation state exists so that conversation starts from evidence.
Does the dashboard cost extra?
No. It is included in every engagement and never sold separately, and that is deliberate: a separate line is the line that gets cut when a date tightens, and the projects under the most pressure are the ones that most need auditing. There is nothing to add to a scope and nothing to decline.
When does it go live, and do we keep it after the project?
It goes live during delivery, not at handover, so it is watching the work while the work can still change. It is built inside your product and runs in your accounts, so it stays when the engagement ends, along with the documentation to operate it. Nothing switches off when we stop.
The possible part of the impossible.
If you have an idea that shouldn't work, bring it. We will tell you which part is genuinely impossible and which part is only hard. Most of it is the second one.