Embedded Dashboard Scoping Gate (Onboarding)
A checklist with 7 steps: Inventory the client's existing data sources before promising any dashboard view.
By InnovaAI ResearchPublished
What are the steps?
Embedded Dashboard Scoping Gate (Onboarding)
- 01
Inventory the client's existing data sources before promising any dashboard view
List every warehouse, product database, and third-party API the client already pays for. Luzmo ships 40+ native connectors including Snowflake, BigQuery, and PostgreSQL, so most stacks connect without custom ETL, but you cannot quote scope until the source list is closed.
- 02
Separate the views the client's end users need from the views the client's executives want
End-user views drive the recurring subscription value; executive views drive the renewal conversation. Mixing them in one backlog is how a two-week build becomes a two-month retainer drain.
- 03
Decide the embedding layer before design work starts
An SDK-layer integration inherits the host application's design system, colors, fonts, and component behavior, which Reveal uses as its core approach. An iFrame or CSS-theming route is faster to stand up but breaks when the client redesigns their product.
- 04
Fix the tenant model in writing, including row-level rules per client account
Multi-tenant security is the part clients audit hardest. Document which fields filter by tenant, who can see cross-account rollups, and what happens when a client adds a sub-brand mid-contract.
- 05
Cap the custom chart list at a number you can template
Over-customization is the margin killer in this category. Approve a fixed count of bespoke visualizations, then route every additional request through a change order with its own price.
- 06
Confirm where natural-language querying sits in the permission tree
If the client wants plain-English querying over their data, verify the model only returns rows the asking user is entitled to see. This is a security decision, not a UI feature.
- 07
Write the handoff note for the client's own product team on day one
State which parts of the dashboard the agency owns, which parts the client can edit without breaking the embed, and the response window for breakage reports.