The CRM your team will actually use
Most off-the-shelf CRMs force you to bend your workflow around someone else's idea of sales. Here's what we learned building one that doesn't.
Every business we've worked with has a CRM story. They bought the popular one, the team filled it in for two months, then quietly went back to spreadsheets and WhatsApp. The tool wasn't broken — it just wasn't theirs.
Workflow first, software second
Before we wrote a line of code for Morgan Oxford, we sat with their advisors and admin staff and mapped the real journey from first enquiry to enrolment. Every status. Every handoff. Every edge case the off-the-shelf tools couldn't model.
What came out wasn't a CRM. It was a system that spoke their language — students and programmes instead of leads and deals, advisor handoffs instead of pipeline stages, role-based screens instead of one cluttered dashboard for everyone.
Why teams quietly stop using software
- It asks for data the team doesn't naturally have at that step.
- It has fields, tabs, or modules they don't use — but can't hide.
- It doesn't model the one handoff that actually matters to their day.
- It replaces a fast informal flow (a WhatsApp message) with a slow formal one.
"The right system disappears. The wrong system makes you think about itself."
Custom isn't always the answer. Sometimes a well-configured off-the-shelf tool is exactly right. But when your workflow is genuinely specific — and a lot of Lagos businesses' workflows are — bending it to fit generic software costs more in lost time than the software ever saved.