Every organisation has a process that no packaged product quite fits. We build the system around it: CRM and ERP, automation of routine work, and integrations with the software you already use. We also modernise older systems, and every release is tested before it reaches your staff.
What we build
A project can combine several of these. The scope lists which ones are included.
- 01
Enterprise applications
Systems that many people in one organisation use through the working day, each in their own role.
- 02
Business process automation
Routine work, such as reminders and reports, is handed from people to software.
- 03
Legacy system modernisation
Older systems that have become hard to maintain are moved onto tools that are still supported.
- 04
Custom CRM and ERP systems
Customer records, orders and stock in one system, arranged around your process.
- 05
Integration services
Connections to the software you already use, through its API or its data exports.
- 06
Quality assurance
Every release is tested against the agreed scope before it reaches your staff.
How the work runs
This is the short version. The full one is on the page about how we scope and quote a project.
- Step 01
Scope
We write down the process the software has to follow, what will be built and what is left out. The quote follows from that.
- Step 02
Integrations
We check what each existing tool allows through its API or data exports, and tell you plainly if a connection is not possible.
- Step 03
Build
We build in stages and show you working software at each one.
- Step 04
Test and handover
The software is tested against the agreed scope, and you review it before it goes live.
After launch
An organisation changes how it works, and its software has to follow. When support is part of the agreement, the quote states what it covers, so you know who runs the system once it is live.
- 01
Fixes and releases
Faults are fixed, and each new release is tested before it reaches your staff.
- 02
New work
A new module or integration is scoped and quoted in the same way as the first build.
Tools
We choose from these to suit the project.
- 01
Interfaces
What a person sees and uses in the browser.
- React
- Next.js
- TypeScript
- Tailwind CSS
- 02
Server side
The data, the rules and the APIs behind the interface.
- Laravel
- Node.js
- Python
- GraphQL
- 03
Hosting and infrastructure
Where the software runs once it is live.
- AWS
- Docker
- Firebase
Questions
What is custom software, and when is it the right choice?
Custom software is built for one organisation and its way of working. It makes sense when ready-made products do not fit the process, or when several separate tools need to be replaced by one system.
What kinds of systems do you build?
We build enterprise applications, custom CRM and ERP systems, business process automation, and integrations between existing systems. We also modernise older systems that are hard to maintain.
Which industries have you built software for?
We have worked in finance and lending, e-commerce and retail, education, networking and VPN products, and professional services. We do not publish client names.
Can the new software connect to the tools we already use?
In most cases, yes. Integration is one of our services. During scoping we check what each existing tool allows through its API or data exports, and we tell you plainly if a connection is not possible.
How is the software tested before it goes live?
Quality assurance is part of every custom software project. The software is tested against the agreed scope before handover, and you review it before it goes live.
Related services
Technology assessments and architecture plans for owners deciding what to build, buy or retire.
More on IT consultingAssistants, prediction models and vision systems, built into the software a business already uses.
More on AI and machine learning
Start here
Describe the process the software has to follow. A few lines are enough to begin.