Foundations First
My mom arrived in Missouri young, newly married, pregnant, and alone. No blueprint. No family within thousands of miles. Just drive, faith, and a very practical understanding of what had to happen first.
She didn't try to build everything at once. She got a job as a nurse. She found a community, a group of Filipino women who became our godmothers, our titas, our family by choice rather than blood. She found the house in Illinois that became our childhood home. She built a nursing career that lasted over 45 years (and counting).
And when my brothers were born, she sent them back to the Philippines.
Not because she wanted to. As a mom now, I understand exactly how much that cost her. We've had some of those harder conversations as adults, and there's a longing there she doesn't try to hide. But my mom is practical. She knew what the decision made possible. My brothers grew up surrounded by family, immersed in a culture they would have never known otherwise. She stayed and laid the ground that everything else would be built on.
She didn't hesitate because she understood something most founders resist: before anything can grow, something has to hold.
I sat across from a founder recently. Her business had a deadline looming, a product that needed to turn profitable, and a calendar full of reactive work. Client follow-ups that should have been automated. Manual processes eating hours she didn't have. She was drowning in the doing and losing sight of the why.
We had to stop. Not to add more to the list. To go back.
What was historically converting? What were we avoiding? The answers came slowly, then all at once. Selling wasn't her strength, and she'd been quietly working around that fact for months instead of naming it. Once it was named, the real question surfaced: could the business afford to hire someone who could sell? And if so, what would that mean for where the money was going?
There were some long pauses. She said "you're right" at one point and I told her it wasn't about being right. It was about making a decision, sticking with it, and the decision was hers to own. I could sit with her in it. I couldn't make it for her.
That's the work nobody puts in the project plan. Circling back. Asking the uncomfortable question. Naming what's been quietly avoided. Rebuilding the foundation that got skipped in the rush to launch.
Before we could talk about growth, we had to answer three questions she had been avoiding: What are we actually doing? Why does this exist? What has to be true for this to hold?
My mom had answers to all three before she made a single move. Most founders I’ve encountered are well into their businesses, and often find them selves circling back to the questions.
I'm not exempt from this. When I started Agile Fox, I was building the website, landing contracts, moving fast. What I almost skipped was the philosophy, the actual north star that would tell me which clients to take and which ones to walk away from. I caught it. But I also missed the financial foundation early on. Despite growing up watching my mom's financial discipline up close, I had to go back and build the expense tracking and tax systems that should have existed from day one.
I know what it feels like to be the founder in the awkward pause. That's why I don't rush people through it.
The foundation work is slow. It's unglamorous. It requires sitting with questions that don't resolve quickly. And it has a real cost, my mom understood that better than anyone. The decision to send her sons away wasn't painless. It was deliberate. She stayed close to what that choice actually meant, and she made it anyway because she could see what it was protecting.
That's the part that gets lost when founders skip the foundation. It's not just that the structure is weak. It's that decisions get made without any real sense of what's at stake. Speed without consequence. Building without knowing what you're building toward.
My mom came to this country with almost nothing and built a life that held. She made decisions I'll never fully understand from the inside. She did it without a framework, without a consultant, without a checklist. Just clarity about what came first and the discipline to do it in order.
That's what Agile Fox exists to help founders do. Not to hand them a template. To help them figure out what their sequence actually is, what has to be built before anything else can hold, and to sit with them in the pauses while they work it out.
Foundations first. Everything else follows.
I wrote this with AI assistance for drafting and editing. The thinking, the stories, and the framework are mine.
