Client
Client platform
Case study
The product was designed around a simple requirement: users should be able to ask useful questions while operators can see why the system succeeds, where it fails, and what needs attention.
Client
Client platform
Role
AI product architecture and full-stack development
Year
2026
Summary
Built a document-grounded AI chat experience with cited answers, guided retrieval, and an administrative view of conversations, errors, feedback, and usage.
The chatbot needed to answer questions from an approved collection of documents rather than rely on general model knowledge. Users needed clear responses, and the team operating the system needed evidence about what happened after launch.
I helped build the product around both of those audiences.
A chatbot can produce fluent text even when it retrieved the wrong passage or lacked the information required to answer. That makes the retrieval layer, citation behavior, and refusal path part of the user experience.
The system was designed to search a curated corpus, assemble relevant context, and keep the final answer connected to the material that supported it. When the available documents could not justify an answer, the workflow needed to preserve that uncertainty.
The product combined a guided chat surface with operational instrumentation:
This made it possible to improve the system through observed behavior instead of judging it from a handful of demonstration prompts.
AI applications create new operational questions. Which questions recur? Where does retrieval miss? Are users giving negative feedback because the source is absent, outdated, or difficult to locate? Did a failure come from the model, an upstream service, or the application?
The administrative experience made those questions visible. It turned the chatbot from a standalone interface into a product the team could monitor and improve.
This project demonstrates my approach to retrieval products: constrain the knowledge boundary, make evidence visible, instrument the complete workflow, and give operators a practical way to learn from real use.
Related writing
Retrieval is not plumbing in an AI product. It directly shapes whether the answer feels relevant, grounded, current, and useful.
AI features improve when teams treat context assembly as product and systems design work instead of assuming the model can infer its way past noisy, stale, or incomplete inputs.
AI product quality depends on the full interface around the model: inputs, controls, evidence, state, review paths, and recovery behavior.
Relevant services
Applied AI that improves delivery, diagnostics, reporting, and internal tooling without turning the stack into a science experiment.
Custom app builds and integration work for teams that need systems to talk cleanly across HubSpot, internal tooling, and the rest of the stack.