Do we have to change the tools we use?
No. We work inside the tool you already use, whether that is Power BI, Tableau, Looker, Metabase or spreadsheets. If you have none, we recommend one that fits your size and budget, and explain why.
Finance, sales and operations each report a different total, and someone spends days finding out why. We're a data analytics service: we agree on the few numbers that matter, then build the dashboards and automated reports your team opens instead of asking for an export.
Billing and reporting automated for a US logistics company, with live dashboards on over 2M records a day. Read the case study
We work hands-on with: Python, Power BI, Tableau, Looker, Metabase, Apache Superset.
DharmOps is a data infrastructure engineering firm, and this is the service that covers the part of your data your team sees every day: the reports.
Your orders, invoices, customers and stock sit in several systems, and each system reports in its own way. Before any report can be built, someone has to pull the numbers out, clean them up and put them side by side. That person is usually in finance or operations, and they do it again every week or every month.
Data analytics, in this service, means ending that cycle. We agree with you what each key number means, connect your systems so the numbers come from one place, check the data as it arrives, and build the dashboards and automated reports on top.
Two terms, in plain words. A dashboard is a screen that shows your key numbers and updates itself. An automated report is a report that builds and sends itself on a schedule, instead of being assembled by hand.
What you get is a set of reports your team can read without asking someone to prepare them, and numbers that match no matter who quotes them.
You do not need a data team, a warehouse or any technical knowledge to start. You need reports that matter to the business and someone who can tell us what the numbers should mean.
Four causes explained why the reports could not be relied on.
The rules lived in people, not in a system.
Several variable billing rules were applied by hand, order by order, so they had to be written down before anything could be automated.
Nothing sat between the sources and the reports.
Data came from several places with no single version anyone fully relied on.
Quality checks were manual and late.
Errors showed up after the reports had gone out.
Only technical staff could get answers.
Operations, billing and management had to ask for every number.
A quick lookup. Every row maps to one of the seven pieces listed below.
| Situation | What we build |
|---|---|
| Finance, sales and operations quote different totals | Agreed definitions for your key numbers, written down in plain words |
| Data lives in spreadsheets, accounting, orders and a CRM, and none of them match | One source that your reports draw from, with checks as data arrives |
| Everyone waits on one person for numbers | Dashboards by role, so each person sees the numbers they use |
| The weekly or month-end report is built by hand | Automated reports that build and send themselves |
| You find out about problems at month-end | Alerts when a number moves outside its normal range |
| Dashboards exist but nobody opens them | Training and a walkthrough, plus a check on whether people are using them |
| You want someone to keep it running as the business changes | Ongoing support |
One service, delivered through these seven pieces. You choose which ones you need, and we scope them after the first call.
We sit down with the people who own the numbers (finance, sales, operations) and agree what each key figure means: how it is calculated, which system it comes from, and who owns it.
You receive: A short written list of your key measures, each with a plain-language definition, a source and an owner.
The same word means the same thing in every report, so the argument about whose number is right stops.
We connect your systems (spreadsheets, accounting, orders, CRM and similar) so the data lands in one place. It moves through three stages: as it arrived, checked and corrected, and ready for reports.
You receive: One set of report-ready data, documented, with access set by role so each person sees only what they should.
Every report draws on the same version of the data, and mistakes are caught before they reach a report.
We build a dashboard for each group that uses numbers: owner, sales, operations, finance. Each shows the handful of figures that group uses, with detail one click below.
You receive: The dashboards, set up in the tool you use or one we recommend, plus a short guide to reading them.
People find their own answers without waiting for someone to prepare a report.
We take the reports someone builds by hand every week or month and make them build and send themselves on a schedule.
You receive: The automated reports, delivered where your team already reads them, and a note on how each one is produced.
The report is ready when you need it, not when someone has time to build it.
We watch the data for unusual activity and message the right person when a number moves outside its normal range.
You receive: Alerts for the numbers that matter to you, sent to the person who can act on them.
You find out about a problem the same day, not at the next audit.
We walk your team through every dashboard and report, and write down how each one works.
You receive: Documentation your team owns and a team that knows how to read and use what was built.
A report nobody opens saves no time, so the walkthrough covers how to read each one, not only where to find it.
We stay on after the walkthrough to keep reports accurate as your business and systems change, and to add new reports when you need them. Each month we review which reports are being used and which numbers are still built by hand.
You receive: A named team that knows your setup and keeps it working, and a monthly review of how the reports are used.
Reports break quietly when a system changes. Someone who already knows the setup fixes it quickly.
You tell us which reports cost the most effort or cause the most arguments, and which systems the numbers come from. A list of your current reports, or a screenshot of one, is enough. You do not need a finished problem statement.
30 minutes · scheduled on our booking page
We look at the reports and systems you use and write down where the numbers disagree.
We build in stages: the agreed definitions, the connected data, then the dashboards and automated reports.
The timeline is set out in the written scope
We walk your team through every report, give you the documentation, and stay on to keep the reports accurate.
Ongoing support has a 3-month initial term, then runs month to month. Either side can end it with 30 days' written notice
We work inside the tools you already use. If you do not have any, we recommend one that fits your size and budget. You do not need to know any of these: we choose with you and explain what each does.
| What | Tools we work with |
|---|---|
| Dashboards and reports | Power BI, Tableau, Looker, Metabase, Apache Superset |
| Where your data comes from | Spreadsheets, accounting systems, order and inventory systems, CRM, and databases such as PostgreSQL |
| Moving and checking data | Python, SQL, Apache Airflow |
From the logistics project.
| Area | Before | After |
|---|---|---|
| Billing calculation | Applied by hand to every order | Automated, applied the same way every time |
| Reporting | Built when someone asked, from several sources that disagreed | Live dashboards used by operations and management |
| Finding bad data | Manual audits, days after the damage | Flagged close to real time |
| Who can get answers | Whoever is technical | Role-based self-service |
| Volume | Handled by hand | Over 2M records a day through a reliable daily pipeline |
| Basis | DharmOps | Spreadsheets and a part-time analyst | A BI-tool vendor's services |
|---|---|---|---|
| Who agrees what the numbers mean | We do it with your finance, sales and operations owners, and write it down | Depends on whoever has time | Rarely part of the offer |
| What you get | Agreed definitions, one data source, dashboards and automated reports | Whatever the person has time to build | Dashboard templates in their tool |
| Who owns it afterward | You do, with documentation | Often only the person who built it | Tied to the vendor's platform |
| After launch | We stay on to keep it accurate | Depends on that person's availability | Support for the tool, not for your numbers |
| Walkthrough | Walkthrough and documentation | Usually none | Training on the tool |
No. We work inside the tool you already use, whether that is Power BI, Tableau, Looker, Metabase or spreadsheets. If you have none, we recommend one that fits your size and budget, and explain why.
Each stage is priced separately, and you see the price before you approve it. The first step is a 30-minute discovery call. The price for the work is quoted in the written scope, after the call. Four things affect it: how many systems the numbers come from, how many reports and which roles use them, the condition of the data, and whether you want a one-time project or ongoing support. We don't publish a fixed price list, because a fixed price given before anyone has looked at your reports is a guess.
No. Scoping, the work and ongoing support are separate stages, and you decide at each one whether to continue. Ongoing support has a 3-month initial term, then runs month to month, and either side can end it with 30 days' written notice. What we build is documented and yours, so stopping doesn't leave you dependent on us.
It is a 30-minute conversation, not a presentation. We ask which reports cost the most effort and which systems the numbers come from, and we tell you plainly whether we can help. You get a written summary within 24 hours of the call. If it is a fit, we scope the work and show you the price before it starts. Bring a list of your current reports, or a screenshot of one.
No. You need people who know what the numbers should mean and who use the reports. We do the technical work and explain it in plain words. Each dashboard shows the few numbers its users need, with detail one click below, and we walk your team through how to read each one.
Yes. We sign an NDA before we get any access. The first call needs no paperwork. Access is read-only, you approve it before it is created, and it is limited to what the work needs. We copy your data out of your environment only with a documented reason and approval, and when we do, it is encrypted, logged and deleted at the end, with the deletion confirmed. If your data includes personal data, we also sign a data processing agreement.
Hire one when the work will keep a person busy and you have someone to manage them. A service fits when the reports and definitions have to be set up first, when the work doesn't fill a full-time role, or when the one person who builds the reports is also the one who can leave. Either way, the documentation we write is for your team to run, so a later hire inherits it.
Before building, we agree with the people who own the numbers what each one means, so the dashboard shows the figures they already argue about. Each dashboard is built for one role and shows only that role's numbers. We walk your team through reading each one. If you stay on, a monthly review shows which reports are being used and which numbers are still built by hand.
We tell you before building on it. If the data needs cleaning up and testing first, that is our Data Reliability work, and we can scope both as one project so the fix happens before the reports, not after.
You own the reports, definitions and documentation from the start. The timeline is set out in the written scope, because it depends on how many systems the numbers come from and how clean the data is. For reference, the logistics project ran roughly 18 to 20 months, because it also automated billing, added monitoring and connected live data to the client's customer-facing systems.
Reporting problems look different in each business. These are the situations we are asked about.
Billing rules applied by hand and reports built on request. This is the situation in the case study above.
Sales, stock and marketing numbers sit in separate tools, so the weekly report is a day of copying and pasting.
Production, stock and sales figures live in different systems and are combined by hand for the monthly review.
Hours, billing and project status are tracked in several places, so client reports and management reports disagree.
Describe the report that costs the most effort, or the two numbers that never match. We'll scope the right fix, one-time or ongoing.