Your fleet reports one number a month. It should report sixteen.
Most managed fleet arrangements settle on a single figure at month end. That number cannot be checked, and it hides the four costs that…
Resources
Technical writing, case studies, the assessment tool, and the documents a procurement reviewer will ask for. No gates.
Free tools
Five working tools: requirements document builder, readiness assessment, cost calculator, project estimator and vendor scorecard. No email required on any of them.
ERP readiness assessment
Twelve questions, scored in your browser. Tells you whether to build, buy or wait, and where the risk sits. No email required.
Custom build or off-the-shelf
An honest comparison of building against Odoo, Zoho and similar. Including when off-the-shelf is the better answer.
Case studies
What was broken, what we built, and what changed afterwards. Written as engineering records rather than marketing summaries.
Insights
Technical writing on ledger design, transaction integrity, AI guardrails and data modelling.
Security & data ownership
Access control, backups, sub-processors, incident handling and what happens if you leave. Written for a compliance reviewer.
How we work
Five delivery stages, each with the deliverable and the condition that closes it.
Accessibility statement
Measured contrast ratios, what is implemented, and the gaps we have not closed yet.
How to use these
Nothing here is gated, and that is deliberate
Most suppliers put their useful material behind an email form, which means it reaches the people who already trust them and nobody else. The material below is the reverse: it is designed to be useful before you have spoken to us, and several pieces of it will tell you not to buy from us.
- If you are working out whether to build at all — start with the readiness assessment, then the build-or-buy comparison. Between them they will tell you to buy off-the-shelf if that is the answer, which it is roughly a third of the time.
- If you have decided and need to approach suppliers — the requirements builder produces the document you send them, and the vendor scorecard compares what comes back. Both work with any supplier, including ones that are not us.
- If you are checking whether we are credible — the case studies name the client and the system, and the security page is written for a compliance reviewer rather than a marketing audience. Both state what we have not done as well as what we have.
- If you want to know how we think — the articles are engineering writing rather than thought leadership: ledger design, transaction integrity, why a month-end close takes a week. They are the closest thing to sitting in on a technical review.
Latest writing
From the Insights archive
How to evaluate software for Hajj and Umrah operations
General travel systems get two things wrong in this sector, and both surface after go-live rather than during a demo. The nine questions that…
UAE fit-out approvals: working out which authority you actually need
A single Dubai fit-out can require submissions to several separate authorities, each with its own portal and review culture. What determines which ones apply…
Start here
Ready to build your next digital solution?
Send the brief and you get a scoped response with approach, milestones and a fixed price range. Not a sales call.
1
A 30-minute call with the engineer who would run your project
Within 2 business days
2
A written scope: approach, module breakdown, milestones, fixed price range
Within 5 business days
3
You decide. No retainer, no obligation, and the scope document is yours to keep either way
Your timelineSend your brief
Three fields to start. Add project details if you have them.