What we set out to build
A way for a small business to answer its own repeated questions without hiring, and without a chatbot that invents answers.
What was built
- A retrieval pipeline over the client's own documents
- A pluggable model layer: local, hosted or mock, so it can run without any external service
- Full onboarding and landing flow, cloned from the studio's own design system
What it achieves
- Answers are grounded in retrieved passages with the source shown, and it declines rather than improvising when retrieval comes back empty
- The mock model path means the whole product is testable and demonstrable with no API key
The stack
Python, retrieval, ollama / hosted models.
Common questions
How was this built?
This was built through Colabs, our sister company. A founder brought the idea and the domain knowledge, Colabs brought the team, the founder funded the build with a monthly subscription, and they hold equity in the company that resulted. We label every case study, because a studio that publishes its prices and argues the other side of its own comparisons has to be equally precise about its own portfolio.
What state is it in?
Built. We state that plainly rather than describing everything as production: several things here are deliberately gated, and the reason is usually evidence rather than a missing feature.
Can you build something like this for us?
That is the point of publishing it. The same patterns are in the catalogue at published prices, and you can scope your own version on the plain-English page without contacting us first.
Where to next
If something here is close to what you need, the same patterns are in the catalogue at published prices, or you can describe your version in plain English and get it scoped and priced without talking to anyone.