About Geod
Geod exists because the analysis behind a million-dollar store decision usually dies in the meeting that approved it. We build network scenario software for multi-unit operators: a ledger of your locations, a simulator for the moves you are weighing, and a memory of what was decided and why.
Four commitments, all checkable in the product
The network is the asset
A multi-unit operator makes some of the largest capital decisions in retail. The thing those decisions affect, the network of stores, usually lives in a spreadsheet someone re-uploads every quarter. We treat it as the durable record everything else refers to.
Analyses should hold still
A report computed on Tuesday should say the same thing when the committee meets on Friday, and when the board reviews the decision next year. Every Geod analysis is pinned to a named data snapshot and a generation date, and refresh is an explicit act.
Numbers must show their work
A score nobody can decompose is an opinion with a decimal point. Every composite in Geod opens into components with visible weights, every figure names its source and vintage, and when something cannot be computed honestly the brief says omitted instead of making it up.
Predictions should face their record
When an analysis claims a closure will hand demand back to nearby stores, that claim is stored with its assumptions and eventually compared against what happened. A model that has to face its own scorecard earns trust differently than one that never looks back.
We publish how everything is computed: data sources, aggregation logic, scoring weights, and the boundaries of what the model does and does not claim. If a method would not survive a skeptical CFO, we do not ship it.