Location strategy builder

What it works from

• Org data, role documentation or headcount exports
• Your own design principles or planning assumptions

What you get back

• A role-level view of the organisation in scope with the reasoning attached
• A roll-up for leadership at the level you report at

Why this is expensive by hand

Work on the organisation in scope normally means pulling org data, role documentation and headcount exports together by hand, then applying a standard that only exists in the head of whoever is doing it. Structural decisions with evidence is the typical trigger — show the role-level basis for a design or headcount decision instead of defending a judgement call. Done properly it is defensible; done at pace it becomes a judgement call nobody can retrace. And "properly" usually means 2–3 weeks of manual work.

How this Skill produces it

Here the same job runs as a Skill. Your material goes in; a role-level view of the organisation in scope with the reasoning attached comes out, alongside a roll-up for leadership at the level you report at. What sits between input and output is the codified method: thresholds, sequencing and the points where a human confirms a call — all of it visible and editable in the Skill. The practical effect: 2–3 weeks of manual work becomes a ~25 minutes run, held to an identical standard on the tenth engagement as on the first.