Like most home builders, Viya Constructions prices each house in an Excel workbook copied from the last similar job. Signal Estimator is the live estimating app built around that work. On top of it we are building Viya Estimator, which turns an approved estimate into the budget that purchase requests, purchase orders and work orders are checked against. The budget step is proven end to end on one real estimate. The checks are designed, not yet built.
[01]Where it standsViya Constructions
As of 5 November 2026, the date of the last build record. Nothing here is a forecast.
On 5 November 2026 one full estimate went from upload to an approved, locked budget that reconciles to the workbook's total to the paisa (a hundredth of a rupee), then to a first revision carrying one named correction.
No quantity, rate or amount in either product comes from an AI model.
[02]Where it startedViya Constructions
Viya's estimator copies the workbook from the nearest earlier job, measures the new drawings into it, updates prices and reads the result off the summary.
Tabs from earlier jobs stay in the file, some still linked, and only the estimator knows which.
Sales needs a clean price, management the margin, purchase the quantities, planning the labor by stage. All open the same file.
A broken reference or a sum over the wrong range still gives a plausible number. Nobody checks hundreds of lines before a client meeting.
It is the most detailed plan the company makes for a building, and nothing in execution reads it. A request for blocks arrives as a chat message with no budget beside it.
[03]How we learned the workViya Constructions
Before building budgets from estimates, we had to know exactly how Viya's estimate is made, and which numbers can be trusted.
Method only. No rate, price or margin from Viya's estimate appears here.
Budgets must come from the lines that feed the price, not the breakdown tabs that look cleanest.
The workbook divides cost by a factor. The software adds a markup. They agree only if the setting is stored precisely, so margin is held to nine decimals.
Checked against cement for the whole house, a site request nearly always passes. The budget keeps quantities per item and per floor.
A labor uplift for upper floors, cubic feet per truckload, wastage on tiles. Each was typed inside a formula. Each becomes a named rate or setting.
[04]What the estimator doesViya Constructions
Signal Estimator answers a builder's three questions in order: how much work, what each unit costs, what to charge. The first version set the price book, the quantity sheet and the outputs. Our October 2026 release rebuilt the drawing reader, added guided steps and made pricing say where a quote is incomplete.
Material prices, labor rates per unit of work, material build-ups and per sq ft labor rates live in one library. A build-up records what one unit of work consumes. The price records what it costs today. Change the price of cement once and every build-up follows.
Every item of work is a line: structure, category, subcategory, scope, element, specification, unit, then count × length × breadth × height. A blank dimension drops out, so counts, running meters, areas and volumes share one sheet. Lines come from typing, a cloned floor, the architect's drawing or the steel calculator.
Steel is often the largest single material cost in an RCC house and the hardest to measure by hand. The calculator builds a bar bending schedule for one member: cover, hooks, bends, laps on 12 m stock bars, wastage and binding wire. The total enters the estimate as one line in kg.
Each quantity line is matched to the rate analysis. Category and unit must match exactly, so a cubic meter of concrete is never priced off a square meter rate. Subcategory, scope and specification pick the closest rate. If nothing fits, the line stays unpriced and says so.
A BOQ (bill of quantities) with margin inside the rates. Cost and margin never appear.
Labor and material by trade, with and without margin.
What to buy, in bags, cft, kg and numbers.
Cost, quote and margin, by trade and by structure.
[05]From estimate to budgetViya Constructions
On 1 November 2026 Viya decided that estimating itself can be done in any tool, and stopped investing in the estimating screens. What it wanted built is the analysis that reads an estimate and derives the budget: Viya Estimator. We are building it on top of the existing estimator. The steps below are built and proven end to end on one real estimate, not yet on a live site.
The workbook is uploaded under a short alias into a project carrying the site code ProjectSignal uses, which ties the budget to the site. The file name is never kept.
Description, quantity, unit, rate, amount. The reader finds the bill, the summary and the rate analysis by what each sheet holds, not its name. A person confirms a new layout once.
Step by step, with the difference shown. Within ₹2 per total it passes. A larger difference is named, never hidden, and must be acknowledged before the import is confirmed.
Margin, overheads and the civil labor allowance are applied as settings, so the app reproduces the estimate's cost and price.
Mapping rules place each line. Leftovers come with up to three suggestions. A person accepts one, picks another or proposes a new item.
On the sample: lines with a zero or missing rate, a quantity × rate that did not equal its amount, a material row labeled as labor. Each flag names the role that may clear it, often the senior QS. Every clear needs a note.
Approval is refused while a blocking flag is open. The first version, R0, is then locked as the estimate budget, and an execution budget is created as the copy the site works to.
[06]How it was builtViya Constructions
Bar bending schedules for 13 kinds of RCC member, exported to Excel and PDF.
Rate analysis, quantity sheet, pricing, budget, material list, with the steel logic carried in. Live from 1 September.
Drawing takeoff rebuilt around what estimators actually receive: native DWG files, sheet sets at mixed scales, quantities written on the drawing.
A written review of the estimator, then a plan tracing each of Viya's 22 request points to a proposal.
Viya chose to build the step from estimate to budget, and named eight workflows it wants first.
One real 37-tab estimate followed cell by cell, written up so the estimation head can check every figure in Excel.
Viya Estimator built on the existing estimator, keeping its price list, rate recipes and margin settings. Each phase stops for a person to check it. Four phases remain.
[07]Connected to ProjectSignalViya Constructions
Viya's own design rule: the estimate work item is the spine linking scope, budget, schedule, work orders, purchases, progress and billing. About 25 requested or planned workflows read the same budget.
Underneath today. ProjectSignal holds three budget figures per site: total, labor and material. Purchase requests typed in a site group become numbered requests tracked to delivery. Bleno produces Malayalam work orders from a photographed quotation. None of these reads a budget per stage yet.
What the build adds, by design. Every budget line gets a fixed id. The estimator holds the budgets. ProjectSignal keeps the requests and orders, and asks for a check when one is raised. Bleno gets read-only budget lookups: each answer cites the site, the budget version and the source, and a site role sees quantities only.
How the write is controlled. Only site totals go to ProjectSignal, in whole rupees, from an approved version. Only an admin or management may send them, after a dry run showing the figures before and after. ProjectSignal's own validation stays the boundary.
The design, not yet built. The push is off by default and every send is logged.
[08]More detailViya Constructions
A management workbook is kept to 500 rows per tab so a Bleno chat can read it from an upload. Ten standard budget questions are ready to test that. The test had not been run as of 5 November 2026.
Built, and proven end to end on one real estimate.
Default roles in Viya Estimator. An admin can change them.
In the Bleno workflows the AI reads, fixed logic calculates and a person confirms. An estimate workbook is structured enough that the reading is fixed logic too.
The estimate stops being a document that is read once and filed. It becomes the budget purchases and work orders are checked against. At Viya the checks are not built yet.
Estimators keep the file they know. The app reproduces it, lists what looks wrong, and waits for you to approve each correction.
Material per stage and labor by type of work. Planning and purchase see rates and costs, never margin. Site roles see quantities only.
Exact decimals, never floating point. Every business number is a setting with history. A real workbook is the acceptance test.
[09]Where this fitsViya Constructions
Send us one real estimate workbook. We will trace it end to end, show you which tabs feed the price, and set out what a budget per stage would look like.