BulletDraw

Engines

Each one sold on its own.

Six engines.One circuit.

Takeoff measures it, Budget prices it, Scheduling plans it, Procurement buys it, Compliance clears the people and the Draw Engine moves the money — each one handing its work to the next.

Book a demo →Talk to sales
Engines, in job order
6
Engines, in job order
Live today
4
Live today
Login across them all
1
Login across them all
Figures re-keyed
0
Figures re-keyed

Live · Harbor Point, Phase 2

Scheduling Engine

Framing 4 days ahead

Roof trusses now needed Tuesday

Hands to Procurement →

TakeoffComing soon
BudgetComing soon
SchedulingFraming 4 days ahead
ProcurementOrder early, never late
ComplianceNobody moves until they clear
DrawAutomate, get funded
In design · coming soonMeasureVerifyLock

Takeoff Engine. Measure once, own the quantity.

Quantities measured off the drawings you already have, held in one register, and locked once a second person has checked them — so the count stops moving and only the price can.

What it will run

  • Quantity registerEvery measurement in one place
  • Verify and lockA checked quantity stops moving
  • Takeoff driversCounts that feed the estimate
  • Honest allowancesWhat is measured, and what is assumed
  • Off your own drawingsNo new set to produce
  • One seam into BudgetQuantities travel, money stays behind

In detail

01.01

Quantity register

One row per measured item: the quantity, its unit, the sheet it came from, and whether it is measured, verified or an allowance.

Source sheet on every row

01.02

Verify and lock

A second person verifies; the quantity locks. From then on the Budget Engine may choose the rate for it, never the count.

Locked once verified

01.03

Takeoff drivers

The quantity a cost package scales on — measured here instead of typed, so the estimate grows from real counts.

Counts that feed the estimate

01.04

Allowances kept honest

An allowance is not a measurement and is never shown as one. It stays an allowance until a real quantity replaces it.

Allowance ≠ quantity

01.05

Drawings you already have

The drawings register is live today — versioned, shared by link, acknowledged. Takeoff measures against the current revision.

Versioned plan sheets

01.06

One seam to Budget

A single link from the estimate line to the quantity. Budget never builds measurement screens; Takeoff never holds money.

Quantity owned once

Built to rules already decided

The seam

Takeoff owns quantities, Budget owns money

Two engines, one seam. No measurement in the Budget Engine, no prices in the Takeoff Engine.

Protected vs adjustable

A verified quantity is locked

A spec tier, a target or a template may pick a rate against it. None of them may change it.

Hand-typed lines survive

Null is not an error

A hand-typed line with no measured quantity behind it keeps working. Takeoff adds certainty; it never becomes a prerequisite.

Set null, never cascade

Retiring a sheet never deletes money

When a drawing is superseded, the link to its quantity is cleared, never cascaded. A budget cannot lose a line to a new revision.

Where it connects

To Budget →Verified quantities the estimate pricesTo Scheduling →Quantities that size the work
In design · coming soonEstimatePricePublish

Budget Engine. Price it with evidence.

A pre-construction workspace that prices every line from evidence — quotes, awards, supplier prices, actuals — then publishes the budget the rest of the platform already runs on.

What it will run

  • Pricing MasterA rate with the evidence behind it
  • Four-factor trustSource, freshness, market, scope
  • Your market's ratesNormalized, never guessed
  • Cost packages by tierStandard through custom
  • AssembliesPrice the thing, not the line
  • PublishThe budget the rest of it runs on

In detail

02.01

Pricing Master

Every activity priced low, recommended and high from an evidence graph — quotes, awards, supplier prices, actuals, rate cards — never one opaque number.

Low · recommended · high

02.02

Four-factor trust

Source, freshness, market and scope, drawn as bars. The most trusted observation takes the price; ties go to the more recent. Never an average.

The winner takes it

02.03

Geographic normalization

A rate from another market is normalized by index, not discounted. A market with no index is never scaled — it is trusted less instead.

Indexed by market

02.04

Cost packages by tier

Packages across spec tiers — Standard, Premium, Luxury, Custom — and project profiles. Moving the planning band moves every rung.

Packages × tiers

02.05

Assemblies

Bills of material built from takeoff quantities and the shared activity master, so a wall is priced as its parts, not as a lump.

Quantity × rate

02.06

AI Reviewer

Reads the estimate for lines priced on weak evidence, gaps that were never priced, and allowances passing as specifications.

Gaps and weak lines, kept apart

02.07

Estimate lifecycle

Draft to approved, with the intelligence kept on the estimate line — evidence, trust and provenance — not on the budget.

Draft → approved

02.08

Publish

One verb sends the estimate into the project budget that draws, change orders and procurement already read. After the lock, changes are change orders.

The only contact point

02.09

Your rates stay yours

Your negotiated rates shadow the shipped catalog and are never served to another organization.

Per-organization evidence

Built to rules already decided

The load-bearing rule

Protected vs adjustable

A verified takeoff locks the quantity. A spec tier may only select the rate. A target may hold an allowance; it may never invent a specification.

