Skip to content
QVUNTABUILD BETTER, MANAGE SMARTER

BUILD BETTER, MANAGE SMARTER

One construction system.From first costto final handover.

QVUNTA holds project costing, quotations, contracts, site progress, payments, documents and client visibility on one project record — in the office and on site.

Launching SoonSee how a project runsBeta · WEB · ANDROID · iOS
  • 01Cost
  • 02Quote
  • 03Contract
  • 04Build
  • 05Report
  • 06Payment
  • 07Variation
  • 08Handover
02The problem

A project shouldn’t live in ten different places.

The estimate is in a spreadsheet. The approval is in a chat. The receipt is a photograph of a screen. Six months later the only person who can reconstruct what was agreed is the one who left.

Spreadsheet

Estimate v7 FINAL.xlsx

PDF

Quote — villa 12.pdf

Message

"can you resend the price?"

Photo of paper

Signed contract (scan)

Site photo

IMG_4471.jpg

Nowhere

Variation — verbal

Screenshot

Bank transfer receipt

WhatsApp

Progress week 11

Spreadsheet

Payments tracker.xlsx

Missing

Handover — ?

ONE PROJECT RECORD

Al Waha Residences — Villa 12

  • Cost build-up
  • Issued quotation
  • Signed contract
  • Variation 01
  • Progress reports
  • Payment ledger
  • Handover file

QVUNTA is the version where all of it is already on the project.

NEXT — HOW A PROJECT RUNS

03Project lifecycle

From first estimate to final handover.

Eight stages, one project record. Each one hands its figures to the next instead of starting again in a new file.

  1. 01

    Cost

    Price the work before you promise it.

    Build the internal cost of a project item by item. Zones, trades and line items roll up into a live total cost, client price and margin that only the people you choose can see.

    BOQ

    Internal cost build-up

    Zones → trades → items

    Ground floor55,740.00
    First floor48,560.00
    External works41,700.00
    Total costSAR 146,000.00
    Margin19.84%
  2. 02

    Quote

    Issue a quotation the client can actually read.

    The same priced structure becomes a client quotation or bill of quantities — laid out, branded, totalled and exported as a PDF, without the internal cost columns travelling with it.

    QTN

    Client quotation

    QV-QTN-2026-000118

    Issued
    Subtotal182,140.00
    VAT 15%27,321.00
    TotalSAR 209,461.00

    Internal cost columns are not carried into the client document.

  3. 03

    Contract

    Turn an accepted price into an agreement.

    A contract agreement is generated from the accepted figures and moves through a defined status flow. It carries a reference number, and it can be verified later against what was issued.

    CA

    Contract agreement

    QV-CA-2026-000042

    Signed
    Contract valueSAR 209,461.00
    Retention5%
    Programme180 days
    DRAFTISSUEDSIGNED
  4. 04

    Build

    The site reports in, from the site.

    Assigned workers post progress updates, site photographs, task completions and issue reports from the mobile app. Each one lands against the project it belongs to.

    UPD

    Site update

    Grid C · 08:42

    Posted
    Blockwork to grid CComplete
    Photographs attached4
    Open issues1
  5. 05

    Report

    Progress becomes a document, not a phone call.

    Site evidence is assembled into a formal progress report with its own lifecycle and PDF output — a record of what was done, when, and who recorded it.

    PR

    Progress report 03

    QV-PR-2026-000027

    Issued
    30%

    Assembled from the period’s site updates and evidence.

  6. 06

    Payment

    Money in and money out, on the same ledger.

    Vendor payments and client receipts are recorded against the project, with a payment statement that reconciles what was contracted, what was invoiced and what has actually been received.

    STM

    Payment statement

    QV-STM-2026-000015

    Current
    Contracted209,461.00
    Invoiced to date146,000.00
    Received105,000.00
    OutstandingSAR 104,461.00
  7. 07

    Variation

    Scope changes. The commercial record keeps up.

    A variation order captures the change, prices it, and adjusts the contract value through the same approval path as the original agreement — instead of a text message nobody can find in six months.

    VO

    Variation order 01

    QV-VO-2026-000009

    Approved
    Added — external lighting+18,400.00
    Omitted — soft landscaping−6,900.00
    Previous contract value209,461.00
    Revised contract valueSAR 220,961.00
  8. 08

    Handover

    Finish the project on the record.

    Handover runs as a workflow: scope, acceptance, a no-objection certificate, a signed copy on file, and a closed project that can still be produced as evidence years later.

    HOC

    Handover certificate

    QV-HOC-2026-000004

    Pending
    • Scope schedule
    • Client acceptance
    • No objection certificate
    • Signed copy on file

    Once issued, the certificate is superseded or voided — never edited.

04The workspace

One project. Six ways of looking at it.

The same record, read by whoever needs it — the estimator, the site, the office, the client. Change the lens, not the file.

01 / 06

Cost, price and margin in one place

