Outreach systems
Outreach research, drafting and follow-up in one system
Sponsorship outreach was running on scattered tabs, ad hoc notes and memory. Trenches Leverage gave it one structured system: a dashboard for the pipeline and a browser extension for the work where it happens.
structured pipeline in place of scattered campaign notes
1
surfaces that share state: a dashboard and a browser side panel
2
history per contact: research, drafts and follow-ups in one record
Full
At a glance
A dashboard and a browser extension that share one pipeline
A custom outreach system for a consulting firm: a Cloudflare-hosted dashboard that holds the pipeline, paired with a Chrome side panel that supports research, drafting and follow-up right where the outreach happens. Sends stay manual and human, with the system doing the preparation and the remembering.
| Client | Trenches Consulting (trenchesconsulting.com) |
|---|---|
| Engagement | Custom workflow system: dashboard plus browser extension |
| Stack | Cloudflare Pages, Functions, D1, JavaScript, HTML and CSS, Chrome MV3 |
| Team | One builder, design through operations |
Situation
The breaking point
- Prospect research living in tabs and notes that never make it into a system.
- Drafting each message from scratch, with quality depending on the hour of the day.
- Follow-ups tracked by memory, which is exactly where they get lost.
- No single view of which brands were contacted, when, and what happened next.
Approach
The build
Give fragmented campaign work one structured system, with research and drafting supported by AI and every send and follow-up owned by a person.
The dashboard runs on Cloudflare Pages with Functions and D1 holding the pipeline: brands, contacts, status and history. A Chrome MV3 side panel rides along during the actual outreach, supporting research and drafting without leaving the page the work is on.
AI assists where judgment is cheap to check: researching a prospect and drafting a first pass. The operator reviews, edits and sends every message themselves, and the system records the touch and schedules the follow-up so nothing relies on memory.

The moving parts
Under the hood
The core components that make the system work, and why each one matters.
Pipeline
One record per relationship
Brands and contacts carry status and full touch history in D1, so the pipeline is a system, not a spreadsheet.
Side panel
Work where outreach happens
A Chrome MV3 extension brings research and drafting support onto the page, instead of a copy-paste loop between tools.
Drafting support
AI first pass, human send
Drafts are generated for review, never auto-sent. The operator owns every message that leaves.
Follow-up
Scheduled, not remembered
Next touches are tracked by the system, so persistence stops depending on memory.
What shipped
- Outreach dashboard with pipeline, statuses and history
- Chrome side panel for research and drafting in place
- AI-assisted research and first-draft support
- Follow-up tracking tied to each contact record
Plugged into
- Cloudflare Pages and Functions
- D1 database
- Chrome extension (MV3)
- AI research and drafting APIs
The safety rails
- Every send is manual: the system prepares, a person decides
- Draft quality is reviewable before anything leaves the building
- Contact history kept per record, so claims about outreach are checkable
- Credentials and keys stay server-side, never shipped in the extension
Outcomes
The payoff
Outreach stopped being fragmented busywork and became a repeatable pipeline.
The slowest parts, research and first drafts, are now the fast parts.
Follow-up happens because the system remembers, not because someone did.