TGH Tech
Case study · ProjectSignal for Viya · Live

More than 40 live sites run on one platform. We rebuilt it for Viya in twelve working days.

Viya Constructions builds individual homes in Kerala. Its first operations app was its own, built by its own people and written down nowhere. We rebuilt it as ProjectSignal, built on what Viya's people know about the work: one platform for staff, homeowners, contractors and architects. Live data moved across while sites kept reporting, and code and hosting went into the company's name. Viya's team now extends it, and we review what they build every week.

Client
Viya Constructions
Offering
Platform · ProjectSignal
Industry
Construction and engineering
Built on it since
Self-Build and 19 guided Bleno workflows
Status
Live and in daily use. Estimate-to-budget links in build

[01]Where it standsViya Constructions

Live since June 2026 and still growing. Most staff roles open on its site board.

Figures from the build log and the platform's documentation, as of late October 2026.

  • 40+
    live sites, each with its own chat group and a named project manager
  • Day 7
    of a 12-working-day build when it went live, a day ahead of schedule
  • 17
    optional modules that can be switched on or off
  • 4
    kinds of sign-in: staff, homeowner, contractor or architect, admin
  • 5
    staff access levels, from site engineer to admin
  • 3
    chat bots: labor updates, tickets, purchase requests
  • 09:00
    each morning, every project manager is told which of their turnkey sites have not filed
  • 19
    guided Bleno workflows live on top of it

What is live. The platform is in daily use. Live on it: sales, planning, site execution, purchase requests, quality, tickets, customer escalations, stage billing and post-handover maintenance. Real use is on record for lead intake, daily site updates, planned-against-actual labor, the action tracker, milestone readiness and purchase requests. Homeowners get a portal, set up customer by customer. Payroll runs beside it with its own sign-in. Viya calls the platform Viya Connect.

What is switched on site by site. The public 11:30 labor escalation stays off until an admin switches it on for a site. Rollout began in October 2026. A one-page site report form inside Telegram is in pilot.

What is in build. The links between departments: the estimate becoming a budget per stage, purchase requests checked against it, work orders from the labor budget, and a vendor ledger from the weekly payment sheets. Purchase orders with approval are designed. Viya asked for these on 1 November 2026. None is live.

Who built what.

The first app was Viya's own. We built ProjectSignal: the rebuild, the move with the business running, payroll, the rebar schedule tool, company-owned accounts and the weekly review. Viya's own team keeps building on it.

[02]Where it startedViya Constructions

The business worked. Nobody could vouch for the software under it.

There are two befores: the company before any software, and what we found in June 2026.

Before any software

  1. 01

    The day lived in site chat groups

    Site engineers posted a morning and an evening update in each site's Telegram group. To know which sites had labor today, someone had to read every group.

  2. 02

    Requests scrolled away

    A tag asking for a drawing or a delivery date had no owner and no age. Unhappy customers were handled by phone, with no record.

  3. 03

    Sheets and phone calls

    Leads and stage collections lived in sheets. Leads went unworked and nobody knew who had changed what. Homeowners phoned the project manager to ask how the house was going.

Viya took this on itself. Its first app began in April 2026 as a chat bot that read labor updates. In about ten weeks Viya's own people grew it into a 14-module system used on its sites every day. That app was good, and it still defines how the platform should behave.

What we found in June 2026

  1. 01

    An app nobody had written down

    Every feature had to be studied line by line, because nobody could simply explain how it worked.

  2. 02

    Accounts in people's names

    Systems sat on rented hosting and personal accounts. If the wrong person left, the company could lose access to its own software.

  3. 03

    Payroll in spreadsheets, steel by hand

    Payroll was run in spreadsheets. Bar bending schedules were worked out by hand for each project, with no consistent record.

  4. 04

    Nobody watching the whole

    Problems were fixed one at a time, whenever they surfaced.

[03]How we learned the workViya Constructions

The old app was the only specification. So we learned it from the people who ran it.

There was no document to read. We studied the running system, sat with Viya's team for a full session, and walked every workflow feature by feature.

