How we implement software, from the first conversation to support
First we understand how your company works, look at where things stand today and what should be different. That is why a quote only comes once both sides know exactly what is being built.
WE BUILD SOFTWARE FOR COMPANIES LIKE THESE
From a conversation to a working system
This is what working together looks like, from the first call to the day your people start working in the new software.
What exactly is in the Business Blueprint?
The Blueprint contains everything that goes into the system, itemised before the build begins.
A list of the processes the system covers.
Specifically, by department and by step, not in broad strokes.
A list of the functionality.
Specifically what the system does and who uses it, itemised before the build begins.
The number of licences and who uses them.
You know exactly how many people work in the system and in which roles.
The rollout order.
What comes first, what comes after, and what is needed from your side before each phase.
It does not end when the system is handed over
A system nobody maintains is out of date within a year. Laws change, the business grows, and people start asking new things of the system they use.
Maintenance and support.
You are talking to the people who built your system, not to a call centre.
Regulatory changes.
When the rules change, the system is brought into line.
New versions and enhancements.
As your business grows, the system is extended.
Training for new staff.
When you hire someone new, you do not have to train them yourself.
What clients often ask us
Does our work stop while the system is being implemented?
No. We implement in phases, and in most cases both systems run in parallel for a while, until we are confident the new one works as it should. The processes with the fastest payoff come first, the rest is added in turn.
Do we have to change the way we work?
No. Where you insist that the system adapts to you, we will adapt it. Where we see a better way, we will tell you, but the decision is yours.
Do you work with companies our size?
Our systems run in companies with a few dozen employees and in institutions with several hundred users. A better question than size is whether you have outgrown spreadsheets and disconnected software. If you have, it makes sense for us to talk.
How long does implementation take?
It depends on how many processes we implement at once, how many locations you have, how much historical data is migrated and how quickly your side signs off on what we ask for. That is why we do not promise deadlines up front. After the discovery phase you receive a phased plan with dates we stand behind.
How much does implementing a system cost?
We cannot tell you until we know what we are building. The price depends on how many processes the system covers, how many people use it and how much needs to be customised. Any figure given before that is guesswork, which is why we start with a discovery phase and a Business Blueprint. After that you receive a detailed and precise quote.
What if our people struggle with the new system?
That is exactly why your people are involved from the discovery phase, rather than only at the end. The system is built around the steps they already follow. Training is part of the implementation rather than an extra line item, and we stay available through the first week of use.
What if we need something a year from now that is not in the Blueprint?
That happens often, you grow and you change. Additional development is handled as a separate project, and since we know your system, we get to a solution quickly.
Why is the discovery phase charged separately?
Because it is demanding work. Our team spends a significant amount of time assessing your current situation, talking to your people and writing a document that stays with you, whether or not we go on to work together.