How a takeoff gets done in minutes
The long version of the four steps: what the system reads, what it refuses to guess, and where a person decides.
What you upload: the plan set as it arrived
The input is the PDF package the builder or architect already sent you — plan sheets, elevation sheets, and the schedule table. No CAD files, and no template to fill in first.
A revision is a new upload against the same job, not a project you start over.
What comes back: every opening, with the conflicts raised
Each opening returns with its mark, its dimensions, and its type — operation, handing, glazing. Where the schedule and the elevations disagree, or a symbol will not resolve, the unit is raised for you instead of filled in.
You clear those before anything becomes a number. Nothing ambiguous turns into a line on the quote without a person deciding it.
Where your catalog and your margins come in
The reviewed schedule maps onto your own product lines: your part numbers, your rules for options and glazing packages, your margins. What comes out is the quote document you would have produced by hand, without the transcription step in the middle.
What you send, and what the shop builds from
Because the schedule was reconciled across the drawings instead of transcribed from a single sheet, the count that wins the bid is the count the shop builds from. The bid goes out while the job is still open, and it does not come back as rework.
What you need to start
A plan set as PDF: floor plans, elevations, and the window schedule. That is the same package you quote from today.
What it doesn’t do
One to Many is not an estimating suite or an ERP — it produces the unit-by-unit schedule and the priced quote, and feeds the tools you already run. And it doesn’t guess: anything ambiguous in the drawings is flagged for your review before it becomes a number.