28Modules in production today
19Distinct role permissions
187Screens already shipped
1Permission model across all of it
Why teams switch

Stop approving four million naira in a chat thread

You already have a process. What you lack is a system that enforces it and remembers it.

Routing you configure

Approval chains are settings, not code. Change who signs for what without a developer.

An answer six months later

Every view, decision and override lands in one immutable log.

Live in weeks

Role mapping, migration and training as one fixed engagement.

Nobody has to chase

Email and push the moment a signature is needed, then automatic escalation.

Spend and approvals

Requests route themselves to the right signature

Nobody picks their own approver. The chain resolves from the role, the department, the site, the category and the amount.

  • Thresholds extend the chain. Under the limit a supervisor closes it. Over it, the same request continues to the ED, the CFO, then the MD.
  • Procurement inserts itself. Two vendor quotes per line item before anything moves.
  • Budgets check themselves. Approved spend commits against the site, and a ceiling breach notifies the MD.
A hand signing the approval line of a financial request form
Signature chain
Approved
RaisedAdaeze Nwankwo Submitted
SupervisorBayo Fashola Signed
Executive DirectorChiamaka Eze Signed
CFO, approvalDamilola Ajayi Signed
Managing DirectorIkenna Obi Signed
CFO, paymentDamilola Ajayi Releasing
People

One employee record, from offer letter to exit

Leave, attendance, appraisals, documents and discipline hang off the same person. Nothing is retyped, nothing goes missing.

  • Leave calculates itself. Balances accrue nightly. An approved absence is never counted twice.
  • Appraisals reach a verdict. Self assessment, supervisor score and the MD decision on one form.
  • An accepted offer becomes a record. Hiring flows into the employee file with the grade already set.
A director standing outside her office building
Leave requests
12 pending
12Pending
4Out today
68%Used
Funmi AdebayoAnnual10 With ED
Gbenga SalamiCompassionate3 Approved
Halima YusufMaternity84 Approved
A management team around a boardroom table in a Lagos office
Who runs on it

Built for how a group actually signs things

Several arms, one board, and an approval that changes shape depending on the site, the amount and who is out that week.

Many arms, one chain Property, motors and facilities under one permission model
Rules that differ per site A threshold on one estate need not apply to the next
Signed from a phone Approvers on site sign without opening a laptop
Revenue

Follow a lead all the way to a paid commission

Leads, sales activities, commissions and client portfolios share one pipeline, so you can say what a site earned and what it cost.

  • Duplicates caught on arrival. Leads matched on phone and email before a consultant sees them.
  • A won lead raises its own commission, which then walks its own chain to the CFO.
  • Activity budgets stay honest. No further event spend while a previous report is outstanding.
Lead pipeline
22% win rate
146Open leads
₦318mPipeline
61From events
Sade Martins₦68,000,000 Negotiation
Tari Georgewill₦45,000,000 Qualified
Northgate Ltd₦120,000,000 Proposal
Guided calling

No random calls, and no lead quietly written off

A pipeline is worth what somebody rings. The CRM hands out one lead at a time and will not let a call end without a date on the next step.

  • The queue chooses, not the caller. Promised callbacks first, then today's, then leads never rung.
  • Every outcome sets a date. Only do not call and wrong number end a lead for good.
  • The calls double as market research, including the demand you currently cannot meet.
Today's calling
0 unscheduled
18In queue
7Promised today
4Never called
OutcomeSetsNext
Booked inspectionTask for the lead owner Saturday
Call back laterTask for this caller Thursday, 6:00pm
No answer, 3rd tryNext rung on the ladder Monday, 11:00am
Wants Ikoyi, no stockParked and counted as demand Nurture, 90 days

Encrypted at rest

Third party access tokens are stored with AES-GCM and never leave the server readable.

Views are logged too

The trail records who looked at a record, not only who changed it.

Your data stays yours

Full export on request, and a snapshot before any destructive operation.

Three colleagues looking at the same laptop screen

See it run against your own approval chain

Forty minutes. Bring the messiest process you have, the one everybody works around, and we will configure it live.