Contact Us

If you have questions, feedback, or suggestions related to ToolsQue, feel free to get in touch. We welcome genuine inquiries and value user input that helps improve the platform.

How to Reach Us

You can contact Toolsque using any of the following methods:

Email: hello@toolsque.com

We aim to review messages and respond when possible, though response times may vary.

What You Can Contact Us About

You may contact us regarding:

Questions about tools or comparisons published on the site
Feedback or suggestions for improvement
Reporting issues or errors
General inquiries related to the platform

Please note that ToolsQue does not provide individual purchasing advice or direct software support for third-party tools.

Transparency Notice

ToolsQue is an informational platform. Messages sent through this page are used only to respond to inquiries and are not shared or sold to third parties.

Reporting a result you think is wrong

Include four things: the tool, the exact inputs, the number it returned, and the number you expected with a sentence on how you got there. That last one does most of the work. "The markup tool is wrong" is unactionable. "Cost 200, rate 30, the contractor markup calculator gave me 285.71, I expected 260" tells me in one line that you are treating 30 as markup on cost while the field reads it as margin on price. The only question left is whether that is a maths bug or a labelling bug.

Type the numbers as text rather than sending only a screenshot, so I can paste them into a test. If the field itself misbehaved, a decimal comma vanishing, a mobile keyboard eating a fraction, name the browser and device. That class of fault is input parsing, not calculation.

Reproducible arithmetic goes to the front

A wrong formula is wrong for everyone who runs it, quietly, every time, which puts it ahead of everything else. The usual culprits are rounding applied at the wrong step, unit conversion that assumes decimal feet when someone typed feet and inches, and floating point drift showing up as 0.30000000000000004. Waste factors are their own category. Adding 10% to a total roof area and then rounding to whole squares is not the same operation as rounding each plane up first, and on a cut-up hip roof the two can differ by a full square. A case where two defensible methods disagree is already a finished bug report.

Questions I will not answer

I write calculators and read specifications. I am not an accountant, a tax adviser, a lawyer or a licensed contractor, and answering as though I were would be worse than useless, because you might act on it. No personalised tax positions, no ruling on whether a deduction survives scrutiny, no legal reading of a party wall dispute. The 1099 tax calculator shows its arithmetic and the assumptions feeding it; whether those assumptions describe your year is between you and someone qualified to say.

"What should I charge" lands in the same bin. A rate depends on your local market, your billable utilisation, your fixed overhead and how much risk you will absorb, none of which arrives in a contact form. The day rate to hourly converter will tell you what a given day rate implies once unpaid time comes out, which is a narrower question I can help with. Which formula a tool uses, and where I took it from, I am glad to explain.

Suggesting a tool

Send the calculation, not the title. "A soffit calculator" is a name. "Takes linear run, board length and corner count, returns board count plus a waste allowance" is a specification, and I can build the second one. If the maths comes from a published document, cite it: an IRC table number, a clause in Approved Document K, an IRS instruction. Check the tool categories first, because sometimes the gap is one missing field on a page that already exists, which ships far sooner than a new tool.

Everything sent through the form gets read. One developer, no support desk, so no invented turnaround time. A reproducible wrong number is what makes me stop what I am doing.