I run the backend operations that founders stop having time for.
Revenue operations, CRM pipelines and workflow automation for U.S. companies. Five years remote with U.S. teams, native Mexican Spanish, C1 English — and a bias for systems that keep running after I hand them over.
supported
Three systems, and what they actually changed.
Real numbers from real engagements. Figures are what I measured or what the client reported — no modeled projections. Screenshots are from live systems, with client-identifying data redacted.
Live system — client-identifying data redacted. Click to enlarge.
Lead pipeline for a U.S. admissions-coaching firm
The firm was getting leads and losing them in the gap between the form and the follow-up. Nobody owned the middle.
I built the CRM pipeline in GoHighLevel — stages, tags, triggers, automated follow-up sequences — and connected it to Make.com so the reporting updates itself instead of somebody rebuilding a spreadsheet every Monday. Then I documented it so the team runs it without asking me.
Two months of a live pipeline, as three numbers that multiply into one. Select a stage to see what I built there.
What I built at the top
Every inbound lead lands in GoHighLevel already tagged and assigned to a stage, and the follow-up sequence starts on its own. No lead sits in an inbox waiting for somebody to notice it. Roughly 100 came through in the first two months.
- Form to CRM, no manual entry
- Stage and tags applied on arrival
- Follow-up sequence fires immediately
What I built in the middle
About one in five closed. My job is the machinery around that: the sequences run whether or not anyone remembers, and Make.com keeps the reporting current instead of somebody rebuilding a spreadsheet every Monday. I build and run the pipeline — a closer closes the deals.
- Automated follow-up, nothing dropped
- Self-updating reporting in Make.com
- Documented, so the team runs it without me
What it added up to
Roughly 20 closed deals at an average value of $6,500 — about $130,000 in closed revenue supported by the pipeline I built and run. The multiplication is the whole claim: there is nothing in that number I cannot show you the source of.
- ~100 × ~20% × $6,500 = ≈ $130,000
- $6,500 average deal value
- Client-reported, not modeled
Figures reported by the client from the live pipeline. I build and run the pipeline; a closer closes the deals.
Billing automation at a U.S. language-services company
Invoicing ran on manual reconciliation: cross-checking scheduled work against completed work against what had actually been billed. Four hours a cycle, and the errors surfaced weeks later as revenue that never got invoiced.
I mapped where the time actually went, then semi-automated the reconciliation and rebuilt the document flow around it. Same accuracy, a fraction of the hours — and discrepancies now surface inside the cycle instead of after it.
Live workspace — client-identifying data redacted. Click to enlarge.
Operations coordination across clients, vendors and contractors
I joined a California language-services company as an appointment setter and left it as Operations & Financial Coordination Manager. In the role I was promoted into, I was the single point of contact holding service delivery and billing together — clients on one side, vendors and interpreters on the other, in two languages.
That meant owning service-to-billing alignment end to end: tracking what was scheduled, in progress and completed against what was invoiced, so revenue and delivery never drifted apart. Plus executive calendars, inbox triage, KPI tracking, and rebuilding the workflows that kept breaking.
The same operation, before and after I touched it.
Billing, scheduling and client communication usually arrive as three separate problems held together by one person’s memory. This is what changes when they stop being separate. Switch between the two states.
- Billing ran on manual reconciliation: scheduled work against completed work against what had actually been billed.
- Scheduling and confirmations were handled message by message, by whoever was free.
- Leads arrived and sat. Nobody owned the middle, so the errors surfaced weeks later as revenue that was never invoiced.
- Billing: the three sources feed one semi-automated reconciliation, and discrepancies surface inside the cycle.
- Scheduling: confirmations and reminders fire on their own, so nobody re-types the same message.
- Communication: every lead lands tagged and staged, and the follow-up sequence starts without anyone remembering to start it.
Three habits, and why they matter more than the tools.
Select a habit to see what it looks like in practice.
A real current-state map from an engagement — client-identifying data redacted. Click to enlarge.
Map before automating
Every engagement starts with the current-state process on a single page: every phase, every owner, every handoff. Automating before you map just makes the mess run faster — and it hides where the real cost is.
Deliverable → owner → date → status, written against the deliverable itself.
One named owner and one date per deliverable
Work doesn't live in a chat thread. Every deliverable has a person and a due date, and progress gets written against the deliverable itself. That is what kills the status meeting: you read where everything stands in three minutes instead of scheduling a call to find out.
SOPs and a structured workspace ship with every build.
The system has to survive the handoff
SOPs and a structured workspace ship with every build. A system only I can operate isn't finished — it's just a dependency with a nicer interface.
I don't just connect tools. I ship them.
Two products I designed, built and run — both of them replacing something I would otherwise have paid a monthly subscription for.
Meeting Notes AI
A transcription product I built with Claude and OpenAI, doing the job a monthly SaaS subscription used to do. First working version shipped in a single night. I own it end to end — the product decisions, the stack, the roadmap.
Open the live productChop-Chop
Chop-Chop strips the dead air out of long recordings. Point it at a three-hour stream and it cuts the silent gaps, so an editor opens a tight timeline instead of scrubbing through hours of nothing. Built for the people who turn long-form into clips — Twitch and Kick editors, TikTok clippers, and YouTubers sitting on hours of raw footage.
Open the live productFour things, done end to end.
CRM & pipeline systems
Pipeline stages, tags, triggers and automated follow-up sequences — built so leads stop dying in the gaps and the team can see where every deal actually is.
Workflow automation
No-code automation connecting the tools you already pay for, so data moves itself between CRM, billing and reporting instead of being re-keyed by hand.
Billing & revenue operations
Service-to-billing alignment, reconciliation and cash-flow visibility — revenue tracked from first touch to paid invoice, with nothing slipping through.
Documentation & handoff
SOPs and structured workspaces, so the system survives me leaving the room. A build nobody else can operate isn't finished.
Built on the platforms you already trust.
Select any platform to see how I put it to work — or trace a flow to see how they chain.
Over 20 platforms I actually work in. Pick a flow above to see which of them chain together, and in what order.
Business training, operator's habits.
Five years working remotely with U.S. companies since 2021: I joined a California language-services firm as an appointment setter and left it as Operations & Financial Coordination Manager, owning billing and the systems behind it. Today I run the lead pipeline of a U.S. admissions-coaching firm.
The business degree behind that is from Universidad Iberoamericana — one of Mexico's top 3 private universities — earned while working U.S. hours the entire time, and finished with a Top 100 national distinction on the CENEVAL EGEL.
The finance training is what makes the automation useful. Plenty of people can wire two tools together; fewer can tell you which part of the revenue cycle is actually leaking and why it shows up on the P&L. I like the problems where nobody wrote the process down and it somehow has to work by Friday.
every day
Five years, one promotion, and a degree earned in parallel.
Move along the line to see what I owned at each point.
Appointment setter, remote from Durango
I joined a California language-services company as an appointment setter, working U.S. hours from Mexico, and started the B.B.A. at Universidad Iberoamericana the same year. Setting appointments is where I learned the operation from the bottom: who touches what, and where it breaks.
Operations & Financial Coordination Manager
I was promoted from appointment setter to Operations & Financial Coordination Manager, and became the single point of contact holding service delivery and billing together — clients on one side, vendors and interpreters on the other, in two languages. Inside that role I rebuilt the billing cycle: four hours of manual reconciliation down to one to one and a half.
B.B.A., Universidad Iberoamericana Torreón
Business Administration, class of 2025, earned while working U.S. hours the entire time. Top 100 nationally on the CENEVAL EGEL in the Business Administration & Finance track. The finance training is the reason the automation is useful — it tells me which part of the revenue cycle is actually leaking, and why it shows up on the P&L.
Running the machine, and shipping my own
I run the lead pipeline of a U.S. admissions-coaching firm: roughly 100 leads in two months, a ~20% close rate and a $6,500 average deal, supporting about $130,000 in closed revenue. Alongside it I build and operate two products of my own — a transcription app and Chop-Chop.
Trained at one of Mexico's top 3 private universities.
B.B.A. in Business Administration from Universidad Iberoamericana (La Ibero, Torreón campus, class of 2025) — one of Mexico's top 3 private universities. Graduated with a national distinction: Top 100 in the country on the CENEVAL EGEL exit exam, Business Administration & Finance track.
What is that workflow costing you right now?
Pick one process your team still runs by hand — the weekly reconciliation, the report somebody rebuilds every Monday, the follow-up nobody owns. The top number is yours, not mine: plain arithmetic on what you enter. Underneath it, the same cut I measured on a real billing cycle, applied to your number.
Time one person spends inside that one workflow in a normal week.
Everyone in the chain, including the person who only checks it.
Wage plus taxes, benefits, tools and overhead — not the number on the offer letter.
936 hours of paid time a year — 3 people × 6 hours a week × 52 weeks, at $25 an hour.
At the reduction I actually measuredHow this is calculated, and what it is not. The figure at the top is plain arithmetic on the three numbers you entered: hours × people × 52 weeks × your hourly cost. Nothing of mine is in it. The band underneath applies the one reduction I have actually measured — a billing cycle at a U.S. language-services company that went from 4 hours to 1–1.5 hours, a 60–75% cut (Case 02 in Selected Work). That is why the band stops at 75%: it is the best result I have on record, not a number I picked. Your process is not that process, so read this as an order of magnitude worth checking — not a forecast, not a promise, and not a quote for anything.
Whatever that number turned out to be, it is worth ten minutes. Five questions about that one workflow →
Not sure where the hours are going?
Five questions about one workflow. I read the answers before we ever speak, so the first call starts with your bottlenecks already on the table instead of with me asking what you do.
Let's talk.
I work with founders and operators on both sides of the border — as a fractional operator on retainer, or embedded full-time with a team that needs someone to own the machine. Available during U.S. business hours, EST through PST. Happy to walk through any of the builds above in detail.