I learned operations from the inside out.
I’m Abby, a business systems strategist and implementor based in the Philippines. Around a decade in corporate administration, business ownership, remote operations, and years of hands-on systems work taught me that good systems make the work clearer for the people doing it.
Behind the systems
I learned operations from the inside out.
I’m Abby, a business systems strategist and implementor based in the Philippines. Around a decade in corporate administration, business ownership, remote operations, and years of hands-on systems work taught me that good systems make the work clearer for the people doing it.
Behind the systems
Client Review
The best EA ever. Highly recommend Abby to be in your corner. The only reason for ending is that Abby was no longer available as she advanced her career to outgrow the support we needed.”
T. FREARSON
Business Systems Strategist & Implementor
Hi, I’m Abby.
I am a business owner, a mum of three, and the person who naturally looks for the structure behind how work gets done.
Before working remotely, I spent around a decade in corporate administration, where I learned the discipline behind documentation, coordination, process, follow-through, and keeping moving parts organised. In 2014, I also started my first business — a cake business — and later built a clothing brand during the pandemic.
Running businesses while balancing family life taught me something formal processes alone never could: a system only works when real people can actually use it. The prettiest workflow on paper means very little if the owner still has to remember every handoff or the team does not know what happens next.
Since moving into remote work, I have combined that operations background with hands-on CRM, automation, website, landing page and funnel design/build, and backend systems implementation. Today, I support coaches and service-based small businesses that need clearer structure behind the work they are already doing.
I work across the business, not just inside one tool.
FROM SUPPORT TO SYSTEMS
My roots are in support. The work I do today is bigger than the task list.
I value my background in administration and VA work because it taught me execution, attention to detail, customer service, and what it is like to work inside the day-to-day reality of a business.
That foundation still matters. But clients now bring me in to understand how the business operates, identify process problems, shape a more practical system, implement what is needed, and help make the setup usable for the people working inside it.
I can still get very hands-on. I just do not stop at execution.
HOW THE WORK EVOLVED
I
Good systems are practical before they are impressive.
Clear structure, sensible automation and documentation matter just as much as the build itself.
What years in administration, business ownership and systems work taught me is simple: the system has to work for the people using it.
Not everything should be automated. Some steps are better kept manual, others work best as a hybrid. And if a system only makes sense to the person who built it, it is not finished.
The method
VISTA — business first, then the build.
VISTA gives systems and operational work a clear order. We understand the current state first, decide what deserves attention, structure the future state, implement it, then refine it as the business changes.
V
I
S
T
A
View the current state
Structure the future state
Understand how the business works today across people, processes, platforms, client journey, handoffs, pain points, and what already works.
Identify gaps and priorities
Find bottlenecks, duplicated work, missed follow-ups, unclear ownership, disconnected tools, unnecessary steps, and risk — then decide what matters first.
Adapt and optimise
Design how the business should work instead, including workflows, responsibilities, CRM structure, data, automation logic, customer experience, and supporting processes.
Transform through implementation
Build, connect, migrate, automate, test, document, and launch the agreed system so the plan becomes usable.
I do not start with “What should we automate?” I start with “What should happen, and what does the business actually need?”
Keep the system useful by refining workflows, updating documentation, and adjusting as the team, offers, volume, or priorities change.
What I bring together
Operations thinking. Systems structure.
Hands-on implementation. Customer-facing sense.
The work is strongest when these are connected rather than treated as separate departments.
Operations thinking
Systems structure
Hands-on implementation
Customer-facing sense
priorities, ownership, delivery, team impact, handoffs, and the day-to-day reality behind the process.
building the workflows, forms, pipelines, automations, websites, landing pages, funnels, integrations, documentation, and supporting backend setup.
how the client journey, CRM, workflows, data, tools, and responsibilities need to connect.
using my creative background to make websites, landing pages, sales pages, funnels, forms, resources, and client touchpoints feel clear, intentional, and aligned with the brand while still connecting them to the business system behind them.
Working style
Systems people understand, not just systems that work.
I build for the people who have to use the system after the project is handed over.
I will ask questions before building because I want to understand how you actually want the business to run. If a manual step gives your team useful control, we can keep it manual. If automation removes repetitive work, missed follow-ups, or unnecessary errors, we can automate it. If the tool you already have can support the process well, I would rather make that work than recommend another subscription for the sake of it.
The goal is not the most impressive diagram. It is a business that is easier to understand, easier to operate, and easier to improve.
Client Review
Abby was absolutely amazing. She built amazing power points which helped us land or extend clients, kept my calendar and inboxed managed and enabled me to be much more productive! An amazing service all around
J. MCCALL
Tool stance
GoHighLevel is a strength, not the whole strategy.
GoHighLevel is currently my strongest implementation platform. I build CRM structures, pipelines, forms, calendars, workflows, funnels, and automation inside it. I also work across connected tools when the business process calls for them.
But the platform is not the strategy. If your current tool already fits the business, I will not recommend a migration just because GHL is familiar to me. The right setup is the one that supports the business process and the people using it.
The same applies to AI. I use it where it can genuinely reduce work, support decisions, improve internal processes, or make a workflow more useful — not because every system needs an AI layer.
Common questions
How do you decide what to automate?
I map what should happen first, including who owns each step. Some steps are best kept manual for judgement or control. I automate repetitive work when it makes the process more reliable and easier to run.
Who does Abby work with?
I work with coaches and service-based small businesses, including founders, internal teams, agencies and existing OBMs. I can help when you need a clearer plan, a hands-on systems build, or continued improvement after launch.
Need someone who can see the bigger picture and still build the details?
Tell me what is happening behind the scenes, and we can work out the right next step.
Business first. Tools second.
© 2026 Partner with Abby. All rights reserved.
Every project supports a child through Unicef.
LINKS
PARTNER WITH ABBY.
Partner with Abby — Business systems and hands-on implementation for coaches and service-based small businesses that want a backend that makes sense.