What came out was a way of running many sites at once that Viya had already worked out: a handful of project managers with five to ten houses each, and leadership that manages by exception. Four ideas carry it. They are Viya's. Our job was to learn them exactly and keep them intact.

  1. 01

    Capture where people already are

    Site engineers keep typing the same update in the same site group. Bots read planned and actual labor, purchase requests, delivery notes and tags from those messages. Nobody fills a second form.

  2. 02

    A named owner for everything

    Every site has a named project manager. Every tag becomes a tracked action for the person tagged. A ticket, escalation, snag or milestone can carry a dated promise by one named person. Never blank, never two people.

  3. 03

    A strict daily clock

    Tomorrow's plan by 18:00 and today's headcount by 09:00, from the first version. A 09:00 summary, an 11:30 escalation and an 18:05 readiness check have since joined the same clock. A silent site is flagged, not assumed fine.

  4. 04

    Status worked out, never typed

    On track, short, delayed, at risk: each is calculated from dates, counts and answers. A status somebody can set by hand will be set by hand, so health is worked out fresh each time someone looks.

Details mattered more than design. The chat bots moved last, because site teams had to be able to post exactly as before. The message readers came across one for one, with what real messages had already taught them. Never take a bare number as a headcount: one had been read out of “2 BHK”, a two-bedroom house. Treat “nil” as a word, not as letters inside a name. When a site writes “2-3 masons”, count three.

Turnkey sites, where Viya executes the work end to end, kept a separate board from PMC sites, where Viya supervises a build the client's own contractors execute. Labor on a turnkey site is the company's own cost, so one mixed board would mislead.

[04]What it showsViya Constructions

Four places where the day shows up. None of them needs a new form from the site.

Each began in Viya's first app and came across in the rebuild. Each has been sharpened since, partly by Viya's own team.

The morning site picture.

Most staff roles land on one board: every live site, worst first, planned labor against the headcount that turned up. The plan is filed the evening before and the fact the next morning, so the gap means something.

  • Five states per site: on track, short, no work, planned off, not filed
  • 09:00: each project manager is told how many turnkey sites have filed, even when all have
  • Fewer came than planned: the bot asks the site group why
  • 11:30, where it is switched on: the project manager is tagged once and commits to a recovery for each short site
Site execution · today
Site APlanned 14 · on site 14On track
Site BPlanned 14 · on site 9Short
Site CPlanned 8 · on site 0No work
Site DNo morning update yetNot filed
Site ENothing planned todayPlanned off
Illustrative. Made-up sites and figures.
The 11:30 escalation
ProjectSignal bot

Short of plan today. 1. Site B: planned 14, came 9. 2. Site C: planned 8, came 0. No update: Site D. Reply with a recovery commitment for each.

Project manager

1. Site B: shuttering gang back tomorrow, two extra masons Thursday, slab date holds. 2. Site C: rain stopped excavation, full crew Wednesday.

Illustrative. The tag a project manager receives, and the reply that goes on record.

The action tracker.

Every tag in a site group becomes an open item against the person tagged. It needs no new habit, because the tag is the request.

  • Overdue after three hours, checked every five minutes
  • A reply or reaction closes it, and the time to close is recorded
  • An FYI tag to the CEO or COO creates no obligation
Action tracker · open asks
Site B · site engineerSend revised staircase drawing. Tagged 3 h 20 min agoOverdue
Site A · purchaseConfirm steel delivery date. Tagged 40 min agoOpen
Site F · planningShare plumbing layout. Answered in 1 h 10 minClosed
Illustrative. Made-up sites, roles and times.

Milestones tied to money.

In home building a milestone is also a payment. Each week leadership plans which stage payments will complete and be billed. Actuals are entered against the plan, and the shortfall is the headline number.

  • Status comes from dates and amounts, never from a dropdown
  • A stage invoice is raised when the milestone completes, and each issued version is locked
  • A paperwork list shows invoices and receipts nobody has raised yet
Milestone collection · this week
Site A · PlinthDone on plan, collected in fullCompleted
Site B · Ground floor slabDone on plan, invoice sent, nothing collectedAwaiting collection
Site C · First floor slabDone six days after the planned dateDelayed
Site D · Roof slabPlanned date passed, not donePending
Site E · PlasteringCollected less than the planned invoicePartial
Illustrative. Made-up sites and stages.

The homeowner's view.

Customers used to phone the project manager for progress. Each homeowner the office sets up now signs in to a portal showing only their own site, from the records staff work on.

  • Planned and actual labor for their house, every day
  • Snags and stage quality checks
  • A ticket channel into the office queue, in place of the phone call
  • The payment schedule shows only where the company has agreed to show it
