AI strategy · Fractional leadership · Speaking
We use every frontier model as it ships, build production software with it, and publish what the work actually costs. The advice arrives with its arithmetic attached.
What it is built on
Eleven ordinary tasks, priced across every frontier-class model that can genuinely do them — the bill for one finished piece of work, not a token price.
For leadership teams and investors deciding what to build, what to buy, and what a generative feature will actually cost in production. Short engagements that end in a decision along with a roadmap.
Senior technical judgment for companies that need it without a full-time hire — architecture and build-vs-buy calls, diligence support, and a technical read on the AI claims in a deck.
For audiences who would rather hear from someone still doing the work. Talks come from current practice — what shipped, what it cost, and what turned out not to work.
The question is rarely which model is best. It is which one is good enough for the job in front of you, and that answer decides where the work can run: on-device, in your own tenancy, or on someone else's API. What a finished job costs, what the model is ever allowed to see, and whether the design survives a compliance review all follow from it. Architectures where sensitive data never reaches a third-party model get designed in, not bolted on afterwards.
And the bar keeps getting cheaper to clear. Work that needed a frontier API last year clears it on open weights today. The design worth having is the one that lets you swap the model underneath without rebuilding around it.
None of that is a forecast. The Frontier Rate Card prices what a finished job actually costs, across every model that can genuinely do it — published, current, and there to be checked rather than taken on faith.
SELC builds and ships its own software. Designed and built with AI tooling throughout. Biblicast turns a Bible verse into a short, produced podcast episode — on the App Store for iPhone.
About SELC →Left Holding: A Field Guide to Private Equity-Owned Software — the difference between the expand path and the extract path, and what happens to a product organization once the deal has closed.
Left Holding →