Introduction — How Darwin Thinks

Your company already knows how to price this. Every project teaches the next one. That’s why it’s called Darwin.

Construction estimation has always relied on experience, judgment, and information scattered across tools that were never designed to communicate with each other. Drawings come from one system, quantities from another, price lists from inboxes, and the final budget must reconcile all of it manually.

The real problem is lost knowledge. Construction companies price the same work again and again — the same concrete, the same walls, the same crews — but that knowledge lives in copied spreadsheets and in a few people’s heads.

Darwin keeps that knowledge inside the company. Capture cost logic as reusable modules and maintain prices separately. Review and formally approve the estimate to establish the baseline for actual costs. Your team reviews any differences and decides which improvements belong in the catalog.

Instead of treating estimation as isolated tasks, Darwin treats it as a repeatable, data-driven workflow.

Darwin is a cost knowledge system designed to preserve, structure, and evolve an organization’s Cost DNA — built around estimating, but reaching well past it.

Darwin’s main workflow is:

request → clarify → estimate → review → approve → track → learn

A request for work becomes an estimate your team reviews. Approval records the baseline for Cost Control. Actual costs and variance give the team evidence to improve future estimates.

As the manifesto states:

Construction does not lack expertise. It lacks durable memory.

To understand how Darwin works, learn the workflow first, then the core principles behind it.

The Request-to-Baseline Workflow

Darwin reflects how construction work usually begins: not as a perfect project record, but as a request, question, scope package, missing drawing, price concern, or change that needs clarification.

The workflow gives that work a clear path:

Request — someone asks for work to be estimated, reviewed, changed, or approved.
Clarify — the team adds drawings, files, comments, quantities, assumptions, and missing context.
Estimate — the estimator turns the request into structured cost logic.
Review — pricing, quantities, assumptions, and recommendations are challenged.
Approve — the estimate becomes the committed baseline.
Track — actual costs and invoices are recorded against the approved baseline.
Learn — variance explains what changed and improves future estimating practice.

This is why Darwin should not be learned as a set of disconnected features. The value comes from how the workflow preserves context from the first request through execution feedback.

1. Projects Are the Center of Gravity

A Project holds the estimating and cost-control record. Your reusable catalog, work requests, and private Quantos drafts can exist before that project does.

A project contains:

work requests and clarification history
IFC models and 2D drawings
estimations and revisions
modules and price lists
documents and correspondence
approvals, activity history, and tasks
approved baselines and cost-control context

By bringing all of this into a single container, Darwin turns a project into a living record of how an estimate was produced.
Keep the files and decisions that explain an estimate with its project, so another person can find and review them later.

A project is the foundation for reliable cost intelligence.

2. Modules Capture Construction Knowledge Once

Instead of writing line items from scratch every time, Darwin uses Modules — reusable building blocks that represent how something is constructed.

A module may include:

materials and quantities
labor and production rates
expenses and overheads
documentation
classification (UniFormat, MasterFormat, IFC context)

Once reviewed, a module captures part of your company’s Cost DNA. You still decide its scope, quantities, and assumptions.

Reusing a reviewed recipe lets you:

start from an existing resource list
check shared assumptions
explain the work to another estimator
correct the recipe when evidence warrants it

Modules transform estimating from reinventing to applying knowledge.

3. Prices Change — Logic Shouldn’t

Markets move. Material costs fluctuate. Labor rates shift.
But the underlying construction logic stays the same.

Darwin separates these two worlds:

Modules store construction logic
Price Lists store economic conditions

This separation allows you to:

explicitly recalculate an editable estimate with reviewed prices
compare estimates across time or regions
maintain consistency across teams

Updating a price list does not silently change an existing estimate. Explicit recalculation can also pick up reviewed recipe changes; inspect the result before treating a difference as price-only.

Most companies already feel this problem in a spreadsheet: the logic and the price sit in the same cell, so updating one risks breaking the other. We love Excel. We just stopped asking it to be our memory.

4. Use BIM and Drawings When They Help

Darwin integrates with IFC models and 2D drawings (PDF, JPG) to accelerate quantity takeoff and connect design with cost.

Importing a model or drawing allows you to:

extract quantities
group and classify elements
map objects to modules
visualize elements in 3D or annotate 2D drawings

But Darwin uses these inputs with a practical mindset:

the model or drawing provides geometry and metadata
Darwin provides the cost structure and traceability

The estimator’s judgment remains central.
You can also build an estimate entirely with manual quantities. BIM and drawings are optional inputs.

Why This Matters

By organizing requests, estimating information, projects, modules, price lists, and imported data (IFC or 2D), Darwin creates a workflow where estimation becomes:

reproducible — run the same logic and get the same results
traceable — every decision has context and history
collaborative — tasks, reviews, and documents live together
adaptable — update prices or design inputs without rebuilding the estimate

Darwin also extends this logic beyond estimating alone.

The same structure supports:

budget vs actual tracking
invoice variance review
system and subsystem cost control
operational cost intelligence after the estimate is issued

Darwin brings structure and intelligence to construction cost decision-making, from estimate creation through cost control.

Start With the Work You Price Most

You do not need to move thirty years of spreadsheets at once. Start with ten or fifteen assemblies your team prices regularly. Capture your first module by hand, or review and correct a draft from Module Copilot when it is available. You decide what enters the catalog.

Supplier prices can come from the Excel sheets you already use. Existing estimate spreadsheets are not automatically converted into modules. Add reviewed knowledge as you work, and use project feedback to improve it.

Every project teaches the next one. That’s why it’s called Darwin.