// SERVICE

General Tech Advisory

Sometimes you don't need someone to build — you need someone experienced to look at what you've got and tell you the truth about it. Is this architecture going to survive the next year? Is this stack choice going to bite you? Should you buy or build? I give you a straight answer and the reasoning behind it.

// WHAT YOU GET

Concrete deliverables.

  • Architecture and code reviews
  • Technology and stack selection advice
  • Technical due diligence (for acquisitions or investments)
  • Roadmap and prioritization sessions
  • Build-vs-buy analysis
  • Written recommendations with tradeoffs

// GREAT FIT FOR

  • Founders about to commit to a big build and wanting a sanity check
  • Teams in disagreement on technical direction
  • Investors or acquirers doing technical due diligence
  • Boards or execs who need an independent technical read

// PROBABLY NOT A FIT

  • Ongoing fractional CTO retainers
  • Team management or hiring decisions
  • Long-term architecture ownership

// FAQ

Common questions.

What is a technology advisory session?

A short, focused engagement — anywhere from a half-day session to two weeks — where an experienced outside technologist reviews your architecture, stack, or roadmap and gives you a straight written answer. You brief me, I dig in, and you get recommendations with the tradeoffs spelled out, plus a follow-up call to work through questions.

When does it make sense to get a second opinion on a technical decision?

Before the expensive commitment, not after. The classic moments: you're about to sign off on a big build, your team is split on technical direction, you're choosing a stack you'll live with for years, or you're acquiring or investing in a company whose technology you can't evaluate yourself. A short review now is much cheaper than unwinding the wrong decision later.

Are you available as a fractional CTO?

Not on an ongoing retainer — I keep advisory work short and scoped so the advice stays independent. If you need someone to own architecture or manage a team long-term, that's a hire. What I can do is help you make the big decisions well, including helping you figure out what that hire should look like.

What do I actually get at the end of an advisory engagement?

A written recommendation in plain English: what I reviewed, what I found, what I'd do in your position, and the tradeoffs of each option. It's a document you can share with your team, your board, or your investors — not a slide deck of generalities. Plus a follow-up call to pressure-test it.

Can you review code or architecture under NDA?

Yes — NDAs are routine for this work, especially for technical due diligence on acquisitions or investments. Your code and findings stay confidential, and the written deliverable goes only to you.

// NEXT STEP

Sound like what you need? Let's talk.

Describe your situation in a few sentences. I'll tell you whether I can help, and how I'd scope the work.

// OTHER SERVICES

View all →