Viya Constructions bills homeowners stage by stage, and ProjectSignal already records those stage payments week by week: planned against actual completion, planned against actual collection, and the week's shortfall. What it does not do yet is age an overdue amount, name the person chasing it or record what was done. That layer is designed and not yet built.
[01]What changesViya Constructions
The first column is live in ProjectSignal. The second is the written design, not yet built.
The first three are live. The fourth is the design. Nothing on this page is a measured result.
A home builder is funded by its customers' stage payments. Working capital, not demand, limits how much it can build, and collections are the cash that pays every contractor and supplier on more than 40 sites. Labor contractors are paid every week, so a stage that is finished and unpaid is work the builder has already funded. When that payment slips two weeks, the builder has lent the customer two weeks of working capital, and nobody decided to.
Of the 131 workflow proposals we scored for Viya in November 2026, this one ranked first: top of the scale for impact, urgency and reach. It answers a requirement Viya wrote into its own plan for the platform. It has no prerequisites: it runs on records Viya already keeps.
[02]Why this is hardViya Constructions
Labor contractors are paid every week while a roof slab is built. The customer's stage payment comes after the stage is done. Every day that payment waits, the builder carries the house.
A weekly shortfall says how much is short, not which customer, for how long, or who is calling them. So it is discussed and waits another week.
Homeowners are usually asked for a stage payment after the stage is done, often by the project manager in the middle of a site conversation. The money then takes days to arrange.
One customer is arranging funds. Another is unhappy with progress and holding payment because of it. Chase both the same way and the second relationship gets worse.
[03]Live todayViya Constructions
This part is live in ProjectSignal, the platform we rebuilt for Viya. It is the record the design reads.
Each calendar week, leadership plans which stage payments will complete and be billed. The plan can be copied forward from the week before. At the week's end, actual completion dates and cash received are entered against it. From those rows ProjectSignal raises the stage invoice, records payments and issues receipts. Both print in a formal layout with the amount in words, and can be shared with the homeowner on WhatsApp.
Nobody marks a stage payment late or short. ProjectSignal works it out from dates and cash, and the first rule that matches wins.
The week's shortfall is the sum of each stage's own shortfall. Extra collected on one stage never cancels what is short on another. Netting hides the stage that is in trouble.
The register also lists paperwork due: an invoice the moment a milestone carries a planned amount, a receipt once money has landed. A planned amount with no invoice is a demand nobody has made yet.
[04]How it worksViya Constructions
This is the design, described as it is meant to run. It reads the register above and needs no new data source.
Every invoice sent or partly collected counts. What is owed is the invoice amount less payments recorded, recalculated daily.
From the invoice's due date, each balance falls into one of four bands, per site and per customer. A part-paid invoice ages on what is still owed.
The site's project manager by default, or the holder of that customer's relationship. ProjectSignal already keeps one holder per customer: never blank, never two people.
Call, visit, statement sent or dispute, with a date. A customer's promise goes into the commitments register that is already live, so kept and broken promises are counted.
A stage with an actual completion date and no invoice after three working days goes on its own list, with invoices approved but not sent. The three-day threshold is a proposal.
An overdue amount with no future-dated next action shows red, to its owner and in the review.
Accounts and directors take the list at 10:00 every Monday: actions past their date first, shown by owner, then the largest and oldest amounts.
[05]Connected to ProjectSignalViya Constructions
Most workflows in this set are Bleno jobs a person starts in chat. This one is a ProjectSignal build, set beside the invoices it describes.
What it reads exists today. The rest is the design.
Writes follow the rules ProjectSignal already has. The owner records the next action in ProjectSignal itself, not in chat. The list needs no approval. Any change to an invoice still goes through the register's own rules: approval, a version check and a kept snapshot once a payment lands.
Bleno cannot read billing data today. The design adds one read-only tool, so the same list can be asked for in chat. Bleno chat answers as the signed-in person and shows nothing that person could not already see in ProjectSignal.
Which product does which part.
[06]Who decides whatViya Constructions
Usually the AI reads, fixed logic calculates, a person confirms. Here there is no document to read, so the AI reads nothing.
[07]More detailViya Constructions
For the accounts head who asks how a status or an age is decided.
Checked in this order. The first match wins. The weekly summary counts delayed, partial and awaiting cash together as deviated.
To start we would need your billing register as it stands, one owner in accounts, and thirty minutes a week to review the list. A spreadsheet is fine. If you keep no register of stage payments yet, that is the first job, and ProjectSignal already does it.
[08]Where this fitsViya Constructions
Send us your billing register as it stands, even a spreadsheet. We will show you how it would age and who would own what. Start with one workflow. You only pay if it works.