Nobody really asks what a dashboard costs. They ask what their dashboard costs, and then get an answer about somebody else’s.

We are not going to publish a market average, because there is not an honest one to publish. What we can do is show the prices we hold ourselves to, explain why we do not fix a price on dashboard work, and be specific about what moves the number — using four dashboards we designed, which you can open while you read.

The prices we publish, and the one we do not

These are our own prices, not a survey. They are what we charge from Surat, in 2026.

  • Free 15-point UX audit — free. One product, one working day.
  • Full UX audit — from ₹85,000. Flow-by-flow review, a test with five real users, a prioritised roadmap, and a Figma file of proposed fixes.
  • Fix sprint — from ₹1,50,000. A two-week sprint that redesigns the top findings, with developer handoff.
  • Landing page — from ₹45,000. Marketing website — from ₹1,75,000. Redesign — from ₹2,50,000.

What we deliberately do not publish is a price for designing a SaaS dashboard, and that is not coyness. A dashboard is not one thing. The four below run from a single-role screen to a seven-module platform, and a number covering both would tell you nothing. So we quote product work per project, after a call.

One band is still a useful anchor. A two-week design sprint is a real unit of dashboard work, and at our rates it is ₹1,50,000. If a piece of dashboard design can be held to two weeks of two designers, that is roughly the shape of the cost. Most cannot, and the rest of this post is why.

Driver one: how many people the product is for

Each additional role is close to a second product. Different permissions, a different landing screen, a different definition of “done for today”.

The investment dashboard is one role. A retail investor opens it for four numbers — index level, amount invested, current value, return — then asks up to three follow-up questions. One audience, one mental model. That is the cheap end, and it is cheap because the decision about what matters only had to be made once.

The audit management dashboard is not. Clients, users, audits, projects and questions are five entity types with different people behind them, and the client switcher had to move into the top bar because almost every task starts by choosing whose records you are in. That is a structural decision, not a screen, and structural decisions are where the hours go.

Driver two: how wide the product is

Count the destinations in the sidebar. Crude, and close to right.

The Abstractally order operations app carries orders, products, mappings, invoices, work orders, business intelligence, user management, partners and API documentation. The Disk Manager carries incident reports, analytics, reporting, learning, communication, audits and history, each its own module.

On a product that wide, the first design problem is navigation, not screens. Getting the rail right — what collapses, what expands, how a page three levels deep still shows where it sits — is work with no visible output that decides whether the next twenty screens are cheap or expensive.

A narrow product with deep screens usually costs less than a wide one with shallow screens. Buyers tend to assume the opposite.

Driver three: states, not screens

The most common way a dashboard quote goes wrong is that somebody counted screens.

A table is not one design. It is the loaded table, the loading table, the empty table before any data exists, the filtered-to-nothing table, the error, the permission-denied version for someone who can see the module but not the rows, and the version on a laptop at 1366 pixels wide. On the audit dashboard, colour marks state in the table and nowhere else, which is what lets hundreds of rows stay legible while clients, users and audits share one layout.

Every dashboard is designed with a full year of data in the mock-up. The version most of your customers meet has three rows and a chart with two points. Both have to be drawn. If a proposal does not mention empty states, the proposal is not finished, and neither is the price.

Driver four: whether a design system already exists

On the investment dashboard, the type scale, spacing and card set were built as reusable components, so a new metric drops in without redrawing the page. That is paid for once, and every screen after it is faster.

If you have a system already — real components with states, not a page of colour swatches — say so early; it takes a meaningful bite out of a quote.

Driver five: research and testing

Testing adds hours, and it removes the most expensive category of rework: the kind you find after your developers have built it. The question for a dashboard project is simple. Can you get us five people who use the current tool for a living, for forty minutes each?

Driver six: what happens after the file is delivered

The gap between a Figma file and a shipped screen is where most design money quietly disappears. Handoff support — sitting with your developer on the first screen, reviewing the implementation, keeping the system current as the product changes — is real time, and belongs in the quote as a line rather than as goodwill.

Ask every studio who answers your developer’s question in week nine. The difference between two quotes is often exactly this line, and it is not the line to cut.

How to read a dashboard quote

  • A quote in screens is a guess. Ask for it in roles, modules and states.
  • A fixed price given before anyone has seen your product is a price for a product the studio already built for somebody else.
  • Ask what is excluded. Empty states, errors, mobile, the settings section and the notification emails are the usual quiet omissions.
  • Ask what a change costs. Not whether changes are allowed — what a second round of stakeholder revisions does to the calendar.

The cheapest first step is the free 15-point UX audit: a ranked list of what is costing you users, in one working day, which you can take to any studio including one that is not us. Our approach to data-heavy products is on the SaaS product design page, and if the marketing site is part of the same decision, the bands for that are on website design and redesign.

Frequently asked questions

Why will you not publish a price for dashboard design?

Because a single-role dashboard and a seven-module platform differ by an order of magnitude, and one number covering both would be useless to you. We publish prices for work we can scope in advance — audits, sprints, websites — and quote dashboards after a call.

What is the smallest useful piece of dashboard design I can buy?

A two-week fix sprint, which is ₹1,50,000 at our rates. It redesigns the highest-impact findings and hands them to your developers. It will not restructure a product, and we would not pretend otherwise.

Does a Surat studio cost less than a metro agency?

Our cost base is a Surat cost base rather than a metro office, and our rates reflect that. It is not the strongest reason to hire us. A studio that has designed the kind of screen you need is worth more than a studio that is cheap.

What makes a dashboard project run over?

Three things, in our experience: a role nobody mentioned at kickoff, states nobody counted, and a decision-maker who is not in the reviews. The first two are scoping failures; the third is why we ask early who can say yes.

Can you work with our existing design system?

Yes, and it usually reduces the cost. Bring the Figma library rather than a screenshot of it. If the system is a colour palette and a font choice rather than components with states, expect to spend part of the project turning it into one.