AS
Aaron SuarezValencia City, PH · remote-first
Universal searchFind your way through the site
A workflow, product brief, and writing paper arranged on a desk
Field log · observations from real work

Field Notes

Short arguments about the moments when work bends, breaks, or quietly succeeds: handoffs, systems, tools, incentives, and the details a dashboard cannot see.

Entries17
Threads5
Reading orderNewest first
Reading desk

Ideas worth carrying forward.

Showing all 17 notes.

Field Notes

34.2% Open Rate from a Landlord List. What Actually Worked.

City-specific subject lines outperformed generic ones by 11 percentage points. Here's the breakdown from the Dual Wing campaign.

Read note →
Field Notes

GHL 101: Why I Published Over a Year of Notes for Free.

Almost everything useful about GoHighLevel lives behind a paywall. That's an operational problem — and operational problems are what I fix.

Read note →
Systems

Stop Training People. Start Building Systems That Set Them Free.

When teams keep asking the same questions, the issue is rarely memory — it's the environment around the work. And environments can be redesigned.

Read note →
Operations

The Escalation Tax: What It's Costing You Every Day.

Ten interruptions a day costs more than ten answers — every escalation bills the switching time too. 10/day can mean 3+ hours of senior focus gone.

Read note →
Operations

Handoffs Are Where Work Goes to Die.

The artifact passes. The reasoning doesn't. The next person starts over, makes wrong assumptions, or stalls waiting for context that should have been included.

Read note →
Operations

The Automation Trap: When You Automate a Broken Process.

Automation amplifies what's already there. If the process is broken, automation just breaks it faster and at scale.

Read note →
Systems

Documentation Nobody Uses Is Just Organized Noise.

Most documentation fails not because it's wrong — but because it's not built for the moment someone needs it.

Read note →
Field Notes

Why Local SEO Beats National for New Businesses.

Rightmove and Zoopla own the national terms. The only realistic path for a new business is hyper-local long-tail. Here's the logic.

Read note →
Systems

The Difference Between a Tool and a System.

You bought the CRM. You have the tool. You don't have the system. Here's the difference.

Read note →
CRM

CRM Isn't Just a Database. It's an Operating System.

Most teams use their CRM as a filing cabinet. A well-architected CRM is an operating system for how your team works.

Read note →
CRM

Pipeline Stages That Lie to You.

When "Proposal Sent" means three different things depending on who moved the deal — the stage isn't a stage. It's a conversation.

Read note →
Practice

Reputation Is Written in Small Decisions.

Most people think reputation is built in big moments. I think it grows somewhere much quieter.

Read note →
Systems

Preserve the Reasoning, Not Just the Result.

We remember the conclusion and forget the path. This library exists to store the reasoning, not just the results.

Read note →
Practice

Knowledge Is a Moving Horizon.

Every new area I learn reveals three more I haven't. The map keeps expanding — and that's the part I've come to enjoy.

Read note →
Practice

The Second Version Is the Real One.

The first version of almost everything I build is an experiment. The second version is where the design actually starts.

Read note →
Systems

The Best Systems Disappear.

The first automation I built, I wanted everyone to notice. Now I have the opposite goal: if someone notices the system, something probably went wrong.

Read note →
Practice

Understand Before You Build.

When someone asks for a solution, my instinct is to understand the problem first. Over time I've realised the questions are often the work.

Read note →
↑ top