ABM target account coverage board for demand gen leads

I want an app my demand gen lead opens every week to review coverage of our ABM target account list. It replaces a spreadsheet we currently colour in by hand. The audience is the marketing or demand gen owner reviewing program health across tiers and campaigns, not a rep working a personal queue, so lead with aggregate coverage metrics and period over period movement at the top, and keep per account detail one click down.

The target account list lives in Google Sheets and must stay the shared source of truth, because sales co-owns it and edits it outside this app. Read it with the Google Sheets Get Values operation. Each row is one account with company name, domain, tier, assigned rep and campaign. The user picks a date range at the top of the board, and that window drives everything on the page.

For every domain in the list, pull activity from Factors.ai with the Get Account Journey operation over the selected window. Factors is queried one domain at a time, with no pagination and no bulk mode, so a target list of several hundred rows cannot be one long blocking fetch. Load the grid progressively: render every row from the sheet immediately in a pending state, then fill each row in as its Factors call returns, with a per row status of loading, loaded, no data or error. Keep the aggregate counters at the top updating as rows land, and make failed rows individually retryable.

Factors returns a 404 when a domain has no activity in the requested window. Treat that as no data, not as zero engagement. A no data row must read visually and textually as not seen or unknown, never as a measured zero, and it must not drag down the tier coverage percentages as though it were a real value. Count it in its own bucket.

Classify every account into one of three coverage states. Engaged this period means Factors returned activity inside the selected window. Engaged earlier but now dark means there is no activity in the window but the sheet holds a saved last seen date from an earlier period, so the account has cooled. Never seen means neither the window nor the saved history has any activity. Colour the grid by these three states, plus the no data case as its own treatment.

Across the top, show tier level coverage percentages: what share of tier one, tier two and tier three accounts are engaged this period, with the underlying counts behind each percentage. Let the user regroup the whole grid by tier, campaign or assigned rep, and recompute the coverage percentages for whichever grouping is active.

Each account row shows visitor count, session count, last seen date and a small sparkline of activity across the selected window, derived from the events in the journey response. Clicking a row opens detail for that account with the underlying journey timeline.

Join each account to HubSpot so the user can see whether an engaged account actually has a CRM record and an open deal behind it. Look the account up with Search Companies on its domain, then pull the matched record with Get Company including its associated deals. Show three things per row: whether a CRM record exists, whether there is an open deal, and the deal stage if there is one. The gap that matters most is tier one accounts lighting up in Factors with no CRM follow through, so make that combination the most visible thing on the board and let the user filter down to just those accounts.

Three actions write back. Save scores writes the engagement status and last seen date for every account back into the target sheet with Update Values, or Batch Update Values when it is writing many rows at once, so the spreadsheet stays the shared record and the next period has a previous window to compare against. Add to list appends newly identified accounts to the sheet with Append Values. Create task raises a HubSpot task with the Create Task operation for the assigned rep on any engaged but uncovered account, associated to the company record where one exists, carrying the account name, tier and last seen date in the task.

Add a Write the program update button that starts a background agent. The agent reads the whole period's coverage, compares it against the previous window's saved scores in the sheet, and drafts an exec ready summary of which tiers and campaigns moved, which accounts went dark since the last review, and where the follow up gaps are. It then appends the finished update to a log tab in the same spreadsheet with Append Values and posts it to the marketing channel with the Slack Send a Message operation. Show the agent's progress in the app while it runs, and show the finished write up in the app when it lands with a link to the Slack post.

Saved scores are what make the period over period comparison work, so the board should tell the user when the current window has not been saved yet. Remember the selected date range, the active grouping and any filters, so reopening the board returns to the same view.