Internal tools
Purpose-built operational software for managing workflows, records, approvals and repeated tasks without spreadsheet sprawl.
Software Development
Software builtaround the work.
I build focused software for real workflows — from internal tools and client portals to custom web applications that need more than an off-the-shelf platform can provide.
- Approach
- Problem-led
- Architecture
- Small + explicit
- Delivery
- Tested + maintainable
Engineering principle
Model the real workflow.
01
Workflow
Understand the decisions, data and hand-offs.
02
System
Turn the workflow into clear application boundaries.
03
Delivery
Ship, observe and improve the product over time.
01 / Software
Build around the process, not the platform.
Custom software makes sense when the workflow matters enough that forcing it through generic tools creates more friction than it removes.
Client portals
Secure workspaces that give clients access to the information, files, projects or actions relevant to them.
Workflow applications
Applications built around a specific sequence of decisions, data and hand-offs where generic software becomes cumbersome.
Existing systems
Improving or replacing brittle processes when an existing application has become difficult to understand, maintain or extend.
02 / Architecture
Complex enough to solve it. No more.
I prefer explicit data models, small application layers and interfaces that expose the workflow clearly instead of hiding it behind unnecessary abstractions.
Clarity
Make responsibilities obvious.
Separate concerns so future changes have a predictable place to live and are easier to reason about.
Reliability
Treat failure as a state.
Validation, errors, persistence and recovery should be deliberate parts of the product rather than surprises.
Maintainability
Optimise for tomorrow.
Readable code and straightforward architecture make the next feature less expensive than cleverness does.
03 / Capabilities
From interface to persistence.
I work across the product rather than treating the frontend and backend as unrelated pieces.
Application logic
Go services
Business rules, HTTP handlers and application boundaries kept explicit.
Data
Relational persistence
SQL, migrations and data models designed around the actual workflow.
Interface
Server-rendered UI
Semantic HTML and focused interactions that keep browser complexity under control.
Delivery
Testing + deployment
Automated checks, container builds and production deployment considered part of the system.
04 / Selected work
A working system, not a mock-up.
The portfolio itself includes a private operational workspace for clients, projects, contracts, publishing and administrative workflows.
Portfolio & Client Workspace
A real application combining public content with authenticated operations, persistence, publishing and deployment.
Read the case study
Operational workspace
Real workflows. Real state.
Clients, projects, contracts and publishing are handled inside the same application.
Clients
Records
Projects
Workflow
Contracts
State
Journal
Publishing
05 / Process
Understand the work before writing the software.
The best implementation starts with a clear model of the workflow, users and constraints — not a premature list of technologies.
Discover
Understand the process, data, pain points and desired outcome.
Model
Turn the workflow into clear states, entities and application boundaries.
Build
Implement incrementally with testing, security and maintainability built in.
Improve
Observe real use and evolve the software where it creates measurable value.
06 / Start a project
Have a workflow that deserves better software?
If your team is fighting spreadsheets, disconnected tools or a system that no longer fits the work, tell me what the process actually needs to do.