Product work behind the offer
I build my own tools, too
Find My Triggers
I designed and built this food and symptom diary as a SvelteKit progressive web app, including voice and text logging, reports, payments and privacy controls. It shows how I take a product from the problem through its interface and working application.
Read the product build story →
TraceWP
I built a WordPress plugin that exports site context for AI-assisted troubleshooting. It packages theme, plugin, server and page information into an export instead of making the owner collect each piece by hand.
Explore TraceWP on GitHub →
Illustrative examples, not client case studies
What a focused tool could do
Turn choices into an estimate
Enter quantities and select options; get a calculation based on your agreed pricing rules. The first version can stop at an estimate rather than becoming an invoicing or payment system.
Make an export readable
Upload a supported CSV; get a filtered summary and downloadable result. Agree the file format, calculations and storage needs before adding live account connections.
Produce a consistent document
Complete a form; generate a document from an agreed template. Keep approvals, signatures and other workflows separate unless they are part of the scope.
From example to working tool
A clear first version, not an endless build
We start with a representative input and the result you want. I check whether an existing product or a simple integration already does the job, then define the screens, rules and exceptions a custom version needs.
I build and test the agreed path, including invalid inputs and failure states. You receive the source code, deployment instructions and a practical handover. Hosting, third-party costs, data handling and any ongoing support are agreed before launch.
If the job is mainly moving information between existing tools, API and webhook automation may be the better fit. For the build-versus-buy decision, read When a Small Custom Tool Beats Another Subscription.