The floor vs the screen
If the warehouse is right and the system is wrong, the warehouse wins. The product has to make it easy to correct a posting — with a trail — not to pretend the count was always perfect.
Enterprise ERP & Workflows
Enterprise in this market is not a slide about digital transformation. It is plants, depots, telecom shops, and FMCG routes — groups that run more than one entity, more than one warehouse, and staff who should not all see the same screen. Dangote, BUA, NNPC, Lafarge sit in that shape of industry. MTN and Airtel sit in telecoms. Unilever and Nestlé sit in the brands on the shelf. SAP, Oracle, Salesforce, and Microsoft sit in the office stack; DHL and Maersk sit in how goods move.
Work is procurement, inventory, depot handoffs, field teams, and approvals that used to live in email. A useful system is role-based, dull on purpose, and still running when the night shift starts. If the warehouse count and the screen disagree, operations will go back to Excel before dawn. NITDA, NCC, FIRS, CAC, and NDPC sit on the digital service, the licence, tax, the company, and personal data. They define that environment. They are not clients.
We build that kind of system — or the piece that has to sit next to the one you already have. We do not replace SAP overnight. We do not run your plant. You keep the process, the licences, and the code.
Who this is for
- Operators who have outgrown a shared spreadsheet and a WhatsApp approval chain.
- Teams stuck in front of an ERP that will not move at the speed of a depot or a field crew.
- Groups that need named roles, stock that can be counted, and a handover another vendor can take.
In this sector
Plants, depots, telecoms, and the office stack.
Operations, not a portal
Stock, jobs, handoffs, and the night shift. The screen has to match the floor.
Telecoms and field teams
Shops, agents, tickets, and people who are not at a desk. Roles so a shop manager is not an admin for the country.
FMCG and the route
Orders, returns, and what left the depot. Unilever and Nestlé name the category — they are not a client list.
What already exists
SAP, Oracle, Salesforce, Microsoft in the office; DHL and Maersk in the lane. We integrate or sit beside. We do not pretend to rip them out in a quarter.
Areas covered
We build the software operations actually touch. Typical work includes:
01
Roles and the desk
Named people, named permissions. Finance is not the warehouse. Support can see an order; they cannot post stock. Shared logins are how this class of system dies.
02
Stock, jobs, and approvals
What came in, what left, who signed. Approvals that used to be an email thread become a record you can export. If it cannot be reconstructed, it is not an operation.
03
Sitting next to the ERP
A custom workflow in front of SAP or Oracle, or a tool the ERP will not grow. We map the fields and the failure modes. We do not promise a greenfield core in six weeks.
04
Handover another team can take
Repo, environments, and runbooks: reverse a posting, export the audit log, add a role. You own it. We are not a permanent on-site IT department unless you hire us as one.
What the software has to survive
An operations product is not finished when the happy path works in head office. It has to survive the night shift, a count that does not match, and a manager who will otherwise reopen Excel.
Shared passwords
One login for the depot is not a control. Named users, or the audit trail is fiction. That is a design requirement, not a nice-to-have.
Excel rebound
If a report takes a day to export, someone will keep a parallel sheet. Exports and a close process are part of the build.
Someone else taking over
Vendors change. The next team has to get a repo, not a black box and a phone number in Dubai.
Questions operations will ask
If the product cannot answer these on a night shift, it will be bypassed. We design so it is not.
- 01
Can night shift work without sharing one password?
- 02
If the warehouse count and the system disagree, which record do you trust — and can you show the difference?
- 03
Who approved the last payment or stock issue?
- 04
What still lives in Excel after go-live?
- 05
Can another team take the repository without us?
How we build it
We build dull systems on purpose. Dull is what still runs at 2 a.m.
Roles before screens
Who may post, who may approve, who may only read. Drawn before the first dashboard.
The existing stack
We ask what SAP, Oracle, or the current sheet already does. We do not duplicate a core you cannot leave.
Trail
Who, what, when. Exports finance and audit can take. No silent rewrite of a posted document.
Handover
Runbooks and environments in your name. We are not the system of record after we leave unless you keep us.
- Someone who works the floor or the depot sits in discovery.
- We do not ship a dashboard that cannot post the thing it displays.
- We do not keep production access after handover.
Where we stop
We build the workflow. We do not pretend to be your ERP vendor, your plant, or your auditor.
- We do not implement SAP, Oracle, or Salesforce as a licensed partner unless that is a separate, named engagement.
- We do not claim Dangote, BUA, MTN, Airtel, NNPC, Lafarge, Unilever, or Nestlé as clients. Those names define the sector.
- We do not hold a NITDA, NCC, FIRS, CAC, or NDPC licence. Those agencies define the environment. They are not clients.
- We do not keep the repository or production keys after handover.
The landscape
Agencies that write the rules, then telecoms, industry, the office stack, and the lane goods already move on. This is the market — not a list of Emicraft clients. Dangote, BUA, and NNPC belong in that picture even when we do not host their marks.
Regulators & agencies
Telecoms
Industry & FMCG
Office stack
Logistics
Replacing a sheet, or sitting in front of an ERP?
Bring how work actually moves on the floor — and what must still live in the system you already pay for. We will say what custom software can carry. We do not invent an enterprise case study we have not shipped.