Homeowner portal · Site A
Today on sitePlanned 12 · on site 11Filed 08:40
QualityGround floor slab stage: all checks completedDone
SnagBathroom door frame out of plumbIn progress
TicketKitchen window size. Raised two days agoOpen
Illustrative. A made-up site and figures.

[05]How it was builtViya Constructions

Twelve working days. Live on day seven. The old system kept running while the data moved.

The sequence and dates from the build log.

  1. 01Days 0 and 1

    Agree the scope, then the shape · by 16 June

    One platform, built to carry Viya's whole business and able to carry more than one company. Viya is its first full user.

  2. 02Days 2 and 3

    Stand it up · 17 and 18 June

    Hosting went up, the screens staff already knew were carried over, and the module switches went live: on for one company, off for another.

  3. 03Day 4

    Move the live data · 19 June

    Viya's real records moved across while the old system kept running, through a read-only path that could not take the live app down.

  4. 04Day 5

    Learn it from the people who ran it · 20 June

    A full session with Viya's team, feature by feature, because nothing was documented.

  5. 05Day 6

    Carry the features across · 22 June

    Almost everything moved. The chat bots came last, because they had to work exactly the way site teams were used to.

  6. 06Day 7

    Switch on · 23 June

    Walked through in person at Viya's office and turned on, a day ahead of schedule.

  7. 07Days 8 to 11

    Make it theirs · 24 to 30 June

    Unused hosting was cleared before anyone was billed for it. Turnkey and PMC execution got their own flows. Storage and database moves were completed, and Viya's team gave the go-ahead.

  8. 08Day 12

    Hand over · 2 July

    In person, at Viya's office, with a recorded walkthrough and a written guide for the wider, non-technical team. The old app was frozen two days later.

Alongside and after: ownership, two modules and a weekly review

Ownership. In July the payroll and rebar tool code moved off personal accounts into Viya's own organization account, and a hosting move onto accounts the business owns began, so access no longer depends on one person. Administration got its own application and sign-in.

Two modules. We built a payroll module and a rebar schedule tool with paid access per project, approval for offline payments, and export to Excel and PDF.

Their team builds. Three to five people at Viya who know construction extend the platform with AI coding tools, and we review what they build every week. That story has its own page.

PartBuilt by
The first app: chat bots, labor board, tickets, purchase capture, quality, sales, milestonesViya's own team, from April 2026
Rebuild as one platform, data move, go-live, handoverTGH Tech, 16 June to 2 July 2026
Payroll module and rebar schedule toolTGH Tech
Code and hosting onto accounts the business ownsTGH Tech, on accounts Viya holds
Additions since handoverViya's own team. TGH Tech reviews what they build every week
Bleno workflows on topTGH Tech, as Bleno's implementation partner

[06]What it made possibleViya Constructions

Sites, people and milestones in one place. Everything since stands on it.

With every site, owner, milestone and daily number in one place, three more things had a record to work from.

  1. 01

    The company's own builders

    Viya's people add to the platform themselves. A weekly review keeps it safe to run the business on.

  2. 02

    Guided workflows

    Bleno workflows do jobs a person used to do by hand. Several read and write ProjectSignal as the signed-in person.

  3. 03

    The estimator

    The budget that purchases and work orders will be checked against comes from the estimate. That link is in build.

  1. Reads

    From ProjectSignal

    • Sites, staff and who runs which site
    • Project plans, milestones and readiness questions
    • Planned and actual labor, site budgets
    • Leads and client contact details
  2. Does

    What a Bleno workflow does in between

    • Reads the document or message a person attaches
    • Works out every total, date and match with fixed logic
    • Shows a preview of exactly what would change
    • Waits for a named person to confirm
  3. Writes

    To ProjectSignal

    • Project plans and milestones
    • Readiness answers with their evidence
    • Planned labor for the week
    • Client records, site budgets, lead updates and receipt emails

Eight of the 19 workflows need the person's own ProjectSignal sign-in. Every write happens as that person, within their permissions. Most of the others produce documents only.

  1. Lead
  2. Estimate and quotation
  3. Agreement and schedule
  4. Milestones in ProjectSignal
  5. Readiness and labor
  6. Purchase and work orders
  7. Billing and collections

[07]More detailViya Constructions

Sales

Sales: every lead gets an owner, a date and a chase.

