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.
[01]Where it standsViya Constructions
Figures from the build log and the platform's documentation, as of late October 2026.
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.
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
There are two befores: the company before any software, and what we found in June 2026.
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.
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.
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.
Every feature had to be studied line by line, because nobody could simply explain how it worked.
Systems sat on rented hosting and personal accounts. If the wrong person left, the company could lose access to its own software.
Payroll was run in spreadsheets. Bar bending schedules were worked out by hand for each project, with no consistent record.
Problems were fixed one at a time, whenever they surfaced.
[03]How we learned the workViya Constructions
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.
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.
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.
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.
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
Each began in Viya's first app and came across in the rebuild. Each has been sharpened since, partly by Viya's own team.
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.
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.
1. Site B: shuttering gang back tomorrow, two extra masons Thursday, slab date holds. 2. Site C: rain stopped excavation, full crew Wednesday.
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.
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.
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.
[05]How it was builtViya Constructions
The sequence and dates from the build log.
One platform, built to carry Viya's whole business and able to carry more than one company. Viya is its first full user.
Hosting went up, the screens staff already knew were carried over, and the module switches went live: on for one company, off for another.
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.
A full session with Viya's team, feature by feature, because nothing was documented.
Almost everything moved. The chat bots came last, because they had to work exactly the way site teams were used to.
Walked through in person at Viya's office and turned on, a day ahead of schedule.
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.
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.
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.
[06]What it made possibleViya Constructions
With every site, owner, milestone and daily number in one place, three more things had a record to work from.
Viya's people add to the platform themselves. A weekly review keeps it safe to run the business on.
Bleno workflows do jobs a person used to do by hand. Several read and write ProjectSignal as the signed-in person.
The budget that purchases and work orders will be checked against comes from the estimate. That link is in build.
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.
[07]More detailViya Constructions
For the sales head who wants to know which leads were never called.
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.
Purchase today captures requests and deliveries and shows who is slow. Budget checks and approvals are in build. Purchase orders are designed.
Problems travel in separate lanes, each with its own clock, so an unhappy customer is never buried under material requests.
Leadership manages by exception. Each screen answers one question.
Access is checked live, so a change of role applies at once.
All times are India Standard Time. 09:00 is a private nudge about reporting. 11:30 is public and about labor.
Which sites have labor, which milestones slipped and why, which collections are short, worked out from what sites already record.
Engineers keep posting in the site group. Project managers act on a short list, and their commitments are on record.
An invoice when the milestone completes, locked once issued, and a list of paperwork nobody has raised yet.
Each kind of user has its own sign-in. Code and hosting sit in your name.
[08]Where this fitsViya Constructions
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.