Every stage below earns its place on its own. Underneath, they all write to the same building. Here is the whole thread, end to end.
The plot is bought on a broker's word. What it will actually let you build arrives months later, from a consultant, in a PDF.
Upload the land sketch and Korbel walks you through the questions that matter: setbacks, zoning, height limits, the permissible envelope. Where government portals allow it, the regulatory data is pulled in directly instead of keyed by hand. The land papers go into a locked vault with its own door, not a lawyer's drawer.
You know what the plot permits before the architect draws a line.
The architect works in one tool, the structural engineer in another, MEP in a third. Each drawing is right on its own. Together, they disagree, and the disagreement is found on site.
Korbel takes the drawings as they come, from AutoCAD, Revit, ArchiCAD, MicroStation and the rest, and builds them into one federated model. Where the model has gaps, it chases the design team on WhatsApp until they close. Clash detection never sleeps: the obvious conflicts resolve themselves, the hard ones rank for review, and a Korbel BIM manager handles what the system cannot. When the machine and the drawing disagree, a person decides.
There is one version of the building, and everyone is looking at it. Including you. You interact with the design directly, not with a print pile. Where a site warrants it, your field team walks the building in VR before it exists.
The BoQ is generated from the model, element by element. The schedule is built from the physical order of the work, then crew sizes and shift patterns turn the sequence into dates. Vendor rates stay live: suppliers submit and refresh prices on the web and WhatsApp, and the project rate book moves with the market.
Then the part no spreadsheet does. Change one thing in the design, and the cost and schedule consequences land in the team's WhatsApp thread before anyone has to go looking. Name a completion date, and Korbel shows what capacity has to change to hit it, and refuses to lie to you. A lift install that takes three days takes three days, however many crews you throw at it.
Feed it your past projects once, plans, bills, invoices, and it prices the next one with your real regional costs, labour included.
Purchase orders cut directly from the live BoQ, batched by lead time and pour window, sequenced just in time so your cash is on the job, not asleep in a stockyard.
The truck arrives. Challan scanned, load photographed, count taken, and the GRN writes itself against the exact elements the material belongs to. If what turned up is not what was ordered, you find out at the gate, not at month end. Invoices reconcile against GRNs, consumption tracks against the model, and site stock is checked against the next few weeks of schedule. Low stock, over-delivery, off-spec: each one lands in the team's thread as it happens.
The site engineer sends a photo and a voice note from the slab. Korbel parses it, checks it, and marks the element complete. Every pour, every wall, every install, recorded against the thing itself, at the moment it happens.
Every morning, Korbel compares the building you planned with the building you have, and tells you where the two differ. The DPR writes itself from what was actually recorded, not from what someone remembers at 9pm. And when it is time to bill, the running bill drafts itself against completed elements, evidence attached. Built to be signed, not disputed.
Every snag carries a photo, a voice note, an assignee and a status, tied to the element it lives on. The as-built model stays current as the real building diverges from the drawn one. Test certificates, commissioning reports and warranties attach to the elements they certify, so the paper and the thing it proves can never lose each other.
On the day, the handover package is already made: the live model, every document in its place, the snag register, the compliance stack. The facilities team receives a building they can question from day one.
A resident reports a fault on WhatsApp. Korbel finds the asset behind the complaint, pulls its warranty, its installer, its service history, and dispatches the vendor with all of it. Every fault, service and part replacement logs against the asset, so the record only gets richer.
Warranties and AMCs run on timers, with alerts before they lapse, and the documents an association needs for a claim are one question away. When your maintenance window closes, the society inherits a clean, continuous record, not a mystery. And where an asset justifies it, the twin upgrades: BMS integration, then live sensor telemetry.
A prospective buyer walks a flat that is not built yet, or one that is, and sees exactly what they are buying. A pre-booked customer watches their home go up milestone by milestone, drawn live from the same site records your engineers file, so the question "what is happening with my flat" answers itself. And the building you hand them is a smart one, its faults and its systems visible on a living model.
The same rigour that ran the build becomes the thing that sells it.
Somewhere between the two numbers is a fight, and it happens every month, on every package, from a standing start. Nobody measured together. Nobody wrote it down against the thing itself.
On Korbel, a subcontract package is not a paragraph of scope. It is a set of named elements, carved from the model, issued with the current drawing attached. The crew's supervisor musters labour on WhatsApp. Progress claims arrive with the photo attached, against the element it belongs to. Measurement is joint, the RA bill drafts itself, and retention, advances and debit notes run on one account both sides can see. When a back-charge comes, it comes with evidence, not a negotiation.
And the one question every subcontractor asks, when will I be paid, answers itself, straight from your accounting system to their WhatsApp.
We are taking on a handful of builders as early partners, not customers.
Just a couple more details.
Privacy: your name, email and phone number are used once, to arrange this call. Korbel does not share them with anyone and deletes them on request. See our privacy policy, or write to hello@korbel.ai.
{{ calledMsg }}