Embedded Analytics Margin Guardrail (Delivery)

Embedded Analytics Margin Guardrail (Delivery)

1. 01

   Freeze the dashboard template set before the first client-specific request lands

   Agree on a named set of chart types, filter behaviors, and layout slots that ship as standard. Anything outside that set enters a change log with an estimated hour count attached.

2. 02

   Cap custom visualization requests at two per client per quarter

   Route overflow requests to a backlog the client reviews at the next retainer check-in. This keeps delivery hours predictable when a single stakeholder wants a bespoke funnel view.

3. 03

   Price every non-template request against a published internal rate before quoting the client

   Use the same blended hourly figure across accounts so account managers cannot discount margin away in the room. A 40-hour build at a $150 blended rate is a $6,000 scope decision, not a favor.

4. 04

   Confirm the embedding surface inherits the client's design system rather than a parallel theme

   SDK-layer integration (the approach Reveal takes) means colors, fonts, and component behavior come from the host app. CSS overrides and iFrame wrappers create two theming systems to maintain and double the QA surface.

5. 05

   Verify multi-tenant isolation before any client-facing demo

   Test with two tenant logins side by side and confirm row-level filters hold under a shared dashboard URL. A leak found in production costs more than the build itself.

6. 06

   Log connector and data-refresh dependencies in the client's delivery record

   Note which warehouse or source each dashboard reads from and how often it refreshes. When a client swaps their database, the agency needs to know which dashboards break within the hour.

7. 07

   Run a monthly margin review comparing quoted hours to actual hours per account

   Flag any account where custom work exceeds 20 percent of total delivery time. That ratio is the early signal that a retainer is quietly becoming a fixed-price build project.