G1 Guides

The guides we wish we had the first time.

Sixteen operator-written guides across seven categories. Written in the same voice as our handbooks, the same voice we use in client meetings. No “ultimate” anything, no listicles, no AI-generated filler. Read before a discovery call, or instead of one.

Start here Filter by role Book a call instead
G1.1 Start here

Two cross-cutting intros.

If you read only two guides before our first conversation, these are the ones.

Start hereMedium · 15-25 min

How we work with Claude

What Claude does at each phase of an engagement. What stays human. How to tell good AI-assisted work from AI slop at a glance.

Start hereShort · 5-10 min

Reading your Signature Handbook

How to navigate a handbook in week one, how to hand it off to an operator, and how to iterate the quarterly refresh.

G1.3 By role

If you are a...

Founder
Start with the cross-cuts, then pricing and process by service line.
CTO / engineering lead
Architecture, evals, security, the serious stuff.
Security lead
The three security guides in order.
CMO / growth lead
Positioning, SEO / GEO, outbound.
PM / product manager
Ship the feature without surprises.
Operator (non-tech)
Use Claude well without engineering help.
G1.4 What these guides are not

Three honest warnings.

These guides will teach you a lot. They will not replace an engagement where one is warranted.

  • They are not exhaustive. They represent the parts of our practice that generalize. The parts that do not generalize - the specific judgment calls for your stack, your customers, your regulatory surface - live in an engagement.
  • They are not pitch decks. We tell you when a guide argues for work that we sell. You can always do it yourself. If you do, and you need a review, book a twenty-minute call.
  • They are living documents. Every guide has a “last updated” date in the header. When we change our mind about something, we update the guide and note the change at the top.