ORBIX helps UK specialist contractors turn a fragmented tender pack into source-linked scope, clear decisions, a BOQ and a supported, reviewable workbook, with your team in control.
0/6 steps complete
Pumping station upgrade (fictional)
No documents yet. Each file is registered with its type and revision.
1/6 · bring it in
Bring in the pack.
Originals and revisions are kept, never overwritten.
Add the tender pack.
Illustrative demo. Fictional project, documents and prices. Simplified from the ORBIX pilot interface. Nothing is uploaded, stored or sent.
Documents
Bring in the pack. Upload the tender documents. Every original and revision is kept.
Scope
See the scope. ORBIX drafts requirements, gaps and conflicts from the pack, with checks prompted by your Client Brain guidance. Requirements and conflicts link to the document, revision and page.
Make the calls. Your team accepts or changes each finding, or carries it as an assumption, a qualification or an outstanding clarification.
Estimate
Build it. Activities are drafted from the reviewed scope. Your team enters and checks the quantities.
Price it. Prices come from supplier quotations or your estimators, with a reason. A missing price stays visibly missing.
Final review
Sign it off. Review what’s still open and approve it for issue. Costs and margin stay in the internal workbook; check the client price schedule and return documents, then submit it yourself.
A person approves the scope, activities, quantities, pricing and the final output.
The problem
A tender pack is rarely one document. It’s specifications, drawings, schedules, contract particulars and pre-construction information, often in more than one revision. The work you have to price is spread across all of them.
What you must supply and install is split across specifications, drawings, schedules and notes.
One says 50 mm, the other says 25 mm, and both are current.
Testing, attendance, access and health and safety requirements sit deep in the contract documents.
Quotations that leave part of the work out, and the chasing that follows.
The same quantities and notes typed again, with the source lost on the way.
None of this is new. ORBIX is designed to bring more of it into view before you submit.
Why ORBIX
ORBIX is designed to cut down the logging, searching and re-keying in tender preparation, so your team can reach a working scope sooner and spend its time on the pricing decisions.
Step 1: Bring in the pack
Upload the tender pack as it arrives. ORBIX logs every file and each revision you upload against it, keeps the superseded versions, reads the text it can and flags what needs checking. While the scope is still in review, uploading a revision reopens the findings that cited the old version.
Step 2: See the scope
Run the analysis and ORBIX drafts the scope from what it has read: requirements buried in specifications, schedules and readable drawing notes, conflicts between documents, and the gaps and questions to raise. Work that could otherwise go unpriced can be in front of your estimators before they price.
A first draft for your team to review, not approved scope, and a second pair of eyes, not a guarantee. How long it takes depends on the size of the pack and how much of it has to be machine-read; on large packs ORBIX analyses what fits within a set limit and lists the documents it left out or cut short.
Step 3: Make the calls
Findings drawn from the documents link to the document, its revision and the page, sheet, slide or paragraph, with the passage one click away, so your team checks the evidence without searching the pack again. Each finding is accepted, changed or carried as an assumption, a qualification or an outstanding clarification, and each decision is saved with the enquiry.
Step 4: Build it
Once the scope is approved, your estimator can ask ORBIX to propose work packages and tasks from it, each linked to the requirements behind it. Your estimator keeps or excludes each one with a reason, and the draft BOQ is created from the approved activities, ready for your team’s quantities.
Step 5: Price it
Each line keeps its basis, such as a supplier quotation line (applied automatically only where the match is clear-cut), a manual estimate with its reason, or a recorded “awaiting quotation”. A missing price stays visibly missing, and the estimate stays PROVISIONAL while anything is open.
Step 6: Sign it off
ORBIX builds the internal Excel tender workbook from what your team has reviewed, including scope, questions and answers, assumptions, estimate, pricing, evidence and the approval history for each stage, plus a separate client price schedule. A reviewer approves one version for issue; your team completes the client’s forms and submits.
Put your company’s knowledge to work. Add your standards, procedures, checklists and client requirements to Client Brain. Each scope analysis brings in available guidance filed for that client, contract or your whole business, within a set limit, and shows which guidance prompted a check. It starts empty and grows with what your team uploads.
How Client Brain worksIllustrations use the fictional demo project.
Client Brain
Keep reusable standards, procedures and working guidance linked to the right client, contract or business. When you run scope analysis, ORBIX selects available guidance to help identify checks and gaps in the tender pack.
See which guidance prompted a check, alongside the project evidence. Your team decides what to carry into the tender.
See it in the demoClient Brain
Live-site changeover checklist · rev 2
Tender check
Missing information Temporary over-pumping during changeover
Estimator decision
Outstanding clarification Temporary over-pumping during changeover
Fictional example from the demo.
What it does, and doesn’t
ORBIX drafts. People decide. This is where the line sits today.
Who it’s for
For specialist contractors juggling detailed tender packs, tight deadlines and commercial decisions that matter.
Built for estimators, commercial managers and owner-directors.
Hours spent searching tender documents.
Brings documents, scope findings and source references into one connected workflow.
Missing scope or conflicting information makes pricing risky.
Highlights gaps, conflicts and unanswered questions for review before the tender goes out.
Prices and assumptions scattered across spreadsheets and emails.
Keeps the estimate, supporting evidence and recorded decisions together.
Client requirements need checking again on every tender.
Keeps reusable client knowledge organised in Client Brain for relevant enquiries.
Complicated software adds more admin.
Guides the team through Documents, Scope, Estimate and Final review, with clear next actions.
Start with a guided pilot using one of your own tenders.
FAQ
It helps your team build and review the price. ORBIX applies a supplier quotation line only where the match is clear-cut: the same reference, or the same wording apart from case and punctuation. Your estimator settles the rest and enters any manual estimate or allowance with a reason. Matching doesn’t read supplier exclusions; your team checks those. Missing prices stay visible and are never counted as zero, and a reviewer confirms the pricing, which stays PROVISIONAL while anything is outstanding.
Partly. It reads the text in PDF drawings and uses OCR on scanned ones, which it flags for checking. It doesn’t read CAD files, and it doesn’t measure quantities from drawings: your team enters and checks those.
No. Approval saves that version for issue, and downloading a file doesn’t approve or send anything. Costs and margin stay in your internal workbook. A separate client price schedule shows selling amounts, with no costs or margin, in a generic layout: your team transfers it to the client’s own form, checks the required return documents and submits through your normal process. ORBIX doesn’t send anything to your client.
It stays visible. Missing information stays on the scope list, clarification questions can be kept outstanding (ORBIX doesn’t send them), assumptions and qualifications are recorded, and lines without a price stay unpriced. The workbook is marked PROVISIONAL while any of them remain.
It drafts, for example: scope findings such as requirements, gaps, conflicts and assumptions; clarification questions; and a proposed breakdown of activities. Drafts stay labelled as drafts until someone on your team accepts, edits or rejects them. It doesn’t approve anything.
The reusable guidance your business files: standards, procedures, checklists and client requirements, each linked to a client, a contract or the whole business. Reusable documents in a tender pack, such as a client standard, can be filed for that client automatically, marked as not approved policy; only a person makes guidance company-wide or approves it. Guidance can prompt a check or a question, but it can’t establish a requirement, quantity or price on its own. Client Brain doesn’t learn from tender results, actual costs or margins.
Not yet. ORBIX is in a private pilot. The workflow on this page is built, but it’s still being tested on real tender packs, and we don’t claim measured time or cost savings. A pilot is how we’d find out whether it works for your team.
Placeholder · owner to confirm before release
The answer to this question will be supplied by ORBIX before the site goes live. It will cover where tender documents and project data are stored, who can access them, how long they’re kept and how AI providers process them. Until then, this preview makes no claim about data handling.
Private preview · the form below doesn’t send anything yet.
Contact
Tell us about your team and the tendering challenge you want to solve.
Private preview. This form doesn’t send anything yet: nothing is booked, and your details stay on this page.