Why documentation matters
How Brex transformed their finance agents, and any great vibe coder successfully executes - it all comes down to documentation.
11/11/2025
Want the secret to great vibe coding? It’s the same as for any AI transformation.
Documentation.
This is how Brex built an entire suite of financial agents.
Take a 10 person engineering team (i.e. super small for enterprise). Add in Claude Code, Cursor, and really strong documentation.
For every feature, the team wrote a highly detailed file for Claude Code in natural language that explained the vision for the end result, how it fit into the broader product, and any other important context.
Claude Code can’t be in your meetings like a human. Without context, your vibe coding is really just that - vibes. And likely slop.
Taking the time to document extensively is what made this possible for Brex. AI only knows what you tell it.
This mirrors what I learned this week with my early experiments using Claude Code and Cursor.
✨ Create a plan
✨ Give context
✨ Outline a to-do list
The upfront work matters.
And if you’re thinking “that sounds like a massive job,” here’s the good news: AI can help with that too.
Use Granola or Whispr, transcribe your meetings, and have an LLM draft your documentation of the necessary context.
This process is key to any AI transformation work. AI is a really smart intern that knows nothing unless you teach it. You can’t assume it will go seek out more context if you don’t provide it up front.
But when you get the context right, magic can happen.
This post was originally published on LinkedIn
