🗺️ Compare Sites Without Guessing

Use answer-first prompts to design data models, approval matrices, executive reviews, portfolio risk systems, job costing, cash scenarios, vendor SLAs, commission trackers, retention dashboards, and customer health scorecards. Each prompt asks for the operating rules and evidence needed before generating an app or workflow.
Compare Sites Without Guessing

Copy

I run several sites and I cannot tell which is genuinely performing. Build me a multi-site app. Hold each site with its size, opening hours, headcount, catchment and any local conditions that affect it. Bring in the operational measures I care about per site per period, and normalize them for size and hours so the comparison is fair rather than favouring the largest. Show sites ranked on normalized measures with the group average and the spread, and show each site trend against itself as well as against the group. Where a site consistently outperforms, capture what they do differently as a note against the site so it can be shared rather than merely admired. Add an AI agent that reviews the comparison and tells me which site is genuinely best on each measure once conditions are accounted for, which practices appear to explain a difference, and which underperforming site would benefit most from a specific change. Automate two things: a scheduled monthly comparison to each site manager showing their own position against the group, and an alert when a site moves materially against its own trend. Two logins: a site manager who sees their own site and the group average, and an owner who sees everything.

STATUS · LIVE
v1

01 / Spark - intelligence awakens

Compare Sites Without Guessing

Compare locations on normalized measures with local conditions recorded, and identify practices worth transferring.

// the spark catches · intelligence awakens · the answer unfolds

Sites are compared on the numbers that flatter the biggest one. This normalizes for size and hours so you can see what is genuinely working and copy it.

What's Included

  • Normalized measures so size does not decide the ranking.
  • Local conditions recorded which explain much of the difference.
  • Best practice identified and shared rather than just noted.
  • An assistant that says what one site does differently.

How To Use

  1. Normalize for size and hours. Otherwise the biggest site always wins.
  2. Record local conditions. They explain a great deal of the variance.
  3. Share what the best site does. Comparison without transfer is pointless.
  4. Show each manager their own position against the group.

Feed it from the KPI scorecard, and act with continuous improvement.