Ways to work with me

Oak outdoor table with a closed MacBook, a yellow mug, a black smartphone, stainless steel water bottle, a potted plant, a plate of salad, and a napkin.
  • There’s no single moment when scaling becomes “hard” it shows up as a series of small cracks, missed decisions, unclear ownership, work slowing as headcount grows.

    How we work together depends on where you are, how fast you’re growing, and what support already exists.

    All engagements are grounded in the same method but shaped to your context.

    • Decisions stall unless you’re involved

    • New hires take months to ramp up because “how things work” lives in people’s heads

    • The same mistakes repeat because there’s no shared process

    • You’ve outgrown the kitchen-table way of working but haven’t replaced it yet

    • Cross-team handoffs are messy, and things regularly fall through the cracks

      If two or more of these feel familiar, the issue isn’t more people, it’s operational clarity.

    • The Clarity Sprint (4 weeks)

    • The Operating System Build (90 days)

    • Embedded Partner

    • Custom Design & Facilitation

  • For teams who need direction fast.

    What you get:

    • Operational audit: Where are your biggest bottlenecks?

    • Workflow mapping: How does work actually flow (vs. how you think it does)?

    • Priority playbook: The 3-5 fixes that'll make the biggest impact

    • Implementation roadmap: What to tackle first, second, third

    Best for:
    "We know something's broken, we're just not sure what."

    Outcome:
    A practical blueprint leaders can act on immediately.

  • For teams ready to fix it properly.

    My Blueprint:

    Phase 1 (Weeks 1-4): Diagnose

    • Full operational audit

    • Decision-making bottleneck analysis

    • Workflow documentation gaps

    • Cross-team handoff failures

    • Output: Diagnostic report + prioritised fix list

    Phase 2 (Weeks 5-8): Design

    • Build decision frameworks

    • Document core workflows

    • Create role clarity maps

    • Design operational rhythms

    • Output: Your Operating Playbook v1.0

    Phase 3 (Weeks 9-12): Deploy

    • Implement 2-3 highest-priority systems

    • Train leadership team

    • Embed new operating rhythms

    • Measure early wins

    Output: Working system + adoption plan

    Best for: "We're serious about scaling the right way."

  • For teams who need ongoing systems evolution.

    What you get:

    • Monthly system tuning (as you scale, what breaks?)

    • Quarterly process improvement sprints

    • Leadership coaching on embedding new rhythms

    • On-demand troubleshooting

    Best for:
    Post-Blueprint teams or those navigating continuous growth.

    Outcome:
    Your systems keep pace with growth without constant rework or founder firefighting.

  • Leadership development that changes how people lead day to day.

    This work builds leadership capability that holds under pressure, with inclusion embedded into everyday decisions, not bolted on.

    We focus on:

    • Leadership habits that scale beyond the individual

    • Psychological safety and allyship in real situations

    • Inclusive decision-making when the stakes are high

    Delivered directly or in partnership with other organisations.

    Best for:
    Leaders who want behaviour change, not box-ticking.

    Outcome:
    Consistent leadership, stronger trust, and teams that stay.

Not sure which option is right?