Working Notes on Agent Systems/Brad Zhang

Correspondence desk

Write with a specific problem. Expect a specific reply.

This is a desk, not a funnel. The publication stays free; the desk is where scoped, paid work begins — usually with a short letter about a workflow that is too important to stay fragile.

Best channel: DM on X · Typical response: within a few days, with a concrete read on fit

Three ways engagements usually start

01 / Design partner sprint

Make one AI workflow reliable enough to ship.

Two weeks

Best for: Agent tooling, internal copilots, devtool UX, technical docs, memory, evals, workflow automation

Outcome: A working module, product surface, or documentation workflow with constraints, examples, quality checks, and handoff notes.

02 / Founding engineer trial

Work together before making a full-time or founder-level decision.

Four to six weeks

Best for: Early AI teams that need product-minded engineering across ambiguity, UX, implementation, and launch

Outcome: A concrete product milestone plus enough operating evidence for both sides to evaluate deeper fit.

03 / Developer-facing proof sprint

Turn an invisible technical capability into a public artifact buyers can understand.

One to two weeks

Best for: Launch docs, repo positioning, demos, diagrams, founder updates, technical onboarding, OSS packaging

Outcome: A founder-ready narrative layer: case study, diagrams, README structure, examples, and a stronger public technical surface.

A useful first letter answers four questions

  1. 01What workflow is currently too fragile, manual, or hard to explain?
  2. 02Who needs to trust or adopt it: developers, operators, customers, investors, or internal teams?
  3. 03What would count as a useful shipped artifact within two weeks?
  4. 04What existing code, docs, diagrams, prompts, or workflows should I inspect first?

Fit signals

  • You are building an AI-native product where workflow reliability matters more than a flashy demo.
  • You need someone who can cross product framing, implementation, validation, docs, and launch packaging.
  • Your team is early enough that one strong builder can still change the shape of the product surface.
  • You want to start with a scoped paid sprint before discussing employment or cofounder-level work.

Before writing, you can inspect the proof: The Lab · Case study · Standing thesis

Work with Brad | Correspondence Desk | Working Notes on Agent Systems