I build solutions to real business problems.

I came into technology through operations.
After more than 15 years working across administration, operations, marketing, events, hospitality and digital platforms, I learned to recognise where businesses lose time, information and opportunities.
The spreadsheet that has quietly become business-critical.
The process that requires the same information to be entered three times.
The software everyone works around rather than with.
The task someone repeats every week because nobody has questioned whether it can be automated.
The information that lives in WhatsApp, email, someone’s memory and three different systems.
Those are the problems that interest me.
Today, I combine that operational experience with product thinking, AI, automation and modern development tools to design and build the systems I once wished existed.
I don’t begin with technology.
I begin with the problem.
How I think
Before I build anything, I want to understand how the business actually works.
What are we trying to accomplish?
How is it being done today?
Where does the process break?
Who needs what information?
What happens when something changes?
What should be automated?
What should remain human-controlled?
What are we paying for simply because nobody has challenged whether we still need it?
And, ultimately:
Could we design something better around the way this business actually operates?
From there, I map the workflow, users, permissions, data, dependencies and exceptions before deciding what the solution should be.
Understand → Map → Design → Build → Test → Break → Improve → Deploy → Observe → Refine
For me, building the first working version is only part of the process.
I use what I build. I test real workflows. I look for edge cases. I watch how other people use it.
And then I change it.
From business problem to working product
I have designed and built applications, internal tools, operational systems, automations, websites and AI-powered workflows.
Each one started with a different problem.
Exploring what AI can actually do
I’m interested in practical AI rather than adding AI to products simply because it is fashionable.
I use projects to investigate where AI genuinely improves a workflow.
LocalLens AI
I explored AI-generated visual content for businesses across hospitality, beauty, real estate, events and ecommerce.
Beyond image generation, I investigated reliability, provider costs, failure handling, output consistency and whether the economics could support a viable product.
Nourish
A glucose-aware nutrition concept that pushed me to think about something different:
How should a product behave when its data is incomplete?
The experience incorporated device status, missing-reading indicators, source attribution, reconnection support and manual fallbacks rather than pretending the system always had perfect information.
BookWiser
An exploration of how appointment-based businesses could bring bookings, staff, customers, payments, reporting and operational workflows together rather than relying on disconnected systems.
These projects allow me to experiment, learn quickly and test ideas against realistic business scenarios.
Building AI workflows, not just prompts
My work with AI has also expanded into reusable skills and operational workflows.
I created products including the Revenue Follow-Up Operator and Event Marketing Campaign Builder.
My starting point is rarely:
What prompt should I write?
Instead, I ask:
What job needs to be completed?
A revenue follow-up system needs context, timing, outstanding opportunities, communication history and next actions.
An event-marketing system needs to understand the event, audience, venue, positioning, channels, timing and required assets.
I therefore think about AI skills as repeatable business processes, not isolated prompts.
Creative technology
I also use generative technology as a creative laboratory.
I’ve developed commercial AI products including Mythic Dragon Studios and a broader fantasy trading-card production system, exploring how complex creative processes can become repeatable systems other people can use.
I created Hearthlight, a fictional cinematic Christmas folk-pop project, to explore another intersection of technology and creativity.
That project has involved concept development, fictional artist creation, visual identity, music, album artwork, music-video planning, scene continuity, social content, distribution and artist positioning.
I learn new technologies by making things with them.
I build for real users
One advantage of building systems within businesses I actually operate is that I am close to the people using them.
I see what happens after deployment.
A user saying:
“This doesn’t make sense.”
is valuable information.
A field appearing at the wrong stage of a workflow isn’t merely a UI problem.
A button that technically works but nobody understands isn’t really working.
And a process that saves one person five minutes while creating ten minutes of work for someone else isn’t automation.
I build, observe and change.
How I use AI
AI has dramatically expanded what I can execute, but it isn’t a substitute for the thinking behind the work.
I use AI as a development partner, research tool, analyst, creative collaborator and accelerator.
I define the business problem.
I map the requirements.
I challenge assumptions.
I make product decisions.
I evaluate the output.
I test the functionality.
I identify failures.
I iterate.
And I deploy.
Through building real products, I’ve developed practical experience with modern technologies including React, Next.js, TypeScript, Supabase, PostgreSQL, Prisma, APIs, authentication, row-level security, role-based access, GitHub, Cloudflare and transactional email infrastructure.
I’m not trying to position myself as a traditional software engineer.
My value is different.
I sit between the business and the technology.
I can understand both conversations.
What I bring
Product thinking
Turning ambiguous business problems into clear requirements, workflows and products.
Business systems design
Understanding how people, processes, information and technology need to work together.
AI-assisted product development
Using modern AI tools to move rapidly from concept to working software.
Automation
Identifying repetitive processes and determining where automation creates genuine value.
User journey & workflow design
Designing around what people actually need to accomplish rather than what a system happens to support.
Application development
Building internal tools, portals, dashboards, SaaS products and operational applications.
Testing & iteration
Testing real workflows, finding edge cases and improving products based on actual use.
Marketing & digital strategy
Connecting technology with positioning, customer journeys, websites, campaigns and commercial outcomes.
Operations
Understanding what happens after the presentation, campaign or product launch — when people actually have to deliver the work.
Sometimes the best solution isn’t more technology.
I have also learned when not to automate.
Sometimes an API isn’t reliable enough.
Sometimes automation creates more complexity than it removes.
Sometimes sensitive decisions need human approval.
Sometimes a manual fallback is essential.
Sometimes buying an existing product makes more sense than building one.
And sometimes the software available on the market is forcing a business into an inefficient process simply because:
“That’s how the system works.”
My objective isn’t to maximise technology.
It’s to improve the operation.
The thread connecting everything I’ve done
My career makes much more sense to me now than it once did.
Administration taught me structure and attention to detail.
Operations taught me how businesses actually work.
Events taught me how to manage people, deadlines, moving parts and unexpected problems.
Marketing taught me how customers think and how businesses communicate value.
Websites and digital marketing taught me customer journeys and digital experiences.
Building products taught me systems thinking.
AI gave me the ability to execute ideas at a speed and breadth that previously would have required a much larger technical team.
Today, those disciplines come together in the work I enjoy most:
Understanding a business, finding what could work better, and building the solution.
I am particularly interested in the space between a business saying:
“This is how we’ve always done it.”
and someone asking:
“But is this still the best way?”
That is usually where I do my best work.