Technical Working Session

A focused working session for one difficult technical decision.

Some problems do not require a large consulting engagement. They require an experienced person who can understand the situation quickly, challenge assumptions, identify tradeoffs, and help determine what to do next.

Common reasons to book a session

Architecture and product

  • Rebuild or refactor
  • Review a proposed architecture
  • Define an MVP
  • Prioritize technical debt

AI and delivery

  • Review an AI product idea
  • Evaluate AI-generated code
  • Diagnose stalled delivery
  • Introduce AI coding tools

How it works

  1. Submit the request.
  2. Holden reviews the fit.
  3. If accepted, receive payment and scheduling instructions.
  4. Complete the short intake.
  5. Attend the session.
  6. Receive a concise written recap of conclusions, tradeoffs, and next steps.

You do not need a formal presentation or extensive documentation. A concise description of the situation and any directly relevant material is usually enough. Extensive codebase or document review may require a Technical Risk Review.

What this is not

This is a paid advisory session, not a discovery call or sales presentation. It does not include staff augmentation, implementation work, or an open-ended advisory relationship. The goal is to create clarity around a defined problem.

Ready to work through your decision?

Describe the problem you are facing and what a useful outcome would look like. I review every request personally.

Request a Working Session

Engagements are scheduled by mutual availability and conducted remotely.