07 / Making it stick
Business analysis · Sales + HR
“We bought the software. Nobody uses it.”
The most expensive failure here, because the money is already spent — and it is almost never a software problem.
Today
- Requirements as prose
- Built to guesswork
- Argument at UAT
After
- Given / When / Then
- Tested against it
- Trained on site
- Used
Requirements you can test, and training that survives go-live.
- 01
Write requirements that can be checked
Given / when / then, so there is one version of done.
- 02
Test against them before anyone signs
A UAT script the client runs themselves.
- 03
Train on site, on the awkward cases
The refund, the split order, the thing that breaks on Fridays.
Built with
- BRD
- Given / When / Then
- UAT scripts
- On-site training
Solved for
Tyre & Tube manufacturer
31 user stories restructured into testable acceptance criteria, so development and UAT ran against one source of truth. Related: on-site training across five modules for a global shipping group.
Other problems I solve
“We track stock by hand, and the count is never right.”
Odoo · Point of Sale + Inventory“Orders and approvals live in WhatsApp, email, and someone's head.”
Custom platform · Multi-tenant B2B“I can't see the numbers without asking someone to build a report.”
Odoo · Dashboards + Accounting“The same information gets typed in three times a day.”
Odoo · Workflow automation“Our website or app is old, slow, or doesn't do what the business needs.”
Custom product · Next.js + Supabase
13 / Contact
Tell me what’s breaking.
One sentence is enough to start. If it’s something I can’t help with, I’ll say so rather than sell you a project.