Beyond the estimate.
The website and inquiry flow Drew designed and built, three customer-facing ROM proposals, and the estimating system behind early budgets, with their evidence showing. From his time leading preconstruction at Fellow, a Denver luxury custom builder.
The Farm · live web proposal
It starts at the front door.
Before any proposal, an owner meets the builder online. Drew designed and built Fellow’s website, including a custom contact-to-consultation flow that takes about 90 seconds and arrives qualified.

Same discipline. Three different conversations.
Each proposal answers a different owner question: what am I building, how will we live through it, and what can I change?
Every page answers a question the owner is already asking.
Two July 2026 proposals: a new mountain home at schematic design, and a whole-home renovation with three ways to live through it.
Not just what it costs. How you’ll live through it.
The renovation proposal compared three ways to live through construction, weighing investment against disruption. Recreated here with the proposal’s actual figures.
Live in the home for most of the work, with a few short move-outs when the work requires them.
Figures and durations from the original proposalFrom project information to a defensible preliminary estimate, to a clear and compelling customer proposal.
ROM Workbench is a custom estimating application built at Fellow. It takes a drawing set through intake, pricing, value engineering and export, and keeps track of what is measured, what is assumed, and how well every rate is evidenced.
The business problem: an early budget has to be fast enough to keep a client’s momentum and honest enough to hold up later. The screens below are the application itself, running one Schematic Design package.
It reads the set before it prices it.
Four inputs are confirmed before anything runs: design stage, fee, fee convention and export destination. The run then reports what it read, what is missing, and where the drawings disagree with themselves. A reviewer decides which figure governs.
123
Every rate shows where it came from.
Most early budgets hide the difference between a number someone measured and a number someone guessed. ROM Workbench scores both, line by line, and says so on the estimate itself.
1234
The library holds the evidence the engine may price from, graded from benchmark to actual cost. It is capped at “partial” until a job closes, and nothing an estimate produces is written back as evidence. Only buyout and closeout figures can teach it.
A preliminary ROM. Not evidence.Buyout
estimating signal = buyoutRate ÷ estimatedRateCloseout
field signal = closeRate ÷ buyoutRate

One estimate, two audiences.
Internally, every line keeps its quantity, rate, basis and verification state across seven cost-code sections. For the client, the same estimate is written as scope only, with no rates, ranges or confidence language. A reviewer edits it in one place.
Internal: the working estimate Quantity × rate on every line, a basis written in words, the documents it depends on, and Mark verified or Calibration record.
123Options, priced as decisions.
1234
Fourteen choices, handed to the homeowner.
Fellow’s live web proposal for The Farm turns its seven savings and seven alternates into switches. Each one moves the total, the ±25% range and the weeks on site together. Nothing is saved, the choices travel in the link, and one button resets to as drawn. Try it below.
It won’t issue a package it can’t stand behind.
One package is built to issue four outputs: a customer-facing ROM, a Buildertrend estimate import, a milestone schedule and an alternates & VE summary. Before any of them, a self-check runs two different kinds of test.
123






