Software Development
Custom software, built by the person you actually talk to
Most businesses don't need software for its own sake. They need the three days a week their team loses to a spreadsheet back. I build the systems that take that work off people's plates, and I'm the one writing the code, not a team you never meet.
Off-the-shelf software is usually much cheaper, and when it fits, you should use it and I'll always tell you that before I quote you. Custom software earns its place when your process is genuinely unique to your business. When the tool you'd have to buy would need bending so far out of shape that you'd end up with a spreadsheet bolted to the side of it anyway.
When that's the case, what you get from me is a system designed around how your business actually runs. I've spent over a decade doing this across healthcare, fintech, logistics, and consumer, on systems handling millions of payments a year and on internal tools used by five to ten people. The care is the same either way.
The part that matters more than the build is what happens afterwards. Software that nobody owns rots away. Every business I've built for, I still work with today, because the person who wrote the code is still the person who picks up the phone when something needs to change.
Custom business systems
The system your business runs on, built around your process rather than a template. Portals, dashboards, job management, scheduling, reporting; whatever the shape of the work actually is. Usually this replaces a pile of spreadsheets and a lot of copying between them.
Internal tools & automation
The unglamorous software that saves the most money. Tools that take the repetitive, manual, error-prone work your team does by hand and make it happen automatically, so people spend their day on the parts that need a human.
Integrations & APIs
Connecting the systems you already pay for so they stop being islands. CRMs, accounting, ERPs, fulfilment, third-party APIs. Most businesses have the data they need already; it's just sitting in four places that don't talk to each other.
Legacy modernisation
Old software that still works but is holding you back: desktop-only, unsupported, or built by someone who left years ago. Sometimes that's a careful migration, sometimes it's an honest rebuild. I'll tell you which one you're actually looking at.
SaaS & product builds
If the software is the product, it needs to hold up under real customers from day one. Multi-tenancy, billing, permissions, and the boring reliability work that decides whether people trust you enough to keep paying.
Taking over existing code
Projects that stalled, or that a previous developer walked away from. I'll read what's there, tell you honestly whether it's worth continuing or starting again, and pick it up from wherever you are. You don't need to start from scratch to work with me.
Scope
I sit down with you and work out where the time and money actually goes, before anything gets built. You get a straight answer on what it'll cost, how long it'll take, and where the risks are, while you can still walk away.
Build in phases
Work ships in phases with milestones agreed upfront, so you're getting value partway through instead of staring at a black box for six months hoping it lands. Protal worked exactly this way, and the team were saving hours before the project finished.
Stay on
Once it's live, I don't hand you a login and vanish. Changes, fixes, and the next thing you think of six months later; I'm still the person who knows why the code is the way it is.
Cartwright Hands were running an entire lettings operation by hand: landlords, tenancies, compliance certificates, and document signing, all manual and all costing them time every single day. No product on the market did what they needed. Protal now runs the whole lifecycle in one place.
Read the Protal case study →How do I know whether I need custom software or something off the shelf?+
Ask what you'd have to change about how you work to make the off-the-shelf option fit. If the answer is 'not much', buy it, and I'll say so. Custom starts making sense when the workarounds become the job; when your team is exporting to a spreadsheet to do the bit the software can't, or when three tools each hold a third of the picture. I'd rather tell you to spend £50 a month on something existing than take your money for a build you didn't need.
Do I own the code you write?+
Yes, completely. The source code and the intellectual property are yours, there are no licence fees to me, and you're not locked into working with me to keep using it. If you ever want to take it to another developer, you can, and everything will be documented well enough that they can pick it up. I'd rather you stay because you want to.
How long does a project take?+
A focused tool that solves one specific problem is usually a matter of weeks. A full business system that several people depend on is more often a few months. The honest answer is that it depends on how much of your process the software has to cover, and I'll give you a real timeline with milestones during scoping rather than a hopeful number now.
What does custom software cost?+
It depends on scope, and I won't pretend otherwise; anyone quoting you a figure before understanding your process is guessing. What drives the cost is how many parts of your business it touches, how many systems it has to integrate with, and how much data needs migrating. You'll get a clear number with the risks laid out before you commit to anything, and if the number doesn't make sense against what you'd save, I'll tell you that too.
Can you integrate with the systems we already use?+
Usually, yes, and it's often the highest-value part of the work. If a system has an API, I can connect to it. If it doesn't, there are normally still options, though I'll be upfront about which ones are fragile. Most of the businesses I work with already own everything they need; the problem is that none of it talks to anything else.
We have a half-finished project from another developer. Can you take it on?+
Yes, and it's something i've done on multiple occasions. I'll read through what exists first and give you a straight assessment. Whether it's a solid foundation worth continuing, or whether carrying on would cost you more than restarting. That assessment is the same either way regardless of which answer earns me more work.
Can you modernise software we already rely on?+
Yes. Old software that still works is a genuine asset and I don't rip things out for the sake of it. Sometimes the answer is incremental; update what's fragile, leave what's fine. Sometimes the system is old enough that a gradual migration costs more than a rebuild, which is what happened with GOLD, a fifteen-year-old desktop application I rebuilt as a mobile-first web app.
Am I actually talking to the person building it?+
Yes! Abyss is just me. There's no account manager, no sales handoff, and no outsourced development team you find out about later. I take on two projects at a time so yours gets proper attention, and if I'm booked I'll tell you straight rather than stretch myself and let your timeline slip.
What happens after it launches?+
Most people want me to stay on, and that's the arrangement I prefer too. Ongoing changes, new features as your business shifts, and someone to call when something breaks. If you don't need that, it's fine; you own the code and you're free to go your own way. I'll still be at the end of the phone if something goes seriously wrong.