Custom dashboard development: one screen for the numbers you run the business on

What a custom dashboard is for

A dashboard is worth building when the same numbers are being assembled by hand every week. The usual sign is a person who spends Monday morning exporting from Tally, the online store, the CRM and two Google Sheets, pasting them into one workbook, and sending a screenshot to the owner. By the time it arrives, the numbers are a week old and nobody is sure which version of "sales" was used.

A custom dashboard replaces that job. It connects to each source, cleans and joins the data in one place, applies one agreed definition for each figure, and shows each role the part it needs: the owner sees margin and cash, the warehouse sees stock below reorder level, the sales head sees the pipeline by person.

WavX builds admin and analytics dashboards, finance and sales dashboards, and reporting screens inside larger systems. Each one is a web application your company owns, running in your own hosting account.

When a BI product is the better answer

Check this before paying for a build. As of October 2026:

If you have one clean data source and a team that is happy to learn a BI tool, start there. WavX will tell you so on a scoping call. The build vs buy guide covers the general version of this decision.

Where custom dashboards earn their cost

• Data from systems BI tools do not reach. Tally on an office computer, a supplier's emailed CSV, a legacy database with no documentation. Getting this data in reliably is most of the work, and it is the part a BI licence does not do. The Tally integration page explains the options for reading accounting data.
• Definitions that need business rules. "Net sales" that excludes cancelled COD orders and returns within 7 days, or "stock" that counts goods in transit between two warehouses. Writing these once, in code, ends the arguments about whose number is right.
• Dashboards that do something. An approve button next to a pending discount, a reorder button next to a low-stock line, a reassign button next to an overdue lead. At that point the dashboard is closer to an internal tool.
• Reports shown to people outside the company. Distributors seeing their own orders and outstanding balance, or franchisees seeing their own outlet. That needs per-account access rules and usually belongs inside a customer or vendor portal.

Modules in a typical build

The step-by-step guide to building a custom dashboard covers choosing metrics and charts in more detail.

What it costs: a planning range

These figures are worked from the model behind the software cost estimator. They are planning ranges for budgeting, not quotes.

Assumptions: standard design and small scale (up to about 1,000 users). The model applies ×1.3 for a growing user base and ×1.25 for custom UI design, and its spread runs from 15% below to 25% above the subtotal. Each extra data source with an awkward export moves a real quote up, which is why the quote comes after we have seen your sources.

Hosting is separate and small for most internal dashboards. Ongoing maintenance, by WavX's published band, runs at 15–25% of the build cost per year (app maintenance cost guide).

Timeline

The cost model ties delivery time to the subtotal: under ₹3,00,000 is 3 to 6 weeks, under ₹6,00,000 is 6 to 10 weeks, and above that 10 to 16 weeks. In practice the first two scopes above land in the first two bands. The time goes roughly like this:

1. Metric workshop (week 1). List every figure, who reads it, and the exact definition. Collect sample exports from every source.
2. Connectors and data store. The longest stage. Each source is connected, cleaned and checked against a figure someone already trusts, such as last month's GST return or the bank statement.
3. Screens. One role at a time, starting with the owner's view.
4. Parallel run. The old spreadsheet and the dashboard run side by side for two to four weeks. Differences are traced to a source or a definition and fixed.
5. Switch over. The manual report stops. Scheduled reports go to the people who need them.

The parallel run is not optional. A dashboard that disagrees with the spreadsheet on day one will be ignored, however good it looks.

What WavX needs from you

• A list of the reports you produce today, with a copy of each.
• Read access, or an export, for each data source.
• One person who can say what a figure should be when two sources disagree.
• The names of the roles that will use it and what each one decides with it.

If you are not sure which figures matter, the outgrown Excel page is a useful first read. It covers the point at which a shared workbook stops being safe.

When not to build one

• One data source, standard reports. If everything is in Shopify or Zoho, their own reports or a free BI connector will do the job.
• The figures change every month. If the business has not settled what it measures, build a spreadsheet first. Code is expensive to change while definitions are still moving.
• Nobody will act on it. A dashboard that nobody checks is a cost with no return. Name the decision each screen supports before it is built.

Dashboards are one part of custom software and business systems at WavX.