Speech Journal
A Telegram bot that takes my voice messages and stores them in a database. Not a product — a personal tool. This very timeline is assembled from it.
September 2026. Three things in focus.
The site came out from behind its password on 10 September 2026. Next: Search Console, the sitemap, and an SEO clock that is now running.
Final stabilisation and a manual review of every screen before it goes into the practice.
Independent specialists in the US with a personal website. A direct conversation with everyone who stopped using it.
One idea — turning speech into a finished, useful result. From there it kept changing: shedding what it didn't need and getting sharper.
A Telegram bot that takes my voice messages and stores them in a database. Not a product — a personal tool. This very timeline is assembled from it.
Interactive wayfinding for a technology park on three touch screens: arena, security zone, campus. Delivered, paid, still running.
The first attempt to make a product out of the bot: a PWA, agents, vector search. I got through the selection and reached the final — fifth place, no prize. The lesson wasn't about code — it was about marketing and being able to explain which problem you solve.
A website for a fishing club. Under maintenance, a small recurring income every year.
Until then I had built products for myself — now the goal was different: take products all the way to a public launch and sales. The marketing course taught exactly that, and Call Copilot became its coursework project. The course ended in November; the project went public, and people have been paying for it since March 2026.
A clean-up of Referity: multi-user mode and images removed, speech recognition and dictation kept. The direct ancestor of Dictation, still alive as a bot.
Management for a physiotherapy practice: patient request → appointment time → confirmation → therapist's calendar → invoice. Since late July 2026 the end-to-end path runs at a working practice. There are three of us.
A browser extension: a live transcript of the call and a summary afterwards. Public since December 2025, paying users since March 2026 — found through Chrome Web Store search. My main pilot project: this is where I practise everything a product needs — ad campaigns, end-to-end analytics, payments through Stripe down to bank disputes, mailings, and a feedback loop with real users: requests, complaints, bugs.
The method changes faster than the products: a move to agent-driven development — and products start shipping in batches.
Starting dictation with one button on the phone. A quick experiment that made it clear a full app was needed.
A subtitle editor in the browser: transcription, timing, styling, export. The video never leaves your machine. The first test client made subtitles on their own.
Speak any language — get clean, formatted text, translated on the fly and shaped by your personal templates. Processed in the EU; sync is encrypted so that I can't read it myself.
A portfolio site with her work, a mobile version and a carousel — built for my wife. Not a client in the usual sense, but a separate, finished project.
One site under all the products: showcase, blog, changelog, one infrastructure and one payment. Every next product launches more easily than the previous one.
A ready website for a Ukrainian Verein: documents, announcements, admin panel, applications, email straight from the site. The same can now be built for any association — Barwa stays the live showcase.
A button in the corner of a site: the client clicks an element on the page and dictates what's wrong — and it becomes a developer task with full context attached. Already working inside Theomedis; will be free.
Cutting long videos and recorded calls into short clips. I built the MVP by hand for a real client — first to understand what's worth automating at all.
Two plans I haven't got to yet: an agent that collects invoices once a year and files them into the books, and a Telegram coach built on a scientific knowledge base.
Direct work with people is added — and the chronicle of notes becomes a blog.
624 notes already sorted into a database: projects, people, milestones, decisions. Posts come out of it — not "ten tips", but a chronicle with dates and no polish. Three languages.
The products are a consequence. I'm rebuilding the way I work itself to get to the main thing: products that find their people and get bought.
I have a full-time day job, a family, two children — and still many tasks running in parallel and carried through to a result. It isn't about the number of hours: alone and by hand, that much doesn't get done. Hence the bet on agents. I don't write code line by line — I draw up a plan of work, and AI agents carry it out; once, twelve such plans ran in parallel in a single night — thirty-six hours of autonomous agent work in total. Such sessions keep getting longer; that is where the whole industry is moving, and I use it to the full. An agent does the review too: it walks the finished screens in a browser and corrects what it finds, leaving me a short list for a final manual check. The machine does the work; the decisions — what gets done, how and why — stay with me.
My voice notes are turned into a knowledge base automatically: projects, people, decisions, milestones. This timeline is its direct product: I didn't recall the dates, I queried them.
The number of projects is not the goal. The goal is useful products people pay for: to find, among all of this, the ones that genuinely help people, find their audience and are worth the money. What is still missing is the last step — a steady source of traffic, so that the product gets found without me. That's what I'm learning now.
Where I'm heading is a one-man company: a living, profitable business with real customers, real revenue and unit economics that work, scaled by technology and AI agents. As soon as one of the products finds its audience and starts to grow, I'll scale that one — and if that takes people, I'll build a team around it.
Products I build and sell myself. Each one solves one specific task.
Notes on building, designing, and thinking about software.
Occasional updates on new projects, writing, and experiments. No spam, no tracking—just thoughtful notes when there's something worth sharing.
Unsubscribe anytime. Your email stays private.