Click anywhere to skip
ABBIE ABANES

Ops & Workflow Manager · Available Now

Ops systems that don't fall apart
when you look away.

I find where a process is being held together by hand, then build whatever closes the gap: intake, escalation, reporting, whatever's actually broken.

Ops & Workflow Management Systems & Automation Fractional or Full-Time
47hr → 2hr average response time on client intake

01 · The Pattern

Ops breaks the same way every time

Small teams rarely lose to bad people. They lose to no system. The signs show up long before anyone calls it a process problem.

01

Every request lives in one head

The one person who knows the status of everything becomes the bottleneck, and the single point of failure.

02

Deadlines slip quietly

Nobody's watching the clock until a client asks why they haven't heard back in a week.

03

The spreadsheet outgrew itself

One tab became six, cross-referenced by memory, breaking every time someone new touches it.

04

Fixes get bolted on, not built in

Every new problem gets a workaround instead of a system, until the workarounds are the system.

02 · What I Do

Three ways I show up

The day-to-day work, the systems behind it, and the fractional layer on top.

01

Ops & Workflow Management

Running the day-to-day (intake, tracking, escalation) so nothing slips and nobody's chasing status updates.

→ Built the SLA escalation system that catches overdue client requests automatically, before a client has to ask.
02

Systems & Automation

Designing and building the tools themselves: forms, databases, AI-assisted drafting, approval flows.

→ Migrated a design-build studio off six disconnected spreadsheets into one working platform, MVP shipped solo.
03

Fractional or Full-Time

Coming in part-time or full-time, depending on scope, to audit a process, then either fix the workflow or build the system, whichever the business actually needs.

→ Start with what's broken, not a build you don't need. Some engagements end in a system, some end in a simpler process.

03 · Deployed Systems

Live and in-progress work

Real client systems, built solo, end to end. More get added here as they ship.

IntakeFlow

● Live

Client intake and SLA escalation: every request logged, drafted, and watched for deadlines. No manual step in between.

Tally n8n Airtable Gemini Slack
~10 min saved per request View case study →

Ops Platform

● In Progress

One platform replacing six spreadsheets for a design-build studio: billing, milestones, and approvals in a single source of truth.

Dashboard Billing Logic E-Sign Client View
6 core features shipped View case study →

04 · By The Numbers

What changes once it's running

2hr
avg. response, down from 47hr
0
missed SLAs since launch
6→1
spreadsheets replaced by one platform
100%
migrated records verified line by line

05 · How I Work

Diagnose before you build

Same process whether it ends in a full system or just a tighter workflow.

01

Diagnose

Sit with the actual process, not the org chart version of it, and find where time and information are getting lost.

02

Design

Map the fix in plain terms first. Sometimes that's a new tool, sometimes it's just a clearer handoff between two people.

03

Build

Ship something simple and reliable, built plainly, on purpose, so a small team can maintain it after I'm gone.

04

Handoff

Document it, train whoever owns it next, and stay reachable for the first real-world edge cases.

06 · About

Who's running this

Portrait of Abbie Abanes
Based in the Philippines · Working with teams anywhere

I've built the ops function from zero, twice. Once scaling a team from two people to twenty while holding a 99% SLA. Once running the QA pipeline that took AI training data from 80% to 95% accurate.

I'm Abbie Abanes. I started out closing B2B deals in agricultural trade, which is where I first watched a process break under its own weight. I've been fixing that exact problem ever since, just with better tools.

At one startup, I built the ops function alongside the founders, from a team of two to over twenty, without letting SLA fulfillment slip below 99%. At another, I ran client onboarding and built the human-in-the-loop QA process behind an AI training pipeline from scratch, then scaled it as error patterns emerged. Now I do the same work independently: diagnose what's actually happening in a process, then build whatever closes the gap.

Right now that's ops & workflow consulting for small teams, fractional or full-time depending on the scope: the diagnostic work, the systems, the follow-through to make sure it actually sticks.

07 · FAQ

Before you reach out

Are you full-time or fractional?

Depends on the scope. A lot of this work fits well as fractional: diagnose, build, hand off. But I'm also open to full-time if the role and the problem are the right fit. Worth a conversation either way.

What if we don't actually need a full system?

Then we don't build one. Some engagements end with a tighter process and a clearer handoff between two people, no tooling involved. I'd rather tell you that upfront than sell you a build you don't need.

Who maintains it after you leave?

Whoever owns the process day to day. Every build ships with documentation and a handoff session, and I stay reachable for the first real-world edge cases that always show up in week one.

What do you actually build with?

Whatever the team can maintain without me: Airtable, n8n, Tally, Slack, and lightweight custom dashboards when a spreadsheet genuinely can't hold the logic anymore. No tool for its own sake.

How fast can we start?

Usually within a week of the intro call. Diagnosis starts immediately; the build timeline depends on scope, but you'll have a clear plan before anything gets built.

08 · Get In Touch

● Available

Let's talk about what's
broken in your process.

Whether that means a new system or just a better way of working, I'd rather start with what's actually broken than pitch you a build you don't need.

Abbie Abanes
work.abbiea@gmail.com
+63 995 524 3072
Mo—Fr 9am—6pm PHT
Abbie Abanes.