Foundry theme
Startups

AI for founders who do not code.

You do not need to understand transformers. You do need to spot the difference between a defensible AI product and a prompt in a trench coat — including when the person telling you is your own contractor.

THE FIVE THINGS THAT MATTER

1. The model is not the product. Everyone can call the same models. What makes a product defensible is everything around the call: your data, the workflow it sits in, the evaluation that keeps it good, and the accumulated handling of cases where it is wrong. If a pitch is entirely about which model is used, there is no moat being described.

2. "It works" is not a measurement. Ask how quality is measured. The right answer involves a set of test cases with known-correct answers and a score that gets tracked over time. "We tried it and it seemed good" means nobody will notice when it stops being good.

3. Inference costs money per use, forever. Unlike normal software, every interaction has a marginal cost. Ask what a single user interaction costs today and what it becomes at ten thousand users. If nobody has calculated it, that is the finding.

4. Hallucination is a property, not a bug to be fixed. Any vendor promising it has been eliminated is either misinformed or hoping you are. The real question is how the system makes wrongness visible — citations you can check, confidence thresholds, human review on the consequential paths.

5. Your data is the asset. Whatever proprietary data you have — support conversations, documents, transaction history — is the part competitors cannot copy. An AI strategy that does not use it is a strategy anyone could execute.

QUESTIONS TO ASK A VENDOR
01

How will we know if quality drops?

Good answer: an evaluation set and automated checks before each deploy. Concerning answer: "we monitor it closely" with no mechanism named.
02

What does one interaction cost?

Good answer: a specific figure with the assumptions behind it. Concerning answer: "it depends" without any subsequent number.
03

What happens when it is wrong?

Good answer: a described path — thresholds, human review, how the user sees uncertainty. Concerning answer: a claim that it will not be.
04

Who owns the code?

Good answer: you do, in your repositories, from the start. Concerning answer: a proprietary platform you would need to rebuild off later.
05

What are you not going to build?

Good answer: a clear scope with named exclusions. Concerning answer: enthusiastic agreement with everything you have said.
06

Could this be an existing product instead?

Good answer: an honest comparison, sometimes recommending one. Concerning answer: reflexive dismissal of every off-the-shelf option.
QUESTIONS
QUESTIONS — 4

Not to start, but you need someone technical whose judgement you trust and whose incentives are not tied to the size of the build — an advisor, a fractional CTO, or a vendor willing to talk you out of things. The risk without that is not being defrauded; it is being enthusiastically agreed with by people paid by the hour.

Frequently yes. If a no-code tool can test your hypothesis in a fortnight for a few hundred euros, do that before commissioning custom work. Custom development earns its cost when you hit the ceiling — usually your own data, real volume, or a workflow the tool cannot express.

Ask what they measured on their last project and what the number was. Strong AI engineers talk about evaluation, failure cases and cost almost immediately; weaker ones talk mostly about models and frameworks. Ask what they decided not to use AI for — anyone who has shipped has that story.

The thin wrapper window has largely closed, and that is a good thing — it never had a business underneath it. What has not closed is applying this to a specific domain you understand better than a generalist team ever will. Domain knowledge plus proprietary data is still where the durable products come from.

Keep reading
30-minute call · no deck

Bring us your
hard questions.

Including the ones you suspect are naive. Those are usually the good ones.

CASE STUDIES

Shipped work.
Go and check it.

The work we can name, with the live site, our scope and the boundary made explicit. Select a project to see the evidence; each is a full case study, not a logo or a claim.

sonora.com
The Sonora homepage on desktop: a full-bleed dune landscape behind the headline “Transform Your Life with Sound”, with App Store and Google Play download buttons.
sonora.com — homepage, 1440×900 sonora.com →
Live Consumer wellness · Mobile + web

Sonora

Cognitive AI Ltd · 2026

A free sound-wellness app, described by its publisher as AI sound therapy that reads a short vocal sample at the start of a session and generates a soundscape for that moment. We designed and built the website and its backend, produced assets for the iOS and Android apps, and supported the application prototype.

Read the case study →

See every published project →

WHO WE HAVE BUILT FOR

Twenty-one years of applications, platforms and campaigns for names you know.

See all of our work →