Write to us
Direct email: hello@costanswer.com
We welcome your input! You can reach out directly to hello@costanswer.com or use the form below for:
- Calculation corrections & wrong figures: if an engine produces an unexpected result or differs from an official agency table. You can also click Report incorrect result on any calculator to send a complete diagnostic with one click.
- New calculator & feature requests: tell us which tools, formulas, or datasets you would like added to the catalogue.
- Broken pages or technical bugs: any issue with inputs, layout, or device responsiveness.
- General suggestions & feedback: anything we can do to make CostAnswer faster and more useful.
The form below opens your mail app with your note pre-filled to hello@costanswer.com. Nothing is posted to CostAnswer servers to store.
Calculator requests
If a calculator is missing, say what it should compute, who it is for, and which official table it should use if you know one. The closest page already on the site helps. A request is read. Building it is a separate decision. There is no queue you can check, and no promise of a date.
Complaints about the product (a page that will not load, a ZIP lookup that hangs, copy that contradicts the numbers) go in the same form. Pick Something broken. Product complaints and wrong figures are different notes. Mix them and the Method line gets lost.
Wrong figures
You can use the Report incorrect result button directly under any calculation result to send a pre-filled diagnostic snapshot, or copy the details into the form below:
- The page URL
- The Method version
- The Data snapshot id, or “Manual inputs / fixed rules” if that is what it says
- What you typed, what the page showed, and what you expected
- A title, period, and link for the official table you are comparing, if you have one
Do not send paystubs, tax returns, account numbers, Social Security numbers, or medical records. The calculators do not need them, and neither does this form.
What this is for
A formula that does not match its worked example. A stored dataset that does not match its hash. A source, period, or geography labelled as the wrong one. A page still showing an older figure as current after the provider has published again. A calculator this catalogue does not have. Copy or layout that gets in the way of reading a result.
Personal tax, lending, medical, payroll, or travel questions belong with the official source named on the page, or with someone licensed to take that on. Common questions about what a result is, where the data comes from, and what the site stores are on the FAQ.
After you send it
A report with the Method and Data lines can be checked against the tests and the stored snapshot. If the engine is wrong, the Method string changes. If the data is wrong or stale, the Data id changes. Older results keep the strings they printed, so a past screenshot still points at that copy.
A calculator request is not a ticket. If it is built, it shows up in the catalogue with a Method version of its own. There is no promised response time. A complete note gets read. A screenshot with no version usually cannot be checked.