// WRITING / TAGS / CONSULTING

How a small technical consultancy actually works. Engagements, judgment calls, and the operational discipline behind the model.

Consulting is the business we're in, and the way we do it is deliberate. We don't take fixed bids that incentivize cutting corners. We don't extend engagements by making ourselves indispensable. We come in, find the leverage, build what's needed, transfer ownership, and leave. That model is harder than it sounds and easier than the alternatives.

These posts are about the practice of consulting itself. Scoping, engagement models, when to say no, how to know if we're the right fit, what the discovery call looks like, what we charge for and what we don't. Some of it is field notes from real engagements. Some of it is the position papers that explain how we think.

If you're considering working with us, this is the category to read. If you're building your own practice, you'll probably find something useful here too.

// POSTS 5 entries
  1. FIG. 01

    Eight Weeks to Twelve Minutes

    We took an eight-week release cycle down to twelve minutes. The pipeline work was the easy part. What the acceleration revealed was that most of those eight weeks wasn't work. It was dwell time, and the processes that owned that dwell time had never had to justify themselves against a world that moved faster.

  2. FIG. 02

    The Workaround Becomes the Curriculum

    When a team doesn't understand their tooling well enough to trust it, they build around it. The build-around becomes what everyone learns. Nobody ever learns the tooling. The distrust gets baked into onboarding. New engineers inherit the wrong mental model and build on top of it. The workaround defends itself.

  3. FIG. 03

    Why Your CI/CD Pipeline Has 47 Steps and Nobody Knows Why

    The pipeline doesn't have 47 steps because 47 things need to happen. It has 47 steps because trust eroded over time and every erosion event got a new step added on top. The steps aren't doing work. They're doing anxiety.

  4. FIG. 04

    Why Infrastructure Is Always Somebody's Second Priority

    Infrastructure work has a visibility problem baked into the nature of the work itself. When it's working nobody notices. When it fails everyone notices. That asymmetry shapes every prioritization conversation infrastructure teams ever have, and it doesn't fix itself with better communication.

  5. FIG. 05

    The Plan Is Not the Schedule

    Good planning isn't about staying on schedule — it's about making better decisions in flight, taking on deliberate technical debt with clear eyes, and arriving at the right destination even when the route changes.