Contact

Email: admin@metrickittools.com

What we can help with

  • Calculator accuracy and formula questions.
  • Content clarity in guides or glossary terms.
  • Requests for new calculators or workflow pages.
  • Bug reports in layout, inputs, or exports.

Bug reports

If you found a bug in a calculator, include:

  • The calculator URL.
  • The input values you entered (screenshots are fine).
  • The output you got and what you expected instead.
  • Your currency and time unit assumptions (monthly vs annual).
  • The browser/device you used.

If the issue is about a formula or definition, include your source or how your team defines the metric so we can align the wording.

Feature requests

If you want a new calculator, send the metric name, your use case, and the inputs you expect to have. We prioritize requests that improve decision-making or remove ambiguity.

Before you send

  • Confirm the calculator version or page URL.
  • Check that inputs use the same time window.
  • Note whether you want a SaaS or ecommerce interpretation.

Content feedback

If a guide or glossary term is unclear, tell us which part is confusing and what decision you were trying to make.

If you can, include the metric name, your business model (SaaS or ecommerce), and the time window you care about so we can improve the explanation.

Partnerships

If you want to collaborate on a guide, share your outline, the calculator it supports, and any data sources you want referenced.

Response time

We aim to respond within a few business days. For urgent issues, include "urgent" in the subject line and a short summary of impact.

What to include for SEO/content requests

  • The target keyword or user question.
  • The page URL and current section you want improved.
  • Any constraints (tone, audience, or business model).

Calculator QA checklist

  • Confirm the time window (monthly, quarterly, annual).
  • Confirm the currency and rounding rules.
  • List whether refunds, churn, or discounts are included.
  • Note if the calculator should use gross or contribution margin.

Data handling

Do not send sensitive customer data. If you need to share a dataset, anonymize it first and provide a synthetic example that reproduces the issue.

Response expectations

We respond in the order received. If a request is time-sensitive, say so and include the business impact so we can prioritize correctly.