Reset Headcount and Org Design for the Post-Turnaround Business

Aim: Turn the Business Around → Objective: Reshape the
organization to match the business the company needs to become, not the
one it used to be → Initiative: Run a structured org-design reset
that produces a defensible headcount plan within 60 days

Fits well at: $1M–$5M businesses with 10–50 people, especially
owner-operated companies where the org chart grew by accretion rather
than design. Also applies to the post-acquisition or post-pivot moment
when the old structure no longer matches the new strategy.

What this is

A strategy exercise — not a cost-cutting exercise pretending to be one.
The question isn't "where can we trim?" It's "what does this business
need to look like in 12 months, and who do we need to get there?" The
answer produces a headcount plan, but the headcount plan is an output of
strategy, not the starting point.

For a sub-$5M business with 10–50 people, org design can be the
difference between survival and not. Every redundant layer, every unclear
role, every span-of-control mismatch drains cash and decision speed in a
company that can't afford to lose either. This page is honest about
that, while holding the frame that these are real humans whose
livelihoods are affected — not line items on a spreadsheet.

What "done" looks like

• A written future-state org design anchored to the 12-month strategy,
  living in the Knowledge Base

• A current-state org map with roles, reporting lines, spans of control,
  and loaded costs — generated from existing people and payroll data

• A gap analysis: current state vs. future state, role by role

• A headcount plan with specific actions per role — retain, redeploy,
  develop, or exit — with rationale documented

• Severance and transition plans for any exits, reviewed for legal
  compliance

• A communication plan — who hears what, when, and from whom

• Updated job descriptions and accountability charts for the
  post-reset org

• A post-reset org health monitoring cadence installed and running

The work, decomposed

• Sub-objective: Map the current state → org chart, role
  descriptions, reporting lines, spans of control, loaded costs

• Sub-objective: Define the future state → 12-month strategy
  translated into functions, roles, and capabilities needed

• Sub-objective: Run the gap analysis → current vs. future, role by
  role, with retain/redeploy/develop/exit recommendations

• Sub-objective: Build the headcount plan → specific actions, costs,
  timelines, legal review

• Sub-objective: Communicate and execute → sequenced announcements,
  transition support, documentation updates

• Sub-objective: Install monitoring → ongoing org health metrics so
  the structure doesn't drift back

How it runs in HAPPEE

Agents involved

• Planning agent (Pam). Facilitates the end-to-end process. Builds
  the project timeline, sequences the decisions, surfaces dependencies,
  and keeps the owner moving through a difficult initiative without
  stalling. Maintains the gap analysis as a living document, not a
  one-time spreadsheet.

• Finance agent (Alex). Owns the numbers. Pulls payroll and benefits
  data, computes loaded costs per role, models severance scenarios,
  quantifies the cash-flow impact of each headcount decision, and
  connects the output to the cash forecast so the owner sees the
  financial consequence in real time.

• Operations agent. Handles the operational mechanics — drafts
  updated job descriptions, accountability charts, and transition
  timelines. Manages vendor communications if external HR counsel or
  outplacement services are engaged.

Where the work lives

• Knowledge Base — future-state org design, current-state org map,
  gap analysis, headcount plan, communication plan, updated job
  descriptions, decision log capturing the reasoning behind each
  retain/redeploy/develop/exit call

• Financial Models — loaded cost model by role, severance scenario
  analysis, cash-flow impact projections tied to the 13-week forecast

• Tracker — each role decision as a work item with a clear owner,
  status, and next step; the overall reset as an initiative with
  sub-objectives tracked to completion

• Analytics time-series — span of control ratios, role clarity
  scores, exit interview themes, headcount vs. plan, payroll as
  percentage of revenue

• Dashboards (Live Views) — org health dashboard showing key metrics
  post-reset, visible to the owner daily

• Channels — #org-reset for the project team during the active
  reset; #leadership for ongoing org health posts afterward

• Recurring meetings — weekly reset check-in during the active
  project; monthly org health review after completion

• Notifications — alerts when org health metrics drift outside
  thresholds (span of control expanding, role vacancy exceeding target
  duration)

Rhythms

• Weekly (during the reset) — Pam posts project status: decisions
  made, decisions pending, blockers. Alex updates the cost model with
  any changes. The owner reviews and makes the calls that only a human
  should make.

• Monthly (post-reset) — org health review: span of control drift,
  role clarity scores, exit interview themes, headcount vs. plan. Pam
  prepares the brief; the owner reads it and acts on outliers.

Data flows

• Payroll and benefits data → loaded cost model → gap analysis cost
  column

• Future-state design + current-state map → gap analysis → headcount
  plan

• Headcount decisions → severance model → cash forecast impact

• Post-reset org metrics → time-series → org health dashboard →
  threshold alerts

Before HAPPEE vs. with HAPPEE

Day in the life

Wednesday, 8am, week three of the reset. Pam's morning brief in
#org-reset is direct: 28 of 34 role decisions are finalized, 4 are
pending the owner's call, and 2 are waiting on legal review of severance
terms. Alex has updated the cost model overnight — the headcount plan as
it stands reduces loaded payroll by $380K annually, and the severance
cash outlay of $95K hits weeks 4 through 8 of the 13-week forecast.
The forecast still clears the $35K trigger threshold, but barely.
Alex flags the option to stagger two of the exits by three weeks to
smooth the cash impact, with a modeled comparison. The owner reviews
the four pending decisions — two are clear, two need a conversation
with the department lead first. She schedules those for Thursday
morning, approves the staggered exit timeline, and moves on. Pam
updates the tracker. By Friday, legal has cleared the severance
language, and the communication plan for next Monday's announcements
is drafted and waiting for the owner's review. The whole process is
painful, but it isn't chaotic — and every decision has a paper trail.

Related Initiatives

• Stabilize cash with a 13-week forecast
• Operating expense audit and vendor consolidation
• Customer concentration and churn diagnosis
• Sales team hiring and onboarding

Features in play: Knowledge Base · Financial Models · Tracker · Workflows · Analytics & Dashboards · Channels · Meetings · Notifications · Reminders & Decisions · Agents