Skip to content
fluidzero

Document intelligence and quality assurance for construction

Software that shows its work.

Construction is decided in documents, proven in records and paid against both. We build software for each, and every answer it gives opens to its source: the page and passage, the inspection and its tests, the bill and the borrowing behind it.

Highway package, two-lane with paved shoulders3 volumes · 612 pages

What bid security is required, and how long must it stay valid?

A bid security of 2% of the bid value, furnished as a bank guarantee. It must remain valid for 45 days beyond the bid validity period, which the instructions to bidders set at 120 days after the submission deadline.

Choose a citation to open its page.

Showing source 1: Vol. 1, page 14, clause 19.1.

Section 1 · Instructions to biddersVol. 1 · p. 14

19Bid security

19.1The bidder shall furnish, as part of its bid, a bid security in the form of a bank guarantee, in the amount of two per cent (2%) of the bid value.box 0.11 0.38 0.89 0.45

19.2Any bid not accompanied by an enforceable and compliant bid security shall be rejected by the Employer as non-responsive.

Source 1Vol. 1 · page 14 · clause 19.1confidence 0.96

Fig. 1One output from each product, traced to what it came from. Choose a product, then a numbered marker.Illustrative — sample tender, road and bill

Working with

  • Group Surya

    Pre-engineered buildings and civil works · Pune, India

    Fennec, in pilot

  • Harsh Constructions

    Civil and road construction · Maharashtra, India

    Chainage, in trial

  • KNT Manufacturing

    Precision CNC manufacturing · Newark, California, United States

01Where construction is decided

Decided in documents. Proven in records. Paid, eventually.

What a contractor commits to is written in the tender. Whether the work is accepted is written in the inspection record. When it is paid depends on a bill’s long walk through a government office. All three are read under pressure, and all three get disputed.

Before you commit · Fennec

A tender pack

Volumes, conditions of contract, specifications and addenda, read against a deadline. The clause that disqualifies a bid or prices a penalty can sit on any page of any volume.

Fennec: tender and project document intelligence

While you build · Chainage

A road under construction

Every 10-metre cell of every layer, on each side of the road, has its own inspection history. A progress chart typed by hand drifts from the register behind it, and a layer laid over unapproved ground is found late.

Chainage: road construction quality assurance

While you wait to be paid · Kosh

A government bill

Certified work walks through certification, invoicing, approval and retention before it is cash. Suppliers, salaries and interest do not wait for it, and the gap is paid for out of the margin.

Kosh: cash visibility for government contracts
02Three products, one discipline

Each answer opens to what it came from.

Fennec, Chainage and Kosh work on their own, at different points in a contract’s life. They share one rule: nothing on the screen is asserted without a source you can open.

01 · Before you commit

Fennec

Tender and project document intelligence

  • Ask a question across a whole tender pack; every claim in the answer is cited to its page and passage
  • Define the fields your bid needs; each value returns with its page, its box on the page and a confidence
  • If a search limit stops it before it has checked everything, the answer says so

In pilot with Group Surya

Highway package, two-lane with paved shoulders3 volumes · 612 pages
Fields extracted from an illustrative tender, each with its source page and confidence
FieldValueConf.
Submission deadline14 Nov, 15:00Vol. 1, p. 30.98
Bid security2% of bid value, bank guaranteeVol. 1, p. 140.96
Bid validity120 daysVol. 1, p. 90.97
Defects liability period24 monthsVol. 2, p. 410.94
Liquidated damages0.05% per day, capped at 10%Vol. 2, p. 380.91
Fig. 2.1A requirements register, extracted. Every value carries the page it came from and a confidence score.Illustrative — sample tender

02 · While you build

Chainage

Road construction quality assurance

  • Raise inspections by chainage range, layer and side, or against a structure and its stage
  • An inspection reaches an approver only when every due test has evidence, and then submits itself
  • The road board is computed from the inspections; nobody types a status

In trial with Harsh Constructions

Illustrative project · 120+000 – 120+480 · 10 m cells

Illustrative Chainage road boardFour pavement layers on each side of a 480 metre stretch. Each cell is coloured by the inspection that controls it. Earthwork is approved furthest along and each layer above trails the one beneath. A stretch of dry lean concrete on the left side is rejected; a granular sub-base stretch on the right was rejected and then cleared by an approved re-test. Use the stretch buttons below the board to read each stretch.L PQCL DLCL GSBL EWR EWR GSBR DLCR PQC120+000120+100120+200120+300120+400120+480
ApprovedAwaiting approvalRejectedNot yet inspectedLeft side above the chainage line, right side below.

LHS · Dry lean concrete

120+120 – 120+160

Rejected · 40 m

The newest inspection of this ground was rejected, so it stays red. Approvals either side never repaint it; only a newer, approved re-test can.

Inspection 1034raised 19 Jul

Rejected

  • Cube compressive strength, 7 day8.6 MPa · limit ≥ 10 MPaFAIL
  • Thickness151 mm · limit 150 mm, −0 / +10PASS
