What makes a good dashboard?
Someone looking at a good dashboard knows within a few seconds what to do next. So we start from questions: which three questions does the person using this screen want answered? The dashboard is built around those three, and everything else moves down a level.
The second principle is separation by role. The field team, the manager and finance don’t need the same screen; the same data produces different views so each can make their own decision.
We take the data from wherever it lives
If your data sits in an existing database, a system with an API or consistently kept Excel files, the dashboard is ready within 1-3 weeks. It takes longer when data has to come out of a system with no API, or when several sources must be joined on the same customer or order number; projects that combine several sources take 4-8 weeks.
| Data source | What’s required | Time |
|---|---|---|
| Your existing database | Read-only access | 1-2 weeks |
| Third-party system with an API | API key and permissions | 1-3 weeks |
| Excel / CSV files | A consistent file format or an upload screen | 1-2 weeks |
| System without an API | An export flow or an integration layer | 3-5 weeks |
| Several sources combined | A shared identity field (customer, order no, etc.) | 4-8 weeks |
The budget follows the scope and is settled in writing after the scoping call. If you want to compare, our published budget bands, rates by role and scope timelines are on the pages below (as of September 15, 2026).
Cost and timeline guide
Every budget band, our rates by role and the timeline for each scope tier, on one page.
Pricing
The four engagement models, payment terms and what the price covers.
Report automation
Automated reporting usually sits alongside the dashboard: a one-page summary emailed to the manager every Monday morning, a monthly PDF management report, or an instant alert when a threshold is crossed. That removes the "forgot to check the dashboard" problem, since the report goes to the user instead.
How data gets from the source to the screen
We pull data from your source systems at set intervals, with read-only access where possible. Then the records are matched, so a customer stored under an account code in your accounting software and under an email address in your online shop ends up as one customer. The matched, cleaned data goes into a shared layer, and the charts are drawn from it last.
The shared data layer is where records from different systems are brought into one consistent shape. In most setups the dashboard reads from this layer and leaves your accounting software or shop platform alone. Your source systems stay fast, and adding a new source later doesn’t mean rebuilding the dashboard.
Refresh rate: live, hourly or overnight?
Refresh the data as often as the person looking at the screen needs to act on it. Not every dashboard needs to be live. The more often the data refreshes, the more it costs to build and to run, and live data is the most expensive option. It is also the decision most often skipped when scoping.
Live
For work that needs a response within minutes: field operations, courier tracking, stock alerts. The source system has to be able to hand this data out.
Hourly
Enough for most sales and order screens that get checked a few times a day.
Overnight
For management reports, monthly comparisons and finance views. The cheapest option, with the fewest moving parts.
How the PulseIQ demo lays out a screen
The screen follows the order in which a viewer’s questions come up. The four numbers at the top show within seconds whether things are going well. One main chart in the middle shows the trend. The panel on the right answers “what should you do today?”, and the action button is on the same screen. The demo tracks competitors on social media, but the layout suits most dashboards.
What to prepare before we start
The most useful thing you can bring is the report someone builds by hand today. Who prepares it, who receives it and which decision it feeds tell us most of what the dashboard needs to show. If you also gather access to your sources and your metric definitions before we start, the matching step, and with it the timeline, gets shorter.
- Who will use the dashboard, and which decision each of them makes in a typical week
- The last few copies of the report someone currently builds by hand (an Excel file, an email or a PDF)
- Access details for each data source, or the name of the person responsible for that system
- Written definitions of your key metrics: is revenue before or after VAT, are refunds deducted, how many days without activity before a customer stops counting as active
- How far back comparisons need to go (the last 12 months, the last 3 years)
Frequently asked questions
Our data is scattered. Can you still build a dashboard?
Yes, and this is the situation we meet most often. Bringing data from different systems and files into one dashboard is a normal part of the work. What matters is that a shared identity field exists across sources, such as a number or code that lets us match the same customer in two systems. If none exists, defining one is the first job.
How long does a data dashboard take?
A dashboard fed by a single existing database is ready in 1-2 weeks; one fed by third-party systems with APIs takes 1-3 weeks. Combining several sources pushes this to 4-8 weeks, most of which is cleaning and matching the data.
Why a custom dashboard instead of an off-the-shelf BI tool?
Ready-made tools are good for standard reporting. A custom dashboard is the better fit when the data needs interpreting through your own business logic, when the dashboard must be embedded inside a process (seeing and acting on the same screen), or when per-seat licensing cost becomes unpredictable.
Where is the data stored?
On your own server or in a cloud account opened in your name, as you prefer. Where read-only access is enough we can work without touching your existing system at all. In every case the data belongs to you.
Will the dashboard slow down our existing systems?
Usually not. We pull data from the source system at set intervals and keep it in a separate layer, so heavy queries run against that copy. Where live data is needed, we agree together on a refresh rate the source system can handle.
What drives the cost of a dashboard project?
The number of sources and how much cleaning the data needs matter far more than the number of charts. Projects start from US$1,000, and our rates are US$25-60 per person-hour, depending on the role. Once we have seen your sources and the questions to be answered, we quote a fixed price for the scope or work on time & materials.
Will we depend on you to add a new chart later?
No. The full source code and IP pass to you on final payment, and delivery includes documentation and setup instructions, so your own team can add new views. If you’d rather keep working with us, a monthly retainer covers that.