For the sales head who wants to know which leads were never called.

What it doesThe rule behind it
Leads board, nine lead sourcesThe form changes with the source, so campaign, partner or referrer is captured at entry.
Status updatesThe date is locked to today and saved history cannot be changed. Only an admin, director or COO may backdate, under their own name.
Promises to clientsA date promised in a remark is picked out, confirmed by the sales executive, then tracked to done or carried forward.
Reminders and escalationA silent lead is chased every three hours, 09:00 to 19:00, Monday to Saturday. After three reminders, management is told at 10:00 the next working day.
Pipeline and forecastA hot lead becomes a deal carrying loan status, land status and decision maker. Every time a closure date moves later, the push is counted.
Access and reportsA sales executive sees only their own leads. Daily, Monday and monthly reports are built from recorded updates, and every breakdown sums to its total.
Planning and readiness

Planning: every week has a checklist and a named answer.

The planning week runs Sunday to Saturday. Every live project is under one of two checklists each week, so no site goes quiet between milestones.

What it doesThe rule behind it
Project planOne plan per site. Four responsibilities, each with one named person: project manager, planning engineer, project coordinator, purchase manager.
Milestone readiness26 questions before a milestone's work starts, nine on client readiness. A “no” needs a reason, an action and, where asked, a file.
Weekly execution readinessFor a week with no milestone due: 11 questions on labor and material plus a seven-day work plan. A labor confirmation older than two days is stale.
Work valueLabor is priced in rupees by each site's own labor share of budget. On track is 85% or more of planned labor, judged on labor so a budget edit cannot flip the status.
Weekly milestone promiseBefore the due date, a forecast: on track, at risk, will not make it. On the date, a fact: achieved or not. Each slip is counted, with a reason from a fixed list of seven.
Schedules and documentsA schedule PDF is read into draft phases on request and saved only after a person confirms. Scope, drawing and work order files are versioned, never hard deleted.
Site execution and quality

Sites: one labor number a day, and a signature on every check.

What it doesThe rule behind it
Morning and evening updatesRead from the site group, the in-app site log, or a one-page form inside Telegram. Whichever channel files it, there is one number per site per day.
09:00 summarySent to each project manager for turnkey sites, even when all have filed. A summary that only arrives with bad news cannot be told apart from a failed job.
11:30 escalationSwitched on site by site. One message per project manager, in a group leadership reads. Updates after 11:30 are not escalated that day. A commitment is final once given.
Reporting scoreA site engineer's two daily updates are scored: on time in full, late at half. 80% and above is green, 50% amber.
Stage qualityChecks across 13 build stages shared with planning. The project manager signs a dated statement per completed check. A reopened check gets a new statement and the old one is kept.
The setback gateOne check is marked as the hard gate: setbacks marked and confirmed on site. A house on the wrong setback cannot be fixed above the foundation. Any override shows in the audit log.
Purchase, billing and payroll

Money out and money in: requests, vendors, stage billing and payroll.

Purchase today captures requests and deliveries and shows who is slow. Budget checks and approvals are in build. Purchase orders are designed.

What it doesThe rule behind it
Purchase requestA site group message starting PURCHASE REQUEST becomes a numbered request. The bot replies with the number, so the site has a reference to quote.
Order and deliveryPending order, order sent, in transit, delivered. Part deliveries are accepted. Receipts cannot exceed what was ordered.
Delay and turnaroundOpen 14 days or more counts as delayed. Time is split into procurement days and vendor days. Under 7 vendor days is green, over 10 red.
Vendor registerOne row per vendor, never per crew or per site. A vendor holding more than three sites is flagged. So is live work with no awarded work order.
Stage billingLeadership plans the week, customer relations enters actuals, finance approves each invoice. Over-collection on one milestone never hides a shortfall on another.
PayrollEight attendance codes, statutory deductions, loans and exits. Each component is rounded to the rupee before it is summed, so payslips and payout list agree.
Customers and problems

Customer care: a clock on every complaint, an owner on every blocker.

Problems travel in separate lanes, each with its own clock, so an unhappy customer is never buried under material requests.

