Built, connected, and kept running.
Three capabilities that overlap on purpose. Most projects start in one of them and, once the system is live, quietly move into the third — which is where the real cost of software usually sits.
Systems built because nothing off the shelf fits.
We take projects through the full life cycle: requirements and analysis, software architecture, development, testing, refinement through pilot programmes, and implementation in a production environment.
We have worked across many technology stacks, programming languages, development tools and database, networking, communication and interface technologies. Having been through a lot of product releases, we know which shortcuts are cheap now and expensive in year three.
Typical engagements
- A system that encodes a process no packaged product supports
- Replacing a spreadsheet or database that outgrew itself
- Extending an existing application rather than replacing it
- A dedicated development team for a project of fixed scope and duration
- Taking over and stabilising software written by someone else
New applications rarely arrive on an empty desk.
Organisations need new systems to work with old ones, which may sit on the cloud, on premise, at a customer or even at a supplier. Application and data integration is usually the difference between software that gets adopted and software that gets worked around.
We identify the right bridge for data to pass between applications and platforms so your existing investment keeps earning. Effective integration also needs process work and change management, not only tooling — we say so up front, because that is normally where projects stall.
What we connect
Also included
- Product consulting: choosing and configuring the right system
- Data migration from the system you are leaving
- Reporting that draws on more than one source
The part that lasts longer than the project.
We provide application support and maintenance as an ongoing service, including remote administrator and remote end-user support. The aim is to keep maintenance costs predictable while making sure operational problems get fixed rather than queued.
This is not limited to software we wrote. A large part of our support work is on systems inherited from other suppliers, where the original team is no longer available.
How it works
- Agreed response times, written into the contract
- Remote administration of the application and its environment
- End-user support for the people who actually operate it
- Updates, patches and version upgrades
- One point of contact, with access to your installation and its history
And when a product already solves it, we say so.
Two of the problems we were asked about most often we ended up solving as products. If one of them fits your case, it is faster and cheaper than building from scratch — and we will tell you when that is true.
Tell us what is not working.
We would rather have a straight conversation about scope before anyone talks about budgets. If the answer is that you do not need us, that is a useful answer too.