TGH Tech
Case study · Workflow 08 of 20 · Plan the job · Live

Client records and site budgets, corrected from chat. ProjectSignal shows before and after first. A person saves.

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.

Client
Viya Constructions
Department
Accounts and client-facing staff, project managers, leadership
Starts from
A sentence in chat: the client or site, and what should change
Gives you
A before-and-after card, then the saved record
Connected to
ProjectSignal, as the signed-in person
Status
Live. Both live since 15 October 2026.

[01]What changedViya Constructions

Two records sit under every later number. They are now corrected in the chat where the error turns up.

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.

Before

Typed once, trusted from then on.

  • A customer was free text on a site, an escalation or a sales record
  • The same family spelled three ways, emails kept in personal phones
  • One labor share used to value work on every site
  • A fix meant leaving the chat for the platform's screens
Now

Ask in chat. See before and after. Then save.

  • One record per client, linked to that client's sites
  • Duplicates on name and place, or on email, refused at save
  • A site with a budget is valued at its own labor share
  • Every edit from chat previewed by ProjectSignal and saved by a named person
  • 6
    kinds of change, each previewed in ProjectSignal before it can be saved
  • 0
    of them can be saved by the chat assistant on its own
  • 1
    retry after a refusal, rebuilt on the latest record

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

Nobody's main job is the client list or the budget split. Everybody's numbers depend on both.

  1. 01

    The customer was typed, not picked

    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.

  2. 02

    One house, two clients

    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.

  3. 03

    Ten workers are not worth the same everywhere

    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.

  4. 04

    The share depends on what you count

    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.

A wrong budget does not look broken.

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

Ask, find, preview, review, save. The same steps for a client and for a budget.

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.

  1. 01The person

    Say what should change

    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.

  2. 02The workflow

    Find the record

    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.

  3. 03ProjectSignal

    Preview inside ProjectSignal

    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.

  4. 04Fixed logic

    Read the card

    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.

  5. 05Person confirms

    Save

    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.

  6. 06The workflow

    If ProjectSignal refuses

    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.

  7. 07The workflow

    Report

    The result lists each field before and after and each site linked or unlinked, or says that nothing was changed.

The client card shows ProjectSignal's own answer.

What will be saved is the platform's validated before and after, including steps it will skip because nothing would change.

  • A duplicate shows the existing client, with a button to open it
  • Without the right to edit, the card is read-only and says why
Review client changes
Emailold address → new addressChanged
Site BWill be linkedLink
Site FAlready linkedNo change
Duplicate checkNo other client with this name and place, or this emailClear
Illustrative. Made-up client and sites. Nothing is saved yet.

The budget card shows what a labor-day will be worth.

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.

  • A share outside the accepted range turns the button into "Save anyway"
Review the site budget · Site C
Total budget₹75,00,000, unchanged
Labor budget₹21,00,000 → ₹24,00,000Changed
Labor share28.0% → 32.0%In range
One labor-day₹4,000 → ₹3,500
Illustrative. A made-up site and made-up figures, in Indian digit grouping.

[04]Connected to ProjectSignalViya Constructions

ProjectSignal decides. The workflow shows its answer and waits.

  1. Reads

    From ProjectSignal

    • Clients: name, place, email, linked sites
    • Each site's budget, labor share and who changed it last
    • Whether this person may edit
  2. Does

    What happens in between

    • Finds the client or site
    • Runs every step as a dry run
    • Shows before and after
    • Waits for Save
  3. Writes

    To ProjectSignal

    • A new client, with site links
    • A changed name, place or email
    • Site links added or removed
    • A site's total and labor budget, or a cleared one

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.

What reads these recordsWhat it takes from them
Customer payment receiptsThe client must be on the register and the site one of that client's linked sites. A client with no email is sent here first.
Customer escalationsA new escalation is raised against a client picked from the register. Typing a name never creates one.
Weekly labor planEach planned day is valued at its own site's labor-day value, never another site's.
The morning site pictureActual headcount against plan, priced by each site's own labor share.

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.

  1. Signed agreement
  2. Client and budget
  3. Milestone plan
  4. Weekly labor plan
  5. Receipts

Next, in build.

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

The AI reads the request. Fixed logic calculates. A person confirms.

StepDone by
Understanding the requestThe assistant, passing on what was said. It is told never to invent a value
Permission, duplicate, validation and version checksProjectSignal, at the preview and again at the save
Labor share and the value of a labor-dayFixed logic
Accepting a labor share outside the rangeThe person, on the card. No software path confirms it for them
SavingThe person with the right to edit, from a preview that still matches
The closing summaryThe assistant, from the saved result only

Neither workflow lets the AI decide a value or save a change.

[06]More detailViya Constructions

The rules it follows

Every rule, written down.

RuleWhat it does
Preview before saveEvery change runs in ProjectSignal as a dry run first. In open chat the assistant can only preview, to answer a what-if question, and says that nothing was saved. A request to save from there is refused before it reaches ProjectSignal, even if the person says to just do it.
Refusals are reportedNo permission, a failed field, a duplicate, a record changed by someone else, a share outside the range. The assistant never retries with a different version or a forced confirmation.
Changed by someone elseIf the record changed while the card was open, the preview is rebuilt once on the latest version with the intended values kept, and says so.
New clients and linksName, place and email are needed before any preview. The preview shows them as they will be stored: spaces trimmed, email in lower case. At most 20 sites at creation. Archived sites cannot be linked.
Budget figuresWhole rupees, with or without commas. Labor more than zero and less than the total. Material is the total minus labor.
Labor share guardA share outside the accepted range is not blocked outright. The card says to save it only if it is right, still shows before and after, and needs "Save anyway", the only path that sends the confirmation.
No budgetThe site runs on the company default share, labeled as default, and ProjectSignal lists such sites first. Clearing a budget puts a site back there.
Who sees amountsLeadership and the site's project manager, the same people who can change a budget. Everyone else sees the share and the labor-day value.
Never offered from chatDeleting a client, or changing records in bulk. On ProjectSignal's own screens a client named on a live escalation cannot be deleted.
What it means for you

Four readers, four answers.

  1. For owners

    The morning numbers rest on a record with a name on it

    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.

  2. For operations heads

    The person who sees the error can fix it

    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.

  3. For accounts

    Receipts go to the address on the register

    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.

  4. For your technical person

    Dry run, version check, append-only history

    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.

Is this your problem too?

Four signs, and what we need to start.

  • The same customer appears under more than one spelling across your sites, complaints and receipts
  • Client email addresses live in someone's phone
  • Every site is measured with the same labor share, whatever its budget split
  • Nobody can say who last changed a site's budget

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.

Who in your company owns the client list and each site's budget?

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.