You know the number and the scope before anything starts. Most builds go live in one to three weeks. These are the actual prices, not starting points — they only move if you change what you asked for.
Sample data, fictional company
Published prices. The build is fixed — you agree it before we start, and it does not move unless you change the scope.
Your existing dashboards migrated, unlimited logins, row-level security, self-service upload with automatic sync, custom validation and mapping, weekly snapshots to leadership, and your own branded address.
Or start smaller and grow into it
The monthly fee is not unlimited work, and pretending otherwise would only cause an argument later.
You approve the scope and the price before anything starts. If the scope changes, we requote — the number never moves quietly.
Code, data, accounts and documentation are yours. Everything runs in your tenancy, on your subscriptions.
We sit with whoever will run it and explain it in plain English, then leave written notes they can use later.
Anything that breaks in the first month after handover, we fix. It is part of the price, not an upsell.
It is rarely the thing people expect. The dashboard is the easy part; getting trustworthy data into it is the work.
One clean database is quick. Six systems, three spreadsheets and an inbox is the part that takes the time — not the dashboard on the end.
If the same customer is spelled four ways, that gets fixed before anything can be trusted. We will tell you at the audit stage if this is you.
A tool for two analysts is not the same build as a portal fifty people log into with different permissions.
Hourly billing makes you pay for our learning curve and puts us on opposite sides of every decision. A fixed number means you can approve the work on its merits, and it is our problem if it takes longer than we thought.
We stop and requote that piece. Small additions usually get absorbed; anything that changes the shape of the build gets its own number before we touch it. You will never get an invoice you have not already agreed to.
Almost always, yes. Most engagements start with what you already pay for — Microsoft 365, Google Workspace, your CRM, your accounting system. We only recommend new tooling when the existing stack genuinely cannot do the job.
Open-ended research and anything where nobody can say what “done” looks like. If that is the situation, take the audit first — that is exactly what it is for.
The audit is paid up front. Build sprints are split — half to start, half on handover. Retainers are billed monthly in advance. Bank transfer or card, and you get a proper invoice either way.
Usually within one to two weeks. Tell us your deadline in the first message and we will say honestly whether it is realistic before you commit to anything.
Yes — completely. You own the code, the dashboards, the pipelines and the data. Everything is handed over with documentation and a walkthrough, and nothing is locked to us. If you never speak to us again after handover, what we built keeps running.
Your data stays in your systems. We work on a least-access basis — the minimum permission needed to do the job, and no more — and we do not retain client data beyond what a project actively needs. Where a build has to move data, it moves between your systems, not through ours.
AI closed the gap between what one person can design and what one person can actually finish, which is why work that used to need a team and a quarter is now one build in one to three weeks at a price agreed up front. It is not AI sprinkled on the product. Everything is still tested and reviewed before handover: speed is the benefit, and the quality bar does not move.
Every build includes a support window after handover. After that, the $199 a month covers fixes, monitoring and minor changes — and anything larger is scoped and quoted before we start it.
Describe the problem in a few lines. You will get a real reply within one business day telling you which engagement fits and roughly what it costs — not a brochure.