Targeting
Segmented list building
Lists by trade, geography, company size, and fit — templates and sender profiles stay separated per brand.
Production outreach built on OutreachEngine — Flask, SQLite, multi-brand campaigns for kl, kg, st, and faithworks lanes with scheduler-driven first_touch and followup sequences.
CRM outreach for local service businesses needs brand separation, send caps, bounce discipline, and reply routing — not copy-paste from a shared spreadsheet. OutreachEngine is the live engine behind kl, kg, st, and faithworks brand lanes.
Screen Team (st lane), Faith Works (faithworks lane), and Knight Group (kg lane) each run isolated templates, caps, and sender identity. KG produced substantial booked work from one well-targeted campaign; ST and FW use the same engine at enclosure and land-clearing scale.
Replies surface in Email-Agent crm_reply views on port 5100 so operators review outreach responses without mixing them into personal Gmail threads.
Copy-pasting between spreadsheets and Gmail destroys deliverability. Replies land in personal inboxes. Follow-ups stop when someone gets busy.
Built from live Knight Logics workflows — not generic agency checklists.
Targeting
Lists by trade, geography, company size, and fit — templates and sender profiles stay separated per brand.
Creative
CTA-heavy emails with service context and proof links that match how your business actually sells estimates and calls.
Replies
CRM replies surface in dedicated queues instead of disappearing in a normal inbox thread.
Cadence
first_touch and followup jobs with daily caps between 20 and 40 sends to protect domain reputation.
Deliverability
Hard bounces flagged and suppressed before they damage future outreach windows.
Reporting
See which lists, messages, and channels produce replies and booked work.
Queue preview, send windows, brand switcher, and reply counts — the same interface used on Screen Team, Faith Works, and Knight Group campaigns.
Scoped to your trade, territory, and ops maturity — not a one-size package.
Outreach sends from OutreachEngine; replies land in Email-Agent views mapped to the correct brand lane; operators triage from Knight Command or dedicated CRM tabs.
A clear path from intake to launch — scoped to what your team will actually use.
Define ICP, geography, and the service story each segment should hear.
Separate sender profiles, CTAs, and proof links per brand lane.
first_touch and followup cadence with caps, bounce rules, and preview sends.
Route replies to Email-Agent views and report lead sources weekly.
Measurable operator results — not vanity dashboards.
Follow-up cadence enforced by scheduler instead of depending on someone remembering inbox checks.
Daily caps and bounce suppression keep domains healthy while lists scale.
KG, KL, and ST lanes stay isolated — templates and senders do not cross-contaminate.
Reply rate per list and message variant visible for weekly operator review.
Estimate-first trades needing consistent outbound beyond referrals
Businesses with multiple brands that must not share sender reputation
Owners who want follow-up discipline without living in Gmail
Teams already getting some inbound but need predictable pipeline
Campaign proof
One well-targeted KG campaign generated substantial jobs from a segmented local list — not a mockup dashboard.
Knight Group case studyLive builds and internal workflows behind this service lane.
Flask SQLite CRM with kl, kg, st, and faithworks brand lanes — scheduler cadence and Email-Agent reply routing on live client campaigns.
36 indexable pages for pool enclosure and screen repair across Tampa Bay — st OutreachEngine lane, Email-Agent mapping, and full growth stack.
82 land clearing and forestry mulching pages across Central Florida — faithworks OutreachEngine lane, schema, GA4/GSC, and GBP alignment in the full growth stack.
We typically cap between 20 and 40 sends per day per brand while warming domains and monitoring bounce rates.
Yes — Email-Agent on port 5100 routes CRM replies into crm_reply views separate from manual conversations.
We deploy and configure OutreachEngine for your brands, lists, and follow-up rules — adapted from our live KL/KG/ST workflows.
We will scope list strategy, brand separation, and reply routing for your trade and territory.
Book a Free Consultation