Case studies
Six projects, told from the beginning
An honest case study does not open with "the client chose us", but with the situation before: what was not working, what had already been tried, and why software was needed. Below are six, each with the decision that mattered most.
What you will find in each one
We do not publish the names of the companies we built the applications below for. Not because we have anything to hide, but because an internal application says how a company works on the inside, and that is not our information to pass on. Every project is identified by its field and by the size of the team using it.
For the same reason you will not find percentages here. "We cut processing time by forty per cent" is the standard sentence in case studies, and almost nobody measured it. What we write under "how the work looks now" are things you can see by opening the application.
The situation it started from
How the work was done before, workarounds included. It is the part missing from most case studies, and the only one that tells you whether it resembles your own situation.
What we built, module by module
Not a feature list, but what each piece does and why it was needed. Including what we decided not to build in the first version.
The decisions and the reasons behind them
The choices that changed the project: where we took the simpler option, where we insisted on the more expensive one, and what would have happened otherwise.
What we learned
Including what we got wrong. A case study in which everything went perfectly is an advertisement, not a description of a project.
All 6 case studies
Each with the situation it started from and the decision that mattered.
-
01Human resourcesRead →
Leave taken out of the spreadsheet and out of the inbox
The record of leave lived in a file kept by one person, and approvals travelled by email. It worked, until two managers approved the same day in parallel.
A company with more than fifty employees across three sites
-
02Property managementRead →
A payment notice the owner understands unaided
The manager spent more time explaining the calculation than doing it. The application did not shorten the calculation — it removed the need for the explanation.
A management company with several associations in its portfolio
-
03FinanceRead →
The receipt photographed on the spot, the claim closed without the pile
Receipts collected in a wallet and reached accounting once a month, creased and without context. Half the time spent on claims went into reconstructing who spent what, where and why.
A company with field teams and monthly expense claims
-
04SalesRead →
A CRM salespeople actually log into
The company already had a subscription CRM. The problem was not a missing tool, it was that nobody filled it in — because it gave nothing back to the person entering the data.
A B2B sales team with a long sales cycle
-
05Financial servicesRead →
A credit file with every step reconstructable
In a lending file, the question is not only what was decided, but who saw what and on what basis. A flow held in email cannot answer the second one.
A non-bank lending institution
-
06TransportRead →
A fleet that no longer depends on a file and one person
The fleet was run from a file of expiry dates someone intended to check every week. It worked until the week that person was on holiday.
A transport and distribution company with a few dozen vehicles
Does any of them resemble your situation?
If you recognise the way you work today in any of them, tell us. The first conversation is about what needs solving at your end, not about what we did for someone else.