Drawing, TOR and spec intake
PDF, Word, Excel or images. Each file is tagged for what it is, so a specification is never mistaken for a drawing.
3 days measuring. 2 days chasing rates. One fixed-price bid.
Draft BOQ in minutes — every quantity traced back to the drawing. Still yours to review.
Sign the contract and the number is final. If a quantity was wrong, the client does not pay for the difference — you do, out of the margin that was supposed to be the job's profit.
3 days gone — before the price is even set.
Counted by hand, on a tender with days left, not weeks.
Whatever time is left over — that's review time.
Supplier calls. Rate checks. Procurement. All week. Review gets the scraps.
It doesn't look like a mistake. It looks like your margin — gone.
Found on site, months later. The number can't be changed.
Sidoku does the sourcing-adjacent work first — matching rates, drafting quantities, flagging what is not yet approved — so review is the first thing a QS's day is spent on, not whatever is left of it.
Not a warning. Just arithmetic — on the number you choose.
A full salary. Every month. Whether the tender lands or not.
$29 a month. No salary, no desk, no leave to plan around.
This is the working prototype, not a picture of one. Pick a region on the plan and Sidoku QS measures it, prices it against the Cambodia rate library, flags what it could not resolve, and builds the supplier request.
Every number here has a reason behind it, shown right under the description — the formula, the source drawing region, and a confidence dot you can hover for how sure the read is.
| Item | Description | Qty | Unit |
|---|
| Item | Description | Qty | Material | Labour | Amount |
|---|
Each step below is a working part of the prototype. Select one to see what the system actually does there — and what it deliberately leaves to the QS.
Upload a CAD-exported PDF drawing, the terms of reference and the specification. Everything stays attached to the job, so the next person does not have to ask where the TOR went.
PDF, Word, Excel or images. Each file is tagged for what it is, so a specification is never mistaken for a drawing.
Files stay searchable against the project, the supplier and the rate they support — not scattered across a chat thread.
Identify construction items, dimensions, units and assumptions, each carrying the drawing reference it came from. Where the sheet does not answer a question, the item says so instead of guessing.
Convert selected drawing pages and specifications into structured construction items with quantities, units, and source references.
Show formulas, dimensions, measurement method, deductions, wastage, assumptions, and drawing references alongside each quantity.
Nothing is approved by the system. A qualified QS accepts, adjusts, rejects or comments on every extracted line, and the trail of who changed what is kept.
Edit quantities, approve items, flag assumptions, add comments, and maintain a transparent review status for every line.
Surface low-confidence items first so QS attention is focused where ambiguity and commercial risk are highest.
Split material, labour and plant against the Cambodia rate library, set margin and add VAT. A rate only prices work automatically if it is both approved and still in date.
Connect quantities to supplier quotations, labour history, rate build-ups, invoices, and approved project rates.
Compare supplier quotes side by side for the same scope. Missing items and unit mismatches are flagged; the recommended pick is a fixed lowest-valid-price rule, not an AI opinion.
Send a priced draft to the tender file and a structured request to your suppliers. Every export carries the draft stamp and the QS review caveat, so nobody mistakes it for a signed-off bill.
Export a reviewable draft BOQ to CSV, Excel, Word or print without manually rebuilding the first draft.
Turn reviewed lines into a request suppliers can price directly, so their reply comes back in a shape you can compare.
A takeoff that never becomes a signed job is unpaid work. The same record now starts earlier — at the inquiry — and carries on through the job, the costs and the invoice, so the number a client accepts is the one the drawings produced.
Enquiries arrive by Telegram, by referral, by a phone call from a developer you met once. The pipeline holds the stage, the value and the date you said you would call back — and turns that date red when it passes.
When it is time to price, the estimate takes its total from the project's draft BOQ. The number the client sees and the number the drawings produced are the same.
So what: a $186,500 job doesn't die because a follow-up date got forgotten.
Once the bid is won the work moves to site, where it stops being a bill of quantities and becomes a list of things somebody has to do this week. Tasks sit against the job they belong to, carry a name and a date, and say plainly when they are blocked on someone else.
Milestones group that work and show how much of it is finished — not a percentage somebody typed in, but a count of the tasks underneath.
So what: a blocked task shows up as blocked — not as silence until the site visit.
Most contractors find out what a job made when the last invoice is filed, which is far too late to do anything about it. The budget here is the estimate the client accepted — not a second figure typed somewhere else — and every cost booked against the job moves the margin in front of you.
Only approved costs count against that margin. Anything still awaiting approval is shown beside it, so a job cannot look healthy simply because nobody has signed off the supplier invoices yet.
So what: you find a job is losing money at week two of five, not on the final invoice.
A valuation goes out, the client is slow, and nobody notices until the month closes. Invoices carry a due date, payments are recorded against the invoice they settle, and anything past its date is called overdue rather than left to blend in.
Part payments are normal on a Cambodian job, so an invoice can be part paid and still show exactly what is left on it. A payment larger than the balance outstanding is refused, because it is a typing mistake every time.
So what: $5,520 sitting overdue shows up on your dashboard, not just in your head.
Three of these are enforced in the database, not the interface — which is why they still hold when someone goes around the screen. The other two are what it always shows you, whether the number is comfortable or not.
Every line the analysis writes lands as Needs review — in demo mode and with a real model. There is no path in that function that can write Approved.
Validity is checked in the same breath as approval, so a rate that lapsed in March is never quietly treated as current.
Every line carries its confidence. The ones a QS must argue with surface before the ones already settled.
The approval rule is restrictive — it AND-combines with every other permission. You can edit all day and still not stamp it.
A quantity links to the formula that produced it and the drawing region it was measured from — the part a client, an auditor, or a QS will actually ask about.
Not a claim — two facts about who built it, and the real Cambodian contractors this was built for.
Sidoku QS is built inside Tepy Build Co., Ltd. by a team with 16+ years in Cambodian construction — measuring drawings, chasing suppliers, and signing tenders that could not be undone. The QS week described above is not hypothetical. It was Tepy Build's own week, for years, before this was built to change it.
Before the client portal shipped, it was tested by signing in as a real client account and trying to see what a client could reach. That found two real holes a policy review alone had missed — a client could have promoted themselves to a staff account, and any signed-in account could have written into the sales pipeline. Both were closed the same day, then re-tested by attacking it again, not by assuming the fix worked.
Tepy Build Co., Ltd.
School and NGO-funded projects.
ASIA ME&P
Infrastructure and soil backfilling.
Zero Architecture and Construction
Steel work.
These are demonstration plans for the Sidoku QS product direction. Actual pricing can be validated with Cambodian contractors and QS teams.
Two ways in. Start a live estimate on the Tepy Build demonstration drawing and watch the draft BOQ build line by line against the Cambodia rate library — or take the finished sample report first and see exactly what comes out the other end before you upload anything of your own.
The demonstration project loads a CAD-exported structural plan, S-101, already indexed and ready to measure.
Select regions of the plan. Quantities are measured, priced against the Cambodia rate library, and flagged where the drawing is ambiguous.
Export a draft BOQ to CSV, or open a printable report you can save as a PDF and attach to the tender file.
| Item | Description | Qty | Unit | Material | Labour | Amount | Confidence |
|---|
Not supported yet: scanned drawings, photographs of printed drawings, and native DWG measurement. Rates are drawn from the Cambodia rate library and must be confirmed against current supplier quotations before any bid is issued.
Tell us what you are building and how to reach you. A quantity surveyor reads every request — nothing here is answered by a machine.
Test the workflow on one real Cambodian project and measure the difference between manual takeoff and AI-assisted preparation.
Start with a drawing →Upload a CAD-exported PDF. This prototype indexes the sheet, then opens the workspace where you select regions to measure. Scans and photographs are not supported yet.