v37.io

AI Unit Economics Sprint

Improve AI gross margin without silently degrading product quality.

A bounded ten-working-day engagement for companies with production AI workloads. Measure total cost per successful business task, test practical alternatives at your quality threshold and leave with an implementation-ready plan.

Two founding engagements available for projects starting by September 30, 2026.

$12,500 plus applicable taxes, where required. Payable upfront.

Policy belongs above app code Specs first, code second Reproducible by construction Tests, not slides

Other ways to work together

Senior support beyond the Sprint when the work needs an ongoing strategic seat or a separately scoped implementation.

Fractional CTO

Technical leadership for teams moving beyond one-model prototypes. Architecture, model-routing policy, evals, hiring, due diligence, and the boring decisions that make AI systems operate.

  • Technical roadmap & architecture review
  • Model-routing and inference strategy
  • Evals, fallback, and observability design
  • Hiring & engineer vetting
  • Build-vs-buy decisions

AI engineering & advisory

Project-shaped AI infrastructure work — model routing, private endpoints, specialist models, evaluation harnesses, and reproducible delivery. The same approach I publish at v37.ai, applied to your stack.

  • OpenAI-compatible routing layers
  • Private and local-first inference setups
  • Specialist model and fine-tune integration
  • Evaluation harnesses & rubrics
  • Persistent agent memory architectures

How I work

Four opinions, in case they save us a discovery call.

Specs first, code second.

I write down what should happen and how I'll know it did. The spec is the contract — the implementation is the easy part once the spec is right. This is how the work survives me leaving the room.

Reproducible by construction.

Pinned versions, deterministic seeds, the artifact built twice with diffed outputs. If I can't produce the same thing twice in a row, the work isn't done. The recipes I publish at v37.ai are written to that bar.

Tests, not slides.

I ship code with the tests that prove it works, not a deck about it. If a stakeholder needs a deck, the tests are still the ground truth — the deck is a translation.

Bounded engagements.

I work on a small number of things at a time. That's how the work stays good. If I'm the right fit for what you need, I'll say so; if I'm not, I'll say that too and point you somewhere better.

About

I'm Daniele Salatti. I've spent fifteen years building data-intensive distributed systems — Amazon, Meta, The Trade Desk — and the AI infrastructure work that came out of that.

v37.io is the consulting face of the same engineer who publishes open recipes at v37.ai. When you hire v37, you get me — not an account manager, not a handoff to a junior. The same person who wrote the deterministic-stack reproducibility kit will sit in your CTO chair or write the AI infrastructure your product depends on.

That bounds what I take on. I work on a small number of engagements at a time, and the work has to be the kind I'd publish about — reproducible, opinionated, defensible. If that's what you need, the call is short.

Contact

Start with a short qualification call.

We will confirm whether the Sprint fits your workflows, available evidence, quality threshold and security constraints. If another engagement is a better shape, I will say so.