Your approval chain, stored as settings
Most tools hard code one approval path and make every company bend to it. We keep the chain as data, so you change who signs for what without anyone touching the software.
STEP 1
Someone raises a request
What they need and what it costs. Never who approves it.
STEP 2
The chain resolves itself
Role, department, site, category and amount pick the path.
STEP 3
Each stage signs or returns
A return carries its reason back. Silence escalates.
STEP 4
Everything is written down
Payment closes the request and opens delivery tracking.
Different rules per site, without a developer
One property needs the MD on everything. A workshop needs two quotes over a quarter million naira. Both are rows in a table your IT manager edits.
- First approver overrides. Replace the raiser's supervisor for one site or category.
- Ordered approval flow. Insert a stage and every future request follows it.
- Visibility rules. Control which departments can even see a site.
- Price hiding. Staff price their own items, or procurement sources them.
Routing rules
Add site| Site | Approval flow | Threshold |
|---|---|---|
| Harmattan Heights | Office of the MD | ₦0+ |
| Cedarline Court | Supervisor, ED, CFO | ₦500k+ |
| Meridian Motors | Procurement Officer, ED | ₦250k+ |
| Osprey Gardens | Sales Mgr, Marketing Mgr, ED | ₦0+ |
| Ridgeway Terraces | Snr Project Mgr, ED, MD | ₦1m+ |
| All sites | CFO payment, always last | ₦0+ |
The parts nobody remembers to ask for
These decide whether a rollout survives its first quarter. All standard, none of them a paid add on.
Nineteen real roles
Office of the MD, CFO, Executive Director, HR, IT and Procurement are first class roles, not checkboxes bolted on afterwards.
Email and push, not just a badge
Approvers are told on their phone, and an overdue stage escalates on its own.
Views are audited too
Most systems log changes. We also record who opened a record, which is the question that actually gets asked.
Works on the phone in the field
Installable as an app, and every screen is built to be approved from a phone.
Break glass, safely
Behind a PIN, rate limited, snapshots any table before a destructive operation, and logs itself.
Migration from what you have
Staff, leave balances, open requests and client records come across during setup. Day one is not a blank system.
Live in weeks, and we do the mapping
A fixed one time engagement. We write down how approvals actually work in your company and configure that, rather than asking you to adopt somebody else's process.
- Week 1. Role and chain mapping with the people who actually sign.
- Week 2. Migration and a parallel run on real requests.
- Week 3. Training by role, then go live with support on the line.
Audit trail
MD access only| 16:55 | Ikenna Obi, MD | Approved |
| 16:54 | Ikenna Obi, MD | Viewed |
| 14:20 | Damilola Ajayi, CFO | Verified quotes |
| 11:02 | Chiamaka Eze, ED | Approved |
| 09:41 | Bayo Fashola, Mgr | Approved |
Bring us your worst process
The one with the exception everybody works around. We will configure it live on the call.