No screen replaced

Authoring upstream, operations downstream

The engine authors an estimate and publishes it. The project budget, draws, change orders and procurement keep reading the table they always read.

Gap ≠ weak

Two failure states

Never priced is a gap. Priced on weak evidence is worse, because it looks finished — so it gets its own flag.

One link back

Intelligence lives on the estimate

Evidence and provenance sit on the estimate line; the budget line carries one link back, so the trace survives publish.

Where it connects

← From TakeoffLocked quantities to priceTo Draw →The published budget every draw bills againstTo Procurement →Budget lines each purchase is bought against
LivePlanCoordinateForecast

Scheduling Engine. Plan the work, watch it happen.

The critical path computed on the server, measured against the baseline you approved — with handoffs, inspections and a lookahead that the trades answer from a link.

What it runs

  • Critical-path forecastThe finish date, computed
  • Three-week lookaheadWhat is actually next
  • Handoffs by linkTrades need no account
  • Inspections & milestonesBooked, not remembered
  • Working calendarWork week, holidays, weather
  • One plan, every unitFanned out across a multi-unit job

In detail

03.01

Critical-path forecast

Activities with finish-to-start and start-to-start links, computed on the server. The forecast finish is the answer; every slip is measured against the approved baseline.

CPM · baseline drift

03.02

Lookahead

Day, week or month, filtered by job. What starts, what finishes, who hands off to whom, and which inspection lands in the window.

Day · week · month

03.03

Handoffs by link

A trade partner acknowledges the handoff from a link with no account. The chase list is folded by partner, so one call clears several.

Acknowledged, not assumed

03.04

Inspections

Authorities as master data, a tracker per job, and a checklist the inspector completes from a link.

Tracker · inspector link

03.05

Working calendar

Work week, holidays and weather days as an organization master, with per-job overrides when a site runs differently.

Org master · job override

03.06

Multi-unit fan-out

Plan one unit, fan it out to every unit, and keep them in step. Repeated buildings get a schedule each without planning each.

One plan · every unit

03.07

Templates & master data

Phase ladders, activities and authorities as reusable masters. A new job starts from a template, not a blank sheet.

Guided setup

03.08

Daily logs & to-dos

The job's rail carries the daily log, with the weather filled in, and to-dos assigned with accept and decline.

On the job's own rail

03.09

Weekly report

A PM-to-GC report drafted from the schedule and the logs, approved once, and read by the client from a link.

Frozen on approval

Watch it run

Where it connects

← From ProcurementOrder-by and delivery dates as bars on the planTo Draw →Percent complete per phase on every drawTo Lender →The inspector's reading beside the builder's claim
LiveQuoteAwardDeliver

Procurement Engine. Order early, never late.

RFQ to purchase order to delivery, with suppliers answering from a link and lead times landing on the schedule — so a late window shows up as a late finish before it happens.

What it runs

  • RFQ to awardQuote it, compare it, commit
  • Quotes from a linkSuppliers never sign up
  • Lead times on the scheduleBuying dates meet build dates
  • Alarms before it is lateNot after
  • Rentals with a clockOff-hire before it bills again
  • Deliveries, with proofWhat landed, and when

In detail

04.01

RFQ & bids

Request quotes from a template, compare bids side by side with their evidence, and award. The scope wording can be drafted by AI and edited by you.

Templates · comparison

04.02

Every kind of commitment

Purchase order, subcontract, rental agreement, service agreement — one model, so a change order or a delivery works the same way on each.

PO · sub · rental · service

04.03

Suppliers quote from a link

A supplier answers the RFQ and later confirms the delivery date without creating an account. Asking them to sign up first is how you stop getting quotes.

No login at the other end

04.04

Lead times on the schedule

Packages carry default lead times per trade. The engine works back from the install date to an order-by date and puts both on the schedule.

Order-by dates

04.05

Alarms that chase

Late quote, order-by passed, unconfirmed delivery, rental due — each alarm with its own reminder ladder.

Reminders per alarm

04.06

Rentals with a clock

On-hire and off-hire dates, a rental-days budget, return tracking and a chase when the return is due.

On-hire · off-hire

04.07

Deliveries & proof

Confirmed dates, delivery proof against a policy you set, and delivery billing that lines up with the invoice.

Proof policy

04.08

Vendor scores & marketplace

Scores computed from what actually happened, and an opt-in marketplace where a vendor is invisible until they choose to be listed.

Opt-in

04.09

Approvals per kind

Chains for bids, purchase orders and change orders, with approvers who need no other permission in the product.

Bid · PO · CO

Watch it run

Where it connects

← From BudgetThe budget lines each purchase is bought against← From ComplianceThe award gate — a sub who hasn't cleared can't be awardedTo Scheduling →Order-by and confirmed delivery dates
LiveCollectVerifyEnforce

Compliance Engine. Nobody moves until they clear.

Every certificate, W-9 and licence read on arrival, chased before it lapses, and enforced where it matters — at award and at payment.

