Metanotech Logo
Metanotech Logo

Have a project in mind? Let's talk.

Contact Us

The project ends, and only then do you find where it bled

The budget sits in a spreadsheet, purchases happen over chat, progress is noted by the foreman, and billing follows later. Each part is fine on its own, but nowhere can answer how much budget is left today.

Free Consultation

Why this happens

It is almost never a matter of effort. These are the patterns we keep running into.

Budget and actuals live in two places

The cost plan is written once at the start, then purchasing happens elsewhere. Comparing them takes manual work, so the comparison only happens when the project is nearly closed.

Purchases happen with no recorded approval

Material requests go out in chat and get approved verbally. When a discrepancy appears, nobody can show who approved what, at what price.

Billing lags behind progress

A payment stage is invoiced when someone remembers, not when progress meets its condition. Cash arrives late for work finished long ago.

Every project keeps its own format

Different projects are recorded in different file layouts by different people. Comparing performance across projects becomes impossible.

How we fix it

  1. 01

    The budget becomes the project's spine

    The cost plan is entered as work lines. Every purchase and cost attaches to its line, so remaining budget reads at any moment without recalculation.

  2. 02

    Request, approval, and purchase as one chain

    A site material request becomes a document, is approved on that same document, then turns into a purchase order. Who approved it and when is recorded automatically.

  3. 03

    Payment stages follow progress

    When progress meets a stage condition, the invoice document is ready with its figures. Nobody has to remember.

  4. 04

    One shape for every project

    A new project uses the same structure, so margin, delays, and the causes of overruns can be compared across projects.

What it looks like

A picture of the screen you would work in, not an illustration.

What this screen shows

  • Draft
  • Running
  • Handover
  • Closed

Case study

Civil contractor

Situation

Five projects ran at once, each with its own budget file. Overruns only surfaced at handover, and nobody could point to the cause.

What we built

The budget was installed as work lines, site material requests were chained to approvals and purchase orders, and payment stages were tied to progress.

Result

  • Remaining budget per project is visible daily
  • Purchases carry an approval trail you can point at
  • Stages get invoiced when their condition is met
  • Project performance can be compared side by side

Packages

Pick the one closest to your situation. We tighten the scope in the first conversation.

Project Control Package

Remaining budget on every project reads today, not after handover.

Who it is for

Contractors running several projects at once who only learn their margin at the end.

What you get

  • Project budget as work lines
  • Cost entries attached to their line
  • Progress per work item with remaining budget
  • An always current plan versus actual comparison
Free Consultation

Procure to Pay Package

Material requests, approvals, purchasing, and billing become one traceable chain.

Who it is for

Contractors whose purchasing still runs on chat and verbal approval.

What you get

  • Site material requests as documents
  • A recorded multi level approval flow
  • Purchase orders and goods receipt
  • Stage invoicing driven by progress
  • Everything in the Project Control Package
Free Consultation

Questions we get asked

How is this different from an off the shelf ERP?

An off the shelf ERP makes your way of working fit its shape, and in construction that shape rarely matches how stages, retention, and subcontractors work here. What we build follows your flow, with the same tidiness.

Our foremen are not used to apps.

The part used on site is deliberately minimal: record progress and raise a material request, both from a phone in a few taps. The complicated work stays in the office.

What about our existing spreadsheets?

Running projects can be entered as opening balances, so you do not re-enter history from day one. Projects close to completion are usually better left to finish the old way.

Can subcontractors use it too?

Yes, with access limited to their scope. They record progress and raise claims in the same place, so subcontractor payments feed the project cost automatically.

Problems that usually come together

Tell us the situation first

No long form. Send one message describing where you are now and we reply with a sensible next step, not a mass quote.

Free Consultation