Most flooring calculators still work from area plus a waste percentage.
That is fine for a rough estimate, but it breaks down as soon as the room stops being a clean rectangle. Direction matters. Offset matters. Cutouts matter. And once reusable leftovers enter the picture, the final count is no longer something you can treat as area plus a guess.
While building RampNerd, I ran into a related problem: I needed a deterministic way to validate layout and sheet results against real geometry instead of estimates. That sent me into flooring, where most tools were still relying on percentages.
I also remembered my grandfather, a carpenter, drawing exact layouts by hand before installation. The software problem was modern, but the underlying need clearly was not.
So instead of building another area-plus-waste calculator, I built Calcufloor: a browser-based layout engine that simulates actual plank and tile placement inside arbitrary room polygons.
You draw the room as real geometry, including cutouts and awkward shapes. Then you enter the material dimensions, choose a direction and pattern, and generate the layout from the geometry itself.
That matters because two rooms with the same area can still produce very different counts. The cut pattern changes with the room shape, the layout direction, the starting offset, and whether leftover pieces can be reused.
The part that changed my thinking most was offcut reuse. If a row ends with a usable leftover, that piece can affect the next row and change the final total. At that point, the tool stops behaving like a calculator and starts behaving more like a placement engine.
That is the part I found interesting: it sits somewhere between geometry processing, layout simulation, and practical installation constraints.
If you work on modeling, CAD-adjacent tools, or geometry-heavy browser apps, I’d be curious how you would classify that kind of system.
Try it here: calcufloor.com
Top comments (0)