Mobile apps, web applications, AI-connected tools and business websites. I work out what needs to happen, then take it from an idea to something people can use.
Products of my own and websites for clients. Different problems, different technology, the same way of working.
It started as a throwaway “I should build an app for that.” Now it’s a live iPhone app that turns short-game practice into a scored challenge, solo or head-to-head.
What it shows: An idea taken from a spreadsheet on a phone to a live iPhone app on the App Store: researched, designed, coded and released.
A live ChatGPT app for understanding your running. Connect Garmin for new runs, import Strava history, then ask about pace, effort and progress.
What it shows: Trusted data and real tools put in front of a model ChatGPT users already have, instead of building another chat window.
An internal business application for finding prospects, reviewing website findings, preparing outreach and keeping track of follow-ups. AI drafts; a person decides what gets sent.
What it shows: Software shaped around a real workflow rather than a generic CRM, with AI only where it helps and a person approving every send.
A complete business website for a Gold Coast bookkeeper, from service content and responsive design to Sanity CMS, search foundations, a paid-search landing page and measured enquiries.
What it shows: A website treated as part of how a business wins work, with content, search, paid acquisition and measurement all built to work together.
Most of what I build lands somewhere in these three. Plenty of it overlaps, because real problems don’t sort themselves into categories.
A customer-facing mobile app, a business tool replacing spreadsheets, or an application that connects the systems you already use. I turn the idea or awkward process into software people can actually use.
Mobile applications · web applications · internal tools · integrations
Seen inPAR-18 →Thommo Prospecting →
Give AI useful access to your business information, add tools to an AI platform, or automate the repetitive parts of a workflow while keeping people in charge of decisions. The job starts with working out where AI will actually help.
Connected data · AI-platform apps · MCP integrations · agent workflows
A clear, fast business website that is easy to maintain. Useful service content, a search-friendly structure and straightforward enquiry journeys, with a CMS and measurement where they make sense.
Business websites · UX/UI · content management · SEO and AEO · enquiries
Tell me what you’re trying to do, what happens today and where it gets awkward. We can work out what makes sense to build.
It might be an application, an integration, AI, a website or something simpler. You don’t need a technical brief to get in touch.
daniel@thommo.aiThere's an assumption that an AI-powered workflow needs AI running inside it every time.
I'm not sure that's true.
AI might help understand the problem, design the workflow, write the code and build the system.
Then, if the answer should always be the same, let normal software do the work.
Sometimes AI should build the automation, not be the automation.
There's a common approach to business software:
Buy the CRM.
Configure the CRM.
Change the process to fit the CRM.
Train everyone to use the CRM.
Then spend the next five years complaining about the CRM.
We're getting much closer to a world where smaller businesses can start with the opposite question:
How should our workflow actually work?
Then build around that.
Every Aussie knows a Thommo. And if you didn’t, you do now.
I’m Daniel. But Thommo is what everyone knows me by.
I’ve spent most of my career around technology: software platforms, solution design, and working out how systems fit together. What’s changed is how much of the build I can now take on myself, from the first question to the working thing.
