What I am building
Portfolio
Two products, both born from a problem I had myself, both still in active development. Below is what each one does, why it exists, and what I ran into building it.
SaaS product
Researched content with sources, not invented text
An AI content platform that researches first and writes second. A verification pass reads every claim back against its source, so no AI hallucination ends up in the text.
Internal product
What I went looking for did not exist, so I built it
A self-hosted support platform with an AI assistant that answers only from its own knowledge base, with citations. Accessible to customers only.
How they came about
I built Nolorem and the support platform on my own, the two of them inside six months, and both run in production with real users. That is not a boast in itself, but it does answer the question of what a one-person business can take on today. What needed a team and a year three years ago is now the work of one person, provided you know which parts to hand to AI and which parts to keep doing yourself.
What each system is
Nolorem
- What it is
- A content platform that researches a subject, writes a post about it, reads every claim back against its source, and schedules and publishes the result as a blog post and as social posts to a site you already have.
- Why it exists
- I needed content myself, and the available tools each solved one slice. A writing assistant has no idea what you published last month, a scheduler posts what you give it, a keyword tool hands you a spreadsheet. Stitching them together by hand turned out to be a part-time job.
- What is interesting about it
- The fact check. Getting a model to produce fluent text is trivial. Getting it to assert only what a cited source actually supports is not. Most of the build went there, and it is the one thing that makes the output publishable rather than merely plausible.
Support platform
- What it is
- A self-hosted knowledge base with ticketing and an AI assistant that answers only from its own documentation, pointing at the article the answer came from. Gated to customers.
- Why it exists
- Anyone paying for Nolorem deserves proper help when something breaks. A hosted helpdesk charges per agent per month and puts customer conversations on someone else's servers, which sits oddly with a platform that treats confidentiality as a starting point. A static documentation site cannot take a ticket.
- What is interesting about it
- That tickets feed back into the documentation. A ticket is not only work, it is also the signal that the knowledge base has a hole. Making that hole visible is what improves the system over time instead of merely enlarging it.