Skip to main content

About This Project

Experience and Method

This website is intentionally built as an educational tax resource, not a black-box calculator. The two core tools expose each decision branch, each threshold, and each output assumption so users can review logic before acting on it. That design is deliberate: in tax compliance, explainability is a trust feature.

Author and Maintainer

Lukmon Isiaq

Software Architect and Tax Tooling Maintainer | Lagos, Nigeria

I build practical tax-compliance products that convert dense policy language into transparent, testable decision tools for founders, finance teams, and cross-border professionals.

My focus is the space between policy and implementation: where tax rules are clear on paper but hard to apply consistently inside real operations. This suite was built as a working reference for teams that need quick screening outputs without losing the underlying audit trail.

Instead of publishing opaque calculators, I document assumptions, expose formulas, and keep validation strict. Every tool output is traceable to explicit input fields and deterministic logic so that users can challenge, verify, or improve each decision branch.

I maintain this project in public with a versioned codebase, reproducible builds, and update notes tied to source documents. That approach is intentional: trust in tax software should come from visible process, not marketing language.

Methodology and Editorial Policy

Every tool in this suite is developed with the same workflow. First, policy inputs are converted into explicit rule statements. Second, the rule statements are implemented as typed logic functions with strict Zod validation at the input boundary. Third, result messages are written to match the exact branch that was triggered so users can audit cause and effect without reading source code.

The platform is versioned and build-tested using reproducible Next.js App Router builds. Documentation and calculators are maintained together so that logic and explanatory text do not drift. This prevents a common low-trust pattern where long-form content says one thing while the tool computes something else.

We also maintain a transparent boundary policy. These tools are built for screening and educational use. They do not replace jurisdiction-specific tax advice, and they do not submit returns to any authority. Where facts are incomplete or edge-case heavy, users should treat outputs as a briefing artifact for a qualified adviser.

Last editorial review: 14 April 2026.

Primary Sources and Verification Links

The links below are the baseline references used for policy context and continuous updates. We cite government-first sources where available and clearly label third-party summaries used for cross-checking.

Support and Update Cadence

We treat this project as a maintained product. Bugs and feature requests are triaged through the support channel, and resolved work is published in the changelog with concrete release dates.

Latest release in this log: April 16, 2026 (v1.12.0).