Available for RevOps / GTM Engineer roles

I build

RevOps professional specializing in CRM architecture, lifecycle automation, and pipeline reporting across HubSpot and GoHighLevel. Built production systems across healthcare, recreation, and manufacturing — cutting lead response time from 24–48 hours to under 5 minutes and tech pack turnaround from 8 hours to 30 minutes. A builder-first thinker who identifies operational gaps and engineers solutions before they're asked for.

24-48hr → 5min
lead response time
8hr → 30min
tech pack turnaround
~90%
liability exposure cut
Build Log

Systems shipped for real clients.

Three production systems, three different failure modes — speed, compliance, and manual documentation. Each one replaced a broken manual process with something that runs itself — and each has a working live demo below it. This page doesn't describe automation; it runs it.

001 — Healthcare Intake

Help2Health

Healthcare services · Lead response & qualification

Problem

Manual, slow lead intake was costing Help2Health clients outright — leads went 24–48 hours without a response, and no system existed to separate high-fit leads from the rest.

System

New lead submits intake form (GoHighLevel)
↓
Insurance type flagged (Medicaid / Medicare)
↓
Qualified leads instantly routed to response queue
↓
Automated response sent — under 5 minutes
GoHighLevel Workflow Automation Lead Qualification Logic
24-48hr → <5min
lead response time
20 clients
acquired post-launch
$720K
annual recurring revenue added
How this was measured: Response time is directly tracked via system timestamps (submission → first automated outreach). Client count and ARR are reported business outcomes in the period following launch.

Live Demo

Submit a referral. Watch the system route it.

This one runs the actual intake & qualification logic. Try Medicare/Medicaid vs. other payment types to see the routing difference, and try Emergent priority to trigger the SMS escalation path.

help2health-referral-intake.demo
Simulated — mirrors the actual 7-workflow intake system built for Help2Health. Try Medicare/Medicaid vs. other payment types to see the routing difference, and try Emergent priority to trigger the SMS escalation path.
002 — Recreation Booking

Wave District

Recreation / booking · Compliance automation

Problem

Riders had to complete a signed waiver and a ~3-hour safety course before a paid appointment could be honored. Manual tracking meant missed completions, late certifications, and refund-driven cancellations.

System

Booking paid → compliance status set to "pending"
↓
Automated reminders sent as appointment nears
↓
Hard gate: ride status locked until waiver + course verified
↓
Staff only intervene on the remaining exceptions
GoHighLevel Status Gating Automated Reminders
~85%
reduction in compliance-driven booking failures
~60%
reduction in staff processing time
~90%
reduction in liability exposure
How this was estimated: Based on the manual failure pattern before automation — an estimated 15-25% of bookings hit a compliance snag (course/waiver incomplete by appointment day), reduced to under 5% with automated reminders and hard status-gating. Staff time estimate reflects ~15-20 min of manual verification per booking dropping to ~5-7 min of exception-only handling. Liability estimate reflects near-elimination of a single defined failure point (unverified riders reaching the water) via hard gating rather than manual catch-all monitoring. Not from a formal A/B test.

Live Demo

Try to get ride-ready without the paperwork. You can't.

Payment alone doesn't unlock the ride — the gate requires a signed waiver AND a completed safety course. Try checking the gate early and watch it hold.

wave-district-ride-ready-gate.demo
↳ Click "1. Book & Pay" to start
Steps 2 and 3 can be done in any order — or skipped, to see the gate block. The gate only opens when BOTH requirements are verified.
003 — Apparel Manufacturing

Bellave

Uniform manufacturing consultancy · Tech pack automation

Problem

Tech packs — the detailed spec documents manufacturers build from — were assembled entirely by hand. Getting one done correctly the first time took most of a working day.

System

Client info + specs collected
↓
Claude aggregates & structures the raw information
↓
Structured specs fed into Six Atomic to build the tech pack
↓
Deliverables auto-sent to client; replies/attachments loop back in
Claude (AI aggregation) Six Atomic Client Automation

Freed capacity has been reinvested into taking on additional client work and faster turnaround for existing clients.

8hrs → 30min
tech pack turnaround time
~135 hrs/mo
labor capacity freed (18 packs/mo)
~65-75%
estimated reduction in packs needing rework (45% baseline)
How this was measured/estimated: Turnaround time is a direct before/after labor-time comparison (8 hrs manual vs. 30 min with the system), reported at ~18 tech packs/month. The 135 hrs/mo figure is calculated directly from that time difference × volume. The 65-75% rework reduction is an estimate — the 45% baseline rework rate is reported, but the post-launch rate hasn't been formally audited; the estimate assumes most rework was caused by manual transcription error, which the Claude-aggregation step directly removes.

Live Demo

Submit incomplete specs. Watch the system catch it before it becomes rework.

Incomplete specs were the source of a ~45% rework rate — so the system detects missing fields at intake, before generation. Try submitting with specs missing.

bellave-tech-pack-pipeline.demo
↳ Click "1. Submit Specs" to start (try leaving a checkbox unchecked first)
Simulates the pipeline architecture designed for Bellave — spec intake with missing-field detection, AI aggregation into Six Atomic, QA gating before delivery, and approval loop closure.

Stack

  • CRM Architecture GoHighLevel · HubSpot
  • Lead Routing & Qualification Logic Workflow Automation
  • AI-Assisted Document Systems Claude
  • Client Communication Automation Email / SMS
  • Enrichment & Data Tools Clay — in progress

Certifications