| Topic | Update | Decision / Next Step |
|---|---|---|
| 🔒 Security — Pirated Plugin | Identified cracked/nulled plugin as probable source of failed login attempts. Removed and replaced with licensed version. | Resolved $85 spend approved by Michele. Active brute-force attempts should stop. |
| 📧 Reengagement Campaign | Initial campaign launched and completed. Over 10% of viable customers successfully reached. Monitoring for stragglers. | Complete Jason will continue tracking deliverability reporting. |
| 🌱 Spring Nurture Campaign | Copy drafted. Spring seasonal insight from Michele: customers tend to wait when things start blooming — need a compelling counter-CTA. First campaign posts scheduled to launch week of April 6. | In Progress Develop spring-specific CTA before launch. Add Jobber appointment link to emails (see below). |
| 🔗 Jobber Appointment Link | Michele confirmed that including a direct Jobber appointment booking link in campaign emails was highly effective in past Jobber-native sends. Customers in system clicked through easily; scheduling was frictionless. | Decision Made Add Jobber appointment request link to all spring nurture campaign emails. Jason to implement. |
| 🌐 WordPress / Security Sprint (WS1A) | Jason confirmed approach: set up hosted WordPress environment, make all security and structural changes there, then copy changes over to existing live server. | In Progress Staged approach confirmed. Reduces risk to live site. Opens path to fully hosted WP in future. Target: changes ready within a few days. |
| 🏷️ Old Stump Removal Campaign | Michele ran a targeted Jobber campaign for stump removal with higher club member discount. Result: bookings made + enthusiastic customer response. | Noted Validates club segmentation strategy. Rob and Michele are proactively exploring campaign opportunities — keep lines open for ad-hoc ideas. |
| 📩 Email Overlap Concern | Michele had concern that structured nurture campaign might duplicate Jobber's automatic follow-up. Clarified: the two campaigns are distinct flows and do not overlap. | Resolved Michele aligned. Encouraged to keep questions coming. |
| WS | Name | What Gets Built | Delivery | Fee | WordPress? |
|---|---|---|---|---|---|
| 1A | Security Hardening | WordFence, 2FA, plugin audit, backups, GA4 + Meta Pixel installation. Pirated plugin removed ($85 — approved). Staged via hosted WP. | Week 1 | $3,500 | In Progress |
| 1B | Phase Zero Blueprint | Site feature architecture, design comps, brand system, conversion page specs | May 1 | Read-only | |
| 2 | Q2 Member Marketing | 11-email Club calendar (Spring Pruning + nurture), res. & commercial segmentation, collaborative copy review. Jobber appointment booking link included in all spring nurture emails (per April 2 client request). | Jun 30 | $3,500 | No |
| 3 | Meta Paid Social | Facebook/Instagram campaign build + execution, creative, res. & commercial audiences, landing pages in Kit | Jun 30 | $7,500 | No |
| 4 | Lead Warming + Club Welcome | 3-email lead warming sequence (Jobber → Zapier → Kit), Club welcome sequence (Kit) | Apr 27 | $2,500 | No |
| Platform | What's Needed | Who Provides | Needed By | Status |
|---|---|---|---|---|
| Kit (ConvertKit) | API key or admin access to Sperry's Kit account. Needed to build sequences, tags, forms, and landing pages. | Michele / Jason (if BT manages the account) | April 1 | Confirm owner |
| Meta Business Manager | Ad account access (Partner access via BOSSTORQUE Business Manager). Pixel ID. Facebook Page admin or advertiser role. | Rob or Michele — invite ads@bosstorque.ai as Partner | April 1 | Not connected |
| Meta Pixel | Pixel creation in Events Manager. Installation on site via GTM or WP header (deferred with WS1A). Pixel ID shared with BT. | Created in Meta; installed by BT (requires WP access) | April 7 (or when WP approved) | Deferred w/ WS1A |
| Google Analytics 4 | GA4 property ID. Editor access for BT to configure events and conversions. Tag installed via GTM or WP (deferred). | Sperry Google account — invite jason@bosstorque.ai | April 7 (or when WP approved) | Deferred w/ WS1A |
| Jobber | API key or Zapier-native Jobber connection. Needed for: (1) "Estimate Created" and "Job Approved" triggers in lead warming automation; (2) Appointment booking link in spring nurture campaign emails. | Rob or Michele — API key from Jobber Settings → API. Appointment link URL from Michele/Jobber dashboard. | April 7 | Not connected |
| Zapier | Zapier account (BT can host). Jobber + Kit connectors. Two Zaps: (1) Estimate Created → Kit tag; (2) Job Approved → remove tag / stop sequence. | BT hosts; needs Jobber API key from Sperry | April 7 | BT account, needs Jobber key |
| WordPress (Sperry site) | Admin credentials or Elementor/header access. Required for: security hardening, GTM install, GA4, Meta Pixel. Not needed for any other workstream. | Michele — share via secure method (1Password, LastPass, or direct) | When WS1A approved to proceed | Intentionally deferred |
The following deliverables can be fully built and ready to load before a single login is shared. This is the core of the automated build strategy — draft everything, verify with Sperry on copy, then execute in the platforms in a single sprint.
Three automated flows that run without manual intervention once built. All built on Kit + Zapier.
| Week | Dates | WS | Key Work | Dependency |
|---|---|---|---|---|
| Pre | Mar 19–31 | All | All copy drafted, automation specs complete, access requests sent | None — starts now |
| W1 In Progress | Apr 1–4 | 1A, 2, 4 |
Completed: Security audit delivered. Pirated plugin identified and removed ($85). Initial reengagement campaign launched — 10%+ of viable customers reached. In Progress: Kit setup; hosted WP environment being staged for security hardening; spring nurture campaign posts scheduled for week of Apr 6. |
Kit access, Jobber API key (needed for appointment link + automation) |
| W2 | Apr 7–11 | 2, 3, 4 | First spring nurture campaign posts go live. Meta ad account connected, ad sets + audiences built, Kit landing pages live. Jobber appointment link added to campaign emails. | Meta BM partner access; Jobber appointment link URL from Michele |
| W3 | Apr 12–18 | 2, 3 | Ad creative finalized, copy review with Michele, WS2 calendar scheduled | Creative assets from Sperry |
| W4 | Apr 19–26 | 3, 4 | End-to-end automation testing, soft launch prep, first Club email sends | All sequences tested |
| W5 | Apr 27–May 3 | 3, 4 | WS4 LIVE. Meta soft launch (low budget). Lead warming running. | WS4 milestone hit |
| W6 | May 4–10 | 1B, 3 | Phase Zero design comps, Meta budget ramp-up, first performance data | — |
| W7–8 | May 11–24 | 1A, 1B | WS1A security sprint (if WP approved), Phase Zero blueprint delivered May 1 | WP credentials |
| W9–13 | May 25–Jun 30 | 2, 3 | Active campaign management, remaining Club emails, pixel optimization | All systems live |
| Jun 30 | — | All | FULL DELIVERY. All workstreams complete. | — |
The goal is maximum automation with high quality output. Here's how the build is structured to minimize manual labor without cutting corners.
Every email sequence, automation flow, and campaign structure is built once and documented in the Exhibit A spec. After June 30, all sequences continue running under the existing retainer with no rebuild required. The only ongoing labor is monitoring, optimization, and content refresh — not infrastructure.
All email copy, ad copy, and landing page copy is drafted and approved by Sperry before a single login is touched. This means platform setup is a mechanical load operation — no back-and-forth after access is granted. Copy review with Michele happens in Week 3 over email; no live session required.
WS2 (email calendar), WS3 (Meta), and WS4 (sequences) build in parallel. WS1A (WordPress) is the only sequential dependency — it's scoped but doesn't block anything else. Phase Zero design blueprint is built independently of platform access.
Meta Lead Forms work without the pixel on the site. Kit landing pages work without the pixel. All four sequences run without WordPress access. The pixel and GA4 add conversion tracking fidelity — they're important but not required to launch campaigns and start collecting leads.