Estimating with CMU units, brick SF, lintel LF — waste factor and mortar coverage built in. Mixed-crew labor on every scope. AIA G702/G703 pay apps with retainage. The same tool from the bid to the deposit.
Generic construction software was built for general contractors who manage subs. The bid view is a list of cost codes, not a wall section. The labor view is one rate, not three. The pay app workflow is a CSV export instead of an AIA G702/G703 the GC actually expects.
The masonry shop's reality — unit math, waste factor per material, mixed labor classifications, retainage on every draw — sits inside the tool from the start. The bid you sign is the budget the foreman uses, is the pay app the GC stamps.
Scope templates, units, labor mix, and the back-office workflow are all set up the way a masonry shop runs — not the way a generic SaaS thinks a shop runs.
Brick by the unit. CMU walls by the SF. Lintels and bond beams by the LF. Cast stone by the EA. Each scope carries its own waste factor and mortar coverage so the bid totals reflect what actually gets ordered.
CMU partitions, brick veneer, manufactured stone, cast stone, repointing, tuckpointing. Scope templates ship with the unit math, waste defaults, and labor classifications already wired in — ready to drop into a bid.
Mixed-crew labor on every scope — not one blended rate that quietly masks where the margin actually goes. Override per project for prevailing wage. Certified payroll outputs roll up automatically.
AIA G702 + G703 with retainage tracking, stored material lines, and a schedule of values that maps cleanly back to your scope buildup. Click once, get a PDF the project owner will sign.
Masonry-aware fields — blocks set, faces laid, joints tooled, scaffold moved — alongside weather, manpower, and on-the-wall photos. Three taps from a phone, not a half-hour spreadsheet at the truck.
The mason taps in once and out once with a PIN. The phone snaps a verification photo and stamps the jobsite location. The office sees the hours by the next morning, not Sunday night.
Every module everything in the platform routes through. On a masonry job, here's how they line up.
The scope buildup becomes the project budget when you win. The foreman opens it on a phone and sees install targets per day, by scope. Blocks set per shift maps back to what was bid.
Photo-verified clock-in feeds the time card. The time card feeds payroll. Mason, tender, and helper hours stay separated so prevailing-wage and certified-payroll outputs are clean.
Percent-complete plus stored material rolls straight into AIA G702/G703. The schedule of values traces back to the same scope rows you bid. Retainage tracks per draw. The PDF the GC stamps is the one the system generates.
You bid the job, you run the job, you bill the job. Stop holding the pieces together in your head and a stack of Excel sheets — one source of truth from the takeoff to the pay app.
Daily logs and crew time from a phone. Pre-populated scope fields. No paper sheets, no tear-out, no Sunday night data entry. The bid you got handed is the install plan.
AIA pay apps with the click of a button. AP with OCR'd vendor bills. Payroll that pulls from the same time data the foreman captured. The full back office runs from one system.
Yes. Count for brick and block, SF for veneer fields, LF for lintels and bond beams, EA for cast stone and accessories. Every scope template carries its own unit definition.
Yes — per material. Defaults ship in (5% for face brick, 6% for CMU, etc.), and you can override per project when the conditions call for it.
Yes. Mixed-crew costing on every scope. Globally configured rates with per-project overrides for prevailing wage. Time cards capture the classification at clock-in.
First-class output. Schedule of values maps back to the scope rows you bid. Retainage tracks per draw. Stored material has its own line so on-site brick palettes don't trip you up at month-end.
Yes. Per-project labor classifications carry the prevailing-wage rate. Certified payroll outputs (WH-347 format) are generated from the same time data, no double entry.
Yes. Change orders track separately from the base contract and roll up into the pay app in their own line. T&M COs pull hours straight from time tracking with the markup applied.
Yes — every contractor on the platform runs multiple jobs concurrently. Time tracking, daily logs, scope rollups, and pay apps are scoped per project. The owner-estimator's CRM dashboard rolls everything up.
Book a 30-minute call. Bring a bid you're working on or a job that's running. We'll walk through the takeoff, the scope buildup, and what the pay app looks like when the whole job runs on one platform.