FluidBuildAI pre-construction OS

THE FLUID THESIS

A project is connected.
Its planning should be too.

From the first idea to the next decision, FluidBuild brings scope, cost, time, risk, and readiness into a shared planning picture.

Conceptual illustration of a facility transitioning from a digital systems model to a built asset
From project information to a connected view of what you could build. Conceptual illustration.

01 / THINK LIKE A PRECONSTRUCTION TEAM

Start with the project.
Build the reasoning around it.

A hospital, a home, and a data center ask different questions. The discipline is shared: define what is needed, structure the scope, understand the implications, and review the basis before committing.

01

Bring what you know.

Start with an idea, a brief, or available project information. Where document workflows are available, drawings and supporting files add detail.

Location · Capacity · Scope · Constraints
02

Give it a structure.

Organize the brief into spaces, systems, quantities, and work packages that can be priced, sequenced, and reviewed.

Requirements → Scope → Planning model
03

See the implications.

Bring cost, schedule, delivery phases, and risks into the same conversation. Make the assumptions and open questions visible.

Capital · Time · Dependencies · Exposure
04

Review and develop.

Your team checks the scope, challenges assumptions, and adds evidence. The planning picture develops with the information behind it.

Human review · Evidence · Decisions

ONE BRIEF, CONNECTED QUESTIONS

What changes when
the project changes?

Use a shared brief to explore the consequences across disciplines. Each output still needs its own review.

02 / WHY THE WORK MOVES FASTER

Less rebuilding the analysis.
More time to review it.

FluidBuild brings AI-assisted generation and structured preconstruction outputs into one workflow. Speed comes from reducing repeated setup and manual assembly around the work.

CONTEXT

Start from a shared brief.

Capture project requirements in a structured conversation so the team can work from a clearer starting point.

STRUCTURE

Organize the first pass.

Generate an itemized planning picture for review instead of manually assembling every initial table and narrative.

REVIEW

Focus the next conversation.

Use visible assumptions, missing information, and risks to direct attention to the decisions that need judgment.

Processing time depends on the workflow, project complexity, and volume of information. Faster generation creates more room for review; it does not remove that review.

03 / WHAT SUPPORTS CONFIDENCE

A number is more useful
when you can examine its basis.

Confidence comes from the scope, quantities, rates, evidence, and checks behind an output. FluidBuild makes that basis available for the team to question and refine.

Read the estimate from the inside out.Method illustration
Quantity×Unit rate=Line cost
Scope

What is included, excluded, or still undefined?

Basis

Which values come from supplied information, a planning baseline, or an assumption?

Checks

Are the returned values usable, and does the assembled plan make sense for this project?

Review

What needs specialist validation or additional evidence before a decision?

Keep three things separate.

Planning assumptions

A starting basis when information is incomplete. Useful for exploration, and open to challenge.

Documented evidence

Project information that supports the scope or a value. Coverage should remain visible.

Reviewed decisions

Choices accepted by the responsible team after evaluating the information and its limitations.

An early planning estimate and a verified tender or commissioning result serve different purposes. Neither a complete table nor a readiness score replaces professional acceptance.

04 / ONE METHOD, DIFFERENT PROJECT QUESTIONS

Built around what
each asset needs to do.

Select a sector to see how the same preconstruction discipline translates into different requirements.

05 / FROM PROJECT EVIDENCE TO PORTFOLIO LEARNING

Each project can improve
the questions you ask next.

In healthcare, portfolio commissioning and systems evaluation bring recorded outcomes into the next planning conversation.

01 / RECORD

Capture what happened.

System tests, interface issues, defects, handover evidence, and acceptance records.

02 / EVALUATE

Review across facilities.

Compare recurring issues and evidence gaps in the context of each facility’s requirements.

03 / APPLY

Improve the next brief.

Carry reviewed lessons into specifications, procurement scope, and commissioning plans.

A learning process led by reviewed project evidence and accountable teams.
Anibal Piccioni, founder of FluidBuild

THE EXPERIENCE BEHIND THE METHOD

Built by someone
who knows the work.

Anibal Piccioni

Structural Engineer · Founder of FluidBuild and Fantastic Calculator

Anibal brings more than 20 years of experience in construction and preconstruction to the design of FluidBuild. His work spans project scope, feasibility, cost, procurement, and delivery planning.

Through Fantastic Calculator and FluidBuild, he has focused on turning that practical experience into tools that help teams organize complex information and make better-informed decisions.

The idea behind FluidBuild reflects that background: planning works better when the project’s requirements, costs, timing, and risks can be understood together.

START WITH WHAT YOU KNOW

Bring your next project
into the conversation.