Project The Masonry Modeler
Sheet B1.1 — Why I Built This
Sheets Shop Drawings Join Waitlist →
Field Notes · B1.1 Founder Story
Field Notes

It's 2026. Why Doesn't Masonry Software Know What a Corner Is?

The Douglas Humane Society job is where it clicked for me.

I was doing the takeoff — wall by wall, opening by opening — and the software was moving fast. Quantity list building up. Looks good. Then I get to the corners and nothing's right.

The bullnose halves aren't there. The corner units aren't listed. The software had counted blocks like carpet — length times height — and called it done. It didn't know a corner existed.

That's when I understood what these tools actually are. They're not masonry software. They're rectangle counters that happen to output a block count.

What the software thinks a wall is

Most construction estimating tools — even the ones marketed specifically for masonry — use the same model under the hood: a wall is a rectangular field of units. Length divided by unit size, height divided by unit size, multiply. Add a waste factor.

That's it. That's the whole model.

A corner is not modeled. A corner is a place where two rectangular fields meet. The software doesn't know the bond has to run through it. It doesn't know the courses have to resolve around the corner, or that a corner calls for different units entirely — special pieces that get ordered separately and never show up when you count a wall like carpet.

You should see some of the things I've tried. It's always a mess. The count comes out wrong, the corner pieces are missing, and I end up in a spreadsheet doing it by hand anyway.

The rake problem

Try to model a building with gable ends in one of these tools.

Here's the workflow I've actually used: place one wall all the way around the perimeter. Then place a second wall at the height of the rake, with returns for the corners. Then place two rake walls — one for each gable. Three separate wall placements, manually stitched together, to represent one building.

And after all that, the takeoff is still wrong. The rake geometry isn't accounted for correctly. The bond doesn't know it's stepping. The corner counts are still off.

So I do what I've always done: take the rough count from the software, open a spreadsheet, and count everything by hand. Every corner piece. Every half unit. Every bond beam block. Every cut. For a big job, that's days of work.

Then the drawings change.

What I actually wanted

I wanted a tool that modeled a masonry wall the way a mason thinks about it — not the way a programmer thinks about rectangle grids.

A wall that knows what bond is. Corners that interlock by default, because that's how you lay masonry. A building with rakes that gets entered once, not assembled from three disconnected wall segments. Lintels that place in the right course — the bond beam course — not wherever the software guesses.

And a takeoff that lists every unit as it will actually be ordered: corners, halves, lintel blocks, bond beam blocks, bullnose, cuts — all counted, all priced. So I don't end up back in a spreadsheet.

And masonry shop drawings that come out of the same model — coursed, labeled, openings and bond beams in place — so I'm not paying a detailer to hand-redraw a wall the tool already knows. One trace. Two deliverables. The takeoff goes to the supplier and the shop drawing goes to the GC.

I looked for that for years. Nothing existed. Not for masonry specifically. The tools that call themselves masonry tools are rectangle counters with a better-looking output.

So I built it.

What The Masonry Modeler actually does

The Masonry Modeler starts with bond. It knows the block size, the joint width, the bond pattern. When you draw a corner, the bond runs through it — automatically. The corner closes, and the corner unit count is correct because the geometry is correct.

Rakes are geometry, not workarounds. A wall with a gabled top gets entered as one wall with a slope. It counts the full courses, the step courses, and the rakes. No three-step assembly process.

Lintels snap to the right course because it knows where bond beam courses fall. Development length past the opening is automatic.

The takeoff lists every unit as its own line item. Corners. Halves. Cuts over 4 inches. (Under 4 inches, it absorbs them — it will never produce a cut that can't be laid.) Bond beam blocks with rebar, counted in pounds, not just linear feet.

That's what I needed. That's what I built.

If you're still doing your exact piece counts by hand in a spreadsheet, I'd like to show you something different.

Join the waitlist →
← All posts