For fit-out & construction contractors

The job does not wait in a queue. Neither does this.

A fit-out project is seven things happening at once — drawings out for comment, materials ordered against a date nobody has written down, a floor being built, variations nobody has agreed to pay for. Software that models it as one sequence of stages is why the real answer still lives in somebody's head.

So Beta does not ask what stage you are at. It answers a harder question: what is waiting on you today, and where is it.

Overview Design Procurement Site Quality Commercial Records
FIT-0114 · Marasi Bay, level 4 · needs you now — 8 outstanding
DesignDWG-302 Small power is past its promised dateDrawings →
ApprovalsSUB-0002 is past its response date with the consultantSubmittals →
ProcurementMAT-0002 is blocked behind SUB-0002, and 2 days past its order-by dateMaterials →
ProcurementMAT-0004 was ordered in good time and still arrives 7 days after it is neededMaterials →
SiteOne working day has no diary entry — this project's site data cannot be trusted until it doesDiary →
Every line is a check a stage already ran, and every one has a way through it. A panel that names something you cannot get to is just a complaint.

Where Beta stands, plainly

Built. Not yet priced, and not yet proven.

Everything on this page is in the app today — you can be walked through all of it on a real project's worth of data, section by section.

What it has not done is carry a live job for a company that is not us. Until it has, it has no price and no launch date, because Alpha earned its price by running a real business for months and Beta will earn its the same way.

What that means for you: a demo is real and available now. A signature is not being asked for, and there is nothing to pay.

7
Sections in a project, in the order the work happens
10
Roles, each editable per company
0
Typed progress percentages, anywhere
0
Money figures a client can see

The project page

Seven sections, in the order the work happens.

Not twenty-three registers down one scroll, all the same size, none of them saying which wants anything from you. The section is in the address bar too — send somebody /site and it opens on the site diary, in their tab, after a refresh, anywhere.

Design

Drawings and submittals

Every drawing issued or waived — and a waiver needs a reason, because the gate stops asking about it afterwards. A submittal cannot go out without a response date: the date is the service level. What the consultant decided is a record nobody can edit, not a status field, so it survives the submittal going round again.

Procurement

Ordered by a date you cannot type

The order-by column is worked backwards from the day the thing is needed, through lead time, production, shipping and buffer. You cannot type into it. To move it you change one of the truths behind it — and every material that is not fine says why in a sentence, not a colour.

Site & Quality

Progress that somebody said

Activities carry recorded progress with a date and a name against it — there is no field to type over. A blocked task cannot be blocked without a reason. A failed inspection demands an NCR in the same action, and the person who fixed a snag cannot be the one who verifies it. Not even an administrator.

Commercial

The number nobody says out loud

Exposure is work already instructed that nobody has agreed to pay for — counted as what it cost, because the margin was never earned. The cost report forecasts from what is committed and spent rather than reporting the spend, and a trade under its allowance is never allowed to subsidise one over it.

Control

You cannot type a percentage.

Progress moves by somebody recording it, with a date and their name on the entry. There is no box to overwrite, on purpose — because "who said 60%, when, and what was it before" is a question asked months later by somebody who was not in the room.

The same principle runs through the rest of it. A blank working day in the site diary is not treated as a good day: a project with no site data is not green, it is unknown, and unknown is a risk that gets its own line. Friday and Saturday are working days here and Sunday is the rest day, so a quiet Sunday is not counted against anybody.

Every register is bounded and every total is true for the person reading it — a subcontractor's figures count only their own packages, and a client's document count excludes what they may not see, because the number alone would otherwise tell them the file exists.

What you actually get

The two screens that change the conversation.

The cost report has four columns and the fourth is the whole point. Joinery looks comfortable on spend alone — and 1,120,600 of a 980,000 allowance is already gone.

It says where the forecast came from, so a QS can argue with it rather than distrust it. The row for money against no budget line has to exist, or the totals quietly stop adding up.

Cost report · 2 of 6 lines over
Budget lineAllowedCommittedForecast
Joinery980,000862,0001,120,600
Ceilings410,000352,400410,000
Flooring295,000240,900295,000
MEP alterations530,000498,000530,000
Not against a budget line31,00031,000

Joinery — heading over budget · forecast from what is committed and spent

And the same project, signed into by your client. Every money figure is gone — not blanked, not zeroed, absent.

No contract value, no variation costs, no exposure, no budget, no invoices. They see the job: what is done, what is waiting, what was decided. It is the screen that makes giving a client a login something you would actually do.

FIT-0114 · signed in as the client
Level 4 fit-out — 3 of 8 stages completeOn programme
Drawings6 issued · 1 late
Snags4 open · 1 verified
Contract valuenot shown
Variationsnot shown
Budget & invoicesnot shown

Then the week, gathered rather than written. You add two paragraphs; everything else is measured — the verdict, the counted facts, the commercial position, and the gaps named rather than left blank.

Issuing it writes a version that can be read back exactly as sent, for ever. The timeline tells the story of the job from the records themselves, so nobody has to remember it.

Weekly report · week 34, issued
Design — every drawing issued or waived
Site — 10 days submitted, 1 working day missing
🔒 Procurement — 2 materials arriving after they are needed
🔒 Commercial — 31,000 instructed and not yet agreed

Everyone on one job

One truth. Not the same truth for everybody.

Inside your company

Ten roles, and you can edit them

  1. The matrix is a default — what a company starts from, not the law
  2. Your edits are yours — only for the roles you actually changed
  3. Two things cannot be ticked away — an admin's own role rights, and money for anyone outside the company
  4. Signing off is not administering — the person who manages accounts is not automatically the one who approves money

Outside it

Subcontractors and the client

  1. A subcontractor sees their packages — and their totals count only those
  2. The client sees the job, never the money — absent, not blanked
  3. Nobody verifies their own work — enforced on the server, not just hidden in the screen
  4. Everything is recorded — who did it, when, and what it was before

Beta · not open yet

See it run on one of your own jobs.

Beta is not open for sign-up. Two things are available now and they are separate: a demo — bring a live project and a floor you are halfway through, forty minutes is enough to see whether it fits — and a place on the list for when it opens.

Running kitchens or joinery as well? Alpha is the same method, finished, and in exactly the same state — ask for that one separately.