Distill: experiments in using fewer AI tokens
An experiment showing why token savings need to be assessed alongside the quality of the resulting work. It does not yet demonstrate financial savings.
All the ways to work together · Versione italiana
From bill to decision
Reconstruct where AI spend goes, what useful work it produces, and what is worth testing to reduce it without hurting service quality.
€10,000 excl. VAT · 2 weeks
Finance, product or engineering teams with one or two live AI applications, significant or unusual spend, and an economic decision to make.
Bills are rising, but it is hard to see which applications, models and repeated attempts generate the spend, or what it costs to produce a usable result.
A picture of spend checked against bills and usage data. Where the data allows, we also calculate cost per accepted result: work that meets the agreed quality criteria. You receive recommendations on what to test, what to leave alone and which data is missing.
Fifteen years building software people rely on.
These results describe my experience. For your project, we define goals and measures around your company’s process.
Portfolio and roles · All services compared, with prices and next step
Fixed price · Remote · up to 2 providers and 2 AI applications or processes
50% at start · 50% at delivery · proposal valid for 14 days
Cloud, tools, travel and data remediation excluded
One clarification call within 14 days of delivery
Fit assessment within 2 business days
An experiment showing why token savings need to be assessed alongside the quality of the resulting work. It does not yet demonstrate financial savings.
Where to start cutting AI costs: unnecessary calls, model choice, caching and context, with worked examples and a 14-day comparison.
B2B service. A request creates no commitment: price and scope become binding only in an accepted written proposal.