At Viya Constructions every receipt, client email and day's work value depends on two records: who the client is, and how a site's budget splits between labor and material. Correcting either meant leaving the chat for the platform's own screens. Now a person asks in chat, ProjectSignal previews the change, and nothing is saved until that person confirms. Both workflows are live.
[01]What changedViya Constructions
ProjectSignal holds both records, added in October 2026, and enforces the rules. Two workflows, Client Register and Site budget, are how people reach them from chat.
From the workflows' own rules.
Neither record is usually anyone's main job, and both are easy to get slightly wrong: an old email address, a site linked to the wrong client, a labor budget typed against the wrong total. The damage shows up elsewhere. A receipt email cannot go out, or every day on a site is valued a little high or low.
[02]Why this is hardViya Constructions
Before the register, a customer existed only as free text on a site, an escalation or a sales record. No record said who should get the receipt, so nothing could send it automatically. Receipts and new escalations now take the client from the register.
A home is often bought by a couple, and one client can have several sites. The register carries both. A receipt can only be issued for a site its client is linked to.
A crew of ten on a labor-heavy renovation and on a material-heavy villa do not deliver the same value. Viya values each day's labor by the site's own labor share of its budget, so two budget figures set what every labor-day there is worth.
Count only the civil lines of an estimate and labor is one share of the budget. Add the other trades and the rest of the scope and it is another. In a worked example, not a measured site, the same crew and week came out about a third apart. Budgets compare across sites only when each is loaded on the same basis.
The site reports a little more or less work, every day. Each budget in ProjectSignal carries where it came from, an imported workbook or a typed entry, and who changed it last.
[03]How it worksViya Constructions
There is no document to read in this job. The AI passes on the request, ProjectSignal checks it, fixed logic works out the figures, and the person saves.
Type "/" and pick Client Register or Site budget, or just ask: change a client's email, link a second site, set a labor budget. The assistant passes on only what was said.
Clients are searched by name, place or email, sites by name or code. One match opens. Several are listed for the person to choose, never guessed.
Each step goes to ProjectSignal as a dry run. The platform applies its own permission, duplicate and validation checks and returns the before and after. Nothing is written.
The card lists what will be saved, field by field and link by link. For a budget it works out the labor share and the labor-day value as the amounts are typed.
Edit anything after the preview and Save stays off until the change is reviewed again. Then only the card's Save writes, against the version the person saw: the client first, then each link, then each unlink.
The card comes back once, rebuilt on the latest record, showing what was already saved and a fresh preview of what remains. A second refusal ends the run in the platform's own words.
The result lists each field before and after and each site linked or unlinked, or says that nothing was changed.
What will be saved is the platform's validated before and after, including steps it will skip because nothing would change.
The labor share is the labor budget divided by the total budget. The larger labor's share, the less of the house each labor-day stands for, so raising the labor budget lowers the value of a labor-day.
[04]Connected to ProjectSignalViya Constructions
Writes happen as the signed-in person and land in ProjectSignal's own append-only history.
ProjectSignal owns the rules: who may edit, what counts as a duplicate, whether the figures are valid, whether the record changed since it was read. The workflow has no account of its own that can write. Every read and save goes through the signed-in person's own connection, so someone the platform's screens would refuse is refused here too.
A budget correction cannot change a verdict. Whether a site is on track is worked out in labor-days achieved against labor-days planned, never in rupees. Work value is worked out each time it is read, never stored, so a correction re-values the site's weeks, past ones included, and history stays on one basis.
A site in ProjectSignal is set up in six steps: client on the register, site created, Telegram group linked, project manager and site engineer assigned, total and labor budget entered or imported, project plan created. These two workflows handle the first and the fifth from chat.
Site budgets today are typed or imported from a workbook. Viya Estimator, in build, turns an approved estimate into labor and material budgets per stage. The plan is for the approved estimate to set the site's budget, with its source shown on the card, and for this workflow to stay for corrections.
[05]Who decides whatViya Constructions
Neither workflow lets the AI decide a value or save a change.
[06]More detailViya Constructions
A site with a budget is valued on it. A site without one is labeled as on the company default. The budget shows who changed it last, and an unusual labor share needs a person to say so.
A project manager corrects their own site's budget from chat, inside their own permissions, and sees what it does to a labor-day's value before saving.
A client with no email stops the receipt email and points here. The address is added on a reviewed card, then the receipt is previewed again.
Writes carry the version the person saw, and a stale one is refused. ProjectSignal logs each machine call by tool and outcome, and never stores the arguments.
To start we need your client list as it is today, each live site's total and labor budget with the workbook it came from, one owner per record, and thirty minutes a week.
[07]Where this fitsViya Constructions
Send us both as they are today. We will come back with how they are kept now and what a first reviewed edit would look like. Start with one workflow. You only pay if it works.