What's this about?
Pick the category that matches your reason for reaching out. It's the single biggest thing that determines how fast you hear back, because it decides whose queue your message lands in.
Calculator error
A result that doesn't match a hand calculation, a code table, or what actually got built. This is the fastest queue to a real fix — see the reporting checklist below.
See what to include →General question
A code question, a request for a calculator that doesn't exist yet, or feedback on a guide. Describe the real problem you're solving, not just a tool name.
Use the form below →Business & press
Partnerships, sponsorships, licensing, or media/press inquiries. Note upfront: we don't accept payment to change a formula or a comparison. See our editorial policy.
See direct email →Data & privacy
Requests related to analytics data or the Privacy Policy. The calculators themselves don't require an account and don't store your inputs after you leave the page.
Read Privacy Policy →Get in touch directly
This opens your email client with the message pre-filled, addressed to the right inbox based on what you select — nothing is sent through a third-party form service, and nothing is stored on our side until it lands in that inbox.
For error reports specifically, fill in the calculator name and input values below — it's the difference between a same-week fix and a report that sits waiting for follow-up questions.
What actually gets a calculator fixed
A report we can reproduce in under five minutes gets fixed in weeks. A report we can't reproduce gets stuck in a follow-up-question loop. Here's the difference.
| Include this | Why it matters | Example |
|---|---|---|
| Exact calculator name | 93 calculators share overlapping terms — "stringer," "riser," "run" — so the name alone can be ambiguous. | Stair Stringer Calculator, not "the stringer one" |
| Every input value | Most errors only show up at specific input combinations, usually near a rounding boundary or a code threshold. | Total rise 108in, run 132in, tread 10.5in |
| Result you got | Lets us confirm we're looking at the same bug, not a different one nearby. | "13 risers at 8.31in each" |
| Result you expected | Tells us whether this is a math bug, a code-citation error, or a UI display issue. | "Should be 14 risers at 7.71in per IRC R311.7.5.1" |
| Source, if you have one | Not required, but a code section or a measurement from a real build speeds up verification a lot. | "IRC R311.7.5.1, table attached" or "confirmed against my framing square" |
Confirmed errors are re-derived from the original cited source — not patched around the symptom — and re-tested against the same edge cases used at launch. The calculator's last-verified date updates so returning visitors can see it's been touched. See the full correction log on our About Us page.
Prefer not to use the form?
These reach the same inboxes as the form above, split by category so your message doesn't have to be re-routed by hand.
Default inbox for anything not covered by the categories below.
Sponsorships, licensing, and partnership inquiries only.
Journalists and media — include your outlet and deadline.
We intentionally don't list a phone number. The team is small and works asynchronously across written channels — this keeps every request in a trackable queue with a stated response target, instead of getting lost in calls that don't leave a record. We're a fully remote team and don't maintain a public mailing address.
A message doesn't go into a void
The same people named on our About Us page triage what comes in through this page — split by the kind of expertise each category actually needs.
Lead Content & Code Review
Editorial queueTriages calculator error reports and general code questions — re-derives fixes from the original cited source rather than patching around symptoms.
Structural Consultant
Advisory reviewBrought in on structural and load-bearing calculator reports that need engineering judgment beyond code text alone.
Site Editor & Developer
Ops queueHandles business, data/privacy and technical (broken page, display bug) messages, plus anything that doesn't fit the other two queues.
Note: these are the same three roles described on our About Us page. We've kept this section role-based rather than naming individuals here to avoid duplicate/stale bios across pages — full names and backgrounds for each person live on About Us, which is the canonical source; update names there first if the team changes.