Custom Software
Software built around your business.
Build systems around your workflows, processes and requirements instead of forcing your business into generic software.
The software fits everyone except you.
Off-the-shelf tools cover the common case. The parts that make a business work — its approvals, its rules, its exceptions — are usually the parts the tool doesn't cover.
Sound familiar?
- A critical process runs on a spreadsheet only one person fully understands.
- Your team re-keys the same data into two or three different systems.
- You pay for software that covers most of the job, and work around the rest.
- You cannot answer 'who approved this and when' without asking someone.
- Month-end means assembling numbers by hand from several places.
- The workaround has become the process, and new staff are trained on it.
What we do
How the work runs
Process and requirements
Map how the work actually happens, including the exceptions people have stopped mentioning.
System design
Model the domain properly — entities, states, rules and who is allowed to change what.
Build and integrate
Build the system and connect it to the tools already in use, so data stops being re-entered.
Roll out
Migrate data, train users and move the business onto it without stopping the business.
What you get
What you end up with.
Deliverables, not promises. Every one of these is something you own and can point at when the work is done.
One system instead of five workarounds
The process, the rules and the exceptions modelled properly, in software that matches how the business runs.
Data entered once
Integrations with the tools you already pay for, so information stops being re-keyed between systems.
An auditable record
Who changed what, when and under whose authority — available without reading a log file.
A system that can be changed
When the process changes next year, the software changes with it instead of becoming another workaround.
Typical use cases
- Internal operations and back-office systems
- Approval and workflow systems with audit trails
- Replacing a spreadsheet-driven process with a real system
- Modernising software that still works but can no longer be changed safely
Engineering capabilities
- Domain modelling and clean architecture
- .NET and C# backends
- PostgreSQL schema design and migrations
- Role-based access control and audit logging
- Background jobs and scheduled processing
- Third-party and legacy system integration
- Data migration
- Reporting and exports
Why Recode
Why bring this to us.
- We map the exceptions people have stopped mentioning, because those are where off-the-shelf systems fail.
- We model the domain before writing features, so rules live in one place rather than scattered across screens.
- We have migrated live operational data onto new systems without stopping the business that depends on it.
Relevant work
Built by Recode.
KalHR
HR & workforce management platform
A workforce management platform covering HR, payroll, recruitment, performance, attendance and employee self-service.
View projectProDriva
On-demand professional driver booking
A booking platform for hiring vetted professional drivers to drive your own car, with fares quoted up front.
View projectHow we work
From problem to production.
- 01
Discover
Understand the business, users, requirements and problem.
- 02
Design
Define the product experience and technical direction.
- 03
Build
Engineer, test and iterate.
- 04
Launch
Deploy, integrate and get the product into production.
- 05
Evolve
Monitor, maintain and continuously improve.
Ways to work together
How to start without committing to everything.
Most clients begin with a discovery sprint: a fixed fee, a few weeks, and a plan you own whether or not we build it.
Discovery sprint
Find out what it takes before committing to build it.
A short, paid engagement that turns an idea or a problem into something you can make a decision on. You keep everything we produce, whether or not you build with us.
- Scoped requirements and a defined first release
- Technical approach and architecture
- Delivery plan with phases and a cost range
- The risks worth knowing about before you spend
Best for
New products, or a build big enough that guessing is expensive.
Product build
A defined outcome, delivered end to end.
We design, engineer, test and launch the product. Work is phased so you see something real early and keep seeing it, instead of waiting months for one reveal.
- Product design and engineering
- Working software in your hands every phase
- Deployment, monitoring and handover
- Documentation your team can actually use
Best for
Getting a product, platform or internal system into production.
Embedded team
Senior engineering capacity that stays.
We work as part of your team — your board, your standups, your priorities — with the scope set by the roadmap rather than a fixed statement of work.
- A named team, not rotating contractors
- Your tooling, your process, your repository
- Capacity that flexes as priorities change
- Knowledge that stays documented, not siloed
Best for
Live products with more roadmap than delivery capacity.
Rescue and modernisation
Take on software that has stalled.
We start with an honest assessment of what exists — what is salvageable, what is not, and what it would cost either way. Then we stabilise it and make it changeable again.
- Codebase and infrastructure assessment
- Stabilisation of the most urgent failures
- An incremental path off what cannot be kept
- A system your team can safely change again
Best for
Inherited, stalled or legacy software still carrying the business.
Questions
Custom Software: common questions.
- Isn't custom software more expensive than a subscription?
- Often it is, and when an off-the-shelf tool genuinely fits we will tell you to buy it. The comparison worth making is against what the workarounds currently cost in hours, errors and duplicated licences.
- Can it work with the systems we already use?
- That is usually the point. We integrate with accounting, payroll, CRM and provider systems over APIs, files or webhooks, depending on what they expose.
- What about getting our people to actually use it?
- We migrate the real data, run the old and new processes side by side where it is sensible, and train the teams who will use it daily. A system nobody adopts has failed regardless of how well it is built.
- How do you price work?
- Fixed fee for discovery, phased fixed scope for builds, and a monthly rate for embedded teams. You get a cost range before any build starts, and we would rather tell you a number you do not like than discover it together halfway through.
- Who owns the code?
- You do. All source code, infrastructure definitions and documentation are yours, in your repositories and your cloud accounts, from the first commit.
Related reading
Worth a look.
What custom software actually costs — and why fixed quotes go wrong
Most software budgets are not wrong about the build. They are wrong about everything that surrounds it.
18 August 2026 · 7 min readOperationsSeven signs your business has outgrown its spreadsheets
Spreadsheets do not fail loudly. They just quietly start costing more than the system that should have replaced them.
2 July 2026 · 6 min readOther services
Need custom software?
Tell us the problem and the constraints. We'll come back with how we'd approach it, what it would take, and whether we're the right people for it.