Case study
From application to payslip, one record for every employee.
MyCity App is a Nigerian technology company behind a city app. We are building the ERP its own team will run on: recruitment, attendance, performance, payroll, partnerships and spending, with an assistant that answers from the company’s own data.
- Client
- MyCity App
- Country
- Nigeria
- Stage
- In build
What they needed
This system manages the company’s staff, not its cities. MyCity App needed recruitment, onboarding, attendance, performance reviews, discipline, payroll and spending to follow its own rules, in one place.
Its records were kept in spreadsheets. The system was designed around their real columns, so that the company’s data moves across instead of being typed again.
What we built
Seven areas, each built on the same employee record and the same approval engine.
-
Hiring
- Vacancies with a public careers page
- Screening and assessment
- Blind panel scoring
- Offers signed online
-
Onboarding
- Documents collected and checked
- Signatures anyone can verify on a public page
-
Everyday work
- Clock-in and clock-out
- Leave and self-service
- Tasks and calendar
- A staff community
-
Performance
- Goals cascaded from the company to each person
- Self-rating, then manager and second-level approval
- Queries and disciplinary steps
-
Money
- Payroll
- Expense requests, approval and payment
- Budgets against actual spending
-
Partnerships
- Partner pipeline and meetings
- Proposals
-
Knowledge
- Policies, procedures and answers to common questions
- An assistant that reads the company’s data and never changes it
What holds it together
One approval engine behind every request. Leave, expenses, queries and offers follow the chain the company sets, and every decision is recorded.
How it runs day to day
One expense, as the system is designed to handle it
- A staff member asks for money for a purchase, with the reason and the amount.
- The line manager approves or rejects it, then operations does the same.
- Operations groups the approved requests into one requisition for the chief executive.
- The chief executive approves the requisition. A line at or above its category’s threshold needs its own approval, so a large amount never passes on the strength of a small one beside it.
- Approved requests wait as approved but not yet paid. When the money goes out, the bank transaction reference is required before the record can close.
What changes
-
One record per person
From application to payslip, each employee’s history will sit in one place instead of separate spreadsheets.
-
Rules the system keeps
Approval chains, spending thresholds and the working week are settings, not habits, so they apply the same way every time.
-
Answers without risk
The assistant reads and explains. Any change goes through the screen that owns it, under the person’s own permissions.
Our role
-
See
We met MyCity App’s team and settled the open questions with it, one by one, before any plan was written.
-
Design
We wrote the milestone plan: the architecture decisions, the inventory of every screen and a definition of done for each milestone.
-
Build
We are building it in eleven milestones, each demonstrated to the client on a test environment.
-
Hold
The last milestone is handover and training, on a test environment that behaves exactly like the live system.
Related work
-
Smart Logistics and Services
Praxis LS, a logistics and freight ERP: shipment files, warehouse, fleet, people and OHADA accounting in one system.
-
A leading pharmaceutical manufacturer
With Tales Consulting: a platform for the sales force, its managers and leadership, from verified visits to a national forecast.
Start with one area of your organisation.
The free audit and demo takes about an hour. We look at how one area runs today and show you what a system like these would change.