In a construction business the decisions that make or lose the money on a project are held by a handful of people, and none of it is written down in a form anyone else can use.
One person reads the agreement and knows what the company has actually committed to. One person builds the programme and can tell you which activity is holding the completion date. One person knows that reinforcement steel takes twenty working days to land, so the order has to go out before the slab is even formed.
When those people are busy, the programme is late. When they are on site, procurement waits. When they leave, the method leaves with them.
This is not a cost problem. It is a method ownership problem, and no amount of extra software fixes it, because the software has nowhere to read the method from.
Those three tests are what make a job worth encoding. Six candidates came out of the conversations with Viya. We started with the two that feed each other.
Reading the scope out of a signed agreement and turning it into a dated work schedule.
Turning that schedule and the bill of quantities into what to buy, how much, and by when.
Steel worked out from drawings, currently done by hand with a scale rule.
Quantities and rates for a tender, where the estimator’s reasoning is the asset.
Measured work, retention, deductions and certification, every month, for every subcontractor.
Several quotes with different scopes and exclusions, made comparable on one sheet.
The two we started with are connected. The programme decides when work happens. The purchase schedule cannot exist without those dates. Encoding one without the other leaves the harder half of the problem untouched.
The whole thing is a conversion. Contract language in, planning documents out, with every line traceable back to something that was actually agreed.
| Flow | Starts with | Produces |
|---|---|---|
| Flow one, programme and critical path | The sale agreement and the scope of work it references | An approved work schedule, and the chain of activities that controls the completion date |
| Flow two, material purchase schedule | The approved schedule and the bill of quantities | Material quantities with required-on-site dates, order dates and enquiry dates |
The intent behind both is traceability. Every scheduled activity should trace back to agreed scope. Every purchase should trace back to a quantity in the bill of quantities and to the date the activity that consumes it starts.
Nothing here is new to a planner. That is the point. What is new is that it exists outside one person’s head, in steps a company can run, audit and improve.
There is no standard that converts a sale agreement into a construction programme. Viya’s method draws on published guidance for project management and for work breakdown structures, and on the critical path method for the calculation itself, but the conversion rules in between are the company’s own.
Writing those rules down is most of the work. Until this project they existed as habit. Now they are a document, which means they can be argued with, corrected, and given to software.
Delay an activity with float and nothing moves. Delay one on the critical path and the completion date moves with it, unless time is recovered somewhere else on the same chain.
Owners already know this instinctively. What they usually cannot get is a current answer, on a Tuesday, for a live project, without asking the one person who maintains the programme.
In a real schedule the driving path can carry the lowest or a negative float rather than exactly zero, because of calendars, constraints and imposed completion dates. The software has to handle that case, not the textbook one.
Every purchase date is calculated backwards from the day the material has to be on site. Get the arithmetic wrong once, on one long lead item, and the critical path moves. This is the piece Viya wanted most, and the piece we think travels furthest to other contractors.
The bill gives the measured quantity. What you buy is a different number once wastage, usable stock, client supplied material and delivery packaging are taken into account. Getting that wrong ties up cash or stops the pour.
Illustrative figures from the workflow document, not a live project.
Bleno holds how this company does each job, so what comes back needs a read rather than a rewrite. In construction that means three specific things.
The conversion rules from agreement to scope, the standard activity breakdowns, approved wastage percentages, approved makes, supplier lead times, production rates and the working calendar.
A person opens “build the programme from this agreement” or “produce the purchase schedule for this floor” instead of describing what they want to a chat window.
Routine extraction runs on cheap models, hard reasoning runs on the best one, every call tied to the job and the person who triggered it, inside a monthly limit.
Viya approve a proposed harness rather than authoring one. A construction firm has nobody whose job is populating an AI platform, and pretending otherwise is how these projects stall in month two.
A workflow waits to be opened. An agent watches and speaks first. Both matter, and the second one is what construction is short of.
A person picks a known job and Bleno helps produce the expected output. The programme, the purchase schedule, the schedule of steel. Useful the moment it exists, and it only runs when someone asks.
Data, a date or a threshold starts the work instead of a person. An order date arrives with nothing raised against it. A critical activity slips. Bleno surfaces what now needs a decision, with the evidence attached.
Scoped with Viya against real problems from real projects. None of these are deployed yet. They are here because they are what the two workflows make possible once the data exists in one place.
Nobody is going to let software touch a live programme or a purchase order on trust. Six limits are set before anything is switched on.
It reaches only the systems and records explicitly permitted for its job, and nothing else.
Thresholds, deadlines and exceptions are written down and can be changed by the company.
Every alert goes to a person or a role, with an escalation path if it sits unread.
It shows the records and the reasoning behind what it raised. No unexplained conclusions.
It may observe, recommend, prepare or act only within the authority it has been given.
Anything commercial, contractual or safety related stays approval bound, by default.
Viya is a design partner rather than a customer buying a finished thing. Bleno for construction is being shaped inside their actual week, on projects they are actually running.
| What Viya gives | What Viya gets |
|---|---|
| A workflow the business genuinely depends on, not a sandbox | The product shaped around how their work is really done |
| A named owner with the authority to make calls, an hour a fortnight | Their problems prioritised ahead of speculative roadmap work |
| Frank reactions on the day, not a summary at the quarter | Partner terms that hold for the life of the relationship |
| Permission to write the method down and argue about it | The configuration and standards stay theirs either way |
One thing we already got wrong. The first version of the method treated the bill of quantities as the purchase quantity. It is not, and a contractor spots that in about four seconds. The rules for wastage, usable stock and client supplied material came directly from Viya correcting us.
Every contractor has its own wastage percentages, its own approved suppliers, its own sequence for a slab. None of that copies across, and it should not.
What does copy across is the shape. A signed agreement that has to become a dated programme. A programme that has to become a buying plan. A completion date controlled by a chain of activities that nobody can name on demand. Those are the same jobs in every construction business of this size, done by two or three people who are always busy.
Bleno holds the method, whoever’s method it is.
The work with Viya is what taught us which jobs to start with, and how much of the method has to be written down before software is any use at all.