OrderExact answers in the units the yard sells.

The problem it solves

Every material calculator on the web will happily tell you that you need 1.85 cubic yards of mulch. That number is correct and completely useless when you are standing in an aisle looking at two-cubic-foot bags, or on the phone to a yard that sells by the half yard with a delivery minimum.

OrderExact ends every calculation with the line you'd actually put on the order. Bags and cubic yards for mulch, squares and bundles for a roof, boards for decking, sheets for drywall, and for fencing the posts get counted rather than divided, because a fence with eight sections needs nine posts.

How it's built

Twenty-one calculators across twenty-eight pages, generated from a Python content module by a build script that uses nothing but the standard library. The output is plain HTML served straight off GitHub Pages; the generator never runs anywhere except on the machine of whoever is editing the site.

All the arithmetic happens in the browser. There is no account, no upload and no server doing the maths, which means nothing anyone types is transmitted or logged, and the calculators keep working when the signal drops halfway through a job. That last part is not a nice-to-have on a building site.

The bit that took the longest

Deciding what not to hard-code. Geometry can be baked in, because the volume of a rectangular bed is not going to change. Coverage rates, bundle counts and bag sizes cannot, because they are printed on a wrapper and vary between manufacturers.

So every one of those is an input with a sensible default rather than a constant, and there's a page explaining where each default came from. A calculator that quietly assumes your supplier's bag size is a calculator that will under-order for somebody.