Weekly pipeline report

This playbook takes a sales pipeline from HubSpot to a page the team opens every Monday. The synced HubSpot records are read-only; the weekly numbers live in a Database you own; an App shows them; a job refreshes them. Each step produces something you can check before the next.

Steps

1. Connect HubSpot. In Settings → Connections, connect HubSpot under CRM. Companies, contacts, and deals sync into the Workspace database. Open Databases → Workspace and find the deals table to confirm the rows and stages you expect.
2. Agree the numbers. In a chat: "Define our weekly pipeline numbers: new pipeline created, closed-won, deals stalled over 14 days, by owner." Meridian proposes a definition for each with the query in plain words. Correct the stage names and the stale threshold until the numbers match what you count by hand.
3. Keep the history. "Create a Database called Pipeline with a table of weekly snapshots." It creates the Database and the table and writes the first week. Open it in the table viewer; a saved view grouped by owner shows the week at a glance.
4. Build the App. "Build me an app that shows the pipeline snapshots as a chart by week with a filter by owner." It builds, saves, and opens the app beside the chat. Ask for changes until the page reads right, then pin it to the sidebar.
5. Schedule the Monday job. "Set up a routine that writes a new snapshot every Monday at 07:00 and posts the app link to #sales." Press Run now, read the run, then turn on automatic runs. Share the app with the team from its menu.

What waits for your approval

Writing to the Pipeline Database once the app is deployed over it asks, because the app's readers depend on it. Sharing the app, posting to the channel, and anything written back to HubSpot ask too. Reading HubSpot, calculating, and building happen on their own.

Limits

• HubSpot syncs on a schedule, not instantly. A deal changed a minute ago may not be in the snapshot.
• Synced HubSpot rows cannot be edited in Meridian. Changes go through HubSpot, or through the Pipeline Keeper agent, which asks before each write.
• Pipedrive and Salesforce connect the same way, but this playbook's stage names assume HubSpot.
• The app is personal until shared. A colleague opening a shared app sees the snapshots; they still cannot see HubSpot records their own access does not allow.