1. My company has 18 people. Are we big enough to need this, or should I wait until we're larger?

The honest answer is that 15–25 employees is exactly when this work matters most — not because the problems are largest yet, but because the decisions you make now are still cheap. The way you structure accountability, how you onboard people, what you pay and why, how you handle the first underperformer — these decisions set patterns that compound in both directions. Made deliberately at 18 people, they build the foundation that holds at 40. Made reactively at 40, they cost you significantly more in time, money, and often in people you didn't want to lose.

Waiting until you're larger doesn't reduce the work. It increases it, and adds urgency to it. The founders who tell me they wish they'd started sooner almost all say the same thing: we were too busy to build it before we needed it, and then we were too busy and also on fire.

2. We already use Gusto / Rippling / BambooHR. Doesn't that cover the HR side?

HR software handles the administrative layer well: payroll, time tracking, onboarding workflows, basic document storage. What it doesn't do — and can't do — is make judgment calls. It can't tell you whether your compensation approach is creating compression problems you'll feel in 18 months. It can't give you the language for the performance conversation you've been avoiding. It can't look at your management structure and tell you where it will break when you hire the next six people.

The software is infrastructure for the mechanics. This work is about the thinking that sits underneath the mechanics — the structure, the decisions, and the judgment that determines whether those tools are being used in a way that actually serves your organization. Most of my clients have all the software. That's usually not what's generating the friction.

3. I'm worried about adding bureaucracy. We've built a culture that doesn't feel corporate, and I don't want HR to change that.

This is the most common concern I hear from founders, and it's a legitimate one — because the wrong kind of HR infrastructure does exactly that. Policies that exist to protect the organization from its own people. Processes that add steps without adding clarity. A handbook that reads like it was written by a lawyer for a company nobody actually works at.

That's not what this work produces. The goal is structure that makes your culture more deliberate, not less. The companies that lose their culture as they scale almost always lose it the same way: the founder stops being able to personally carry the context, and there's nothing built to carry it instead. The norms become unspoken again, inconsistently applied, and the culture drifts into whatever the loudest voices in the room are modeling. Good people infrastructure doesn't replace your culture. It's the mechanism that carries it when you can't be in every room.

4. How is working with you different from hiring a full-time HR person?

A full-time HR hire makes sense when you have enough ongoing, day-to-day HR work to justify a full-time salary — typically at 50–75 employees, depending on how fast you're growing and how complex your operations are. Before that point, a full-time hire often means you're paying a senior salary for someone who spends a significant portion of their time waiting for the work to arrive, or doing administrative tasks that software handles more efficiently.

What I offer is the strategic and structural thinking without the full-time overhead — someone who has worked through these problems across many companies at your stage, rather than an in-house person whose entire reference point is your organization. It's also not permanent overhead: a project ends, a retainer can scale up or down, and you're not carrying a headcount through a slow quarter. When you do reach the point where a full-time hire makes sense, I'll tell you — and I can help you hire that person and set them up to succeed.

5. I have a specific, urgent situation right now — someone I need to let go, or a performance issue that's gotten serious. Can you help with just that, or do I need to start with the full diagnostic?

You can start with the immediate situation. I work with founders on active, specific people problems regularly — and those situations often don't wait for a six-week engagement. If you have something that needs to be addressed now, the right starting point is a direct conversation about what you're dealing with, what your options are, and how to move through it in a way that is legally sound and doesn't make things worse.

The diagnostic work is valuable precisely because it identifies the structural root of why that situation developed — so the same pattern doesn't repeat with the next person in a similar role. But it doesn't have to come first. The immediate situation gets addressed. The structural question gets answered. Usually in that order.

6. What do I need to have in place before we start working together?

Less than you think. Most founders arrive with a patchwork of things: a handbook that came from a template, some offer letter they've been modifying for two years, a compensation approach that made sense at the time, and a general sense that they've been figuring this out as they go. That's a completely normal starting point and exactly the situation this work is designed for.

What helps more than documentation is clarity on what's generating the most friction right now — which hire didn't work and why, which conversation has been avoided and for how long, where you feel the organization straining under growth. That context is more useful than any document you could prepare, and the intake process for any engagement is designed to surface it clearly.

7. How long does it typically take to see results?

That depends on what you mean by results, and it's worth being specific about the difference between two things.

The immediate clarity — a cleaner picture of what's actually happening in your organization, what's driving the friction, and what to do first — that typically arrives in the diagnostic conversation, or in the Kickstart session. Founders consistently describe that conversation as one of the most clarifying they've had about their organization. That part is fast.

The structural change — where the patterns shift, the team starts operating differently, and the people problems stop compounding in the same ways — that takes longer. Most organizations working through a significant structural build see meaningful change in 60–90 days. The work that sticks is the work that gets embedded into how the organization actually operates: the conversations managers start having consistently, the onboarding process that runs without the founder in every loop, the compensation framework that means pay conversations stop happening as surprises. That kind of change compounds over time, not overnight.

8. What happens if we start working together and it turns out I need something different from what we scoped?

Every engagement starts with a diagnostic for exactly this reason. The presenting problem — the thing that made you book the call — is rarely the only thing worth addressing, and sometimes it's not even the most important thing. The diagnostic creates a shared, honest picture of what's actually driving the friction before we decide what to build. That means the work we scope together is grounded in what your organization actually needs, not what seemed most urgent in a first conversation.

If something changes mid-engagement — if an unexpected situation surfaces, if the organization shifts in a way that changes the priorities — we recalibrate. Project work is scoped before it begins, so scope changes get a direct conversation rather than a surprise invoice. Retainer engagements are designed to flex with what the organization needs month to month. The goal is that the work remains useful as your situation evolves, not locked to a plan that was right three months ago.