Our principles
Eight principles
We are building Five Dots around a small set of clear principles. They decide what we build — and, more often, what we refuse to.
We orchestrate. We don't replace the stack.
We are not building another CRM, workflow builder or BI tool. The product works by orchestrating the systems companies already run — your CRM stays the system of record, your call platform keeps the calls, your warehouse keeps the numbers. We supply what to look for across all of them.
Your data stays in your environment.
The diagnostic runs inside your own environment, through your own AI assistant and the connector permissions you grant. Raw records — contacts, deals, transcripts — never reach us. Only the aggregate findings that appear in your report are transmitted: counts, percentages, configuration facts. EU-hosted, deleted on request. The full split of what crosses the wire in each direction is on the data page.
We build on the AI infrastructure you already trust.
If your team already works in an AI assistant, that becomes the interface — we ride the infrastructure you have rather than forcing another tool-adoption motion. Today that is Claude, connected over an open protocol; the approach extends to whatever assistant your team trusts next.
RevOps value starts with foundations.
Before advanced automation, a company needs clarity on system structure, data quality, process design, the flow from lead to close, and whether its reporting can be believed. The first job is not to automate everything. The first job is to understand what exists and what is usable — automating on top of a broken foundation just produces mistakes faster.
Recurring value, not one-off output.
RevOps is not a one-time audit; it is an operating discipline. The product is built to be run, acted on, and run again — so the second report can say what moved, not just repeat what is wrong. That is why it is a subscription and not a PDF.
Humans stay in control.
Recommendations, orchestration and insight can be automated. Control cannot: approvals, decisions and anything that touches your customers stay with you. We hold ourselves to the same rule — no operator here can hand-edit a score, and nothing changes in your systems unless someone on your side does it.
Domain expertise is the moat.
The technology matters, but the edge is knowing what to check, what matters, and what to do next — accumulated across Revenue Wizards’s operating work inside real revenue teams, not derived from a prompt. The skills library lists every check by name; the methodology and remediation playbooks behind them are the product, delivered into your own Claude to run.
Simplicity beats service-heavy delivery.
You should be able to start without calls, onboarding projects or custom support — one plan, one price, connected in an afternoon. Where a human is involved, it is because a human adds judgement, not because the product needed hand-holding to work.
If one of these turns out to be wrong, we would rather change it in public than defend it in private — how we work through that is on the building-in-public page.