#strategy
Every post tagged "strategy".
7 posts · showing 1–7
-
What I'd Tell a Team Starting Their First Agent Project
Seven things, none of them about model capability, and most of them cost a quarter before they're visible. The first one eliminates more candidate projects than anything else — and should be applied at the idea stage.
-
Who Owns the Agent? The Team Structure Question
Prompts need domain expertise; tools need engineering; evals are specification. That split doesn't match team boundaries, which is why agent ownership goes ambiguous — and ambiguous ownership shows up as quality nobody watches.
-
Pricing an Agent Product When Your Costs Are Variable
One customer can cost a hundred times another on the same plan, and they're often the ones getting the most value. Five pricing models, their failure modes, and the trap where every quality improvement cuts your margin.
-
Where Agents Don't Belong (Yet)
Six task shapes where the agent architecture is the wrong fit regardless of model quality — each with a tell you can check in an afternoon, before committing a quarter to it.
-
The Demo-to-Production Gap Is an Evaluation Gap
Demos answer "can it?" Deployments ask "how often, across everything real users send, when the tools misbehave?" Five variants of your demo scenario will tell you more than the demo did.
-
The Skill Agents Erode Fastest: Reading Unfamiliar Code
Delegating code traversal is pure gain. Delegating comprehension means not having the model — and review quality is bounded by the model you don't have.
-
Agent Adoption Stalls at Trust, Not Capability
An agent whose errors cluster somewhere describable beats a more accurate one whose errors are scattered. Ask your users when they double-check its work — the answer is your real roadmap.