Revenue Systems Operator: own the sales system behind sales teams (GHL + Zapier + HubSpot)

WHO YOU ARE You're the person who can't sleep when a system is half-wired. You take a messy stack of funnels, CRMs, and automations and make every lead land exactly where it should. You don't "do tasks." You own outcomes. And you understand that the system is not the point. The point is a prospect who shows up warm, educated, and already half-sold. When you say it's done, it's done, because you tested it end-to-end and you know why every piece exists. WHY THIS ROLE EXISTS (read this part closely) Our clients run high-ticket sales teams. They already get leads. The money is won or lost in the window between the booking and the call. That window decides two numbers: show rate and close rate. Here is the logic the whole job is built on: A confused prospect does not show up. A cold prospect who does show up doesn't buy. The single biggest predictor of whether someone closes is how much of our pre-call material they actually consumed before the call. Little consumption closes low. Full consumption closes far higher. And prospects who confirm their appointment show at a far higher rate than those who don't. So the system we deploy does one job: it moves a cold, unaware lead to problem-aware, then solution-aware, then product-aware, before they ever get on the phone. Each email breaks one specific belief or objection. Each asset answers a question the closer would otherwise burn the call answering. The call stops being an education call and becomes a decision call. You are not wiring automations. You are building a belief-sequencing machine that manufactures prepared buyers. Every field, every trigger, every stop-condition either protects that warmth or destroys it. If you understand that, the rest of this post will feel obvious. WHAT YOU'LL ACTUALLY DO (the real chain, and why each step matters) Audit the client's existing account before you touch anything. Map their live workflows, tags, custom values, pipelines, and trigger links, and document every conflict with our snapshot. Why it matters: on accounts with live automations, the wrong import breaks their business on launch day. Import our CRM snapshot and verify it landed clean (workflows, custom fields, pipeline stages, tag logic, email/SMS timing). Why it matters: the snapshot is the proven belief-sequence. If it lands corrupted, the warming sequence misfires and the prospect shows up cold. Wire the data layer. Map every form field to its CRM custom field, populate the Appointment Date field correctly, and wire UTM/lead-source for accurate attribution. Why it matters: the Appointment Date field drives the timing of every value email and reminder. Wrong date, wrong timing, and the entire pre-call education arrives at the wrong moment, or after the call has already happened. Template and test every automation across Zapier, HubSpot, and GHL (new-lead software to CRM, no-show, reschedule, cancel), both the source side and the CRM side, every one tested live, with tags, triggers, and flows firing in the right order so nothing double-fires or silently drops. Why it matters: if the lead doesn't land in the CRM cleanly and fast, none of the warming starts. Speed to the lead is itself a conversion multiplier. Set the stop-conditions and routing so nobody ever gets the wrong message. Cancel exits reminder and value sequences. Reschedule exits and re-enters on the new date without re-sending value emails. A reply to a no-show text alerts the rep and pauses automation. An existing booking goes to the Reschedule flow, not a fresh cold sequence. Why it matters: one wrong message, like "Excited for your call!" to someone who cancelled, destroys the exact trust the whole sequence was built to create. Stop-conditions are not edge cases. They are the brand. Stand up the Call Outcome loop (Won, Lost, Follow-up, No-show, Thinking) and the outcome-driven workflows that fire from it. Why it matters: post-call follow-up has to match reality, and a "let me think about it" is only recoverable if the system knows about it. Run email domain warming and confirm test sends land in inbox, not spam, including the daily warm-up reset when the tool route isn't available. Why it matters: the best belief-sequence in the world closes nothing if it lands in spam. This is often the 2-3 week bottleneck that gates launch, so it starts day one. Install tracking (session-recording pixel and conversion events). Why it matters: we need to see exactly where leads drop so the sequence can be tuned with data, not guessed at. Keep everything in DRAFT until Deploy, run real test bookings in incognito, then go live, and monitor daily. Why it matters: founders should never touch the backend, and no lead should ever slip through a gap you didn't test. THIS IS FOR YOU IF You can explain why a pre-call email exists, not just build it You've built real sales/CRM systems in GHL, Zapier, and HubSpot, not just followed a checklist You know how automations actually work, not just where the buttons are: tags, triggers, flows, and the exact order things fire, and you can open someone else's build and tell good from bad in minutes You're fluent in UTMs, link tracking, and conversion tracking, and you know what clean attribution looks like versus a broken mess You ask "what already exists here and what will break?" before you build, and "what belief does this step move?" while you build You push back when the spec is wrong instead of quietly building the wrong thing You'd rather ship the work than schedule a call to talk about shipping the work Reading the list below makes you nod, not flinch THIS IS NOT FOR YOU IF You think the job is clicking buttons in GHL and the strategy is someone else's problem You need someone to project-manage you step by step "Done" means "I think I finished" instead of "I tested it and here's proof" You go quiet when you're blocked instead of flagging it within the hour THINGS THAT GET YOU FIRED IN WEEK 2 I'm listing these on purpose. The right person reads them and feels relief: finally, a team with standards. The wrong person feels attacked. Every one of these has actually happened on a real deploy, and almost every one comes from not understanding why the step mattered: Texting "it's done" when the build checklist isn't all-green and you never opened the steps that were still locked Importing the snapshot before auditing the client's existing workflows, then their live automations break the moment we launch Populating the Appointment Date field wrong (or not at all) so every reminder and value email fires at the wrong time and the prospect shows up cold Pasting an email into the wrong workflow, like a reschedule email living inside the no-show sequence Skipping the stop-conditions, so a prospect who cancelled still gets "Excited for your call!" the next morning (the number one way we embarrass a client) Doing the easy workflows first and leaving the hard ones for the deadline, the hard ones are the whole job Marking a funnel "tested" when you only checked desktop, or never ran a real booking through it in incognito An automation or pixel firing on the wrong trigger and you didn't catch it because you didn't check the live events Editing a client's live workflow without duplicating it first Sitting blocked all day instead of sending one message: "I need X to proceed" "I'd love to hop on a call to discuss" instead of just doing the work WHAT SUCCESS LOOKS LIKE New clients onboarded smoothly, every time, with zero launch-day breakage Show rates across accounts climbing toward 70-80% Prospects arriving at calls already educated, so closers run decision calls, not education calls Dashboards the whole team actually trusts The founder never has to touch the backend or be your project manager PROCESS Short written screen (the questions below), then a live call where we tear apart a real workflow together, then a paid 4-6 hr trial: audit a test account's existing setup, import our snapshot, and produce the pre-build system audit plus a tested booking flow. If you ask the right questions during the trial without being told to, you're in. TO APPLY Send a 3-min Loom showing: (1) a funnel or automation you built end-to-end, (2) a time you caught and fixed a problem before it shipped, (3) how you decide a system is actually "done."