Business intelligence services. From scattered data to numbers people trust.
We take the data your company already has and build the reporting it runs on: finding where the data lives, agreeing what each number means, automating the collection, then building the dashboards and scheduled reports on top.
- Starts with
- A look at the data you already have
- Connects to
- Your CRM, spreadsheets, databases and custom APIs
- First result
- A single dashboard or report in one to two weeks
What does business intelligence cover?
- Business intelligence
- The whole job: taking the data a company already has and turning it into numbers people trust and act on. It covers the data, the definitions, the pipeline, the reporting and keeping all of it current.
- A dashboard
- One thing that work produces: agreed figures on a screen, for leadership and for each team.More on custom dashboards
- Data automation
- The part underneath: collecting, checking and reshaping the data on a schedule, so nobody assembles it by hand.More on data automation
- A scheduled report
- The same numbers sent weekly or monthly to the people who will not open a dashboard.
What does the service include?
What we build after the first step depends on what it finds. It is usually some mix of these six.
Data discovery
A clear picture of your sources and how they connect, including the manual steps between them.
Metric definitions
One agreed meaning for each number, and a named owner for it, because a metric nobody owns is a metric nobody acts on.
Data integration
Connections to your CRM, spreadsheets, databases and custom APIs, fitted to your current stack.
Automated pipelines
Collection, checks, reshaping and sending run on a schedule. When a source is down or a check fails, the run stops, keeps the last good figures and tells someone.
Dashboards and scheduled reports
An executive view and team-level views of one set of numbers, and the reports that go out from them each week or month.
Keeping it current
Updates to sources, definitions and views as the business changes, so the reporting keeps matching it.
How an engagement runs
Five steps, always in this order. The dashboard is step four, which surprises people. Pick a step to see which part of the system it builds.
How long does it take?
| What you start with | How long it takes |
|---|---|
| A single dashboard or report | One to two weeks, on a single, clean source. |
| Several data sources | Usually four to ten weeks, with milestones agreed before we start. |
| Data that needs cleaning first | Longer, and we tell you before we start. If some of it only exists on paper or in someone's head, capturing it is the first job. |
What drives the cost?
This site lists no price for this work, because it depends on what the first step finds. These are the things that move it, with us or with anyone else.
How many sources there are
Each system is another connection to build, check and keep running. One clean source sits at the small end of the range above.
The state of the data
Figures that disagree, have gaps or live only on paper have to be settled or captured before anything can be built on them.
How many views and metrics
Every extra audience needs its definitions agreed, an owner named and a view kept up to date, so it pays to start with the numbers somebody will act on.
Which kind of tool
A BI tool you already pay for adds nothing new to host. An open-source tool avoids a licence for every seat but has to be set up. A coded dashboard is more to build, and is what you need inside your own product.
How often it refreshes
A report that runs once a month asks less of the pipeline and the source systems than one that has to be current through the day.
What happens after launch
Sources and definitions keep changing. Ask what keeping it current will cost, not only what the first version costs.
What should you ask a provider?
Put these to anyone you are considering, including us.
- Will you look at our data before you propose a dashboard?
- Who owns each metric once it is built, and what decision is it for?
- What does a report do when one of its sources fails?
- Does our team keep the logins, and what do we hold if we stop working with you?
- What can you show us running, and is it client work, your own product or a sample?
What we can show you today is a working sample dashboard, a sample run you can break, and the reporting inside DenwaysHR, our own product.
Questions about business intelligence
How the tool gets chosen, in more detail. We are not tied to one tool
What are business intelligence services?
Work that turns the data a company already holds into reporting people can decide from. That usually means finding where the data lives, agreeing what each number means, automating the collection, and building dashboards and scheduled reports on top.
Which BI tools do you work with?
We are not tied to one. If your company already pays for a BI tool, we build there, so your team keeps the logins and skills it has. If you want people to explore the data without a licence for every seat, we set up an open-source BI tool. If it has to live inside your own product or follow your own permissions, we code the dashboard. We choose with you in the planning step.
How long does it take?
A single dashboard or report can go live in one to two weeks. Work that involves several data sources usually takes four to ten weeks. We agree milestones before we start and keep you updated against them.
How much does it cost?
It depends on the number of sources, the state of the data, the kind of tool and what has to happen after launch, so this site does not list a price. Send a few lines about what you run today and we reply within one to two business days.
Do we need a technical team to work with you?
No. You explain the problem you are trying to solve and we handle the technical side. It helps to have one person on your side who knows where the numbers come from.
What happens when a data source fails?
The run stops, keeps the last good figures, marks them as out of date and tells the person who owns it. It does not publish numbers it could not check. The sample run on the data automation page shows this.
Can the dashboard live inside our own product?
Yes. When it has to sit inside your own product or portal, or follow your own permissions, we code it. That is how the dashboards in our own products are built.
What happens after it goes live?
We stay involved. New sources get added, definitions change and teams reorganize, and the reporting has to keep matching the business.
Do we have to replace the systems we use?
No. The work is built around what you already run. It reads from your systems; it does not ask you to move off them.
What if our numbers do not agree with each other today?
That is normal, and it is what the discovery step is for. We find where they diverge before building, because a dashboard on top of disputed numbers only moves the argument.
Do we have to use your products to work with you?
No. Reporting work is built around the systems you already run. DenwaysHR and DenwaysMeet are separate, and each stands on its own.
Tell us where your numbers come from.
Send a few lines about what you report on today and how it gets assembled. We reply within one to two business days.