Contact us
Questions, corrections, partnership inquiries, or feature requests. We read every message and reply within 1-3 business days.
Prefer email? Reach us at funplay486@gmail.com.
What to include in your message
The faster you give us context, the faster we can answer well. For fact-checks or corrections, please include the exact URL of the page and the specific sentence, table cell, or chart label you believe is wrong, along with your source. For feature requests, describe the question you were trying to answer when you needed the missing feature — that helps us decide whether to build the requested feature, surface an existing one we did not link well, or build something different that solves the same problem. For partnership and press inquiries, include the publication or company name, your role, the angle you are working on, and any deadline.
We do not have a customer-service team, a sales team, or an SEO team. Every message is read by a human (most often the founder) and answered personally. Because of that, response time varies from a same-day reply for short questions to two or three business days for substantive corrections or research questions that require checking a primary source. We do not respond to outreach for unrelated link-building, mass cold partnership pitches, or unsolicited "guest-post on your blog" requests. If your message is one of those, no reply is the answer.
What we are looking for
The most valuable messages we receive are corrections — typos, math errors, outdated tax limits, links that have rotted, calculator inputs that behave unexpectedly on uncommon edge cases. We publish a public corrections log linked from our editorial standards and credit substantive corrections by name (or anonymously if you prefer). Second most valuable: domain expertise we do not have. If you are a CPA, tax attorney, mortgage broker, financial planner, or actuary and you spot a nuance we missed, please tell us. Third: real-world stories where one of our calculators clarified a financial decision — those help us prioritize which tools to deepen.
Other ways to reach us
For machine-readable site information (sitemap, structured-data dumps, citation strings), see /llms-full.txt and /cite. For our editorial process, fact-checking standards, and corrections policy, see /editorial-standards. For the master index of primary sources behind every quantitative claim on the site, see /sources.