A project costing panel that holds the internal build-up and the client-facing price side by side, so the margin is a number you manage rather than a number you discover.

  • Zones → trades → items, with live roll-up
  • Total cost, client price, margin and VAT
  • Internal figures stay internal

QVUNTA INTERFACE · ILLUSTRATIVE PROJECT DATA

05Access

One project. The right view for every role.

Five people can work on the same project without all five seeing the same thing. Who sees what is decided by the server on every request, not by which button the app happens to draw.

06The agent layer
IN DEVELOPMENT

Speak it. QVUNTA builds the workflow.

A voice-first layer over a project that is already connected — so running a job stops meaning living inside the dashboard. Different language, same project intelligence.

This is what we are building, not what ships today. QVUNTA has no voice interface. The agent foundation that runs now is read-only, internal, and proposes rather than acts — the ledger below sets out exactly where the line is. Voice is being developed for English, Urdu, Bangla, Hindi, Arabic and Chinese; of those, the interface itself renders three today.

YOU SAYCONCEPT SEQUENCE

Prepare this week's progress report.

VOICE LANGUAGE

The command changes language. The workflow below does not.

  1. 01

    VOICE

    You say it once, walking the job. No app to open, no module to find.

  2. 02

    UNDERSTAND

    The sentence resolves into structured intent — which project, which action, which source, and under whose permissions.

  3. 03

    PLAN

    The intent becomes a route through the project you already have, not a reply in a chat window.

    • PROJECT CONTEXT
    • LATEST SITE DATA
    • PROGRESS WORKFLOW
    • DOCUMENT ENGINE
    • APPROVAL GATE
    • READY FOR REVIEW
  4. 04

    EXECUTE

    The workflow takes the same path the interface would have taken, and the document assembles from real project data.

  5. 05

    CONTROL

    It stops. Drafting is agentic; issuing is not. Anything carrying commercial or legal weight waits for a person.

  6. 06

    COMPLETE

    A numbered draft sitting on the project, ready for you to read when you are somewhere you can read it.

    PROGRESS REPORT

    Progress report 04

    QV-PR-2026-000031 · DRAFT

    READY FOR REVIEW

    Not issued. Awaiting a person.

WHERE THE LINE IS

What runs today, and what does not.

RUNNING TODAY

  • A read-only agent foundation, running in shadow mode on internal builds only.
  • Ten named read capabilities — project summary, costing, tasks, site updates, documents, document state, variation orders, certificates and pending approvals.
  • Every read runs as the signed-in user, so the same server-side rules that govern the app decide what the agent can see. It holds no credential of its own.
  • Questions answered deterministically in English, Arabic and Chinese before any model is called.
  • Where a model plans a multi-step answer, it proposes. It does not execute.

IN DEVELOPMENT

  • Voice input. There is no microphone in QVUNTA today, and none in the current agent build.
  • Drafting a document from a spoken instruction, as the sequence above shows.
  • Turning a proposed plan into a real draft inside the project — still stopping at approval.
  • Availability outside internal builds.

OTHER THINGS YOU WOULD SAY

EACH MAPS TO A REAL CAPABILITY

  • What is waiting for my approval?

    Collects the documents and variations sitting at your gate across your projects, in the order they arrived there.

    READ ONLY · RUNS TODAY IN SHADOW MODE

  • What changed on Darya Prime since yesterday?

    Site updates, tasks and open issues for that project, resolved into one short answer instead of four tabs.

    READ ONLY · RUNS TODAY IN SHADOW MODE

  • Draft this week's progress report.

    Assembles the period’s evidence into a numbered draft on the project — and leaves it as a draft.

    IN DEVELOPMENT · STOPS AT APPROVAL

Hands full. Project moving. QVUNTA stays within reach.

Asking and drafting are meant to work hands-free and eyes-free. Anything that needs reading, approving or issuing waits until you can look at it properly.

07Client visibility

Keep the client informed without giving up project control.

A client who can see the current progress and the documents issued to them stops asking. A client who can see your margin starts negotiating. QVUNTA issues one and withholds the other, by design.

INTERNAL — YOUR TEAM

CLIENT — READ ONLY

Issued, not exposed

The client sees documents that have been issued to them, and the progress on their own project.

Internal stays internal

Cost build-up, margin and vendor payments are not part of the client view at any point.

One version of events

What the client is looking at is the record, not a copy someone remembered to send.

08Documents

Documents that move with the project.

Not attachments someone uploaded. QVUNTA generates the document from the project’s own figures, numbers it, records who issued it, and keeps it where the project can still produce it years later.

QTNIssued

Client quotation

QV-QTN-2026-000118

QVUNTAPAGE 1 / 4
CASigned

Contract agreement

QV-CA-2026-000042

QVUNTAPAGE 1 / 4
VOApproved

Variation order 01

QV-VO-2026-000009

QVUNTAPAGE 1 / 4
PRIssued

Progress report 03

QV-PR-2026-000027

QVUNTAPAGE 1 / 4
HOCPending

Handover certificate

QV-HOC-2026-000004

