Insights

What we have learned building systems that cannot fail.

Written by the engineers who run these platforms in production — not a content team. Here is what is in the writing queue, and why each piece exists.

This is our editorial plan, not an archive. Nothing here is backdated — each piece appears once it is actually written.
TopicsCompliance & AMLChoosing softwareDeployment & hostingLocal integrationsOperations
Compliance & AMLIn draft

What AML screening actually has to prove

A screening tool that returns the right answer is not enough. When an examiner asks what you checked, against which list, and on what date, the system has to answer — and most cannot. This is what we learned building the platform running across scheduled banks.

Written by our Infrastructure & Compliance team
What it covers
Why the audit trail matters more than the match rate
PEP, sanctions, criminal and adverse media as four different problems
Where manual review stops scaling, with real thresholds
What data residency rules mean for your deployment choice
Choosing softwareIn draft
ERP: buy, configure, or build from scratch
The honest version of a question we get weekly. Configuring an existing platform takes weeks; building takes months. Here is how to tell which one your operation actually needs — including when we tell clients not to buy from us.
Product & Design
Deployment & hostingPlanned
Cloud, private cloud, or on-premise
Three deployment models, three sets of trade-offs. What each costs you in control, in maintenance, and in the conversation with your regulator — written for the people who have to sign off the decision.
Infrastructure & Compliance
Local integrationsIn draft
Why POS software must work offline in Bangladesh
A counter that stops billing when the internet drops is not a software feature discussion, it is lost revenue on a Friday evening. How we build offline-first billing that syncs back cleanly, and where that gets hard.
Engineering
OperationsPlanned
What a visa consultancy loses to spreadsheets
An enquiry can take a year to become a visa decision. We counted where threads actually get dropped across counsellors, documents and university partners — and what that costs in commission.
Product & Design
Local integrationsPlanned
Payment gateways and couriers: what actually breaks
Integration documentation describes the happy path. This is the other one — timeouts, duplicate callbacks, reconciliation mismatches — and the patterns we now use by default on every ecommerce build.
Engineering
OperationsPlanned
Why admissions and billing must be one system
Hospitals routinely run patient records and revenue on separate software, then reconcile days later. What that split costs a private hospital, and what changes when the two share one record.
Product & Design
Why we write these

Most software content is written by people who have never been on the call at 8pm.

Ours comes from the teams who built the compliance screening running inside banks, the POS that has to bill through an internet outage, and the CRM tracking a student for a year. Every piece answers a question a client actually asked us.

No piece is published unless someone here has actually done the thing it describes.
We name the trade-off, including the cases where our own products are the wrong answer.
No backdated posts, no ghostwritten bylines, no invented statistics.
Want a piece first?

Tell us which topic matters to you and we will send it when it is written — and move it up the queue.

Request a topicAsk us directly