About · systems and operating memory

I look for the structure underneath the work.

CRM, automation, payments, AI workflows, documentation, and continuity are different surfaces of the same problem: helping work survive complexity, handoffs, and time.

BasedValencia City, PH

WorksRemote-first · async

Leaves behindSystems people can explain

01 · The thesis

Most operational breakdowns are not effort problems. They are structural.

This site began because I kept needing my own notes. Payment processing taught me that undocumented knowledge walks out the door with people. CRM work taught me that a system nobody can explain is not much of a system.

So I write the manual for everything: first as working reference, then as a public artifact. The library doubles as a portfolio, but that is the side effect. Its primary function is still the same one it had on day one. It is where I look things up.

I work across roles because real operations do not respect job-title borders. A handoff can begin in marketing, break in a CRM, surface in payments, and finally become a management problem. The useful unit of analysis is the whole path.

02 · Working method

From field reality to something that lasts.

The software matters. The sequence matters more.

01 Observe

A survey begins before the tool opens. I look for handoffs, workarounds, exceptions, and what experienced people notice without writing down.

02 Model

I reconstruct the mechanism: dependencies, ownership, incentives, failure modes, and the information each decision actually needs.

03 Build

Then the structure becomes fields, automations, safeguards, interfaces, fallback logic, and a path people can follow under pressure.

04 Write

The handoff is not finished until the next person can understand, verify, repair, and extend what was built.

Documentation is not the receipt for the system. It is one of its working parts.

03 · Evidence

The same pattern, in different rooms.

Different tools and industries. The recurring work is finding structure, reducing ambiguity, and preserving judgement.

Payments and systems operationsKnowledge spread across 10+ processors

Reverse-engineered undocumented workflows and built institutional memory around decisions that had previously lived in individual heads.

Zero knowledge loss after key departures

Service operationsField-to-office handoffs

Introduced structured capture and fallback logic so incomplete information stopped becoming reconciliation fire drills.

98% process compliance

CRM and automationA production operating spine

Aligned 76 fields, 24 automations, and a full QA layer to the way the work actually moved rather than an idealized pipeline.

About 70% faster lead response

Marketing and revenue systemsTwo audiences, one operating model

Connected SEO, email, pipelines, and automation across UK and US audiences without hiding the differences between them.

34.2% open rate · 18 consultations

Founder continuityOwnership that survives absence

Translated “we need to be more organized” into explicit ownership, visible work, and routines that reduced founder dependency.

15+ hours returned each week

04 · The through-line

Competence over appearances. Mechanisms over theatre.

My first question is rarely “what should I do?” It is “how does this work?” Once the mechanism is clear, the fix usually becomes reconstructable instead of mysterious.

That is why the same approach keeps working across CRMs, payment processing, marketing engines, organizational design, and the occasional motorcycle. They are all systems of forces, tolerances, dependencies, and consequences.

Off the clock, I tend toward machines with mechanical honesty and fiction about hidden infrastructure, reality, and control. The subjects change. The curiosity does not.

05 · Working together

Two doors, clearly marked.

Roles, collaboration, writing, and anything addressed to me directly come to me. Full build-and-handoff systems engagements go through a separate studio.

Choose a door → See the evidence

A note from the workbench

The work should keep making sense after the person who built it leaves the room.

That standard runs through every artifact here — and through the Operator Workbench, a set of local-first tools that turn the thinking into instruments you can actually use.