Why I can say yes when a bigger competitor has to say no
An email landed in my inbox this week from the compliance team at a regulated financial firm. A routine annual training requirement, the kind every licensed institution in Malaysia has to run, covering things like anti money laundering, conflict of interest, and how staff are expected to handle non-public information.
None of that is unusual. What made me read the email twice was the second paragraph.
For years they had used one training partner. A well known name, the kind the whole industry used, the kind you would assume had this locked up forever. That partner had just quietly stepped back from offering this kind of programme. So a compliance team that had never once had to think about where this training comes from was suddenly emailing companies like ours, cold, with a deadline already sitting on the calendar.
This is not a story about a deal. I do not know yet whether we will run that session. That is not the point. The point is what the email accidentally reveals about why a big, well known name lets go of work like this, and why a smaller company like mine can pick it up and actually keep it.
Why the big ones eventually let go
A large training institution is not built the way people assume. It is built to protect a margin across everything it runs, decided somewhere above the people actually doing the training. A course has to clear that bar every year, against overhead, against headcount, against whatever the finance team upstairs has decided the whole division needs to return.
When a course stops clearing that bar, somebody cuts it. Not because the content stopped mattering, and usually not because clients stopped wanting it. It gets cut because it stopped being efficient at the scale that institution is structured to require. The work does not disappear. It just becomes somebody elseās opportunity, with no notice and a deadline already sitting on the calendar.
Why I can say yes instead
I do not have a head office two layers above me asking whether one course cleared a margin target this quarter. That is the actual difference, more than effort or talent.
When a client asks me for one course, I can say yes to that and quietly add two or three more that round out what they actually need, priced closer to what it is worth to them than to what it costs me to run. The extra cost of doing that is small on my end, and I am not required to defend it against a quota that exists three levels above the person actually deciding. That is not generosity. It is just a structural advantage of staying small and leanly run, and I have kept Orbix built that way on purpose, even as it grows.
It shows up in smaller ways too. In 2019, on the four months we had to ship PahangGo, I hired a graphic designer who had never done product or UX work in her life. Nothing on her CV said she could do this. A bigger, more margin-conscious organisation would never have made that bet, the cost of training someone from nothing does not clear a quarterly return. I trained her anyway, on that project and the ones after it, and UI and UX design became her actual profession. She has built a career on it since, entirely her own now. The same project gave me a programmer who came on part time and stayed long enough that the arrangement stopped making sense as anything other than permanent. He runs technology for a state digital agency today.
Neither of those decisions would have survived a margin review at a bigger company. They were only possible because nobody was asking me to justify them against one.
The part I am less proud of
Staying lean is not the whole answer either.
Being free of a margin target does not mean being free of a cost. Every extra course I add for free, every person I train from nothing, is still money and time I am choosing not to collect elsewhere, and I do not always price that choice as carefully as I should. The designer I trained still needed someone to notice when the brief itself was wrong, not just execute it well. The chief legal and compliance advisor I hired at Orbix still needs someone above the process who can depart from it when a situation shows up that nobody built a rule for.
That is the job I have not fully solved. Staying flexible is the easier half. Knowing when flexibility is actually costing me something is the harder one, and I do not think you ever finish learning it.
What I actually think about when I read an email like that
A well known institution just found out, in public, what it costs to be built around protecting a margin instead of protecting a relationship.
I did not build Orbix to be the biggest name in this market. I built it so that when a client needs one more thing than what they originally asked for, saying yes does not require a meeting. That email sitting in my inbox this week is the closest thing I have to proof it actually works, and I would rather keep finding that out this way than by trying to become the kind of company that eventually has to say no.