Stretch 7 of 51
Fig. 2.2The road board. Hover or tap the road, or step through the stretches: each one names the inspection that paints it and the tests it was judged on.Illustrative — sample road, derived with Chainage’s status rule

03 · While you wait to be paid

Kosh

Cash visibility for government contracts

  • Every rupee of work done sits in one place: collected, billed and awaiting payment, retention, or unbilled
  • The date the contract says and the date to expect are kept apart, and every estimate is labelled
  • Interest is worked out line by line on money actually borrowed, so the cost of each week of delay is visible

Early access: an open preview on sample data

  1. 01Awaiting certification
  2. 02Eligible for billing
  3. 03Invoice submitted
  4. 04Approved for payment
  5. 05OverdueRA-9 is here
  6. 06Disputed
  7. 07Retention awaiting release
Fig. 2.3Kosh follows each bill through seven stages, from awaiting certification to retention release.Stages as Kosh models them · sample bill

Move a payment date and watch the interest and the margin change on the Kosh page, or open the preview, which runs on a sample company’s books.

03How we build

Cite it, derive it, or don’t say it.

Construction runs on documents that get disputed and records that get audited. So the products are built to be checked, by rules that are enforced in code rather than promised in a brochure.

Read the approach, principle by principle

01Every answer carries its source
A Fennec answer names the blocks it rests on, and each opens to a page, a box on that page and the quoted text. Every Kosh total opens to the bills and obligations behind it.
Fennec · Kosh
02Status is derived, never typed
Chainage computes the colour of each stretch from the inspections covering it, every time the road is drawn. The same rules run in the browser and on the server, so the screen and the API cannot disagree.
Chainage
03Rules are frozen at the time of work
An inspection keeps the acceptance limits it was raised under, and activated configuration cannot be edited. Changing the catalogue tomorrow never re-judges what was approved today.
Chainage
04Records cannot be rewritten
Append-only logs record who changed each record and who opened each inspection. The database refuses a rewrite; it is not left to convention.
Chainage
05Uncertainty is stated, not hidden
Fennec says when a limit stopped its search. Kosh marks every expected date as an estimate. Chainage draws no progress bar for work it cannot measure.
All three
06Where things stand

What is ready, stated plainly.

We would rather you know the edges before a demo than find them after one. This is where each product is today, and what it does not do yet.

Status, access and current limits of each product
ProductStatus todayAccessNot yet
FennecIn pilot with Group SuryaBy invitation, in the browserReads PDFs only, and does not yet transcribe every dimension on a drawing sheet.
ChainageIn trial with Harsh ConstructionsBy invitation, in the browser on phone or desktopLoads only with a connection; inspections raised and decisions taken while it drops wait on the device and send when it returns. API keys read inspections and do not write. Webhooks are built but not yet switched on.
KoshEarly access: an open preview on sample dataPreview open to anyone; early access by requestRuns on sample data. No bank, ERP or tax-portal connections.

We do not hold SOC 2 or ISO 27001 certification today, and we will not show a badge we have not earned. The security page lists the controls in place, and we share architecture and data-flow details on request.

Questions

Frequently asked

What does fluidzero make?

Software for construction and infrastructure companies. Fennec reads tender and project documents and answers questions or extracts fields, citing the page each answer comes from. Chainage runs quality assurance on road and highway works: inspection requests, test evidence, approvals, and a status map of the road derived from them. Kosh, in early access, shows companies paid by government bodies where their money is tied up and what the wait costs.

Do we need all three?

No. Each works on its own. Road contractors often use Fennec on tender packs and Chainage on site. Bid teams and builders usually start with Fennec. Kosh is for finance and leadership teams waiting on government payments.

Is Chainage only for roads?

Chainage is built for linear road and highway works. It addresses inspections by chainage, layer and side, and tracks structures, drains and junctions along the alignment. It is not a general building-project tool.

Who uses fluidzero today?

Group Surya, a pre-engineered building and civil works company in Pune, India, is piloting Fennec. Harsh Constructions, a civil and road contractor in Maharashtra, India, is trialling Chainage. KNT Manufacturing, a precision CNC manufacturer in Newark, California, also works with us. We name them; we do not show their logos, quotes or data.

Are the figures on this site real customer data?

No. Every figure that shows product data is labelled. The tenders, roads, bills and companies in them are illustrative and describe no real customer. The rules they follow are the products' own.

How do we get access?

Book a demo. Accounts for Fennec and Chainage are set up for your organization after we have talked through your work; there is no self-serve sign-up. The Kosh preview is open to anyone, and early access on your own contracts is by request.

How is our data handled?

Fennec and Chainage run on AWS. Access is by invitation through single sign-on, and each organization's data is scoped to that organization. We do not hold SOC 2 or ISO 27001 certification today; the security page lists the controls that are in place.

Next step

Bring a tender pack, or a stretch of road.

In a demo we load your documents or configure a road like yours, and show you the source of every answer. We will tell you plainly what the product does today and what it does not.

Waiting on government payments? Request early access to Kosh.