Add analytics to your product without building a BI tool
Your customers expect dashboards inside the product. We build the multi-tenant data model, semantic layer and embedded front end so your engineers can stay on the core roadmap.
Book a free discovery callIt is harder than it looks
Attribution, benchmarks and drill-downs get complicated once you have thousands of tenants.
The tools are new to your team
Cube, Embeddable and row-level security are powerful and easy to set up wrong the first time.
The core roadmap slows down
Every sprint spent on charting code is a sprint taken from the product customers pay for.
An analytics feature customers will pay for
Secure, fast and multi-tenant
We build tenant isolation into the data model, pre-aggregate for speed and add deployment to your CI/CD pipeline. The feature ships and updates like the rest of your product.
What you get
- Tenant isolation from warehouse to UI
- Dashboards that load in under a second
- Components styled to your design system
- Deploys through your existing pipeline
- A feature that can support a premium tier
What the engagement includes
Each engagement has a fixed list of deliverables, agreed before work starts.
Multi-tenant architecture
dbt and Dagster pipelines that build shared or per-tenant models safely.
Conformed data layer
Metrics that mean the same thing for every customer.
Semantic API
A Cube semantic layer with row-level security, caching and pre-aggregations.
Embedded UI
Dashboards and charts that match your product, built with Embeddable or your own front end.
Predictive features
Optional forecasts, scores and anomaly alerts shown inside the app.
How the work runs
Multi-tenant design
Isolation and scale from day one.
Performance tuning
Caching and pre-aggregation.
CI/CD integration
Ships with your product.
This works best if
- You run a B2B SaaS product with customer data worth showing
- Customers regularly ask for reports or exports
- You want in-product analytics without hiring a BI team
Should we use Embeddable or our own front end?
Either works. We recommend one during scoping based on how much design control you need and how soon you want to launch.
How an engagement starts
The work runs in three steps. You see working output within weeks and can stop after any stage.
Discovery call
A 30 minute call with the engineer who would do the work. We look at your setup, tell you what we would fix first, and whether you need us for it.
Day 1Blueprint sprint
We map your sources, stakeholders and goals, then give you an architecture and a prioritised roadmap. You keep it whether or not we do the build.
2 to 4 weeksBuild in sprints
We ship working tracking, models, dashboards and agents every two weeks. You can stop after any sprint, and everything built stays yours.
Every 2 weeksWhat happens on the call
Book your call- 30 minutes with the engineer who would do the work
- No slides or sales pitch
- A clear answer on whether we can help, and a referral if we can’t
- The first fix we would make, which you can use either way