Custom apps
I build applications around one company's process: the flow of enquiries, quotes and reports, a panel for the team's daily work, a link between systems, a chatbot that answers from your own materials. I start with a workshop where we agree what should change in how you work. The code and the data are yours from day one.
A tool built around your process
I start with a workshop: we write down how a customer enquiry turns into a quote today, how a report gets made, and where someone retypes data from one spreadsheet into another. The scope comes from that, and it contains only what your team will actually use.
Typical uses are an enquiry form that assembles a quote from your template, a monthly report pulled together from Google Search Console, analytics and your CRM, a ticket queue built from incoming email, and a chatbot that answers from your own documents.
The code and data stay with you
The application runs on your accounts, and you receive the code and documentation in your company's repository. I write readable code, so any developer you hire can get into the project without guessing how it works. I do not leave code that cannot be taken over.
What I have already built and how I work
I built two tools for myself that are public and need no sign-up: the AI visibility test, which runs 20 checks and gives a score out of 100, and the Webflow migration readiness audit, an interactive checklist.
I work with AI assistants when I build, but I decide the scope and the architecture, and I am responsible for the code I hand over.
After launch I stay on: Care and growth, including the Integrations package, which makes sure the connections between your systems do not quietly stop working.
