Economics and Routing
Description
Section titled “Description”Fully agentic software development only scales if model spend, provider concentration risk, and throughput are treated as first-class design concerns. Cost control is not separate from workflow design because execution routing affects which work is feasible, how often feedback can run, and how dependent the organization becomes on a single vendor.
Price Factors
Section titled “Price Factors”The cost of an agentic system is shaped by more than token price.
- Model invocation price and context-window cost.
- Tool execution cost, especially for cloud environments and long-running agents.
- Human review cost for low-confidence or high-risk work.
- Rework cost when low-quality routing creates avoidable failures.
- Switching cost when the workflow assumes a single provider or API shape.
Local Models As a Hedge
Section titled “Local Models As a Hedge”Local LLMs matter even when they are not the best model for every task. They reduce dependency on external pricing decisions, help limit exposure to provider-side supply shocks, and provide a fallback path for internal or sensitive work.
The practical pattern is usually hybrid. Use local models for drafting, triage, summarization, and low-risk transformations, then reserve expensive frontier models for ambiguous design work, difficult debugging, or critical review stages.
Smart Routing
Section titled “Smart Routing”Routing decisions should combine task complexity, confidence, latency, and policy. That makes Smart Routing a core operating mechanism rather than a minor optimization.
Useful routing signals include:
- Complexity classification from Ticket Enrichment.
- Runtime feedback from prior similar tasks.
- Domain sensitivity, including code ownership and compliance boundaries.
- Budget envelopes for a team, repo, or workflow stage.
- Human preference for when escalation to stronger models is allowed.
Multimodal Intake and Planning
Section titled “Multimodal Intake and Planning”Economics is also affected by how information enters the system. A short voice memo or annotated screenshot during planning can be cheaper and clearer than forcing a human to translate everything into perfect text up front. Agents can convert those inputs into structured issues, plans, or review requests while preserving the original source artifact for later audit.
Related Concepts
Section titled “Related Concepts”- Software Development - Parent concept for the full workflow.
- Smart Routing - Existing optimization page for model selection.
- Execution and Feedback - Routing affects where execution happens and how feedback is gathered.
- Collaborative Development Structure - Planning rituals create the metadata routing needs.