FlexiSystem

The situation

Payroll in Nigeria carries a weight most people underestimate. The math is manageable. What makes it heavy is what sits underneath the math: PAYE, NHF, NHIS, pension deductions, tax bands that change, and compliance rules that don’t care whether you’re a five-person startup or a 500-person company. Miss one, and you’re not just late on salaries. You’re in trouble with the state.

I heard that weight in the interviews. Payroll officers told me about the stress of month-end, the fear of missing a compliance update, the small mistakes that turn into big fines. One of them told me she rechecks her numbers three times before submitting, even when she knows they’re right. The pressure never really goes off.

I also heard the excitement. Every single person I interviewed lit up when they heard the product could reduce that pressure. Not a small “oh, nice.” A visible, hopeful lit-up.

The founder wanted to build for that gap. Payroll software built for Nigerian businesses, scalable from small teams to large ones, and designed to make the compliance part feel less like a monthly panic. That became the promise:

Run payroll in minutes. Stay compliant with confidence.

What I did

I designed the product from the ground up. That meant product strategy, UX research across five user groups (payroll officers, HR leads, finance, employees, and admins), competitor research across nine platforms, deep dives into Nigerian statutory requirements, information architecture, the whole design system, all the core flows, the marketing site, the brand refresh, and the interaction patterns that hold it all together.

How I approached it

Payroll is an ecosystem, not a task.

Before I designed a single screen, I mapped how payroll officers actually think. What happens before payroll. What happens after. What causes mistakes. Where the delays come from. Which actions happen every month, and which show up once a year and catch everyone off guard. Once I saw it as an ecosystem, the product structure basically wrote itself. Dashboard, People, Payroll, Compliance, Security, Settings. Named around what users are trying to do, not around database tables.

Trust had to be built into the interface.

Payroll handles people’s livelihoods. Every button, confirmation, and status label had to reinforce that the system knew what it was doing. So I designed for progressive disclosure, only surfacing complexity when it was needed. And I made compliance visible everywhere. A payroll officer should never wonder whether the system remembered PAYE. The answer should be right there, quietly reassuring her.

Nigerian-first, globally inspired.

I studied Deel, Gusto, BambooHR, ADP, and Workday for structural patterns and enterprise UX. Then I designed for Nigerian payroll specifically. Local tax bands, local statutory bodies, local employment language. The result feels native, not imported.

A hybrid onboarding that respects first-time users.

The team debated whether to force onboarding before the product, or drop users straight in. I landed on both. Users create an account and step immediately into FlexiSystem, but a guided setup wizard walks them through company details, payroll settings, employee import, and compliance setup. They can explore the product at any point. The wizard just waits patiently. Nobody gets locked out of their own tool.

A design system that could stretch from startup to enterprise.

The same product had to work for a ten-person team and a 500-person company. So I built the system with real range: buttons with full state coverage, inputs designed for clarity over decoration, tables that scale, status chips that communicate at a glance, and empty states that teach. Consistency was the promise. Scalability was the payoff.

What happened

The design was approved and moved to development, where the team is actively building. The client is running the FlexiSystem name and identity, and the product is on track to serve Nigerian businesses from small teams up to enterprise scale.

Looking back

FlexiSystem was the deepest research project I’ve done. Not just interviews, and not just design.

The statutory side of Nigerian payroll pulled me into territory I’d only thought about in passing. It was mostly new ground for me, and some days the reading was heavy. PAYE calculations, pension contribution rules, tax band updates, statutory filing deadlines. I’d read, take a break, come back, and then read some more. I had conversations with people on the tax and audit side to check my thinking. I wanted to be sure the product wouldn’t quietly ship a compliance mistake, because for the users on the other end, that mistake would cost them real money and real sleep.

That’s the part of product design that doesn’t show up in a portfolio screenshot. But it’s the part that decides whether the tool is trustworthy or not.