Internal audit & GRC
Assure
Internal audit management software that unifies the audit universe, risk register, working papers, findings and continuous monitoring in one system.
DetailsEnterprise software
Enterprise software development and system modernisation
Large systems that have to survive contact with the systems already in the building.
An enterprise build is rarely a greenfield. There is an ERP that owns the general ledger, an HR system that owns the establishment, a payments rail that owns settlement, and a decade of data in a system nobody wants to touch. The new application has to sit among those and be correct about which one is the source of truth for each field.
So we plan the integration first. Before the interface design, we work out what data crosses which boundary, in which direction, how often, and what happens when a load fails at two in the morning. That analysis usually reshapes the scope, and it is much cheaper to reshape it at that point than after the build.
The rest is the discipline that large systems need and small ones survive without: role and permission modelling done explicitly, load testing against realistic volumes, and a phased rollout so the first department through is a pilot rather than the whole organisation at once.
What you get
- Integration design against existing systems
- Role and permission modelling
- Performance and load testing
- Phased rollout plan
Who this is for
- IT directors and CIOs
- Organisations running an ERP
- Public bodies and regulated institutions
How the engagement runs
Six steps, in this order.
Skipping one of these is how projects end up rebuilt. The order matters more than the ceremony.
- 01
Consultation
We sit with the people who do the work and find out what actually happens, including the workarounds nobody documented.
- 02
Planning and proposal
Scope, timeline and cost in writing, with the assumptions listed. If something is unknown, it is named as unknown.
- 03
Design and development
Data model first, then interface. You see working software early and often rather than a demo at the end.
- 04
Testing and refinement
Functional, load and user acceptance testing. Findings go on a list that gets closed, not a list that gets discussed.
- 05
Implementation and integration
Migration, integration with existing systems and a cutover plan that accounts for the day the old system is switched off.
- 06
Training and support
Your team is trained on the system they will use, and we stay on for maintenance, updates and the questions that arrive in month three.
Already built
You may not need a build.
Where this work is the same in every organisation, we have already productised it. These platforms cover it off the shelf.
Questions
Asked before we start.
Something not covered here? Email us and a person will answer.
Which enterprise systems can you integrate with?
In production we have connected to SAP, Oracle, Microsoft Dynamics, eTIMS and KRA. Beyond those, if a system has an API, a database we can read, or a file export on a schedule, it can be integrated. We assess the source systems during discovery and say plainly which ones will be difficult.
Can you work with our existing development team?
Yes. We take architecture and integration work alongside an in-house team, or embed with them for the duration. The handover documentation exists either way, because the point is that your team can carry it afterwards.
What happens to the legacy system?
Usually it stays running while the new system takes over one process at a time, with data flowing between them until the last dependency is gone. Switching everything on one date is possible but it removes your ability to roll back, so we only recommend it when the old system is genuinely unusable.
Scoping
Send us the process that keeps breaking.
A short description is enough to start. We will come back with whether it is a product, a build, or something you can fix without buying software.
Nairobi office
10th Floor, Applewood Adams, Ngong RoadNairobi
Kenya
- Phone
- +254 701 684 754
- Hours
- Mon–Fri, 08:30–17:30 EAT