Methodology
This page explains how MetricKit builds calculators, glossary entries, and guides. The aim is not to pretend that every business uses the same metric definition. The aim is to make assumptions visible so a team can decide whether a page matches its own operating model.
How calculators are built
- Each calculator uses an explicit formula or compact decision rule.
- Inputs are user-provided; we do not import live account data.
- Outputs are intended for planning, interpretation, and comparison.
- Where a shortcut is used, we try to state the tradeoff clearly.
Formula design principles
- Prefer standard business formulas before introducing custom logic.
- Make units obvious: monthly vs annual, dollars vs percentages, users vs accounts.
- Keep variable names legible so operators can reproduce the result in a model.
- Link to a guide or glossary page when interpretation is more important than the raw math.
Examples and worked numbers
We use worked examples to show how a result moves when one assumption changes. Example values are illustrative and should not be treated as benchmarks unless the page explicitly says so.
Assumptions and limits
- Metric definitions vary by business model, accounting policy, and team convention.
- Some calculators simplify reality to stay useful in a browser workflow.
- Outputs do not replace accounting, finance, legal, or tax advice.
- Attribution and incrementality metrics can diverge from platform reporting.
How glossary and guide pages are written
- Glossary pages define a term, clarify common misuse, and link to practical next steps.
- Guide pages explain when to use a metric, how to interpret it, and what mistakes to avoid.
- We try to connect formulas to operator decisions rather than leaving them as isolated definitions.
Corrections and updates
We revise pages when a formula is unclear, a definition is commonly misread, or a better explanation would prevent bad decisions. If a change materially affects interpretation, we try to make that visible in the linked page set.
Sources and references
Not every page currently carries a full source list, but our direction is to increase explicit references for benchmark-heavy and definition sensitive topics. When you send feedback, including your source or team convention helps us evaluate whether a page should be clarified.
Feedback loop
If a page is ambiguous, inconsistent, or missing an important use case, email admin@metrickittools.com with the URL, your business model, and the exact point of confusion.
See also: Editorial Policy, About, and Contact.