Teardown
One narrow question, one fast read. I go through the system myself, then write up what I found and what I’d change, in order.
Consulting
Hi — I’m Miguel. Eleven years on lifecycle, web and marketing operations, mostly fintech with some SaaS and ecommerce. Consulting runs through MNM Alaminos Consulting Ltd.
Most people come to me with a number that’s moving the wrong way and a theory about why. The first thing I do is check the theory, because it’s usually not the thing everyone’s looking at. Activation that looks like an email problem turns out to be a promise the product isn’t keeping. Falling opens turn out to be a shared IP with a damaged reputation.
Then I decide what actually needs to change, pick the number that will tell us whether I read it right, and build it — or hand you a plan precise enough that your team can.
What I work on
Have a look at whichever one sounds like your problem.
Lifecycle & retention
Most lifecycle programs are a set of campaigns that were never designed as a system. I read the whole path — product events, onboarding, web, the ESP — find where the promise and the experience come apart, and rebuild the triggers around real behaviour.
Typically includes
Braze · Klaviyo · Iterable · Segment · Amplitude
Conversion & web
Lifecycle work keeps ending at a page that undoes it. This is the read on the journey from the click to the completed action — what the page promises, what it asks for and when, and who owns it internally, which is often the real problem.
Typically includes
Webflow · WordPress · GA4 · GTM · Ahrefs · Hotjar
AI & automation
The mandate is usually "go use AI" with no platform, owner or roadmap behind it. The work is deciding what should be automated and what should stay human, building the connective tissue, then training the people who own the process to maintain it without me.
Typically includes
n8n · Zapier · AWS · OpenAI and Anthropic APIs · Make
How it’s scoped
Showing what’s available for lifecycle & retention. Not everything fits every area, and I’d rather say so than sell you the bigger one.
One narrow question, one fast read. I go through the system myself, then write up what I found and what I’d change, in order.
The whole system — data, triggers, journeys, tooling, and the ownership between teams. Includes talking to the people who run it, because the org chart is usually part of the diagnosis.
I do the work. Rebuild the flows, the site or the automation infrastructure, alongside your team, and leave it documented enough that they can keep going.
A standing second read for a team that already has hands. Strategy, prioritisation, reviewing what your people build. No execution from me.
Inside the team, owning the function — running the roadmap, making the calls, hiring the person who eventually replaces me.
Advisory, a one-off build, an interim stretch while you hire, a second opinion on someone else’s plan. Tell me the shape and I’ll tell you honestly whether I’m the right person.
Fixed fee, quoted with the proposal before anything starts. No hourly billing after the intro call.
Receipts
24% → 38%
Activation, two months into the Mogo lifecycle rebuild
35% → 23%
First-year churn, after the longer-term flows went in
~54K
Dormant customers activated or returned across two rounds
15+
Automations in production, run by the Ops teams themselves
Fit
Good fit
Not a fit
How it starts
Booking is by email for now. Send me the number that’s moving the wrong way and what you think is causing it — I’ll tell you whether I agree, and whether I’m the right person.
Consulting now · open to the right senior role
Vancouver, BC
If you’re in town, coffee’s on me. I’d rather hear it out loud anyway.