Operations Strategy Brief · April 2026
Jordan is sending an estimated 1,000+ reminder messages every 6 months — manually doing what HighLevel and JobTread automations were built to handle. This brief proposes a clean system division to change that.
Biggest drain
Proposal follow-ups are manual
"Did you go over it with them?" appears 100+ times in 6 months. Every one is avoidable.
Trend
Volume is accelerating, not slowing
Oct → Apr message volume up 133%. The pipeline grew; the automation didn't keep pace.
The opportunity
Jordan already knows the answer
"I'm planning on making automations for a lot of these things, but right now we have to do something." — Jordan, April 2026
01 — The Problem
HighLevel handles sales, communication, and lead follow-up. JobTread handles jobs, costs, and production. But right now, both are being used for everything — and the gap between them is filled by Jordan manually.
What's happening now
Every time a proposal stalls, a payment is late, or a lead needs follow-up, Jordan writes a message. This is human automation — it works, but it doesn't scale and it burns the person at the center of it.
What should happen
Every repeatable touchpoint — proposal reminders, payment nudges, review requests, lead follow-up sequences — should be automated. Jordan's attention should be reserved for creative decisions, escalations, and relationships.
"We need a follow-up system for these proposals without me prompting the questions… What do you think is best?"
— Jordan Webb, JobTread message, April 9 202602 — The Data
We pulled and analyzed 2,093 of Jordan's messages from October 2025 through April 20, 2026 — out of 8,636 total messages he's sent in JobTread. Here's what they reveal.
Monthly volume — total vs. estimated reminders
Where Jordan's nudges go
Most targeted
Jackie receives the most action nudges — follow-ups, scheduling, invoices. Andrew is most often prompted on proposal walkthroughs and client meetings.
Most repeated phrase
This single phrase — or a close variant — appears in over 20 messages in the sampled pages alone, suggesting 100+ occurrences across the full 6 months.
Jordan's stated goal
"I'm planning on making automations for a lot of these things, but right now we have to do something so that they don't slip through the cracks."
03 — The System Split
The proposal: draw a hard line at the point a deal is signed. Before signature — HighLevel owns it. After signature — JobTread owns it. This is already how the tools are designed; we just need to enforce it.
Everything from first touch through signed agreement. Speed, consistency, and nurture are the priority. HL handles all outbound communication and pipeline movement before a job exists.
Everything from signed deal through final payment and closeout. Accuracy, cost control, and job visibility are the priority. JT is the system of record for production reality.
Cross-system sync (the bridge)
The two systems talk at specific moments — not constantly. A Cloudflare Worker listens for JobTread events and updates HighLevel pipeline stages automatically.
What stops breaking
With proper automation in place, these specific tasks come off Jordan's plate permanently:
04 — Journey Map
Every phase mapped to who owns it, what the customer sees, and what failure looks like. HighLevel handles the front half; JobTread handles the back half. The handoff is proposal approval.
| Phase | What the customer experiences | System | Failure to avoid |
|---|---|---|---|
| 1. Discovery | Finds Deck Masters via referral, search, or ad. Reaches out. | HighLevel | Slow or generic reply kills trust immediately. |
| 2. Qualification | Shares scope, budget, and timeline. Confirms fit. | HighLevel | Pushing a bad-fit lead into a bid wastes everyone's time. |
| 3. Site visit | Meets the team. Job details are captured. | HighLevel | Showing up unprepared. No notes left in system after. |
| 4. Proposal | Receives a clear, professional estimate with scope and price. | JT doc + HL pipeline | Proposal sent and never followed up on. Jordan has to remind manually. |
| 5. Decision | Compares options, asks questions, approves or passes. | Both | Radio silence after the bid. Lead goes cold. No automated sequence. |
| 6. Kickoff | Agreement signed. Knows start date and what to expect. | JobTread | Sales → ops handoff gap. Customer doesn't know who to call. |
| 7. Production | Crew on site. Receives updates. Change orders in writing. | JobTread | Schedule changes with no communication. Surprises are expensive. |
| 8. Completion | Walkthrough, punch list, final invoice arrives as expected. | JobTread | Invoice surprise at the end. Missing milestone payment steps. |
| 9. Aftercare | Asked for a review. Invited to refer others. | HighLevel | Disappearing after payment. No review request. No referral ask. |
"I see that no one responded to Bill's message on JT. Can you help make sure we respond to them — he is ready to sign it seems like."
— Jordan Webb, April 20 2026 — a message that an automated HL follow-up cadence would have prevented needing to send05 — The Automation Roadmap
These are not hypothetical. The infrastructure (HighLevel + JobTread + Cloudflare Worker) is already in place or nearly there. This is an implementation sequencing decision.
| # | Automation | What it replaces | Impact | Status |
|---|---|---|---|---|
| 1 | No-decision follow-up cadence HL auto-sends at day 3, 7, and 14 after proposal is sent. Stops when approved or declined. |
~348 manual "Did you go over it with them?" messages | Highest | Build now |
| 2 | Approved → Closed Won sync JobTread proposal approved webhook → HighLevel pipeline move. Job creation alert to ops. |
Manual stage updates and handoff messages | High | Done — monitor logs |
| 3 | Declined / expired → Closed Lost sync Stamps loss reason from JobTread. Keeps HL pipeline forecast clean. |
Stale pipeline data, inaccurate close-rate reporting | Medium | Map reason codes |
| 4 | Job complete → Review request JobTread job complete event → HL sends SMS first, email fallback. Stops if review posted. |
~100+ "Can you get a review?" messages per 6 months | High | Build now |
| 5 | Closed Won → Job creation check Alert ops if a JobTread job record isn't created within 15 min of Closed Won in HL. |
Sales-to-ops handoff gaps, missed job creation | Medium | Build next |
| 6 | Overdue invoice dunning JobTread overdue event → HL sends payment reminder daily until paid. Auto-pauses on payment. |
"Let me know when they plan on making the payment" messages | Medium | Build after #4 |
Idempotency
Every webhook event gets a unique key (JobTread document or job ID). The Worker checks this before acting — retries won't fire twice.
Reliability
3–5 retries with backoff on transient failures. Failed events go to a dead-letter queue with Slack/SMS alert — nothing disappears silently.
Cross-system IDs
HL Contact and Opportunity store the JobTread Document ID and Job ID. JobTread stores the HL Contact ID and Opportunity ID. Records stay linked no matter where you query from.