SaaS product company
Conversational Product Assistant
Built the company's product site and embedded an AI assistant into the core product, so users get answers in context without leaving the interface.
Getting AI to answer from your own documents — accurately, with sources — instead of from memory.
Most of the AI systems I build start with documents: medical records, claims, internal manuals. The hard part is rarely the model. It's parsing messy files, splitting them sensibly, finding the right passages, and making sure every answer can point back to where it came from.
SaaS product company
Built the company's product site and embedded an AI assistant into the core product, so users get answers in context without leaving the interface.
Independent clients
Ongoing freelance work: retrieval systems, domain chatbots and end-to-end AI implementations, scoped and delivered directly with each client.
How you cut documents into pieces decides what your AI can find. Seven ways to do it, what each costs, and the order I try them in.
Ordinary RAG answers 'find me the paragraph' well and 'what does this 400-page file say overall' badly. Keeping the document's structure, with summaries at each level, lets one system answer both.
Open OCR models now rival paid APIs, but the best one for a scanned form is wasted on a clean PDF. This pipeline sends each page to the cheapest tool that reads it well and escalates only when it can't.
There are dozens of named RAG techniques and most teams need four or five. What each pattern does, what the evidence says, and the order I'd reach for them.
Contact
I'm open to AI engineering, architecture and training work. Tell me what you're building and what the constraints are — that's usually enough to start.