LaneThe rule behind it
Customer escalationA priority, a named owner and a call clock: 2, 7 or 12 hours, around the clock. The customer is picked from the client register, never typed. Closure records whether the promise was kept.
Site ticketA numbered blocker routed to execution, scope, material or vendor. Only the person who raised it closes it, with a comment. An admin may close a stale one after 14 days.
CommitmentOne dated promise by one named person. The date is never edited, nobody confirms their own promise, and a new date given after the old one passed counts as broken.
SnagA defect to put right during the build, raised by staff or the homeowner and assigned to a named person. In the outside-contractor workspaces, whoever fixed it never verifies their own fix.
MaintenanceAfter handover the site moves to a maintenance period under one maintenance project manager. Each task carries a commitment date.
Leadership view

Leadership: the exceptions, already sorted.

Leadership manages by exception. Each screen answers one question.

The questionWhere the answer is
Which projects need someone to step in this week?The project list, grouped: blocked, due in three days, waiting for an update, on track.
Is labor delivering to plan, and which project manager is behind?Work value by project manager: planned against achieved each day, against the 85% line.
Where is the cash short?The weekly collection review: planned, actual and shortfall, with sites ranked by shortfall over 13 weeks.
Which unhappy customer has not been called?The escalation queue, sorted: call now, call today, needs an update, on track.
Whose promises can be relied on?Commitments kept per person over the last 90 days, worst first.
Who sees what, and when

Each kind of user sees what the role needs. One clock runs under all of them.

Kind of userSees and does
Site engineerTickets, quality and escalations for assigned sites only; anything else is reported as not found. Files two updates a day, raises purchase requests and tickets, answers tags.
Project managerOwn sites. Owns plans, milestones, quality sign-off and escalation replies.
Planning engineer, project coordinator, purchase managerTheir own readiness questions on every project they serve. The title grants nothing. Rights come from the responsibility held on a project.
Leadership and customer relationsAll sites. Budget amounts show to leadership and the project's own manager, collection amounts to leadership only.
Admin, HR and accountsUsers, sites and customers in an admin app with its own sign-in. Payroll in its own module.
Homeowner, contractor, architectOnly the sites or projects they are given.

Access is checked live, so a change of role applies at once.

TimeWhat happensWho
By 18:00, the evening beforeTomorrow's plan and planned workersSite engineer
By 09:00Morning headcount by tradeSite engineer
09:00“N of M sites filed”, missing sites namedEach project manager
11:30Shortfall escalation, one commitment per siteProject managers
18:00The day's actual labor becomes dueProject manager
18:05Each readiness role is told its open gapsPlanning, coordination, purchase

All times are India Standard Time. 09:00 is a private nudge about reporting. 11:30 is public and about labor.

Who decides what

Fixed rules calculate. People commit. AI reads only where something has to be read.

StepDone by
Reading headcount and tomorrow's plan from a site messageFixed reading rules, tuned on Viya's real messages. No AI in the path that produces the numbers.
On track, short, delayed, at risk, kept, brokenFixed logic, from dates, counts and answers.
Why labor was short, and what to do about itThe site engineer gives the reason. The project manager gives the commitment.
Reading a schedule PDF, or a document in a Bleno workflowThe AI reads, fixed logic calculates, a person confirms.
What it means for you

Is this your company too? And what it would take to start.

  1. For owners

    Every site, before the first call

    Which sites have labor, which milestones slipped and why, which collections are short, worked out from what sites already record.

  2. For operations heads

    Site teams keep their habit

    Engineers keep posting in the site group. Project managers act on a short list, and their commitments are on record.

  3. For accounts

    Billing follows the stage

    An invoice when the milestone completes, locked once issued, and a list of paperwork nobody has raised yet.

  4. For your technical person

    One platform, your accounts

    Each kind of user has its own sign-in. Code and hosting sit in your name.

Signs that this is your problem

  • Someone reads every site chat group to piece the day together
  • A labor shortfall is noticed when the slab date moves, not on the morning it starts
  • The app or sheets the company runs on were never written down
  • Hosting, domains or code sit in a personal account
  • A stage is complete on site and the invoice has not been raised

What we would need from you

  • One full working session with the people who know how the company runs
  • What the business runs on today: the app, the sheets, a real week of site group messages
  • A decision on which company accounts the platform will sit on
  • Thirty minutes a week once it is live

At 09:00 tomorrow, could you say which of your sites has labor on it?

Send us one real example of how your sites report today: a week of site group messages, or the sheet your team trusts least. We will trace how the work runs now and show where a platform like this would start.