Field Notes

Notes from the field.

What we see in the field, and how we think about it.

  1. Note 01 Why we built RYEHAUS A founder's note on why the traditional MSP model can't keep up, and what we built instead. Read →
  2. Note 02 When you're the only one who knows where everything is The hidden job a CEO takes on when technology partners are scattered across categories, and what changes when one partner spans them. Read →
  3. Note 03 How to tell AI leverage from AI theater A buyer's framework for AI spend: four questions to ask before you commit budget, and what a real deployment looks like. Read →
  4. Note 04 Why threat actors prefer growing businesses now The structural reasons the threat economy flipped from selective targeting to volume, and the four controls that actually matter at SMB scale. Read →
  5. Note 05 When you should stop using a traditional MSP A decision framework: six observable signals that the model your MSP runs on no longer fits the business it's serving. Read →
  6. Note 06 When you already have someone in the seat For CEOs with internal IT: how to add support without displacing the team you already have. Read →
  7. Note 07 What an AI-native operating model actually requires How to tell architecture from features when evaluating a technology partner, with four questions that surface the structural reality. Read →
  8. Note 08 Defense starts the day you sign The security gap most onboarding leaves open, and what the first sixty days look like when defense runs in parallel with discovery. Read →
  9. Note 09 The true cost of vendor sprawl A framework for the four costs of vendor sprawl, with back-of-envelope math for a growing business, and the order of operations for fixing it. Read →