Work ↗About ↗Contact ↗
Custom Software

Software Built Around Your Business

Management systems, internal tools and platforms built for how your organisation actually works — instead of changing how you work to fit someone else's product.

ROLE-BASED SYSTEMAdminStaffManagerACLOne systemOne source of truthPDFXLSCSVReports
Overview

When off-the-shelf stops fitting

Most organisations outgrow their tools the same way: a spreadsheet becomes three spreadsheets, then a shared drive, then a subscription that does 60% of the job while someone re-keys the rest by hand. Custom software is worth building at the point where that manual work costs more than the build.

I've shipped this kind of system before — a college management platform covering admissions, fees, timetables and records for five different user roles, now running in production at a government college with real staff and real student data.

You can see how that one was built in the College Management System case study, including the role model and the reporting side.

What I Offer

Custom Software Development services

Management Systems

Platforms covering a full operational workflow — records, scheduling, billing and reporting in one place instead of five.

Internal Tools & Dashboards

The admin interfaces your team lives in: searchable data, bulk actions, and views built for the people who use them daily.

Role-Based Platforms

Different users, different permissions, different dashboards — with access control enforced on the server, not just hidden in the UI.

Workflow Automation

Replacing the manual steps between systems: approvals, notifications, scheduled jobs and data moving where it should.

Reporting & Exports

Reports your team can actually use — PDF, Word, Excel and CSV exports generated from live data rather than assembled by hand.

Desktop Applications

Windows and macOS software with Electron or Tauri, for tools that need to run locally or access the machine directly.

Process

How the work gets done

Six stages, each with something you can see and sign off.

Get a free quote
  1. 01

    Discovery

    I sit with how the work is done today — the spreadsheets, the workarounds, the steps nobody has written down — before proposing anything.

  2. 02

    Planning

    The domain gets modelled properly: entities, roles, permissions and reports, agreed with you before a line of code is written.

  3. 03

    Design

    Interfaces designed around the people who'll use them every day, prioritising speed of data entry over decoration.

  4. 04

    Development

    Built in milestones by module, so you can start using the first part while the next is still being developed.

  5. 05

    Testing

    Tested against real scenarios and real data volumes, including the permission edge cases that matter most in multi-role systems.

  6. 06

    Launch

    Deployed, data migrated from your existing spreadsheets or systems, and your team trained on it before it goes live.

Why Work With Me

What you actually get

One software engineer, not an agency layer. Direct communication, one person accountable, no budget spent on account managers.

Shipped in production

My college management system runs daily at a government college with five user roles — not a portfolio demo.

Your process, not a template

The software is built around how your organisation works. No forcing your workflow through someone else's assumptions.

Scalable architecture

Proper data modelling, migrations and separation of concerns, so adding a module in year two doesn't mean starting again.

Access control done properly

Permissions enforced server-side and tested per role. Hiding a button is not security, and I don't treat it as such.

Migration included

Getting your existing data out of spreadsheets and into the system is part of the project, not a problem left for you.

Documentation and handover

You get documented code and a trained team, so the system isn't dependent on one person remaining available.

Selected Projects

Related work

Real projects where custom software development was part of the build. Each one has a full case study.

View all work
FAQ

Common questions.

The things clients ask most before starting a custom software development project. Anything not covered here, just ask.

Not always, and I'll say so. If an existing product covers your process, buying it is cheaper. Custom makes sense when the gaps cost real hours every week, when your process is genuinely unusual, or when per-seat licensing has grown past what a build would cost.

Larger than a website — usually a few months for a full multi-role platform. I build module by module so you get working software early rather than waiting for everything at once.

Yes. Importing from spreadsheets, CSVs or an existing database is part of the work, including cleaning up the inconsistencies that always turn up in real data.

Systems change as businesses do. I offer ongoing development and support, and the code is documented so another developer could take over if you'd rather bring it in-house.

You do — code, data and infrastructure. I build on standard open technologies so you're not tied to me or to a proprietary platform.

Yes, and it's usually a core requirement. I build role-based access with permissions enforced on the server, so what each role can see and do is properly controlled.

Outgrown your spreadsheets?

Tell me how the work gets done today and where it breaks down. I'll map out what a system would need to cover, and what it would take to build.