Your site, your lifecycle emails, your checkout, your analytics — whatever tools you're running, none of them really talk to each other. You don't need another strategy deck. You need someone who can wire it together.
Not generic "is your funnel leaking?" stuff. Specific situations I've been hired to fix more than once.
You're running Customer.io, but no one really knows what's still sending, or why. The email templates haven't been touched in months. The rules for who counts as an 'active' user were set up by someone who left the company a year ago.
Your website is fine. But everything past it — checkout, the emails that go out on their own, your analytics, the way users get grouped — is a pile of disconnected tools held together by hope and one developer's memory.
You have a growth plan on paper — a nicely written deck. What you don't have is anyone who can actually build it. The roadmap has been sitting in a Notion doc, untouched, for a quarter.
You're paying for n8n, Pipedrive, Clay, Apollo — pick your four. None of them are really talking to each other, so data slips through the cracks and every report your team pulls disagrees with the next.
If any of that landed, keep reading. This is exactly the work I do.
Most teams split this work across four to six different people or agencies — a website shop, an email person, an analytics person, someone for ads, someone for ops. Each one does their bit well. No one is responsible for the whole thing working together. That's usually the real problem. The tools below are just examples — I work with whatever you've already got.
A website that pulls its weight.
A site that doesn't break the moment you launch a campaign, that Google can actually find and rank, and tracking that keeps working even after a privacy update. The pages that bring people in, built to keep bringing them in.
The path from 'interested' to 'paying', with no gaps.
Free trials, paywalls, checkout, upgrades. Your billing set up so it's the one place that always knows who's paying — instead of a dashboard someone has to double-check twice a week.
Emails that match what your users actually did.
Your welcome, onboarding, and win-back emails rebuilt so they send based on what's really happening in your product and billing — not on stale rules. Templates your own team can read and edit after I'm gone. The campaigns nobody trusts anymore, cleaned up or switched off.
One version of the truth, across every tool.
Everything tracked the same way everywhere, so the same person is the same person whether they're a visitor, a signup, or a paying customer. The unglamorous layer that finally makes every report agree with the next.
The tools you already pay for, talking to each other.
Automations that move information where it needs to go — a new signup filled out and pushed into your CRM, an in-app action showing up for sales, your lead tools sharing one source of truth. The brittle, half-working shortcuts from years ago, replaced.
The quiet layer under all of it.
The custom pieces off-the-shelf tools can't handle, built so nothing silently drops or breaks. The small bits of glue that turn six disconnected products into one system that actually holds together.
Most companies hire four to six specialists for this.
I do it as one system, with
one person responsible for it working end-to-end.
For five years I've been the technical person behind ProductLed (Wes Bush's PLG consultancy), reporting to the CEO. These are real systems — shipped, in production, still running.
ProductLed wanted a tool that audits a website against product-led growth principles — not by scanning a single page, but by actually living the signup-to-onboarding flow the way a real user would, then reporting back on the gaps.
The system drives a real browser through Browserbase across a target's signup and onboarding, screenshotting each step and passing it to an AI vision step that reasons about what it's seeing and decides what to do next. To get past signup it generates a sub-addressed inbox on the fly, catches the verification email with Cloudflare Email Routing, stashes it in KV, and reads it back to finish. The whole audit runs as a background job on Upstash QStash, with Redis holding state between steps.
The first design ran the audit inside a single request — and would have crashed against Webflow Cloud's 120-second limit. I caught that, moved the work to an async QStash job so it runs to completion, and sized concurrency to how long each automation actually takes instead of maxing out the plan. Built on a tight timeline, integrating several tools that were new to the stack — directed end-to-end with an AI-orchestrated workflow.
Two things Webflow couldn't do on its own. The book content needed clean nested URLs (domain.com/book/name/chapter-1) — Webflow only produces flat collection paths and can't combine two collections into one. And the image bill was creeping to roughly $150/month, with assets locked behind Webflow's CDN on URLs that were never really ours.
Modeled the books as two related collections — Books and Chapters — then used Cloudflare at the edge to rewrite and proxy the path, so visitors get a clean nested URL while Webflow still serves the underlying page. Then built a proxy image setup: a request hits a clean path on our own domain, Cloudflare fetches from the origin CDN and caches it at the edge.
Nested, SEO-friendly URLs without leaving the platform. Images now serve from our own domain, cached at the edge — cheaper, faster, and finally ours. One tool, used at the edge, solving two problems the platform couldn't.
Books sold under different license types, and the buying experience had to onboard people without anyone stepping in — let the product itself do the work.
Built self-serve signup and purchase flows on PLG principles. Single-license buyers get an instant download. Kit-license buyers provision their whole team by adding member emails right after checkout, no back-and-forth.
The product onboards the buyer. No manual steps, no waiting on a human to grant access — the purchase experience is the onboarding.
Signups came in half-filled — a name, an email, sometimes a company. That made it hard to tell who was a real fit for ProductLed's programs and who wasn't.
Designed and built enrichment automations that fill in the gaps on incomplete signups using tools like Apollo, then qualify new users and route them by fit — into Customer.io for lifecycle and onward for follow-up.
Incomplete records become qualified, routed leads automatically. The team stops guessing who's worth their time.
ProductLed moved its entire email-marketing and CRM operation off ActiveCampaign onto Customer.io — and it had to happen without losing data or breaking active workflows.
Working as part of the team on the migration, I handled moving customer data across and rebuilding the email-marketing workflows on the new platform, keeping continuity through the switch.
The operation moved platforms without dropping data or breaking live campaigns. Continuity held through the cutover.
More on a call — happy to walk through the wiring of any of these, including the parts I can't put in writing.
Five years embedded with ProductLed, with selective capacity for one or two more companies at a time. You get someone senior, embedded, fast — without making it a full-time hire.
I direct a modern AI toolchain — Claude Code, AI-native workflows — across the routine parts (boilerplate, tests, the second pass on a Liquid template), so my time goes where it counts: architecture and judgment. I'm orchestrating the build, not handing it off. That's what ships two to three times faster than typical dev work.
Every piece of work I do is a layer in your integrated stack — not a one-off project. Wiring Stripe to Customer.io isn't 'a Stripe job.' It's the lifecycle foundation. I'm always thinking about what comes next and what this opens up for you.
What I build, your team can run. I leave behind a doc your next hire can actually read — not a Notion graveyard, not a Loom you'll never rewatch. The goal is your team owns this in six months, not that you keep paying me forever.
I'm based in the Philippines. For the past five years I've been the technical person behind ProductLed — Wes Bush's PLG consultancy — building the integrated growth stack that B2B SaaS companies need.
My role there is Website Manager — I own their web systems end-to-end. On the open market, that same work is what I package as PLG infrastructure for SaaS companies.
Webflow, Customer.io, Stripe, Cloudflare Workers, n8n, analytics — all wired together as one system. Not six tools maintained by six people who disagree about what a paying customer is.
Most of this kind of work is split across four to six different specialists or agencies. I do all of it as one connected system, orchestrating a modern AI toolchain to ship two to three times faster than typical dev work. One person, one stack, end-to-end.
I'm not a consultant who shows up with a deck. I'm the person you'd hire if you could find one — five years deep with ProductLed, with selective capacity for one or two more companies at a time, so you get someone senior without making it full-time.
You have a product, real users, and growth that's working — but the tech underneath it is held together with tape.
No website, no tools wired up yet? I'll build the whole thing from the ground up. It costs more than fixing what you've got — but you end up with one clean system instead of a mess to untangle later.
You know what you'd do if you had the engineer. You don't have the engineer, and you don't want to hire one full-time.
You've sold the engagement and the client's great. They need someone who can actually build the thing your deck described.
Building your actual app from zero is a co-founder or product engineer's job, not mine. I build the growth side around a product — even if everything else is brand new.
There are cheaper developers. They'll cost you more later. I'm worth the rate or I'm not — that's an honest call to make.
Need a single landing page and nothing more? A freelancer is cheaper. I take on the whole system, not one-off tasks.