D
Chat with Delamain
Ask me to build anything
BF
Ben Fischbein9:00 AM
We have 12 clients across clean energy, gun safety, tech regulation, and more. My team is manually checking Congress.gov, pulling clips from three different tools, and writing briefs in Google Docs every week. I need one platform that tracks every hearing, vote, and media mention per client — and tells us what to act on each morning.
D
Delamain9:01 AM
Got it, Ben. Let me make sure I scope this right — a few questions before I start building:
1. Client data source — how should I load your 12 client profiles?
AUpload a spreadsheet with client names, issue areas, and priorities
✓Connect to your existing HubSpot CRM and pull client records directly
CDescribe each client in chat and I'll build the profiles
DStart with 5 key clients, add the rest later
2. What should I monitor for each client?
ACongressional hearings and bill activity only
BCongress + media monitoring across major outlets
✓Everything — Congress, media, social media, and sentiment tracking
3. Client-issue mapping — how should I connect clients to relevant activity?
AManual tagging — you assign each client to their relevant issues
✓Smart matching — I analyze each client's issue areas and priorities to auto-detect relevant activity
CHybrid — I auto-detect and you review before alerts go out
4. Output format — how do you want intelligence delivered?
ADashboard only — you check it when you want
✓Daily brief — one email each morning with everything that matters
CReal-time alerts for urgent items plus a daily digest
DAll of the above
5. Actionability — how detailed should recommendations be?
AInformational — "Here's what changed and why it matters"
BDirectional — "This affects Client X, consider reaching out to Sen. Y's office"
✓Full action items — specific talking points, Hill meeting prep, and media response drafts
BF
Ben Fischbein9:03 AM
1. B — HubSpot has everything
2. C — all of it, I need the full picture
3. B — smart matching, that's the whole point
4. B — daily brief is the killer feature
5. C — full action items, my team needs to know exactly what to do
2. C — all of it, I need the full picture
3. B — smart matching, that's the whole point
4. B — daily brief is the killer feature
5. C — full action items, my team needs to know exactly what to do
D
Delamain9:04 AM
Two more quick ones before I build the spec:
6. Delivery time — when do you want the daily brief?
✓7:00 AM email — before your first meeting
B9:00 AM email — when you're at your desk
CSlack message so it's in your workflow
DDifferent preference
7. Media spike alerts — how should I notify you when a client issue spikes in coverage?
✓Immediate Slack alert when mentions spike >200% in 6 hours
BInclude in daily brief only — no real-time interruptions
CBoth — immediate Slack for major spikes, daily brief recap
BF
Ben Fischbein9:05 AM
1. A — 7 AM, I read it before my first call
2. A — yes, immediate Slack alerts for spikes, that's the whole point
2. A — yes, immediate Slack alerts for spikes, that's the whole point
D
Delamain9:06 AM
Perfect, Ben. Here's the spec I've drafted — it covers client ingestion from HubSpot, congressional hearing and bill tracking, Meltwater media monitoring, Twitter/X social listening, sentiment analysis, daily intelligence briefs at 7 AM, real-time Slack alerts for hearing starts and media spikes, and weekly PDF digests per client. Take a look and let me know if there's anything you'd change.
BF
Ben Fischbein9:10 AM
This is exactly what I need. Build it.