Every Monday morning, somewhere in Delhi, a manager opens three spreadsheets, a CRM export and an ad report, then spends two hours making them agree. The final summary goes into an email, and by Wednesday it is out of date. Nobody doubts that the numbers matter. The trouble is that they take too long to assemble, and too many people quietly distrust them.
This page explains business dashboard development in Delhi as PC Media House delivers it online: how data is chosen and connected, which tools make sense at which size, how refresh and access really work, and why pricing is a custom quote. It also covers data protection duties under India's DPDP Act and Rules, and the mistakes that turn good dashboards into unused ones.
A dashboard does not make a business better. It makes decisions faster and arguments shorter, provided the numbers are defined, reconciled and kept current. The rest of this page shows what that takes.
What a business dashboard is, and what it is not
A dashboard is a small number of views built to answer recurring questions. It is not a dump of every chart a tool can draw. The best ones start with a decision, such as which leads to chase today, which customers are overdue, which products to reorder or which campaigns to stop, and show exactly what is needed to make it.
| Dashboard type | Questions it answers | Typical data sources |
|---|---|---|
| Owner overview | How are sales, collections and costs moving against target this month? | Sales sheet or CRM, accounting exports, bank summary sheet |
| Sales pipeline | Which deals need follow-up, where do leads stall, and who is converting? | Zoho CRM, HubSpot or a sheet-based pipeline |
| Marketing and ads | What did spend produce in enquiries and revenue, by channel? | Ad platforms, website analytics, lead forms and CRM outcomes |
| Receivables and cash | Who owes what, for how long, and what is likely to come in? | Invoice exports, ageing reports, payment records |
| Stock and operations | What is running low, delayed or slow-moving across branches? | Inventory exports, order sheets, production logs |
| Team performance | Who is meeting targets, and where is workload uneven? | CRM activity, task trackers, attendance sheets |
Most businesses need one or two of these first, not all six. We recommend starting with the view that saves the most reporting time.
What a dashboard is not: a substitute for clean records. If an invoice is entered twice or a lead has three spellings, a dashboard will show the mess faster. Cleaning the data is part of the work, and sometimes the biggest part.
Design choices that make a dashboard get used
- One headline view that answers 'are we on track', with detail one click away and not crowding the first screen.
- Comparisons that mean something, such as this month against target or the same month last year, instead of raw totals alone.
- Plain labels and units, with rupee formatting and the April to March financial year applied consistently.
- A visible 'last refreshed' stamp, so no one mistakes yesterday's numbers for this morning's.
- A short note on each metric explaining what it includes and excludes, drawn from the metric dictionary.
These small choices decide whether a dashboard becomes part of the weekly meeting or a link nobody opens after the first fortnight.
Where the data comes from, and how fresh it can be
Every dashboard is only as good as its sources. The first practical question is not 'what chart do you want' but 'where does this number live, who updates it, and how often'. Common sources include spreadsheets, CSV and Excel exports, a CRM, website analytics, ad accounts, databases and exports from accounting or billing software.
Connectors and credentials
In Looker Studio, Google-built connectors reach sources such as Google Sheets, Google Ads and Google Analytics at no cost, while community connectors built by other developers may charge. An extract creates a stored snapshot for speed, and file uploads must be re-imported by hand. Credentials matter too: with owner's credentials, viewers do not need access to the underlying data, while viewer's credentials require each viewer to have it. The right choice depends on how sensitive the data is.
Refresh is not instant
People often assume a dashboard is live. It rarely is. Google's documentation sets different freshness behaviour by connector: for example, Google Sheets can refresh every 15 minutes, Google's own ad and analytics connectors every 12 hours, and database connectors anywhere from minutes to 12 hours. In Power BI, imported data is a point-in-time copy refreshed on a schedule. Pro allows up to 8 scheduled refreshes a day and Premium Per User or Fabric capacity up to 48, and refreshes on shared capacity must finish within 2 hours.
On-premises sources, such as a database on an office server, need a data gateway for scheduled refresh. Cloud queries can also carry costs: Google notes that BigQuery runs queries on every refresh, so charges apply. We design around these limits and state them in the proposal, so nobody expects a live feed that the source cannot provide.
Choosing the tool: Looker Studio, Power BI or something custom
There is no single best dashboard tool. The right one depends on how many people will use it, how heavy the data is, which software you already pay for, and what you can maintain. Here is how the common options compare.
| Approach | Where it works | What to watch |
|---|---|---|
| Manual spreadsheets | Very small teams with one or two sources and a weekly routine | Copy-paste errors, version confusion and a single person who holds the process |
| CRM built-in reports | Pipeline and activity reporting inside the CRM | Limited when you need to combine CRM data with finance, stock or ads |
| Looker Studio dashboard | Marketing, web and Google-centred data; teams wanting a free, shareable tool | Freshness depends on the connector; heavy logic can strain it |
| Power BI model | Deeper modelling, larger data, finance and operations, Microsoft-centred teams | Per-user licences for sharing, and refresh limits tied to the plan |
| Fully custom web dashboard | Unusual logic, customer-facing portals or tight integration with your own software | Highest build and upkeep effort; justified only when ready-made tools do not fit |
On licensing, Microsoft's India pricing page lists Power BI Pro at ₹1,165 per user per month and Premium Per User at ₹1,995 per user per month, both billed yearly with GST extra, at the time of writing. Power BI Desktop can be downloaded free, but sharing reports needs Pro or Premium. Looker Studio is described by Google as a no-cost tool, with a paid Pro tier for enterprise collaboration and administration. Always confirm current prices before committing.
CRM tools bring their own reporting. HubSpot's free CRM includes reporting dashboards, and Zoho CRM has a free edition for a small number of users along with an API family that supports bulk transfers, SQL-style queries and change notifications. If your questions stay inside the CRM, its built-in reports may be enough. A custom dashboard earns its place when you need to combine the CRM with money, stock or marketing data.
Who needs this, and what we need from you
Suppose a building-materials distributor with two branches keeps orders in one sheet, payments in another and customer details in a CRM. The owner wants to know, by branch, what is sold, what is overdue and who has not ordered in sixty days. That is a good dashboard brief: three sources, clear questions, a person who will use the answers daily.
- Sample data or access: exports or role-based access for each source. Please do not share passwords.
- Definitions: what counts as a sale, a qualified lead, an overdue invoice or a repeat customer in your business.
- Questions and decisions: the five to ten choices you want to make faster.
- Owners: the person who knows each data source and can explain unusual entries.
- Users and permissions: who should see what, including any figures that must stay restricted.
- Existing reports: the spreadsheets you build today, because they show how you already think about the numbers.
Time on your side is mostly in definitions and validation. Plan for a few short sessions rather than one long workshop, and nominate a single person to give consolidated feedback.
How a dashboard project runs
Step 1: Decisions and discovery
We list the decisions the dashboard should support, who will use it, how often, and what they rely on today.
Step 2: Data audit and metric dictionary
Each source is inspected for access, quality and refresh limits. Every metric gets a written definition, formula and owner.
Step 3: Wireframe and tool choice
You see a simple sketch of the layout and filters. We recommend a tool with its licence cost and refresh behaviour explained.
Step 4: Connection and modelling
Sources are connected, cleaned and joined into a reliable model, with refresh schedules matched to what each source allows.
Step 5: Build, validate and refine
The dashboard is built and reconciled against your records. We trace and fix differences before sign-off.
Step 6: Access, training and handover
Permissions are set, users are trained, and documentation covers sources, definitions, refresh and ownership.
The metric dictionary is the quiet hero of this process. It stops arguments before they start: if 'revenue' means invoiced value net of GST in the dictionary, no one can quietly mean something else on the dashboard. It also lets someone else maintain the work later.
Validation is the second safeguard. We compare dashboard totals with your own records for a sample of periods, and investigate any mismatch, whether it comes from a formula, a duplicate entry, a missing date or a sheet that someone edits by hand. Only then does the dashboard go live.
Pricing: why it is a custom quote, and what shapes it
Our pricing label for dashboards is Custom quote. We do not publish a figure because the same-sounding request can mean very different amounts of work. A sales dashboard on one clean sheet and a multi-branch model drawing on a CRM, accounting exports and ad accounts are different projects, even if both are called a dashboard.
| Factor | Simpler end | Heavier end |
|---|---|---|
| Data sources | One or two clean sheets or a single CRM | Many systems, including exports that arrive in different formats |
| Data quality | Consistent names, dates and categories | Duplicates, missing fields, free-text entries and hand-edited sheets |
| Integrations | Built-in connectors | API work, scheduled exports, or custom scripts to combine systems |
| Platform and users | A few users on a no-cost tool | Many users, per-user licences, mobile access and strict security |
| Logic | Totals, filters and simple comparisons | Multi-currency, ageing buckets, branch targets, cohorts or row-level access |
| Change and upkeep | A stable layout that rarely changes | New views each quarter and frequent source changes |
Software licences are paid to the vendor, not to PC Media House, and their prices can change.
After a short data audit, you receive a scoped proposal that lists the sources, the number of views, the platform, the validation approach and the handover. If the scope changes, you receive a revised quote and approve it before any extra work starts. There are no hidden charges.
Security, access and India's data protection rules
Dashboards often hold sensitive information: margins, salaries, customer names, phone numbers. Treat them like any other business system. The points below are informational, not legal advice.
- Role-based access: give people the views they need and nothing more. In Power BI, row-level security filters rows by role, for example by branch, but it does not restrict columns, so sensitive fields need separate planning.
- No shared passwords: use named accounts so you can see who has access and remove it when staff leave.
- Minimise personal data: if a view does not need a customer's phone number, leave it out.
- Processor arrangements: under the DPDP Rules, 2025, a Data Fiduciary must apply security safeguards that extend to data handled by processors, and processor contracts should carry appropriate provisions.
- Breach readiness: the Rules require breach intimation to the Data Protection Board and affected people, so know where your data sits and who can export it.
At the time of writing, the DPDP Rules were notified on 13 November 2025, with the core duties, including notice, security safeguards and breach intimation, scheduled to apply from 13 May 2027. The government has discussed shortening the timeline for certain categories of businesses, so check the current position with your advisor. Starting good access habits now costs little and avoids rework.
Mistakes to avoid, keeping it alive, and how we work
- Starting with charts, not decisions. A dashboard with twenty visuals and no clear action is rarely opened twice.
- Leaving metrics undefined. If two managers calculate margin differently, the dashboard will cause an argument instead of ending one.
- Skipping reconciliation. Trusting a connected sheet without comparing totals is how wrong numbers reach a boardroom.
- Ignoring refresh and ownership. Power BI pauses scheduled refresh after two months of inactivity, and renamed columns are a common cause of failed refreshes. Someone must watch for both.
- Showing everything to everyone. Salary, margin and customer data should reach only the people who need it.
After launch
A dashboard is a living tool. People will ask for a new filter, a source will change its format, and a metric will be redefined when the business changes. We offer maintenance and change support so that refresh failures are caught, definitions stay current and new views are added in a planned way. Dashboards also work best alongside the systems that feed them, such as accounting software, bookkeeping and virtual CFO support that keeps records clean, and performance marketing data that shows what ad spend produced.
If repetitive manual steps remain, such as copying leads from a form into a CRM or sending payment reminders, automation and chatbots can remove them and feed cleaner data into your dashboard. For the website side of your data, see our website development service.
How PC Media House works
- Online-first from Delhi, serving Delhi NCR and India, with calls and meetings by appointment.
- A short data audit before any quote, so the price reflects real scope.
- Written metric definitions and a reconciliation round before sign-off.
- Dashboards that live in your own accounts, with documentation for handover.
- No invented numbers or promises, only transparent method.
To begin, contact PC Media House with a list of your data sources and the five decisions you want to make faster.
Frequently Asked Questions (FAQs)
It is a single screen or set of screens that shows the figures a business uses to decide things, such as sales, collections, stock, leads or ad return. Data comes from your own sources, and each metric has a clear definition, so everyone reads the same number the same way.
Because the effort depends on things we only learn after looking at your data: how many sources, how clean they are, what integrations are needed, which platform fits and how complex the calculations are. A fixed price before that would be a guess. The quote is written after a short data audit.
We recommend the lightest tool that meets your needs. Looker Studio, which Google's documentation now calls Data Studio, is a no-cost tool well suited to marketing and Google data. Power BI suits deeper modelling and finance or operations work, but sharing needs per-user licences. The choice is explained in the proposal.
It depends on the source and tool. In Looker Studio, Google Sheets can refresh as often as every 15 minutes, while Google's own ad and analytics connectors refresh about every 12 hours. Power BI Pro allows up to 8 scheduled refreshes a day. We design around what the source actually allows and tell you upfront.
Usually yes. Zoho CRM provides REST APIs with bulk and query options, and HubSpot offers APIs and its own reporting dashboards, so data can often be pulled into a wider model. The effort depends on which objects you need, how clean the CRM data is and whether the plan you use allows access.
Yes. Access can be set by user or group, and in Power BI row-level security can limit which rows each viewer sees, for example a branch manager seeing only their own branch. Rules need careful setup and testing, and they restrict rows, not columns, so we plan sensitive fields separately.
We write metric definitions first, then reconcile dashboard totals against your own records during a validation round before sign-off. Any difference is traced to its cause, whether a formula, a duplicate entry or a missing date, and fixed or documented. Nobody should rely on a number we cannot reproduce.
Refreshes can fail when a column is renamed or removed, and Power BI notes schema changes as a common cause. We document each source and set up monitoring, then offer a maintenance arrangement for fixes and new views. Without maintenance, dashboards tend to drift out of date quietly.
Safety depends on setup. We use role-based access, share only what each person needs and avoid sharing passwords. If dashboards include personal data, India's DPDP Rules require security safeguards and processor contracts, with core duties scheduled from 13 May 2027. We cannot promise absolute security, only careful practice.
The dashboards sit in your own Google or Microsoft account, or your own hosting, so access and control stay with you. We hand over documentation of data sources, metric definitions and refresh settings, so another professional can maintain it if you ever change provider.
Sources and Official Links
Facts on this page were checked against the sources below, last reviewed on 7 October 2026. Fees, thresholds and rules can change, so confirm the current position on the official site before you pay or file.
- docs.cloud.google.com/data-studio
- docs.cloud.google.com/looker/docs/studio/manage-data-freshness?hl=en
- docs.cloud.google.com/looker/docs/studio/about-data-sources
- microsoft.com/en-in/power-platform/products/power-bi/pricing
- learn.microsoft.com/en-us/power-bi/connect-data/refresh-data
- learn.microsoft.com/en-us/fabric/security/service-admin-row-level-security
- zoho.com/crm/zohocrm-pricing.html
- zoho.com/crm/developer/docs/api/v8
- hubspot.com/pricing/crm
- pib.gov.in/PressReleasePage.aspx?PRID=2190014®=3&lang=2
- jsalaw.com/?p=55573
- consentos.in/learn/dpdp-compliance-timeline