Raza Ullah
Founder & Principal Engineer
Fifteen years building operational software for businesses that cannot afford it to break. Writes code most days.
About
We build for the person using it at 4pm on a Friday.
Not for the procurement committee, and not for the demo. The test of a system is whether the person under pressure reaches for it or works around it.
Why we exist
Most business software is sold to people who will never use it.
That single fact explains almost everything wrong with the category. The buyer sees a reporting suite in a boardroom. The user gets fourteen mandatory fields and a screen that takes four seconds to load, and quietly goes back to the spreadsheet.
We started BooleanWorkshop in 2016 after watching a retail group spend six figures on a system that its own staff refused to use. The software was not broken. It had simply never been designed for anybody who had to work at speed.
So our process starts on the shop floor, at the counter, or in the clinic — with the people who will live with the result. Everything else follows from what we learn there.
We also hand over the source code on every single project. Not because clients ask, but because a studio that has to keep earning your business behaves differently from one that has you locked in.
140 +Systems shippedAcross 18 industries since 2016
11 yrsAverage client tenureOur first customer is still with us
99.98 %Uptime across managed systemsMeasured, not claimed
0.4 sMedian page loadOn mobile, on a real 4G connection
The workshop
Small, senior and permanent.
No account managers relaying messages, and nobody you meet at the pitch who then disappears from the project.
Amara Osei
Head of Delivery
Keeps projects honest. Ran operations for a 40-site retail group before deciding to fix the software instead of fighting it.
Tomas Vlk
Lead Front-End Engineer
Angular since the beta. Cares more about interaction latency than most people care about anything.
Priya Raman
Product Designer
Designs for the person using it at closing time with one hand full. Ex-hospitality, which shows.
Daniel Whitfield
Infrastructure & Security
Backups, restores and the boring things that turn out to matter enormously exactly once.
How we work
Six stages, and you can stop after any of them.
01 Understand
Week 1We sit with the people who will use the thing. Not the org chart — the person doing the job at 4pm on a Friday. Most of what matters comes out in that conversation.
02 Shape
Week 2A clickable prototype and a fixed-price plan, phased so the useful part lands first. You approve the number before anyone writes code.
03 Build
Weeks 3+Two-week cycles with something working at the end of each. You see progress continuously rather than receiving a surprise in three months.
04 Prove
Pre-launchYour team uses it on real data before launch. We fix what they find. Nothing goes live on the strength of our own testing alone.
05 Hand over
LaunchSource code, documentation, admin logins and training. You could take it to another agency the next day. Most people do not, but you could.
06 Keep running
OngoingA care plan with a named engineer, a response time in writing and a monthly report of what was actually done.