Not campaigns. Not email blasts. The operational backbone (lifecycle architecture, CRM design, lead qualification, automation infrastructure). The part that makes everything else run.
I design and build lifecycle infrastructure (lead capture, qualification routing, conversion flows, onboarding, retention). The full stack, end to end.
I walked into Ontraport with zero experience and was running independently in two weeks. The tool is secondary. The architecture is what I'm actually doing.
I align everything to pipeline and conversion. Lead scoring, funnel visibility, attribution, marketing-to-sales handoff. Ops that moves the number.
Most people describe me as the person who understands how everything connects. That's not an accident. It's how I'm wired. I see a lead enter a form and I'm already mapping the conditional logic, the downstream sequences, the tag schema, the suppression rules, and how it all feeds into pipeline.
I've spent 11 years building marketing operations infrastructure for digital businesses. Not managing campaigns. Designing and building the systems underneath (lifecycle architecture, CRM design, lead qualification flows, automation logic, integration layers).
At my last full-time role, I was the sole marketing operations owner for a seven-figure digital education business (100k+ contacts, multiple product lines, a recurring revenue model). I built 100+ automations covering the entire customer journey. Every system, every workflow, every integration. I owned it.
Let's talk about what you're building →"I care about clean data getting to the right person at the right time. And when there are hiccups, they get found and fixed fast. I don't want workarounds. I want to build something that actually scales."
On tools: I came into Ontraport with zero experience. Two weeks later I was running independently. The architecture is the skill (the platform is just where I build it).
On ownership: I work best when I'm designing the system, not just executing someone else's blueprint. I want to understand the full picture and be responsible for how it works.
On data: Clean data isn't a nice-to-have. It's the foundation. If the data is bad, every system built on top of it is bad too.
On teams: Strong IC who can work across sales, product, and data. I'm the person people come to when something breaks (or when they need to build something new).
Every case study below is work I owned end-to-end (the problem definition, the architecture, the build, and the result).
The business's highest-ticket offer was a coaching program with real eligibility requirements (prospects needed to be at a certain stage in their business and earning above a specific threshold to be a good fit). Without a system, intake was manual: someone reviewed each lead, calls got booked (including plenty with people who were never going to convert).
The cost wasn't just wasted sales time. Leads who weren't right for coaching but were a great fit for a lower-priced course offer were falling through entirely.
The System I BuiltA form-based qualification flow that did the sorting automatically. Every question mapped to a qualification criterion. The logic ran on submission.
The form used conditional logic to assess each response against qualification criteria. On submission, tags were applied based on qualification status, triggering the appropriate downstream sequence (either toward a sales call or the course offer). Appointment reminders fired automatically. The routing was invisible to the prospect and required zero human involvement after setup.
The business stopped spending sales time on calls that weren't going to close. Unqualified leads (who previously fell off) now converted on a different offer. The system ran end-to-end without manual intervention. Intake went from a manual process to a fully automated qualification engine.
The business ran multiple lead magnets across different topics and channels. Each needed its own entry point, content delivery, and downstream routing. The challenge wasn't delivery. It was what came after. A lead who downloads a guide and never hears from you again isn't a lead; they're a lost opportunity.
The business needed a system that would take someone from a free opt-in all the way into the core revenue funnel (automatically, and differently depending on where that person already was in their journey).
The System I BuiltA modular lead magnet system with a consistent architecture, implemented 13 times across different content offers. Each deployment shared the same core logic:
The system assessed where each contact was in the funnel the moment they opted in. It didn't treat every lead the same. A brand new contact went one direction. A contact who'd already purchased went another. The suppression logic meant no one got dropped into a nurture sequence mid-launch.
The modularity was the unlock. I built the architecture once, proved it worked, and deployed it again and again (adjusting content variables without rebuilding the logic). Each new offer got a proven system from day one.
This system was the top of the entire revenue funnel. Lead magnets fed the free webinar. The webinar converted into course sales. Course customers became coaching clients (the highest-revenue offer in the business). It ran automatically, at scale, across 13 separate implementations. The architecture held every time.
Monthly launches are only sustainable if the infrastructure is reliable. A business doing recurring live launches needs to know that every confirmation, every reminder, every post-event sequence fires correctly. Every single time. One failure in a high-volume send window is expensive. Manual processes don't scale and don't recover gracefully.
The System I BuiltComplete end-to-end infrastructure for monthly webinar launches (designed to be repeatable from the start):
The infrastructure was built to run, not to be rebuilt each month. A monthly launch meant loading the content (subject lines, dates, offer details) into an already-proven architecture. Tags fired at the right moments. Sequences advanced based on behavior. The replay went to the right people. The sales sequence ran on schedule.
Consistent, reliable monthly revenue generation on the same infrastructure without operational failures. The system removed the human error variable from the launch process entirely. The team's energy went into making the content and offer better (not into worrying about whether the automations would run).
The business needed to move to a new webinar platform. This wasn't a tool swap. It was a full operational migration. The existing infrastructure had automations, tag schemas, and trigger logic built around the old platform's event structure. Replacing the platform meant rebuilding the integration layer, re-architecting how behavioral data flowed into the CRM, and doing all of it without breaking campaigns that were actively running.
The System I BuiltI owned the entire migration (research, selection, technical build, and deployment):
The new platform's API gave access to event-level behavioral signals the old one couldn't expose. I used that to build a tighter integration (instead of basic registration and attendance data, the system now tracked richer engagement signals and fed them into the CRM in real time). The migration was sequenced to keep active campaigns intact throughout.
The business came out of the migration with better infrastructure than it went in with. The new integration provided more detailed behavioral data, improving segmentation accuracy and downstream automation precision. The transition happened without operational disruption. What could have been a painful platform swap became a systems upgrade.
I'm looking for Senior IC roles in Marketing Operations, Lifecycle, MarTech, or RevOps (where I can own and build the system, not just run it). If you're working on something that needs clean infrastructure and someone who understands how all the pieces fit together, I'd like to hear about it.