Analytics · BI · Dashboards · Decisions

Analytics and BI consulting: dashboards people open, and the screen a shift runs from.

Turn data into insights that drive better business decisions. Business intelligence and reporting, dashboards and performance analytics, and command centres and decision applications, built by a Pune team that contributes to Apache Superset and runs it in production.

What the conversation usually starts from

Four sentences we hear on the first call. Each is a modelling or ownership problem wearing a tool problem’s clothes.

  • A six-figure BI licence and no answers

    Two hundred and forty dashboards, a renewal coming up, and nobody can say which twenty matter. The fintech case study below started here.

  • Two dashboards, one metric, two different answers

    Two teams, two revenue figures, one warehouse. The tool is almost never at fault; the credit rule and the owner are.

  • Forty tiles where four would do

    The screen on the wall shows yesterday to people deciding today, and the real command centre is a WhatsApp group.

  • Nobody has opened it since the launch demo

    Every BI estate has dashboards nobody reads. The usage logs to prove it are already in the tool, and pruning is a day’s work.

This is why the Week 1 audit starts with the decisions people need to make, and only then with the charts.

Proof from this vertical, with the numbers the customer checked

Two published case studies are filed under Analytics. Both figures carry their time window and were verified by someone outside Woodfrog.

8Dashboards left from an estate of 240, fintech, Series CA six-figure BI licence replaced with a tuned embedded Superset stack, in a six-week fixed-scope engagement.
4.6 to 4.8Enterprise CSAT in one quarter, B2B SaaSChurn signals from three systems read together for the first time, and $480k of ARR stayed on the books.
15s to under 3sOne logistics dashboard after tuningThe same query, the same data, a different plan. Dashboards after tuning run about five times faster.

How an engagement runs

Fixed scope, fixed price, and a pod of three who stay on it.

  1. 01

    Week 1, fixed-fee audit

    Two calls and a written one-pager. Yours to keep whether or not you continue.

  2. 02

    Weeks 2 to 6, build

    Something real in front of real users by week three. Median six weeks to the first production-grade artefact.

  3. 03

    Week 7 onward, operate

    Quarterly reviews and on-call governance. The people who built it pick up the phone.

What buyers ask about analytics work

Do you do BI consulting, or only Apache Superset?

Most of our BI work lands on Apache Superset, because the licence is $0 and we contribute to the project, and Antvia is our own BI tool. The consulting part is the same whichever tool renders the charts: deciding which numbers matter, who owns each one, and what happens when it breaches.

What does analytics modernisation mean here?

Usually migrating off a licensed BI tool without rebuilding every report ever requested. The fintech case is the pattern: the estate was cut to eight boards and the licence went.

Can you put dashboards in front of our customers, inside our product?

Yes. Embedded dashboards are one of the five situations the Superset page is organised around, and the isolation, load shape and support queue that come with customer-facing analytics are part of the build.

How long until something is live?

The floor can open a first screen by week three, and the median to the first production-grade artefact across our engagements is six weeks.

Where are you based?

Pune, India, delivering across India, APAC and the US.

Start with the decisions, then the charts

Two calls, a fixed fee, and a one-pager you keep either way: the decisions the numbers have to serve, the dashboards worth keeping, and what we would build first.