A research workspace and assistant, built for a health founder and the community he writes for.

The founder had years of health research and a growing audience, but no focused place to actually use any of it. Questions came in faster than he could answer; his own material lived across scattered posts and notes. He didn't want a generic chatbot bolted on. He wanted a calm research surface, grounded in his own work, that he and his community could rely on.
Discovery. Mapped how the founder researches and what his community repeatedly asks, then scoped the smallest product that would feel indispensable.
Design. A chat-first, editorial interface, calm by default, that gets out of the way. The screen invites a question and nothing else.
Build. A full-stack app with streaming responses, designed for fast iteration and privacy.
AI layer. A retrieval pipeline over the founder's corpus so answers cite their sources, with evaluation to keep answer quality honest.
A single research prompt answers from the founder's own material and links what it used, so the reader can trust and follow up.
More than a chat box: a focused home for research, built to grow into collections, exploration, and reporting.
Deployed at folio.science, in the founder's hands and improving against how he actually uses it.
Folio replaced a scattered research habit with one place the founder uses directly. It went from idea to a deployed product in his hands quickly, and it keeps earning use rather than sitting in a demo folder.
"I don't know what you did in the last 48 hours, but it's actually incredible. I'm going to be using it more and more."Jack S. · on Folio
Sole builder: product, design, full-stack engineering, and the AI layer, end to end. Built with Next.js and Supabase, streaming responses, and a custom retrieval pipeline.