Security is structural
Audit logs, scoped permissions and encryption are designed in from the first schema, not bolted on when a client asks about compliance.
Business Software We Build and Run
Advice is cheap. Working systems aren’t.
Most consultancies stop at the recommendation. We kept going. These are three systems Mimir designed, built and runs in production — each one started as a business problem that no off-the-shelf product solved properly, and each one is available to deploy for your business.
Mimir ePOD
Electronic proof of delivery. The recipient signs on their own phone through a single-use QR code — signature, photos, timestamp and location sealed into a PDF and pushed into your ERP. Works with no signal.
Mimir B2B
A trade ordering portal that knows each customer’s contract prices, checks their credit live before accepting an order, tracks catch-weight through to invoice, and reconciles itself against your ERP every night.
Mimir PSA
Professional services automation with AI triage on every ticket, an encrypted knowledge base and password vault with folder-level permissions, and versioned processes that attach to live tickets.
Built the Same Way
Different problems, one engineering standard.
Your data stays yours
Every system is containerised and deployable on your own infrastructure. No lock-in, no hostage data, documented backup and restore from day one.
They integrate, not isolate
Each product assumes you already have systems that matter. Adapters, signed webhooks and documented APIs mean nothing gets re-keyed by hand.
Configured to your business
These are products, not templates. Branding, workflow, roles and integrations are shaped to how your business actually runs before go-live.
Why a consultancy builds software at all
It is a fair question. The short answer is that all three of these started as somebody else’s problem that we were brought in to solve, and in each case the honest recommendation would have been to buy something — except that what was available either did not do the job or priced a small business out of it entirely.
The longer answer is that building keeps the advice honest. It is easy to recommend an integration when you have never had to maintain one. Having to run these in production, with real users who complain when something is slow, is a useful corrective to the kind of architecture advice that sounds good in a document and falls apart on contact with a bad mobile signal in a depot.
These are products, not projects
An important distinction, because it changes what you are buying. A project ends with a handover and a maintenance conversation nobody wanted. A product is already running, already has the awkward edge cases handled, and improves without a change request.
What that means practically: configuration rather than development for most of what a new deployment needs, a known deployment path rather than a discovery phase, and fixes that arrive because another user hit the same thing first. Where genuinely bespoke work is required we will say so, scope it separately, and price it as development rather than hiding it in a licence fee.
How this connects to the consulting work
Most engagements are not a product at all. They are the strategic IT services that sit alongside them — and deploying any of these three properly draws on the same disciplines:
- Identity and access. Every one of these systems needs to know who your users are and what they may do, which is an architecture decision before it is a configuration screen.
- Integration. The ERP adapters and webhooks are the fragile, business-critical connections that the architecture work exists to document rather than leave in one person’s head.
- Security and data protection. Signature images, delivery photos and service-desk records are personal information under POPIA, so access control on them is a risk management question, not a feature.
- Recovery. A system the business now depends on needs a tested restore. That is disaster recovery work, and it is part of the deployment rather than something to get to later.
If you are not sure whether your problem needs one of these products or simply better use of what you already own, that is what the assessment is for. It is a legitimate outcome for it to conclude that you need neither.
If one of these looks like a problem you have—
Let’s talk about what it would take to run it in your business.
Request a Strategy Session Accepting new clients