Fit-out runs across four or five companies who don't share a system. The work gets done. The account of the work never exists — until a unit slips, and everyone reconstructs March from WhatsApp in July.
Seven stages — FOL, drawings, approval, execution, audits, SPAD, operational — running across companies that each keep their own version of the truth. When a unit slips, the answer gets assembled days later, and it's settled by whoever remembers most confidently.
The deadline everyone watches is the opening date.
The deadline that governs is RCD.
An intelligence layer for complex fit-outs and expansions — where the thing that costs you is always the thing nobody saw in time. It understands the operation, and tells you what needs you. You keep the calls.
Enter Vigil →The PMC, the contractor and the architect sit in the same chain. They feel the same delays, carry more of the blame, and have nobody building for them. Same chain — pick your seat and see how it reads.
Your progress report is assembled by hand every morning — accurate, and silent. It won't tell you that 144 units have design cleared and haven't started, or that the two units on hold are three times the size of an average one. Vigil generates that report in your own stage names, and adds what a snapshot can't hold: what moved since yesterday, and what's ageing against its date.
Design received against in fit-out. The difference is the largest number on the page and the only one without a bar of its own.
“2 on hold” reads as trivial. Two large-format units can be three times an average unit and a tenth of the leasable area.
A daily report with no delta is a photograph. Nothing in it tells you what changed, or what hasn't changed in eleven days.
Nobody changes how they work. Vigil is configured to the chain and the stage names already in use — rename a stage and the date math follows it.
Vigil doesn't run your tender, price your BOQ, certify a bill or approve a drawing. Those are your decisions, in your systems. Vigil holds what was agreed, notices when what comes back doesn't match, and says so.
Vigil observes, then suggests. A person confirms. Nothing changes status on its own, because in this work a wrong match costs more than no match.
Every operation runs on one rare person who holds it all in their head — the state of everything, the rules, what a delay really costs. It works, right up until they get busy, or leave.
Mail files itself to the right unit. The daily report generates instead of being assembled. Hours come back. Nothing you couldn't have described in advance.
Every approval cycle, every silence, every revision and every slip is retained and comparable. Have we seen this before — yes, here's what it cost last time, and which vendor it was. That part can't be bought late.
B.Arch and M.Arch. Currently reading Project Management (Complex Systems) at the University of Adelaide.
Vigil encodes how the job is actually done — that RCD outranks the opening date, that a landlord's silence functions as approval, that a wrong match costs more than no match. None of that is in a requirements document. It takes years on site to learn, which is why a general-purpose platform hasn't built it.
"You solve site problems over coffee — you invite people in, talk it through, get it done. No fuss."
Someone said that to me once. My mind jumped: coffee beans over concrete beams. He had no idea what I meant. I barely did either — but it stuck, because it's true.
The warmth of a good conversation, and the structure you build from it. I ran these operations for years, drowned in them, and built the first version of this by hand out of desperation. Beans-n-Beams is what I wish I'd had.
Unit list only to begin — no tenant drawings, no lease terms, no correspondence until you choose to connect a mailbox. Nobody on your team changes how they work.
One live property, and the report your team already builds by hand.
How long that report takes today, and how late a slip currently surfaces.
Unit list imported, chain configured to your stage names, report generating daily.
Hours returned per week, and days of warning gained on real slips.
More properties — or stop, and the workspace is deleted.
We'd like to hear from you — send a message and we'll get back to you.