Your engineers know their sites. But the BOQs are in Excel, the progress is in WhatsApp, and the cash position lives in somebody's head. BuildPro puts every project, every naira and every approval in one place — so the firm is as legible as the site.
None of these are dramatic alone. Across four or five active sites, together they're the difference between a healthy margin and a mystery one.
A supervisor requests, a driver delivers, and three weeks later no one remembers who signed off — or at what price.
Every requisition carries a real approver — in-app sign-off, an external approver's evidence, or an honest self-approval. It lands in inventory on delivery.
By the time it reaches the office it's a screenshot of a screenshot — no dates, no photos filed against the task they belong to.
Progress, photos and manpower logged against the actual task and date — visible to the office the moment they're filed.
Spend is tracked receipt by receipt, never against the BOQ — so the real position only surfaces at handover.
Costs post against the BOQ as they happen. A project drifting shows up in week three, not at handover.
One keeps a spreadsheet, one keeps a notebook. There is no firm-wide view until somebody builds one by hand.
Engineers work inside the same structure, so the owner sees cash, progress and risk across all sites without asking for a report.
Pricing a new job means guessing last year's rebar cost, with no record of what was actually paid, where, or when.
The next BOQ suggests unit rates from your own purchase history — matched on unit and size, never mixed. Pricing stops being a guess.
Every problem above multiplies by however many sites and engineers you run. Past a certain size, the answer stops being a better spreadsheet.
Engineer and Team are sized to a site and a small crew. Company is the only tier built for an owner who needs to see everything at once — and prove it later.
Every site lead works inside the firm's account, not a personal login you have to chase. Need more than thirteen? Extra seats are ₦8,000 per engineer per month — no tier change, no renegotiation.
Progress, spend and risk rolled up across every active project on one screen, updating as sites report in.
See which sites are earning their budget and which are quietly eating it — side by side, in the same currency and the same period.
Every requisition, approval and payment attributable to a person and a date — the record a bank, an auditor or a new partner will ask to see.
| Engineer | Team | Company | |
|---|---|---|---|
| Engineers on the account | 1 | Owner + 5 | Owner + 13 |
| Extra engineers | — | — | ₦8,000 / month each |
| Projects | Unlimited | Unlimited | Unlimited |
| BOQ, finance & earned value | ✓ | ✓ | ✓ |
| Requisition audit trail | ✓ | ✓ | ✓ firm-wide |
| Cross-project financial reporting | — | — | ✓ |
| Company-wide analytics | — | — | ✓ |
| Foreman AI messages | 500 / month | 500 / month | Unlimited |
| Best suited to | A solo engineer | One small team | A firm running several sites |
Not a mock-up of an idea. These are the surfaces the Company plan ships with today, with the real numbers and the real refusal messages the software produces.
The owner and the managers they appoint can open any of these and see the requisitions, orders, deliveries, manpower, subcontractors, stock and reports inside — work they never entered themselves. It is strictly read-only, and it never crosses into another company. A site engineer still sees only their own projects.
Rank and permission are separate on purpose — a firm can call someone a Site Manager without handing them authority over money. Everyone can see the line; only the owner can change it, and the server refuses a loop.
| Description | Ord. | Recd. | Var. |
|---|---|---|---|
| Portland cement 50kg | 400 | 420 | +20 |
| Sharp sand | 12 | 12 | OK |
| Reinforcement bar 16mm | 180 | 174 | −6 |
| Binding wire | 25 | 25 | OK |
The quantities above exceed what PO-0002 authorised.
Do not pass for payment until the excess is agreed.
Twenty extra bags is about ₦190,000 nobody authorised. It is invisible until ordered and received sit on the same page — which is the entire job of this document, and why it prints for every delivery.
The site asks for what it needs. Raised on a phone, at the site, with its lines — 200 bags of cement, 10 trips of sand.
Routed to a named manager who approves or rejects with a reason. One person can approve their own — allowed, and recorded as self-approved, no second party reviewed this. Never disguised.
Raised from the approved requisition, and printed for the supplier with the approval named on it.
Recorded against that order, quantities checked against it, stock updated.
“A purchase order must come from an approved material request. Raise the request first, get it approved, then create the PO from it.”
“A delivery must be recorded against a purchase order, so the quantities are checked against what was ordered.”
A genuine emergency still gets through — a site that runs out of cement mid-pour on a Saturday must be able to buy. But the reason is typed, stored against the order and printed on it, so an exception is visible in the record instead of being indistinguishable from authorised work. A chain with no escape hatch just gets worked around outside the system, where you cannot see it at all.
Every account begins with a 14-day trial — no card required. Yearly billing on Company is ₦1.2M, which is two months free.