Building a Nigerian tax product people could actually trust.
TaxCalc.ng began as a straightforward tax calculator. The real work was turning it into a finance product with fast calculations, saved results, exports, account flows, admin operations, and Cloudflare-backed delivery working together.
People did not need another calculator. They needed confidence.
Nigerian tax and payroll questions often begin in a messy place: a salary figure, a few deductions, a vague idea of PAYE, and a spreadsheet that nobody fully trusts. TaxCalc.ng had to make the answer feel quick, explainable, and reusable without pretending to be a tax adviser.
TaxCalc.ng became more than one calculator page. It now has saved tax sheets, exports, salary simulation, account flows, early payroll workspace flows, and owner operations. That is the useful proof: not one clever formula, but a finance product with enough real surface area to test the engineering.
People used it, returned to it, and pushed it past a demo.
The useful signal was not a vanity launch number. People came in with salary and tax questions, ran calculations, reviewed results, saved work, exported records, and came back when they needed to check another scenario.
That changed the standard for the product. It needed to be fast, explainable, and calm to use, while the admin and operations layer stayed strong enough to support a real finance workflow behind the scenes.
The product had to stay simple, even when the rules were not.
Tax rules, reliefs, deductions, saved sheets, exports, account flows, and admin controls all had to feel like one product. The user should not have to think about the plumbing. They should get an answer they understand, then have a clear next step.
Performance context: Signal references a roughly 10ms backend/database budget for the calculation path. Broader application response-time claims should be read as complete request behavior across Cloudflare production traffic, and uptime claims should be tied to a named monitoring window.
- A.
Fast answers, clear explanations
The calculator had to respond quickly, but speed was not enough. The result also had to be understandable enough for a non-specialist to trust.
- B.
A product, not just a formula
Saved records, exports, account flows, admin tools, and product operations were part of the work because real finance software does not end at the first successful calculation.
FIG 1.1 - LOGIC IMPLEMENTATION
export const payeFlow = ( grossKobo: number, pensionKobo: number) => {
// JS floats after converting kobo back to naira
const gross = grossKobo / 100;
const relief = deriveRelief(gross);
const taxable = normalize(gross - relief - pensionKobo / 100);
const bands = deriveBands(taxable);
let tax = 0;
for (const band of bands) {
const slice = Math.min(taxable, band.cap) - band.floor;
if (slice <= 0) continue;
tax += slice * band.rate;
}
return round2(tax);
}
What had to work together
Input
Salary, deductions, reliefs
PAYE tax engine
Rules, bands, calculations
Output & operations
Result, PDF, payment, support
Useful if your product has finance logic people need to trust.
Payroll and HR platforms that need localized PAYE logic without turning the product into a spreadsheet with a login screen.
Fintech or accounting teams building calculators, entitlement flows, exports, dashboards, and subscription billing into one coherent system.
SME finance operators who need internal tooling around tax, payroll, deductions, approvals, or reporting.
Start with the part that has to be correct.
If TaxCalc.ng looks close to what you need, the first project can stay practical: a tax engine, a finance calculator MVP, a payment flow, an internal dashboard, or a backend/API review.
TaxCalc.ng provides estimates and product workflows, not legal, tax, accounting, or financial advice. The proof here is software delivery, not a compliance guarantee.