Stories from people dealing with AI Pricing and Access — what changed, who decided it, and what the ordinary days look like now.
15 stories
AI Industry & Models
A router can send routine support work to a cheaper model. The savings disappear when a short refund request hides a policy exception, so routing and model quality need separate tests.
Tobias Lund · October 1, 2026 · 7 min
AI Industry & Models
Automatic routing makes cheaper models practical for routine work. The hard part is detecting when the router, rather than the selected model, caused the failure.
Tobias Lund · 8 min read
AI Industry & Models
OpenAI, Anthropic and Google accept PDFs, but their ingestion paths preserve different evidence. A four-page test shows when direct upload works and when preprocessing is the safer choice.
Tobias Lund · 7 min read
AI Industry & Models
A cheaper model can handle routine requests, but one bad routing decision may create retries and manual review. Logging the decision makes the real savings measurable.
Tobias Lund · 7 min read
AI Industry & Models
Routers can send routine prompts to cheaper models and reserve stronger models for difficult cases. The savings disappear if quality misses and second calls stay outside the ledger.
Tobias Lund · 7 min read
AI Industry & Models
Sending routine requests to cheaper models can lower inference costs. The savings survive only when the router detects mixed, unfamiliar, or high-risk requests before a bad answer triggers another call.
Tobias Lund · 8 min read
AI Industry & Models
Moving model names remove upgrade work, but they also weaken regression evidence and incident replay. Here is when to pin a snapshot and how to stage the next one.
Tobias Lund · 8 min read
AI Industry & Models
A two-tier model pipeline can lower inference spend, but only when escalation works before the cheap model produces a plausible mistake. The real comparison is total cost per accepted answer.
Tobias Lund · 8 min read
AI Industry & Models
Routing routine requests to a cheaper model can lower inference costs. The test is whether the router catches difficult cases without hiding errors or adding intolerable delay.
Tobias Lund · 8 min read
AI Industry & Models
A replacement model can change tool calls, refusals, latency, and tone. Test it against customer-visible outcomes before a provider’s deprecation deadline forces the switch.
Tobias Lund · 7 min read
Consumer AI Hardware
Microphone counts matter less than searchable audio, correctable transcripts and files you can keep. Test the exit path before paying for another AI subscription.
Devin Oyelaran · 7 min read
AI Industry & Models
Smaller models can classify, extract and route routine work with less delay and expense. The useful boundary appears only when each task is tested separately.
Tobias Lund · 7 min read
AI Industry & Models
A shared request format gets code talking to a second model. A 60-case replay test shows whether instructions, JSON, tools, refusals, and retries still behave.
Tobias Lund · 8 min read
AI Industry & Models
A support assistant can reuse the computation behind a static policy manual instead of processing it from scratch. The savings depend on keeping that manual at the start of every request, unchanged.
Tobias Lund · 7 min read
AI Industry & Models
Sending every file can turn one coding task into millions of repeated input tokens. Prefix caching helps, but a code map and selective loading usually cut cost, delay, and distraction further.
Tobias Lund · 8 min read
Other impacts
One story a day
One real story about AI each morning — no hype, no alarm, just company for the road.