"If you have Claude, you can really automate a lot of work, and that's kind of what we see over and over,"
"There's this interesting thing when you underfund everything a little bit, because then people are kind of forced to Claude-ify,"
"Let's say they build something awesome, and then it takes a huge amount of tokens, and then the cost becomes pretty big,"
"That's the point at which you want to optimize it, but don't do that too early."
Boris Cherny outlines three guiding principles for teams at Anthropic. Claude functions as the central automation engine, enabling teams to offload repetitive work and increase productivity. Teams are intentionally kept small and a bit underfunded to force creative reliance on Claude and rapid automation. Early-stage cost optimization is discouraged; engineers should receive ample tokens to experiment and iterate. If a successful prototype proves token-intensive, optimization and cost controls can follow later. Rising token costs are a growing concern for companies, making thoughtful timing of optimization important. A final principle emphasizes speed and fast iteration.
Read at Business Insider
Unable to calculate read time
Collection
[
|
...
]