Things I built because I wanted them to exist
Client work pays the bills. These are the ones I own, and this page grows every time I ship another.

A bot answering an order question from a read replica of the shop's database.
Answers only from your content
Your help centre, your documents, your order data. It does not borrow answers from the internet.
Says when it does not know
A question your content does not cover gets an honest reply and a person, not a confident guess.

Knowledge sources: a website, documents and a database replica, re-checked every night.
Shows its source
Each answer carries the page or the record it came from, so anyone can check it.
Read only by design
Order lookups read a replica, limited to the tables and columns you allow. It can never change a record.

The console, where a team builds and tests its bots.
Sees what customers ask
Conversations grouped by topic, with the ones that still needed a person.
Many bots, one console
A bot per brand, product or site, each with its own knowledge, colours and logo.

The workspace: one note in focus, the rest out of the way.
Live Markdown
Renders as you type, with autosave and search.
Folders, files and notes
Use as much structure as you need. A note can stand alone or sit deep inside folders.

Goals, broken into phases and steps.
Goals
Link notes or whole folders to the objectives they serve, and watch the steps add up.
Stickers
A scratchpad for passing thoughts that clears itself after 24 hours.

Markdown that renders as you type.
Templates
Write a structure once and reuse it whenever.
Private vault
A locked place for the notes that are nobody else's business.
Your storage
Plain Markdown in your own Google Drive, or kept on your device.
Open to your tools
A developer API and an MCP endpoint, so an assistant can take the notes for you.
There is always a next one.
I usually have something half-built on the side. When it is ready to be used by someone other than me, it shows up on this page.
Ask me what I’m building