Meeting Notes — Kelley Weaver, Melrose PR / Bitwire
Date: Feb 24, 2026 | Type: Discovery | Owner: Luke Scorziell
Quick Summary
Kelley is a personal convert — uses Claude heavily for content drafting, emails, and LinkedIn, and she gets it. The org isn’t catching up to her. Pain is real: Fathom notes go nowhere, Slack is disorganized, nothing talks to each other, and the team hasn’t unlocked AI at scale. She wants internal trainings and a smarter workflow before she’ll commit budget. She’s the final decision maker but told us not to start with her — she’s routing us to Hunter for the demo and follow-up.
Stage: Networking → Discovery. Next: Demo call with Hunter (Kelley’s operator).
What Kelley Told Us
How she currently uses AI
- Claude is her primary tool — content drafting (almost exclusively), follow-up emails, LinkedIn posts, grammar and editing
- Usage is highly personal and manual — she runs things through it herself, one at a time
- Finds it genuinely valuable but hasn’t systemized anything
Where the org is falling short
- The team as a whole isn’t using AI nearly enough — Kelley has “a million chats,” the team has almost none
- Fathom notes go nowhere. She takes meeting notes but they don’t connect to anything downstream
- Slack is messy and disorganized — information gets buried, hard to reference
- Manual pipeline work — she’s literally copying Fathom links into Trello by hand
- Nothing is integrated. Tools aren’t talking to each other yet
- She’s learning things and has no clean way to share operational knowledge with her team
What she wants
- Internal AI trainings — wants her whole team to use AI the way she does
- Knowledge flow — what she’s learning, what’s in Fathom, should reach her team without friction
- Optimized workflows — content drafting, note-taking, and meeting follow-ups done smarter
- Team-wide access — she wants AI to be open and usable for everyone, not just her
- Proper Claude project setup — she’s aware Claude Projects exist (foundational client profiles, messaging, etc.) but hasn’t implemented it as an org
Tools they currently use
| Tool | How they use it |
|---|---|
| Claude | Individual content drafting (Kelley-led) |
| Fathom | Call recording + notes — disconnected from everything |
| Trello | Pipeline board — manually updated |
| Slack | Team comms — described as “messy and disorganized” |
Company context
- ~12 full-time, closer to 20 total including part-time
- Manages both Melrose PR and Bitwire
- Hunter and Kayla are the operators who touch both entities — they’re the right people for the demo
- Bitwire described as “basically a well-oiled machine” — Melrose likely has more friction
- Kelley flagged Claude’s February updates specifically — she’s paying attention
Budget signal
- Hasn’t done much research on solutions yet
- Flagged they don’t have a huge budget for anything
- Framing: “Set that up and provide feedback” — she wants to test before she commits
Next Steps
| Action | Owner | When |
|---|---|---|
| Send info on internal AI trainings | Luke | This week |
| Send info on local architecture / private deployment | Luke | This week |
| Kelley connects Luke with Hunter | Kelley | TBD |
| Hunter schedules follow-up demo call | Hunter | TBD |
| Prep demo for Hunter + Kayla | Luke | Before follow-up call |
Demo Call Notes (for when Hunter schedules)
- Come with a demo — Kelley said this explicitly. Don’t show up with slides.
- Target audience for demo is Hunter and Kayla, not Kelley
- Show how Fathom → structured notes → team knowledge can actually flow
- Show how Claude Projects can be set up for Melrose/Bitwire (client profiles, messaging, shared context)
- Address Trello/Slack chaos: can we show a workflow that reduces the manual copy-paste?
- Budget sensitivity is real — frame around ROI of team productivity, not software cost
Pain to lead with
“Your team calls are generating information that disappears. Kelley’s taking good notes, building good content — but none of it compounds. We build the system that makes your best work reusable.”
Deal Sizing (Preliminary)
- ~12–20 people
- Both Melrose PR and Bitwire in scope
- Hunter and Kayla as operators → broader team rollout if it works
- Trainings + workflow setup + possible ongoing = likely $10–20K initial engagement
- Flag for Robert to weigh in once we have Hunter’s context
Created: 2026-02-24 | Discovery call with Kelley Weaver | Owner: Luke Scorziell