Skip to content

Custom web application development

When off-the-shelf software almost fits, people end up working around it. I build web applications around your actual process, so the software does the work instead of adding to it.

Start a project

What’s included

  • Client and member portals
  • Booking, ordering and request systems
  • SaaS products and first versions of new products
  • Integrations with the tools you already use
  • Accounts, roles and permissions
  • Testing, deployment and documentation

A good fit if

  • Your process doesn’t fit existing software
  • You have a product idea and want it built properly
  • Customers or members need to log in and get things done

How I approach it

I start by finding the one thing your users most need to do, then build the smallest version that does it well: accounts, that core journey and an admin panel to run it. You see a mockup before I build and working software at every check-in. Once real people are using it, their feedback decides what comes next.

Web applications, Business systems 2026

Civic engagement platform

A product experiment I built end to end: one platform that gives each organization a public website and a private dashboard for working with the community it serves. It was designed around local public officials and is shown here with demo data.

Read the Civic engagement platform case study
The platform’s demo site on desktop and mobile. The desktop shows the Commitments page, with five commitments summarised by status. The phone shows the form residents use to report a local issue.
The problem
Local officials mostly talk to residents through social media. Plans get buried in the feed, questions scatter across comments and messages, and there’s no simple way to show what has actually been done. The data involved is sensitive too, so the platform had to protect residents by design, not by policy alone.
What I built
One platform that serves many organizations from a single codebase. Each gets a public site for its plans, projects, commitments, events and volunteers, and a private dashboard for its team. The privacy rules are part of how the data is stored, not just a policy page.
Outcome
Built and running end to end with demo data: public sites, the team dashboard and the privacy safeguards. It started as a product experiment and isn’t offered to clients. Its foundations (logins and roles, dashboards, inboxes, themes and custom domains) are ready to reuse in client portals and business systems.

Questions about web applications

What is an MVP, and why start with one?

An MVP (minimum viable product) is the smallest version of your app that’s useful on day one: user accounts, the one thing your users most need to do, and an admin panel to run it. Launching that first lets real users show you what to build next, instead of guessing up front.

Can you connect to the software we already use?

Often, yes. If your current tools have an API or a data export, I can work with them instead of replacing them. I check this early, during discovery.

Will we own the website or software?

Yes. Once the final payment is made, the site or app and its code are yours. Your domain, hosting and paid services are set up in your name from the start, so you’re never locked in. Third-party themes and plugins stay under their own licences.

Tell me what you’re working on

You don’t need a full brief. Send a few lines about what you want to build or fix, and I’ll reply with clear next steps, usually within a few working days.