PYRGO

Your project control tower

From signed contract to final payment: drawings, changes, and money move in one connected flow instead of five separate spreadsheets.

See how it works
Where the margin goes

Three leaks every detailing shop knows

Hours nobody billed

Extra scope gets delivered. The hours never make it onto an invoice.

Approvals stuck in limbo

A transmittal sits with the client for weeks. An RFI goes unanswered.

The truth spread across files

Drawing log, RFI, ECN, and billing each live somewhere else.

None of these losses are visible in the moment. They surface after the job closes, when there's nobody left to argue with.

How it works

One flow, five steps

Contract

Scope, values, and rates recorded once, at the start.

Production

Drawings and work tickets track what was actually done.

Change

RFIs and ECNs capture extra scope as it happens.

Release

Transmittals record what left the office and when.

Money

Contract value, variations, and cash flow follow automatically.

Each step feeds the next — nobody fills in the financial section by hand.

What you see

The actual screens

Not mockups. These are the working product.

Portfolio summary showing every active job in one table
01

Every job at a glance

The portfolio view puts all active projects in one table: contract value, delivered work, what's still open. You stop asking three people for a status before a client call.

Project dashboard with health indicators, alerts, and financial totals
02

One screen per project

Health, alerts, and finances sit together on the project dashboard. What's late and what it's worth are the same conversation, so they live on the same page.

Contract summary comparing original scope, approved variations, and pending variations
03

Original scope, approved, pending

The contract summary keeps all three numbers visible at once. Approved variations raise the contract value the moment they're approved; pending ones stay in plain sight until someone answers.

Work ticket list and the new work ticket form
04

Work is measured in hours

A work ticket is a unit of extra work — beyond the original scope. It records what was done, how long it took, and who prepared it. The list shows hours, not dollars. The amount is calculated on the printed sheet, from the hours and the rate behind them.

Change notice screen showing available work tickets and linked work tickets
05

Money lives on the change notice

Tickets hold the hours; the ECN carries the value to the client. Attach tickets from the ECN side, detach them just as easily. One line decides where the money sits: before the client approves, it's a pending variation — after, it's part of the contract.

Operational alerts listing overdue RFIs, approval delays, and overdue releases
06

The delays find you

Five cards, each watching one thing that tends to slip: unanswered RFIs, tickets sitting with the client past two weeks, approvals not returned, releases overdue. Click a red card to see exactly which records are flagged. Nothing to dismiss — fix the record and the alert clears itself.

Cash flow table showing expected, overdue, and collected amounts
07

Every billable item in one list

Changes billed as ECNs and deliveries of contracted scope, side by side with their payment status. Read-only by design — nothing is typed in here. It's assembled from the billing dates already recorded on each source record, so it can't drift from what actually happened.

Why it's different

Pyrgo is built lightweight on purpose — not one of the big bloated platforms that take months to roll out and cost a fortune. Just the pieces a small shop actually needs, priced for one.

Let's look at one of your real jobs

Happy to send over a short deck and a quick video walkthrough — no call needed, just a look at what it does.

Request a walkthrough