QVUNTAPAGE 1 / 4

GENERATED BY QVUNTA TODAY

  • BOQBill of quantities
  • QTNClient quotation
  • INVInvoice
  • RFQRequest for quotation
  • POPurchase order
  • GRNGoods received note
  • CAContract agreement
  • VOVariation order
  • PRProgress report
  • STMPayment statement
  • NOCNo objection certificate
  • HOCHandover certificate
ISSUED INEnglishLTRالعربيةRTL中文LTR
09Web and mobile

What happens on site happens in the office.

Web and mobile are not two products with an export between them. They are two ways into the same backend, so an update from a phone is already on the project by the time anyone opens a laptop.

  1. ON SITE

    Phone

    Blockwork complete to grid C

    Update posted

    A worker posts the update and four photographs against the project they are assigned to.

  2. IN THE OFFICE

    Web

    The project record moves

    Timeline updated

    The update, the evidence and the timestamp land on the project timeline where the manager is already working.

  3. IN THE OFFICE

    Web

    Progress report 03 is issued

    Document issued

    The manager assembles the evidence into a formal progress report and issues it as a numbered PDF.

  4. WITH THE CLIENT

    Phone or web

    The client sees it

    Client informed

    The report appears in the client portal — issued, dated, and the same document everyone else is looking at.

04 STEPS · ONE BACKEND · NO RE-ENTRY

10Across markets

Built for projects across borders.

QVUNTA is designed around the way international construction teams actually work — across languages, currencies, roles and regions.

Contract value

‏٢٠٩٬٤٦١ ر.س.‏

SAR · ar-SA

Issued

١٨ مارس ٢٠٢٦

Same day, every market

Quantity

٢٤٨٫٥

248 m² of blockwork

One figure, one date, one quantity — re-rendered by the browser’s own internationalization data, not by a table somebody has to maintain. The separators, the numerals, the currency placement and the date order all change. The project underneath does not.

IN THE PRODUCT TODAY

Interface languages
English, العربية and 简体中文, with Arabic rendered right-to-left throughout the app.
Country-aware setup
A complete ISO 3166-1 country catalog ships in the app. Choosing a country sets the regional defaults and proposes the interface language for that market.
Document currency
SAR, AED, USD and EUR, held per document — so a contract keeps the currency it was written in.
Documents in three languages
A generated PDF carries its own language, so an Arabic contract and its English counterpart come out of the same project.

DESIGNED FOR, NOT YET SHIPPED

More interface languages
Urdu, Bangla and Hindi are already recognised in the country catalog as target languages. Until their translations exist the app deliberately falls back to English rather than showing a half-translated screen.
Voice, in six languages
English, Urdu, Bangla, Hindi, Arabic and Chinese are the priority languages for the agent voice layer — which is itself in development.
A localized marketing site
This site is English-only today. The routing is ready for locale segments; nothing is published until a real translation exists.

INTERFACE TODAY

Englishالعربية简体中文

DOCUMENT CURRENCY TODAY

SARAEDUSDEURheld per document, so a contract keeps the currency it was written in
11Plans

A plan for the way you build.

Three scales of the same system — from a single controlled workflow to several company workspaces under one account.

  1. GET STARTED

    Free

    Start with the essentials.

    FREE

  2. FOR ACTIVE TEAMS

    Business

    Built for active project teams.

    PRICING AT LAUNCH

  3. MULTI-COMPANY

    Enterprise

    For work spread across more than one company.

    PRICING AT LAUNCH

Compare plansBILLING OPENS AT LAUNCH
12Control

Records you can still rely on next year.

Construction disputes are settled by documents. That puts a particular obligation on the software that produced them — to enforce access where it cannot be bypassed, and to leave issued records alone.

How QVUNTA handles your data
  • Permission is decided on the server

    Your role is resolved from live company membership on every request. Access is enforced by the backend, not hidden by the interface — a screen you cannot see is also a record you cannot read.

  • One company cannot reach another

    Companies and projects are isolated from each other at the data layer. Deactivating a member removes their access immediately and drops their project assignments with it.

  • Records that carry weight do not quietly change

    A signed contract, an approved variation, an issued certificate: these are superseded or voided, never silently edited. What you relied on last year is still what it was.

  • Documents are private by construction

    Generated PDFs and signed copies are stored privately and are not reachable by a public link. They are served only through an authorised request, and their integrity is re-checked each time.

  • Every action leaves a trace

    Who did what, when, what changed and any reason given — recorded as an audit trail the owner can read, so an approval can still be accounted for long after the conversation.

  • No analytics SDK. No ad SDK. No tracking.

    QVUNTA carries no analytics, crash-reporting or advertising SDK, and no advertising identifier. We do not collect your location. We do not track you across other apps or websites, and we do not sell personal data.

BUILD BETTER, MANAGE SMARTER

Build with clarity.
Finish with control.

QVUNTA is in beta and open to construction companies who would rather run a project on one record than on ten. Open it in a browser, or tell us what you need it to do.