How to Vet a Unit Economics Dashboard Vendor

A practical checklist for evaluating unit economics dashboard vendors — data model, CAC and payback maths, and the questions to ask before signing.

Maysan Insights · · 4 min read

Xin

Most SaaS finance teams go shopping for a unit economics dashboard because a board deck needs a CAC payback number by Friday. The problem is that two competent vendors will show you two different CAC figures for the same business, both defensible, and you find out which one your board sees only after signing. If you are the finance or operations lead who has to defend those numbers, the evaluation is less about charts and more about definitions.

What should a unit economics dashboard actually compute?

A usable dashboard computes four numbers from one source of truth: CAC (blended and by channel), gross margin per account, CAC payback in months, and net revenue retention by signup cohort. Everything else — MRR charts, logo counts, pipeline views — is context around those four.

Vendors tend to sell the chart library first and the metric definitions second. Reverse that order. Before any demo, ask for a one-page definition sheet: which costs sit inside CAC, whether payback uses revenue or gross profit, how a paused subscription is treated in retention. If a vendor cannot produce that page in a day, they are selling a reporting tool, not a finance tool.

Why do two dashboards report different CAC?

CAC is a definition, not a measurement, so it changes the moment you decide which costs count and which quarter they land in.

Take a quarter with ₹8,00,000 of paid campaigns, ₹2,00,000 of two sales salaries, ₹1,00,000 of tools, and 55 new logos closed. Count only ad spend and CAC is ₹14,545; count the full go-to-market cost and it is ₹20,000. At ₹2,000 MRR and 80% gross margin — ₹1,600 of gross profit per month — payback moves from roughly 9 months to 12.5 months. One number supports a second sales hire. The other says fix retention first.

Neither definition is wrong. What is wrong is discovering the gap in a board meeting, with no way to explain it.

Which data sources should the vendor connect to?

At minimum, four: your subscription billing system for revenue, your CRM for pipeline and source, your ad and campaign platforms for spend, and your accounting ledger for the costs nobody tags. Three out of four produces confident nonsense.

Revenue is the weakest link in most Indian B2B setups. Invoices are raised in one system — often through GST billing automation — and money arrives via payment gateway or bank transfer four to eight weeks later. If the dashboard reads only the gateway, collection timing gets mixed into booked revenue and every cohort looks worse than it is. Insist on reconciliation between invoice and settlement, and ask what happens to a TDS deduction sitting against a receivable.

Channel-level data deserves the same scrutiny. If email is a real acquisition channel for you, the dashboard needs spend and attribution per campaign, not one lumped marketing line — the sort of data a tool like MailSender already holds.

What should you ask in the demo?

Ask the vendor to compute your numbers, live, from your data — not to walk through their sample tenant.

  • Which costs sit inside CAC, and can I toggle them per view?
  • Does payback use revenue or gross profit, and is onboarding cost amortised?
  • How is a downgrade treated in NRR — netted into expansion, or flagged separately?
  • If a customer pauses for a quarter, do they stay in their original cohort?
  • Can I see CAC by channel and by salesperson without exporting a CSV?
  • Who owns the data model when we add a plan type you have never seen?

The last question matters most. Pricing changes — annual to monthly, seat-based to usage-based, rupee to dollar — and a dashboard that needs a vendor ticket every time you launch a plan turns into a monthly argument rather than a finance tool.

How do you test a vendor before signing?

Run a paid pilot on one to two quarters of real historical data, and reconcile three outputs by hand: total spend, new logos, and CAC for your largest channel.

That exercise typically takes 2-4 weeks and surfaces what the demo hides — duplicate CRM records, a billing system treating upgrades as new subscriptions, agency fees baked into ad accounts. Get the setup fee in writing before you start, alongside per-seat or per-connection pricing, and ask whether setup is credited against year one. Compare against published pricing where a vendor offers it; the total absence of a number is itself information. Also ask what happens to your data model and historical data if you leave — that answer tells you how much of the work is genuinely yours.

Where to start

Start with the definition sheet and one reconciled quarter of data; that combination will disqualify half the vendors you speak to before you sit through a single demo. Get finance and sales to agree the four definitions in writing, then look at interfaces. We build finance and operations dashboards at Maysan Labs, and the first hour of those projects is always spent on exactly this argument about definitions — not on charts.

Buying software or a website?

Twelve questions to ask any vendor before you sign: price, your data, fit for an Indian business and support.

Get the free checklist

Written by Maysan Insights at Maysan Labs, a software studio in Gurgaon, India. Follow us on LinkedIn