The quick version: A variable in Numi is a named value you set once and reference anywhere below it in the same document. Change the value at the top and every line that depends on it recalculates automatically. It’s the single feature that turns a one-off calculation into a template you actually reuse, and it’s available in the free tier.
The basic mechanic
Write “rent = $2,400” on any line, and from that point forward, rent is a valid term anywhere else in the document. Reference it directly, use it in a formula, combine it with other variables. Change the original line and every line that used rent recalculates the moment you edit it, without touching any of the formulas that reference it.
Scope: variables live inside one document
A variable defined in one Numi document doesn’t exist in another. If you have a budget document with income defined and a separate invoice document, they’re entirely independent, and defining income differently in each causes no conflict. This is worth understanding early, because it’s the reason a template built with variables in one document needs to be duplicated, not just referenced, when starting a new project. It’s also what makes custom functions, covered separately, the feature you reach for once you need a formula to persist across documents rather than just within one.
Chaining variables together
Variables can reference other variables, which is where they become genuinely powerful rather than just a named shortcut for a single number:
hourly = $85 hours = 6 subtotal = hourly × hours tax = subtotal × 8% total = subtotal + tax
Each line builds on the one before it, and changing hourly or hours at the top ripples through every calculation below without needing to touch subtotal, tax, or total directly. This is the actual reason to use variables over just typing raw numbers on every line — the dependency chain updates itself.
Redefining a variable partway through a document
If the same variable name is set again further down a document, the new value applies from that point forward, while lines above the redefinition keep using whatever value was active when they were calculated. This is useful for a document that tracks something changing over time — a rate that increased partway through a project, for instance — but it’s also where mistakes happen if you’re not paying attention to line order. Keeping key variables defined once, near the top, avoids the confusion entirely for most everyday use.
Practical patterns
A single source of truth for a repeated number
Anywhere the same number appears more than twice in a document — a rate, a tax percentage, an exchange target — define it once as a variable rather than retyping the raw value. The Numi app then only needs one edit to update every dependent calculation, which is both faster and less error-prone than hunting down every instance of a hardcoded number.
Descriptive names over generic ones
Name variables for what they represent, not just a letter or a short abbreviation: hourly_rate reads clearly months later when you reopen an old document, while x or r requires re-deriving the context from scratch. Since Numi documents often get reopened and reused well after the original context has faded from memory, this small habit saves real confusion later.
Building toward a function
If a variable-based calculation in one document turns out to be something you rebuild constantly across new documents, that’s the signal to promote it to a custom function instead, which persists across documents rather than needing to be retyped every time. Variables are the right tool for document-specific values; functions are the right tool once the same formula shape needs to travel with you everywhere.
Why this matters more than it sounds
The difference between a calculator and the Numi calculator specifically is that variables turn a single calculation into a small, living model of whatever you’re actually trying to figure out — a budget, a quote, a schedule — where changing one input tells you the real consequence everywhere else, instead of forcing you to redo the whole thing by hand every time a number changes.
Frequently asked questions
Do Numi variables work in the free version?
Yes. Variables within a single document are available in the free tier. Reusable custom functions that persist across documents require the paid license.
Are variables shared between different documents?
No. A variable defined in one document only exists within that document. Defining “rate” in one file has no effect on a variable with the same name in a separate file.
What happens if I define the same variable name twice?
The later definition overrides the earlier one for any line below it. Lines that referenced the variable before the redefinition keep using the value active at that point.