Territory command center for SLED sales teams

Starting promptUse this prompt as a starting point to build your workflow.

Build a personal CRM "command center" web application for a sales rep and their BDR who sell into U.S. state & local government and higher-ed (SLED). It should be a single account book that unifies Salesforce data, call intelligence, partner/competitive signals, AI research, and outreach drafting into one interface — the goal is to give a territory owner a live cockpit over their accounts without living inside Salesforce all day. Persist everything in a shared database (a named volume) so the app has its own fast, queryable store independent of the source systems. Front end: build one main web app served at a route (e.g. /crm) — an account list/board with per-account detail (pipeline, stage, contacts, calls, news, activities, notes, follow-ups) plus a metrics/dashboard view and an embedded AI assistant chat. Back it with a set of internal JSON API route steps (accounts, metrics, contacts, campaigns, signals, news, research, intel, partners, history, todos) that the front end fetches. Keep internal routes authenticated to the space; only expose what must be public. Data ingestion (mostly scheduled via cron, plus manual trigger routes): Sync customers, open opportunities/pipeline, and contacts/leads from your CRM — Salesforce, or whatever CRM you use. Match incoming records to the account book by name so only relevant records land. Scope revenue metrics (ARR, renewals, pipeline) to the account owner, and scope contacts/leads/calls to a small team but filter them to accounts already in the book. Pull call recordings and summaries from your conversation-intelligence tool — Gong, or similar — and attach them to matched accounts. Ingest partner/overlap data (Crossbeam or your partner platform) and buyer-intent signals (6sense or your intent tool), routing hot accounts somewhere the team sees them (an inbound email address and/or a chat alert). Periodically fetch news about accounts and generate digests. AI agents (each a "begin" route or scheduler that feeds an agent step, persisting results): account research, meeting-brief prep, campaign/outreach drafting, case-study generation, signal-based outreach, grant/RFP scouting, and state-level market intel. Use an LLM — Anthropic Claude, or your model of choice. Add a conversational assistant and a "war room" strategist that can query the CRM and Salesforce live to answer questions and surface portfolio risks. Optionally expose the CRM to AI clients as an MCP server over an OAuth-protected route. Notifications & ops: send a morning brief and intraday alerts to your team chat — Slack, or your tool — and email drafts via your mail provider (Gmail/Google, or another). Include admin utilities: a scheduled backup of the database to cloud storage (Google Cloud, or your provider) and a restore/upload path, plus seed/import steps to bootstrap the account book. Keep all credentials in connectors — no secrets in code — and pin any owner/team identity to clearly-labeled, guarded config constants so scoping can't be changed by accident. Tools used: 3B (Tines), Salesforce, Gong, Anthropic Claude, Slack (bot + user OAuth), Google Cloud (Gmail/Google Drive), Crossbeam, 6sense, Notion, SQLite (named volume), MCP (OAuth-protected route)

New to Tines?Sign up free for Tines 3B Explore Edition

What this prompt builds

A unified sales command center that consolidates Salesforce pipeline data, Gong call intelligence, partner signals from Crossbeam, buyer intent from 6sense, and AI-generated research into a single web application for territory owners. The workflow ingests data from multiple sales tools into a shared database, surfaces hot accounts through automated alerts, and provides an AI assistant that can query live CRM data to answer questions and draft outreach. Built for sales reps and BDRs selling into state, local government, and higher education accounts who need a fast alternative to living inside Salesforce.

The problem

Sales reps and BDRs selling into state, local government, and higher education accounts lose hours every day toggling between Salesforce, Gong, partner platforms, intent tools, and research tabs to understand what's happening in their territory. Critical signals—hot intent, partner overlap, recent calls, pipeline movement—are siloed across systems, forcing reps to manually hunt for context before every meeting and making it nearly impossible to spot risks or prioritize the right accounts. This workflow builds a live territory command center that unifies Salesforce pipeline data, Gong call intelligence, Crossbeam partner signals, 6sense buyer intent, news, and AI research into a single web application with its own fast database, giving territory owners a real-time cockpit over their accounts without living inside Salesforce.

Solution and impact

Territory owners and their BDRs gain a single live view of every account, with pipeline stages, contact history, call summaries, partner overlap, intent signals, news, and AI-drafted outreach consolidated in one interface. The workflow automatically syncs data from Salesforce, Gong, Crossbeam, and 6sense on a schedule, routes hot accounts to Slack and email alerts, and provides an AI assistant that queries the CRM live to surface portfolio risks, generate meeting briefs, and draft campaigns. Reps reclaim hours each week previously spent context-switching, and the shared database ensures the BDR and account owner always work from the same up-to-date picture of the territory.