Source Coverage Gap Map (Onboarding)

Source Coverage Gap Map (Onboarding)

1. 01

   Inventory every data source the client's retainer currently touches

   List ad platforms, analytics properties, CRM pipelines, call tracking, and billing systems by name, then mark which ones feed a client-facing number today and which ones only feed internal decks.

2. 02

   Count the connectors each candidate platform actually supports against that inventory

   AgencyAnalytics advertises 85+ integrations, DashThis covers 30+, and Klipfolio reaches 200+ sources and APIs; the gap between your list and the connector count is the first real cost of adoption.

3. 03

   Flag any source that requires a custom API pull or warehouse layer

   Platforms such as Improvado and Windsor.ai exist because some sources never ship a native connector, and those pulls carry maintenance hours that a per-seat price does not show.

4. 04

   Test data freshness on the three sources the client asks about most

   Record the actual refresh interval you observe, not the marketing page claim, because a dashboard that lags by 24 hours will still get rebuilt by hand before every client call.

5. 05

   Reconcile one month of platform totals against the client's own source of truth

   Pull the same 30-day window from the ad platform, the analytics property, and the client's finance export, then document every variance above 2% before anyone presents the number.

6. 06

   Score each source on whether it supports the narrative the account actually sells

   PostHog-style product event data answers retention questions that a channel dashboard cannot, so decide early whether the report needs behavioral depth or only channel totals.

7. 07

   Write the exclusion list and get it signed off by the account lead

   Name the sources that stay out of scope for the first reporting cycle, with the reason, so scope creep does not arrive disguised as a missing widget in week three.