Advisory Practice

Executive & Founder Coaching

A confidential sounding board for the decisions you cannot workshop with your team or your board. Thirty years of operating experience, applied to your specific situation.

Business leader working through a decision in a strategy session

What this service actually is

Technical leadership is lonely in a specific way. You cannot think out loud with your team about whether to replace one of them. You cannot tell your board you are uncertain about the architecture bet you defended last quarter. You cannot tell your co-founder that you think the roadmap is wrong. The result is that the highest-consequence decisions get made with the least outside input of anything you do.

This is a working relationship that fills that gap. It is not therapeutic coaching and it is not a framework program. It is time with someone who has spent more than thirty years leading technology, security, and business consulting across corporate, private, and individual engagements, and who has made most of the mistakes available in that space already.

Sessions are driven by what is actually in front of you. Common subjects: whether to build, buy, or delay; how to structure an engineering team as it crosses the point where informal coordination stops working; how to have the conversation with an underperforming senior hire; how to present technical risk to a board without either alarming them or being dismissed; how to price and package a services business; when to take money and when to grow slowly.

The distinguishing feature is domain fluency. Coaches who have never shipped software cannot help you evaluate a technical hire, sanity-check an architecture decision, or tell you whether your security posture will survive an enterprise customer's review. Because this practice also does the engineering and security work, the advice is grounded in what current systems and teams actually require.

What clients typically bring

Decisions with no safe audience

A personnel change, a pivot, a co-founder conflict, or an admission of uncertainty that cannot be raised internally without consequences.

First-time engineering leadership

A strong individual contributor now managing people, discovering that the skills that earned the promotion are not the skills the role requires.

Scaling past informal coordination

Around 15 to 25 engineers, everything that worked by conversation stops working. Structure, ownership, and process have to be deliberately designed.

Technical credibility with non-technical stakeholders

Boards, investors, and executive peers who need risk and roadmap translated into their terms without being condescended to or snowed.

Build, buy, or wait

A capital-allocation decision disguised as a technical one, where the honest answer often depends on hiring capacity rather than technology.

Founder burnout and sustainability

The operating pace that got the company here is no longer survivable, and the delegation required to change it feels like risk.

How the engagement works

  1. 01

    Initial conversation, no charge

    A candid 45-minute call about your situation and what you want to be different in six months. If coaching is the wrong instrument, or if I am not the right person for what you are facing, I will say so on that call and where useful point you elsewhere. That happens often enough to be worth stating plainly.

  2. 02

    Context and objectives

    A longer first working session to build real context: the business, the team, the technical estate, the pressures you are under, and the two or three outcomes that matter most. We agree on what we are working toward and how we will know it moved, so the engagement has a spine rather than drifting into a standing chat.

  3. 03

    Regular working sessions

    Typically 60 to 90 minutes every two weeks, remotely, or in person for Orange County and Southern California clients. Sessions are agenda-driven by what is live for you. We work the specific problem, and where it helps, rehearse the actual conversation you have to have, whether that is a board update, a termination, or a renegotiation.

  4. 04

    Between-session access

    Decisions do not wait for the calendar. Clients can reach me between sessions for time-sensitive judgment calls, which is frequently where the highest-value moments occur: a hiring decision that has to be made today, an incident in progress, an offer with a deadline.

  5. 05

    Quarterly review and honest continuation

    Every quarter we review against the objectives set at the start and decide deliberately whether to continue, change focus, or stop. Coaching relationships that run indefinitely on inertia stop being useful, and I would rather end one cleanly than bill for a habit.

What you get out of it

A confidential outside perspective

Someone with no stake in internal politics, no reporting line, and no reason to tell you what you want to hear.

Domain-fluent judgment

Advice from someone who can read your architecture, assess your security posture, and evaluate your technical hires, not only your leadership style.

Rehearsal for hard conversations

Board presentations, performance conversations, terminations, pricing negotiations, and investor updates, practiced before they happen for real.

Frameworks you keep

Reusable ways to make hiring, build-versus-buy, prioritization, and escalation decisions, so the same class of problem gets easier over time.

Access when it counts

Reachability between scheduled sessions for the decisions that will not wait two weeks.

Accountability with a review point

Stated objectives, a regular cadence, and a quarterly honest assessment of whether the engagement is earning its cost.

Who this is for

Startup founders

Technical and non-technical founders making architecture, hiring, and capital decisions with consequences that outlast the quarter.

CTOs, VPs of engineering, and IT directors

Leaders new to the level, or experienced ones without a peer they can be genuinely candid with about risk and uncertainty.

Owners of established businesses

Where technology has become central to the business model and the leadership team has no one with senior technical judgment.

Frequently asked questions

Related services

Book a candid first conversation.

Forty-five minutes, no charge, no pitch. Bring the decision you have been circling and we will work it.

Start a conversation