Revenue operations & lifecycle automation The strategy and the build, same person.

I build the systems that turn leads into revenue: lifecycle email and SMS, CRM trigger architecture, and reporting you can trust. When you need it, I lead the marketing function on top of them.

Eleven years across sales, product, and ops. I sold leads before I built the systems that follow up on them.

Sales, product, and ops
11 yrs
Lifecycle systems built
8 brands
Lift in booked-to-close rate
+15%

Selected work

Lifecycle automation, built from zero

A multi-brand group with a high-volume, high-cost-per-lead funnel and no automation layer. The figures stay private; the result below is directional, and I'll walk through the detail on a call.

The problem

Follow-up was manual and inconsistent. No triggers, no documentation, no reliable reporting.

What was built

Stage-triggered email and SMS from first verification through close, with consent, suppression, and brand routing handled before anything sends.

What it moved

+15%

Relative lift in booked-to-close rate

How a message gets sent

Nothing sends until it clears four gates.

The part most programs skip, and the reason this one runs unattended.

Trigger CRM stage change Salesforce

Gate check · all four must pass

  1. ConsentOpt-in on record for this channel. TCPA and 10DLC.
  2. SuppressionUnsubscribes, do-not-contact, and closed records drop out.
  3. DuplicationOne send per stage, even when a record re-enters.
  4. Stage mappingStage resolves to the right template and step.

Any gate fails → held, not sent. Logged with the reason, so exclusions show up in reporting instead of disappearing.

Route Brand routing Template + sender
EmailConstant Contact
SMSSMS Magic
Reporting layer Every send and every hold, tied to pipeline movement: stage velocity and win rate.

More from the record

Problems I found, and what changed

A public dataset turned into an acquisition channel

Replaced boilerplate city pages with structured local data from the public SAMHSA database, so each page carried real service and insurance detail.

Outcome: city pages that rank for high-intent local searches.

A product tier that started as a sales objection

Sized a segment the core product couldn't serve, built the case, and ran the build of an outpatient tier and client portal with engineering.

Outcome: a new revenue lane alongside the core product.

The reporting that checks itself

Found an unreliable close-date field corrupting cycle-time figures, rebuilt timing from pipeline movement, and added a QA layer that flags exclusions.

Outcome: leadership sees what was excluded and why, next to the result.

Things I've built

Built and shipped, not just scoped

The reason I can scope engineering work honestly is that I ship it. The first two ran an esports team I founded and were retired with it; the third is client work.

Sentinel VII stats platform: KPM and KDR distribution charts across 72 infantry players

Competitive stats platform

Player profiles, charts, and leaderboards, fed by a Python scraper and a direct game-server API.

Next.js · Python · REST · Vercel

SVII Live Stats bot posting a player stats leaderboard in Discord

Discord bot infrastructure

Live stats, awards, and a map vote that runs native polls and applies the result to the server automatically.

Node · Discord API · Railway · webhooks

Fishfolk Apparel storefront homepage: an angler casting at sunrise under the headline Gear for water people.

Headless storefront

A custom storefront for an apparel brand on a headless commerce backend. The full build is on the demo while the brand readies its first drop.

Next.js · headless Shopify · Vercel

View the storefront demo →

What I do

Revenue operations first. Demand when it's the bottleneck.

  • Lifecycle automation

    Email and SMS off your pipeline stages, documented so your team runs them without me.

  • GTM systems & reporting

    Trigger architecture, field mapping, data integrity, and numbers leadership can trust.

  • AI lead re-engagement

    Conversational SMS, chat, and voice for leads your team stopped calling, segmented by why they went cold.

  • Also: SEO & web

    Technical SEO, site architecture, and conversion-focused rebuilds when demand is the constraint.

How we'd work together

Start with a free consultation. Stop after any step.

  1. Step 1 · Start here

    Consultation

    45 minutes on your funnel and stack. You get a one-page readout of the top three fixes.

    Free · 45 minutes

  2. Step 2

    Diagnose

    Your funnel, stack, and data, reviewed in depth. You keep the plan either way, and the fee is credited toward the build.

    From $3,500 · 2–3 weeks

  3. Step 3

    Build

    One system, scoped up front. Shipped, tested, and documented before I call it done.

    Fixed scope, fixed price

  4. Step 4

    Lead or hand off

    Stay on as fractional marketing lead and keep building against the plan, or a clean handoff to your team.

    Retainer, or done

Tyler Fadrigon, revenue operations and lifecycle automation consultant

About

I started on the sales floor.

Selling pay-per-lead and pay-per-call advertising taught me what a good lead looks like to the person who has to call it. Then eight years in product, running a five-site portfolio with a developer, designer, SEO specialist, and content editor working to my roadmap. Most of my work since has been in healthcare, where leads are expensive and slow follow-up costs real money.

I report what the data supports, and I'll tell you when a result is directional instead of proof.

Common questions

Do I have to commit to a retainer?

No. Most engagements start with a free 45-minute consultation, then a paid diagnosis or one fixed-scope, fixed-price build: a lifecycle program shipped end to end, or a reporting rebuild. Some clients never move to a retainer.

What does a funnel diagnosis include?

Two to three weeks inside your funnel, stack, and data: CRM architecture and field mapping, trigger and lifecycle logic, consent and suppression handling, and the reporting layer. You get a prioritized plan covering what to fix, in what order, and what it takes. It starts at $3,500, and the fee is credited toward the build if we keep going.

How long does a lifecycle automation build take?

Most builds run six to ten weeks, depending on how clean the CRM data is and how many brands and channels are in scope. The diagnosis sets the exact timeline before any build starts.

How is marketing ops different from marketing?

Marketing brings people in. Marketing operations is the machinery that decides whether those people convert: CRM architecture, trigger logic, field mapping, lifecycle email and SMS, lead routing, and the reporting that tells you what actually moved pipeline. Most companies that think they have a lead problem have an operations problem.

Which tools do you work in?

Salesforce, Constant Contact, SMS Magic, Twilio, HubSpot, GA4, Tableau and Power BI, plus SQL and Python for the data work. For conversational AI I handle vendor selection, segmentation, and the handoff into the sales team rather than tying you to one platform.

What industries do you work with?

Most of my work has been in healthcare and multi-location service businesses, where a single lead costs real money and slow follow-up is expensive. The systems transfer to any business with a considered purchase, a sales team, and a CRM worth trusting.

Start here

Tell me what's broken, or book a free 45-minute consultation. I reply within one business day.

Free 45-minute consultation

Your funnel and stack, reviewed live. You leave with a one-page readout of the top three fixes.

Book a free consultation (opens Cal.com in a new tab)

Prefer email? tyler@tylerfadrigon.com

Your details go to me and nobody else.