What it runs

  • Every document a sub owesCollected in one place
  • Two gatesAt award, and at payment
  • AI reads the certificateThe expiry, off the document itself
  • Chased for youRequests and reminders by link
  • Pay readinessWho can be paid, right now
  • Exceptions on the recordWho waived what, and why

In detail

05.01

Every document, cataloged

Certificates of insurance, W-9s, workers' comp, liability, auto, licences, bonds — each with a scope (company or job) and who supplies it.

Company or job scope

05.02

Two gates, three modes

Every requirement carries an award gate and a payment gate, each set to none, warn or block. Warn lets it through with a flag; block stops the money on the draw.

Award × payment

05.03

AI reads the certificate

Fields and expiry dates come off the COI or W-9 itself, so the renewal is chased before it lapses instead of discovered on the draw.

Expiry off the document

05.04

Requests and reminders by link

A subcontractor answers a document request from a link — no account. A reminder ladder escalates on a schedule you set per requirement.

Chase ladder · no login

05.05

Exceptions ledger

When you pay someone anyway, the ledger records who accepted the risk, why, and until when. The exception expires; the gate comes back.

Who · why · until when

05.06

Pay readiness

One screen per draw: who can be paid, who is held, and the exact requirement holding them. The Draw Engine reads the same answer.

One answer, both engines

05.07

Requirements by trade

A baseline policy for everyone, then per-trade overrides. A roofer's bond doesn't apply to a painter, and the override wins.

Trade overrides baseline

05.08

Compliance reports

Payment alerts, expiry horizon, insurance adequacy, subcontractor scorecards, portfolio exposure and the exceptions log.

Per job or portfolio · CSV

05.09

Command Center

Findings across every job ranked by what is holding money, and the chase list folded by partner so one call clears several.

Findings · chase list

Watch it run

Where it connects

To Procurement →The award gate on every bidTo Draw →The payment gate on every drawTo Lender →Every payee's standing, in the package
LiveExtractPackageFund

AI Draw Engine. Automate, get funded.

Invoices in, a bank-ready package out: lines read by AI, the lender's own template filled, waivers signed on the state's form, and subs paid by ACH or check.

What it runs

  • AI invoice extractionDrop a PDF, confirm the lines
  • The bank's own templateFilled, every draw
  • Lien waivers, all 50 statesSigned and tracked
  • ACH or checkHowever the sub gets paid
  • Approval chainsSign-off before it goes
  • The lender dashboardThe package, already read

In detail

06.01

AI invoice extraction

Drop a PDF, photo or scan. The lines come out mapped to a budget line, with retainage and net worked out. You confirm; you never re-key.

Invoices · quotes · proposals

06.02

The bank's own template

Upload the lender's Excel draw form once. Every draw fills it, with previously funded and retainage carried per line, rolled up to the bank's rows.

Bank template fill

06.03

Lien waivers for every state

Conditional and unconditional, progress and final, on the statutory form for the job's state, filled per payee and signed through DocuSign. The unconditional waits for the money to settle.

Statutory forms · DocuSign

06.04

Pay by ACH or check

Subs are paid by ACH with no bank sign-up on their side, or by a printed check. A photo of a check becomes the payment record.

ACH · checks · check scan

06.05

Approval chains

Org-wide chains or one per job. Sequential sign-offs, send-backs with a reason, and approvers who need no other permission in the product.

Sequential approvers

06.06

The lender dashboard

The package as data: review signals folded into one verdict, every line of the schedule of values, each invoice beside its check, billed beside inspected.

One verdict

06.07

Command Center & pipeline

Every draw across the portfolio by status, billing period and pace, with an over-budget line flagged before the package is built.

Grid · board · timeline

06.08

Cash flow & reports

From the draw register and cycle time to the retainage ledger and the year-end 1099 summary — per job or across the portfolio.

Per job or portfolio · CSV

06.09

Record & audit trail

A closed draw becomes a read-only record. Who approved, what was sent back and when the lender opened it — all on the trail.

Immutable once funded

Watch it run

Where it connects

← From BudgetThe budget lines every invoice lands on← From ComplianceThe payment gate — who can be paid today← From SchedulingPercent complete per phaseTo Lender →The package, read as a dashboard
Separately sellable

Buy the engine you need. Add the next when you need it.

The product is built and permissioned as engines, not a monolith. Turning one on adds its screens, its Command Center and its reports; turning it off hides them and nothing else changes.

Its own Command Center

Every engine opens on a Command Center built for its question: what is late, what is unpaid, who has not cleared, which draw is ready.

A dashboard per engine

Its own permissions

A role can see the invoices and never the configuration. Navigation hides what a role cannot use.

Screen × action grants

Its own outside door

Suppliers quote from a link. Trades acknowledge a handoff from a link. Lenders get an account that owns exactly the packages sent to them.

Links, not logins

Six engines. One job, funded.

Tell us about your projects and your lenders, and we will show you the engines you need — live, on a real draw.

Book a demo →Talk to sales

Works with any lender · Subs answer from a link