Software built around the way your business works
Custom software, web applications, modernization, migration and integration. We start by understanding the problem, then build only what it needs.
Most software problems are not coding problems.
The software does what was asked. What was asked did not solve the problem. Or the business changed and the system stayed where it was, and people filled the gap with spreadsheets, re-typed entries and reports built by hand.
So we do not begin with a quote. We begin with what is going wrong, what you already have and what the business needs next. Sometimes the answer is new software. Often it is something smaller: modernizing one part, connecting two systems, or moving what you have somewhere better.
- Problem first. We ask what is going wrong and what it costs before we talk about solutions.
- Assessment before quotes. An existing system is examined before anyone prices its replacement.
- The smallest fix that works. If configuration, integration or a packaged product would do, we say so.
- Yours at handover. Source code, documentation and credentials are transferred to you.
Six kinds of work, often several at once.
Custom software
Business applications designed around a defined workflow, where no packaged product fits without constant workarounds. Read more
Web applications
Browser-based systems for teams working across locations and devices, with central data and access by role. Read more
Software modernization
Older systems improved one part at a time: interface, reporting, database or integrations, keeping what already works. Read more
Software and database migration
Applications and their data moved to a new server, host or platform, planned and tested before cutover. Read more
System integration
Your website, CRM, accounting, inventory and payment tools connected so data is entered once. Read more
Workflow automation
Repeated manual steps removed from the chain between first enquiry and final report. Read more
Before you commit to anything, find out what you have.
A rebuild quoted without looking at the existing system is a guess with a price attached. An assessment replaces the guess with evidence. It can examine:
- Architecture and how the parts depend on each other
- Source code: availability, structure and readability
- Database design, data volume and data quality
- Hosting and how the environment is configured
- Libraries, frameworks and licences still in support
- Performance: where the system slows down and why
- Security considerations and outdated components
- Integrations with other systems and services
- The workflows people really follow each day
- Documentation, and what lives only in memory
- Backups and whether they can be restored
- Who controls hosting, domain and service accounts
Usually one of these, sometimes several.
Six steps, and the first two decide the rest.
Understand the business problem
What is going wrong, who it affects and what it costs. In your words, not technical ones.
Look at what exists
Current software, data, hosting and the workflow around them. For an existing system this is the assessment.
Lay out the options
New development, modernization, migration, integration or leaving things as they are, each with its trade-offs.
Build what was agreed
Development in stages you can see and comment on as they take shape, not a reveal at the end.
Deploy in a planned way
Testing first, then a move into real use at a time that suits the business, with a way back if needed.
Keep improving
Fixes, updates and new requirements after launch, because the business will keep changing.
See the approach on real work: our case studies on school and college ERP modernisation and migration and an ERP implementation across a large education network.
The damage is rarely visible at launch.
What people expect to go wrong
The project runs a little late, costs a little more, and has a few bugs to tidy up after go-live.
What actually goes wrong
The software does exactly what was specified, and the specification did not solve the problem. Rules the old system quietly enforced surface later as missing features. Staff go back to their spreadsheets.
Software is judged a year later, on whether people still choose to use it.
What you have when the assessment is done.
A plain-language document a business owner can act on, whoever does the work that follows.
- What the system is and how it works
- What condition it is in
- What you hold and what is missing
- The risks that need attention, in priority order
- Realistic options with their trade-offs
- A basis for comparing any proposal fairly
An assessment is not a commitment to build. You can act on it with us, with another provider, or decide to change nothing. Sometimes its conclusion is to leave the system alone and fix three things.
Built for businesses whose software has a job to do.
This is worth doing where the software runs daily operations, where a mistake in it costs money, or where it has to be maintained for years by people who did not write it.
Honest note: if a packaged product already does what you need, buy it. It will be faster and usually cheaper. We will tell you that rather than quote for a build you do not need.
- Businesses whose workflow no product follows
- Organisations running software nobody can safely change
- Schools, colleges and institution groups on an outdated ERP
- Companies with several systems and no shared data
- Teams tied to one desktop application in one office
- Anyone planning to move an application or its database
The things worth knowing before you start.
Do we need a written specification first?
No. You need to be able to describe what the system does today, what it no longer does well and what the business needs next. Turning that into a specification is part of the work.
How much does custom software cost?
It depends on what has to be built, and nobody can answer honestly before understanding the requirement. That is why we scope first. For an existing system, the assessment is what makes a reliable estimate possible.
Will you work on software someone else built?
Yes, subject to an assessment. We need to see the code, data and hosting before saying what is realistic, and we will tell you plainly if a system is not in a state we can responsibly maintain.
Who owns the code?
You do. Source code, documentation and credentials are handed over, so you are not dependent on us to keep the software running.
Which technologies do you use?
We choose based on what you already run, what the software has to connect to and who will maintain it afterwards. We explain the choice in plain language before any work starts.
Do you support the software after launch?
Yes. Software needs fixes, updates and changes as the business evolves. We discuss ongoing support at the start so it is planned for, not an afterthought.
The rest of the technical side.
Migration Services
Sites, mailboxes, databases and applications moved between hosts and platforms without losing anything. Read more
WordPress Development
Building, extending and maintaining WordPress sites that are meant to be worked on. Read more
Backup Solutions
Automated, tested backups, so a bad day stays a bad day rather than becoming a bad quarter. Read more
Tell us what is going wrong. We will tell you what it needs.
Send us three things: what the software does, what it no longer does well, and what you need it to do next. We will come back with an honest view and, where it helps, a proposal for an assessment.