GTM Org Chart, Roles and Hiring Plan — Implementation

Project One-Pager

Quick reference for architects. One per project type. Fill this out FIRST — it serves as the project's identity card.

GTM Org Chart Roles and Hiring Plan One-Pager

Project Type

• Category: Strategic
• Primary Deliverable: Complete GTM organizational blueprint — current-state org chart, future-state org design tied to revenue triggers, standardized role definitions with career ladders, and a phased hiring plan

Phase Relevance

Phase	Applies?	Notes
1. Strategy	Yes	3-5 refinement loops across leadership interviews
2. Engineering	Optional	Doc creation only — no CRM/system config
3. Enablement	Yes	Training on how to use the org design and hiring roadmap
4. Handoff	Yes	Internal + External — HR/People team receives docs

· · ·

Phase Overview

  ┌──────────────┐     ┌──────────────┐     ┌──────────────┐     ┌──────────────┐
  │ 1. STRATEGY  │────▶│ 2. ENGINEER  │────▶│3. ENABLEMENT │────▶│  4. HANDOFF  │
  │    Heavy     │     │    Light     │     │    Medium    │     │    Medium    │
  │ 1a→1b→1c→1d │     │ 2a→2b→2c→2d │     │ 3a→3b→3c→3d │     │ 4a→4b→4c→4d │
  └──────────────┘     └──────────────┘     └──────────────┘     └──────────────┘
   3-5 refinement       Doc production       Training on org      HR/People team
   loops + interviews   (no CRM config)      design + hiring      receives docs

This project's flow:

• Full 4-phase. Heavy strategy (60-70%), light engineering (10-15%), medium enablement (15-20%), standard handoff.
• Phase 2 is document production — creating polished org chart visuals, role documentation packages, and hiring roadmap spreadsheets. No CRM or system configuration.
• Some customers skip 3c Hypercare if their HR/People team is mature and can adopt independently.

· · ·

Pre-Kickoff (1a)

Track A: Customer Homework

• Watch intro video on GTM org design principles and what the engagement covers
• Complete intake form with current headcount, revenue data, growth projections
• Provide existing org charts, HRIS data, and any role documentation
• Get exec sponsor alignment on project scope (org design only vs. including hiring plan)

Track B: Architect Prep

• Review intake form and map current-state org structure from provided data
• Pull industry benchmarks for similar-stage B2B SaaS org structures
• Draft v0 current-state org chart from available data
• Prepare gap analysis framework and interview guide

· · ·

Refinement Loop (1b → 1c → 1d)

Meeting	Sub-Phase	Focus	Stakeholder	Output
Kickoff	1b	Present v0 org chart, gather corrections, validate	VP Sales, CRO, CEO	Info for v1 org chart
Leadership Interviews	1c	Individual interviews with GTM leaders	VP Sales, VP Mktg, VP CS, RevOps	Interview summaries, gap findings
Role Definition	1c	Review proposed job families, levels, career paths	GTM Leaders + HR/People	Draft role definitions
Future-State Design	1c	Present future-state org with revenue triggers	Exec Sponsor + Finance	Revenue-triggered org roadmap
Hiring Plan Review	1c	Review phased hiring roadmap and budget alignment	VP Sales, CRO, Finance	Draft hiring plan
Sign-Off	1d	Full package review and strategic approval	All stakeholders	Final approved org design + hiring plan

· · ·

Phase Checklists

Phase 1: Strategy

• 1a. Pre-Kickoff complete (Track A + Track B)
• 1b. Kickoff call held
• 1c. Refinement loop complete (v0 → vFinal)
• 1d. Strategic sign-off obtained

Phase 2: Engineering

• 2a. Document spec created (polished visuals, templates)
• 2b. Internal review of deliverables
• 2c. Document package built (org charts, role docs, hiring roadmap)
• 2d. Customer review and sign-off on deliverable formats

Phase 3: Enablement

• 3a. Training materials prepped
• 3b. Training sessions delivered (Leadership + HR/People team)
• 3c. Hypercare period complete (if applicable)
• 3d. Enablement sign-off

Phase 4: Handoff

• 4a. Maintenance schedule documented and handed off
• 4b. Internal handoff (SME → Architect) complete
• 4c. External handoff (LeanScale → Customer) complete
• 4d. Project closed and archived

· · ·

Document Types

Working Documents (iterate together)

Document	Purpose	When Complete
GTM Leadership Interview Notes	Capture insights, pain points, and org gaps	All interviews complete, themes compiled
Current-State Org Chart (draft)	Map existing GTM structure	All roles, reporting lines, headcount mapped
Gap Analysis Table	Identify structural gaps, overlaps, and issues	Gaps prioritized by impact
Role Definition Working Doc	Draft job families, levels, responsibilities	All GTM roles defined, KPIs assigned
Hiring Prioritization Matrix	Stack rank immediate and future hiring needs	Roles sequenced by impact and timing

Deliverables (polished outputs)

Deliverable	Created From	Customer Uses For
Current-State Org Chart (visual)	Draft org chart + interview data	Board presentations, internal alignment
Future-State Org Chart (visual)	Gap analysis + growth projections	Strategic planning, board communication
Role Documentation Package	Role definition working doc	HR implementation, job postings, reviews
Career Ladder Visuals	Role definition working doc	Employee communication, retention
Phased Hiring Roadmap	Prioritization matrix	Recruiting planning, budget approval
Revenue Trigger Matrix	Future-state design	Decision-making on when to hire

· · ·

Enablement Details

Training Types

Type	Audience	Focus	Duration
Leadership	CRO, VP Sales, CEO	How to use the org design for strategic decisions	45m
HR/People	Head of People, HR Manager, Recruiters	Role docs, career ladders, hiring playbooks	60m
Technical	RevOps, Ops Managers	Maintaining org chart, updating hiring triggers	30m

Hypercare

• Applies: Yes (optional based on HR maturity)
• Duration: 2 weeks
• Office Hours: Weekly 30-min slot for questions on role definitions or hiring plan execution

Training Assets to Create

• Video walkthrough: Org chart walkthrough (current-state and future-state)
• Video walkthrough: Hiring roadmap walkthrough with revenue trigger explanations
• Doc: Role documentation template for future role additions
• Doc: How to update the hiring plan as revenue milestones change

· · ·

Handoff & Retention

Internal Handoff (SME → Architect)

• Key context for Architect: Which revenue triggers are closest, any stakeholder sensitivities around org changes, any roles that were deprioritized but may resurface
• Escalation trigger: Any structural org redesign request, new market entry requiring new roles, or material change in growth projections

External Handoff (LeanScale → Customer)

• Final meeting agenda: Review org design, hiring plan, documentation package, maintenance cadence, Q&A
• Documentation package: Org chart visuals, role documentation, career ladders, hiring roadmap, revenue trigger matrix, training recordings, written guides

Maintenance Schedule

• Quarterly review of hiring plan progress against revenue triggers
• Who owns: Single project = customer's Head of People owns | Dedicated = Architect owns

Retention/Expansion Path

If Single Project: Upsell: Managed Services → if no → Downsell: Another project (e.g., Quotas & Target Setting, Compensation Plan Design) → Retry retainer

If Multi-Project (Dedicated):

• Refinement check-in scheduled: ~1 quarter after handoff
• Internal prep trigger: 2 weeks before
• Decision: Architect handles / SME needed

· · ·

Definition Alignment Terms

Term	Typical Definition
Job Family	A grouping of related roles that share similar skills and career progression (e.g., SDR → AE → AM)
Level	A position within a job family indicating scope, complexity, and seniority (e.g., Associate, Senior, Principal)
Span of Control	The number of direct reports a manager oversees — typical B2B SaaS benchmark is 6-8 for complex sales, up to 10 for transactional [1]
Revenue Trigger	A specific ARR, headcount, or customer count milestone that signals when to add a role or management layer
Career Ladder	A documented progression path showing how an IC or manager advances within a job family
IC Track	Individual Contributor career path — advancement without people management responsibilities
Management Track	Career path involving people leadership and team management responsibilities
Future-State Org	The target organizational structure designed to support projected revenue growth over 12-24 months
Hiring Roadmap	A sequenced, time-bound plan for adding headcount tied to revenue triggers and budget constraints

· · ·

Common Gotchas

• Designing only for the current revenue stage instead of 18 months out → Always include future-state with revenue triggers. Companies that design only for today face constant reorganization [2]
• Creating new silos while removing old ones → Include cross-functional collaboration requirements in every role definition and build regular coordination touchpoints into the structure
• Building a hiring plan without Finance sign-off → Involve Finance from the first interview round, tie hiring triggers to revenue milestones that fund the headcount
• Ignoring career path impact on retention → 94% of employees would stay longer at companies that invest in career development [3]. Document career ladders explicitly for every role
• Stakeholder disagreement on role ownership → Use the Definition Alignment Document to force written agreement before designing the org chart. "Who owns expansion revenue?" is a question that derails projects if not resolved early
• Comparing to aspirational companies instead of stage-appropriate peers → Benchmark against companies at similar ARR ($5M-$100M), not industry leaders at $500M+

· · ·

Methodology Options (if applicable)

Option	When to Use	Complexity
Org Audit Only	Client needs clarity on current state but has no immediate growth plans	Low
Full Org Design + Hiring	Client is growing and needs both future-state design and hiring plan	Medium
Full Design + Hiring Playbooks	Client also needs structured interview guides and onboarding plans for key roles	High

---

Phase 1: Strategy

Goal: Get stakeholder sign-off on the GTM org design, role definitions, and hiring plan.

Output: Definition Alignment Document + Current-State Org Chart + Future-State Org Design + Role Documentation + Hiring Roadmap (all signed off by stakeholders).

1a. Pre-Kickoff

Two parallel tracks run after the AE closes and before the kickoff call.

Track A: Customer Homework

What we send:

Item	Purpose	Format
Intro video	Explain what an org design project covers and why it matters	Video (5-10 min)
Definition Alignment Document	Get stakeholder sign-off on key organizational terms	Google Doc
Pre-filled intake form	Capture current headcount, revenue data, growth projections, existing org charts	Google Form or Doc

The intake form asks for: current ARR, rep count by function, growth targets (12-24 months), existing org chart or HRIS export, any open requisitions, and known structural pain points.

Completion tracking: Someone's job to follow up. Don't cancel kickoff if incomplete, but push hard after. The intake form is critical — without headcount data and revenue projections, the Architect cannot build a useful v0.

Track B: Architect Prep

What the Architect does:

Step	Action	Output
1	Review intake form, HRIS data, and existing org charts	Raw data collected and organized
2	Pull industry benchmarks for similar-stage B2B SaaS orgs	Benchmark reference set
3	Build v0 current-state org chart from intake data + benchmarks	v0 current-state org chart (all ASSUMED)
4	Run gap analysis comparing current org to benchmarks	Draft gap analysis with flagged issues
5	Prepare kickoff assets: org chart visual, interview guide, questions list	Presentation-ready materials

Critical: Mark everything as ASSUMED. The kickoff call and leadership interviews validate.

Stakeholder Alignment Document

Get stakeholder sign-off on terms BEFORE building anything.

Term	Our Definition	Internally Approved?
Job Family	A grouping of related roles with shared skills and career progression	[ ] Yes / [ ] No
Level	Seniority tier within a job family (Associate, Senior, Principal, etc.)	[ ] Yes / [ ] No
Span of Control	Number of direct reports per manager — we recommend 6-8 for complex sales	[ ] Yes / [ ] No
Revenue Trigger	ARR/headcount milestone that signals a new hire or management layer	[ ] Yes / [ ] No
IC vs Mgmt Track	Two parallel career paths — advancement without or with people management	[ ] Yes / [ ] No
GTM Function Scope	Which functions are in-scope (Sales, Marketing, CS, RevOps, Partnerships)	[ ] Yes / [ ] No

Instructions to customer:

Review each definition with your leadership team. Check "Yes" when approved. We cannot proceed until all terms are aligned. Pay special attention to "GTM Function Scope" — this determines the breadth of our org design work.

---

1b. Kickoff Call

Purpose: Present v0 current-state org chart and get alignment. We walk in with work done — customer reacts, not creates from scratch.

Agenda (60-90 min)

Time	Topic	What Happens
0-15	Walk through v0 org chart	"Here's what we mapped from your intake data and HRIS"
15-30	Validate assumptions	ASSUMED roles/lines → CONFIRMED or corrected
30-40	Review gap analysis	Present initial gaps identified from benchmark comparison
40-50	Definition alignment	Review Definition Alignment Doc terms
50-60	Interview scheduling	Schedule individual GTM leader interviews
60+	Next steps	Assign homework, set expectations for interview round

What We Bring

• v0 current-state org chart (built in Track B prep)
• Benchmark comparison for company stage (ARR, headcount ratios)
• Draft gap analysis highlighting potential structural issues
• Definition Alignment Document (pre-filled with our recommendations)
• Interview guide with customized questions per leader

What We Leave With

• Corrections on v0 org chart (info needed to create v1)
• Confirmed definitions (or clear blockers if stakeholder sign-off needed)
• Interview schedule with GTM leaders (VP Sales, VP Marketing, VP CS, RevOps)
• Clear homework assignments (e.g., "provide updated HRIS export," "confirm open reqs")

---

1c. Alignment Loop & Strategic Meeting Cadence

Purpose: Iterate on the org design and hiring plan through leadership interviews and refinement meetings.

The Pattern

Kickoff Call (present v0 org chart, gather corrections)
    ↓
Update org chart → v1
    ↓
Leadership Interviews (4-6 individual sessions, gather deep input)
    ↓
Gap Analysis + Role Definition → draft role docs, gap analysis
    ↓
Future-State Design Meeting (present future-state org + revenue triggers)
    ↓
Hiring Plan Meeting (review phased roadmap, budget alignment)
    ↓
Final Review → Sign-off

Before Each Meeting

1. Process previous meeting notes and interview transcripts
2. Update org chart, gap analysis, or role definitions (v[n-1] → v[n])
3. Prepare questions for next validation round
4. Run relevant analysis (gap analysis, role definition, or hiring plan) with latest inputs

During Each Meeting

1. Walk through current version of relevant deliverable
2. Capture corrections and refinements
3. Validate what's now CONFIRMED
4. Identify remaining ASSUMED items and missing data

After Each Meeting

1. Update deliverables based on meeting output
2. Track what moved from ASSUMED → CONFIRMED
3. Update working documents and flag any blockers

Meeting Types for This Project

Meeting Type	Focus	Stakeholder
Kickoff	Present v0, validate current-state, schedule interviews	VP Sales, CRO/CEO
GTM Leader Interviews	Deep-dive on roles, gaps, pain points per function	Individual: VP Sales, VP Mktg, VP CS, RevOps
Gap Analysis Review	Present findings, prioritize structural issues	VP Sales + RevOps
Role Definition Workshop	Review job families, levels, career ladders	GTM Leaders + HR/People
Future-State Design	Present future-state org with revenue triggers	Exec Sponsor + Finance
Hiring Plan Review	Review phased hiring roadmap, budget alignment	CRO/CEO + Finance
Final Review	Full package walkthrough, sign-off	All stakeholders

Typical Timeline

Milestone	Timing
Pre-kickoff prep	2-3 days
Kickoff call	Day 1 of engagement
Leadership interviews	Week 1-2 (4-6 sessions over 2 weeks)
Refinement meetings	Week 2-3 (gap analysis, role definitions, future-state)
Final review + sign-off	Week 3-4 (when all inputs CONFIRMED)

---

1d. Strategic Sign-Off

Purpose: Confirm we have everything before proceeding to document production.

Validation Checkpoint

• Definition Alignment Document signed off by stakeholders
• Current-state org chart validated and CONFIRMED by all GTM leaders
• Gap analysis reviewed and accepted — all critical gaps addressed in future-state
• Future-state org design approved with revenue triggers documented
• Role definitions (job families, levels, KPIs) reviewed by current role holders and managers
• Career ladders approved — both IC and management tracks defined
• Hiring plan reviewed by Finance — budget alignment confirmed
• Customer understands what we're producing in Phase 2 (polished docs)
• No blockers for document production

Decision Point

• Proceed to Engineering (Document Production) → Customer wants polished deliverables produced
• Project complete → In rare cases, the strategic working documents are sufficient and customer does not need polished visuals/packages

Most customers proceed to Phase 2 because leadership and board communication requires polished org chart visuals and formatted role documentation. The strategic working documents alone are rarely the final product.

---

Phase 2: Engineering

Goal: Produce polished, presentation-ready deliverables from the approved strategic working documents.

Output: Visual org charts, formatted role documentation package, hiring roadmap spreadsheet, career ladder visuals — all ready for customer to use internally.

Project Type	Engineering Weight	What This Means
This project	Light (10-15%)	Document production only — no CRM or system config

Sub-Phases

2a Doc Spec → 2b Internal Review → 2c Build (Doc Production) → 2d Customer Review

---

2a. Doc Spec

Purpose: Define the format, structure, and visual standards for all deliverables.

Input: Signed-off strategic package from Phase 1 (org charts, role definitions, hiring plan)

What happens:

1. Architect determines deliverable formats based on customer's systems (Google Slides, PowerPoint, Notion, etc.)
2. Architect selects org chart visual tool (Lucidchart, Miro, Figma, or slide-based)
3. Architect outlines the role documentation structure (template for each role)
4. Architect defines hiring roadmap spreadsheet structure (columns, filters, views)

Output: Deliverable specification containing:

• Format and tool for each deliverable
• Structure/layout for org chart visuals
• Role documentation template (sections, fields)
• Hiring roadmap spreadsheet schema

---

2b. Internal Review

Purpose: Review deliverable specs before building.

Agenda (30 min):

Time	Topic	What Happens
0-10	Walk through spec	Architect explains format choices and layout decisions
10-20	Review against strategy	Verify deliverables match signed-off strategy
20-30	Finalize approach	Confirm structure, flag any formatting concerns

---

2c. Build (Document Production)

Purpose: Create polished deliverable package.

Input: Approved doc spec + signed-off strategic working documents

Build components:

• Current-state org chart visual (polished, color-coded by function, headcount annotated)
• Future-state org chart visual (with revenue triggers annotated, new roles highlighted)
• Transition view showing phased org changes over time
• Role documentation package (all GTM positions: summary, responsibilities, KPIs, competencies)
• Career ladder visuals (by job family, IC and management tracks)
• Hiring roadmap spreadsheet (roles, triggers, timing, budget, priority)
• Revenue trigger matrix (ARR/headcount thresholds mapped to org changes)
• Title taxonomy document (standardized titles mapped to old titles)

Execution approach: Manual build — document production does not lend itself to automation. Architect creates each deliverable with attention to visual quality and consistency.

---

2d. QA / Review + Sign-Off

Purpose: Verify deliverables are accurate, complete, and presentation-ready.

Two types of review:

Type	Who	Purpose
Internal QA	Architect + peer	Verify accuracy against strategic docs, check formatting
Customer Review	Customer	Verify deliverables are usable for their internal needs

Internal QA checklist:

• Org chart headcount matches approved numbers
• All roles from strategy appear in role documentation
• Career ladders are internally consistent (no dead-end paths)
• Hiring plan totals match budget discussed with Finance
• Revenue triggers are consistent across org chart and hiring roadmap
• Title taxonomy maps correctly to current titles
• Visual quality is presentation-ready (board and leadership meetings)

Customer review:

• Walk customer through each deliverable
• Verify formatting works for their internal systems
• Capture feedback on layout, terminology, or emphasis
• Make final adjustments

Document production sign-off checkpoint:

• All deliverables match signed-off strategy
• Customer has reviewed and approved formats
• Deliverables are ready for enablement
• No outstanding formatting or content issues

---

Phase 3: Enablement

Goal: Customer team can actually use the org design, role documentation, and hiring plan independently.

Output: Trained leadership and HR/People team with documentation, capable of executing the hiring plan and maintaining the org design.

Sub-Phases

3a Training Prep → 3b Training Sessions → 3c Hypercare → 3d Enablement Sign-Off

---

3a. Training Prep

Purpose: Create training materials from the strategic and deliverable documentation.

Input: Complete deliverable package from Phase 2

What happens:

1. Architect identifies training audiences and their specific needs
2. Architect creates training scripts and presentation materials
3. Architect prepares FAQ based on common questions from similar org design projects

Output: Training package containing:

• Video script: Org chart walkthrough (current-state, future-state, transition)
• Video script: Hiring roadmap and revenue trigger explanation
• Written guide: How to update the org chart and hiring plan as conditions change
• Written guide: How to use role documentation for job postings, performance reviews, and career conversations
• FAQ: Common questions about org design changes, role definitions, and hiring sequencing

---

3b. Training Sessions

Purpose: Transfer knowledge to customer team.

Two types of training:

Type	Audience	Focus
Leadership training	CRO, VP Sales, CEO	How to use org design for strategic decisions, when revenue triggers fire
HR/People training	Head of People, Recruiters	How to use role docs for hiring, how to execute the hiring roadmap
Ops training	RevOps, Ops Managers	How to maintain the org chart, update headcount data, track trigger metrics

Session details:

• Leadership session (45 min): Walk through future-state org design rationale, revenue triggers and decision tree, how to communicate org changes internally. Focus on "when you hit $X ARR, here's what changes and why."
• HR/People session (60 min): Walk through role documentation package, career ladders, title taxonomy, hiring roadmap execution. Focus on "how to post these roles, interview for them, and track progress."
• Ops session (30 min): Walk through where documentation lives, how to update headcount tracking, how to monitor revenue trigger metrics. Focus on "how to keep this current."

Training delivery:

1. Schedule sessions with appropriate stakeholders
2. Deliver training live (record for reference)
3. Record video walkthroughs for future team members
4. Answer questions, note gaps for FAQ updates

Output:

• Trained stakeholders across three audiences
• Video recordings
• Questions log (feeds into FAQ)

---

3c. Hypercare

Purpose: Support the customer during initial adoption of the org design and hiring plan.

Duration: 2 weeks (optional based on HR/People team maturity)

What happens:

• Quick response to questions about role definitions or career ladder interpretation
• Office hours: weekly 30-min slot for Q&A
• Support for first hiring plan execution decisions (e.g., "Should we hire this role now based on where we are?")
• Review any early-stage org changes the customer is considering

When to skip: Customers with a mature HR/People team and clear ownership of the hiring plan may not need hypercare. Strategic-only projects where the deliverable is a recommendation document often skip this.

Output: Customer team is confidently using the org design documentation and actively executing the hiring plan.

---

3d. Enablement Sign-Off

Purpose: Confirm customer can operate independently.

Validation checkpoint:

• All training sessions delivered (Leadership, HR/People, Ops)
• Training recordings and documentation provided
• Hypercare period complete (if applicable)
• No critical questions outstanding
• HR/People team can independently use role documentation for hiring
• Leadership can independently interpret revenue triggers
• Ready for handoff

Decision point:

• Proceed to Handoff → Customer is enabled, project wrapping up
• Extend Hypercare → Customer still needs support on hiring plan execution or role definition interpretation

---

Phase 4: Handoff

Goal: Clean project close with maintenance plan established and retention/expansion path set.

Output: Maintenance schedule documented, internal context transferred, customer owns the org design and hiring plan, project archived, future revenue path established.

Structure:

4a Maintenance Schedule → 4b Internal Handoff → 4c External Handoff → 4d Project Close
                          (SME → Architect)     (LeanScale → Customer)  (Archive + Debrief)

Maintenance ownership by engagement type:

Engagement Type	Who Owns Maintenance	Handed Off At
Single Project	Customer owns	4c (External Handoff) — customer receives maintenance schedule and runs it themselves
Dedicated (Multi-Project)	Architect owns	4b (Internal Handoff) — Architect receives maintenance schedule and runs it for customer

---

4a. Maintenance Schedule

Purpose: Document what needs ongoing attention after the project is complete — cadences, tasks, triggers for re-engagement.

Standard Maintenance Framework

Monthly Tasks:

Monthly Task	What to Check	Red Flag Threshold
Hiring Plan Progress	Actual hires vs. planned hires for the month	>1 month behind on critical hires
Revenue Trigger Monitor	Current ARR/headcount vs. next trigger threshold	Within 10% of trigger with no hiring activity started
Open Req Status	Are open requisitions progressing through pipeline	Any critical role open >60 days without candidates

Quarterly Tasks:

Quarterly Task	What to Review	Action if Off-Track
Org Chart Accuracy Audit	Does the actual org match the documented design?	Update chart, investigate why divergence occurred
Span of Control Check	Are any managers over/under the target SOC range?	Adjust team assignments or plan for new manager
Role Definition Relevance	Have any roles materially changed in scope?	Update role documentation, notify affected employees
Hiring Plan vs. Revenue	Are revenue triggers firing? Is hiring keeping up?	Accelerate or decelerate hiring based on actuals

After First Business Cycle (90 days post-launch):

• Review whether first 1-2 hires from the plan are on track
• Validate that revenue triggers are calibrated correctly against actual growth
• Check if career ladder conversations are happening in 1:1s
• Assess whether the org chart changes have been communicated to all affected employees

Refinement Triggers (when to re-engage):

Trigger	Threshold	Response
Revenue growth acceleration	ARR growing >30% faster than projected	Accelerate hiring plan, review future-state for earlier triggers
Revenue growth deceleration	ARR growing >30% slower than projected	Pause non-critical hires, adjust trigger thresholds
Unexpected attrition	>2 GTM leaders or >15% of GTM team leaves	Emergency org review, reprioritize hiring plan
M&A or new market entry	Any acquisition or new geography/vertical	Full org design refresh required — scope new project
Org chart divergence	>3 roles exist that are not in the documented org	Update documentation, assess if structural redesign needed

Every 6-12 Months:

• Full org chart refresh against actual headcount and structure
• Career ladder review — are employees progressing as designed?
• Hiring plan recalibration based on actual revenue trajectory
• Benchmark refresh — are comp bands and role definitions still market-competitive?
• Revenue trigger recalibration based on actual vs. projected growth patterns

---

4b. Internal Handoff (SME → Architect)

Purpose: Transfer context so Architect can manage ongoing relationship.

What the Architect needs to know:

• What was built and why: GTM org design, role documentation, career ladders, hiring plan tied to revenue triggers
• Customer context: Which stakeholders were most engaged, any sensitivities around title changes or reporting line changes, any roles that were contentious
• Common issues: Questions about career ladder interpretation, requests to re-sequence hiring plan, revenue trigger recalibration
• When to escalate back to SME: Any structural org redesign, new market/vertical requiring new roles, material change in growth trajectory

Escalation guidelines:

Issue Type	Who Handles	Example
Hiring plan timing questions, minor role tweaks	Architect	"Can we move this hire up one quarter?"
Structural org changes, new function creation	SME	"We're adding a Partnerships function"

For Dedicated engagements: Architect also receives the maintenance schedule (4a) and becomes responsible for executing it. SME walks Architect through each maintenance task, especially the revenue trigger monitoring.

---

4c. External Handoff (LeanScale → Customer)

Purpose: Formal project completion with customer.

Final project meeting:

• Review what was delivered (org charts, role docs, career ladders, hiring plan, trigger matrix)
• Walk through documentation package — where everything lives, how to find things
• Confirm nothing outstanding
• Answer final questions
• Make it explicit: "Project complete"
• For Single Project engagements: Hand over the maintenance schedule (4a) and walk the customer through each task

Documentation package:

• Current-state and future-state org chart visuals
• Role documentation package (all GTM positions)
• Career ladder visuals by job family
• Hiring roadmap spreadsheet with revenue triggers
• Revenue trigger matrix
• Title taxonomy document
• All training video recordings
• Written maintenance guides
• FAQ document
• Definition Alignment Document (final version)
• Maintenance Schedule

For Single Project engagements: Walk the customer through the maintenance schedule in detail. Record a video walkthrough. Emphasize the quarterly span-of-control check and revenue trigger monitoring — these are the highest-impact maintenance tasks.

Output: Customer owns the org design and hiring plan. Project formally complete.

---

4d. Project Close

Purpose: Clean internal wrap-up + establish retention/expansion path.

Archive Checklist

• All project artifacts saved to proper location
• Handoff documentation complete
• Project status updated in tracking system
• Time/billing finalized

Internal Debrief (Optional but Recommended)

• What went well?
• What would we do differently?
• Were the industry benchmarks accurate for this customer's stage?
• Any learnings about org design patterns to feed back into our benchmark library?

Retention / Expansion

Two paths based on engagement type:

Engagement Type	Path
Single Project	Upsell → Downsell → Retry
Multi-Project (Dedicated)	Schedule Refinement Check-In

Single Project Path:

1. Upsell: Managed Services (retainer — ongoing org optimization, hiring plan execution support)
   ↓ if no
2. Downsell: Another one-time project (Quotas & Target Setting, Compensation Plan Design, Sales Qualification Methodology)
   ↓ if yes
3. Retry retainer at end of next project cycle

Natural next projects after org design:

• Quotas & Target Setting (now that roles are defined, set their targets)
• Compensation Plan Design (now that career ladders exist, align comp bands)
• Sales Qualification Methodology (now that roles are clear, define the process)
• Forecasting Process (with the org structure in place, build the forecasting cadence)

Script:

"Now that your GTM org design and hiring plan are complete, there are two ways we can continue working together. Option 1: We can set you up on managed services where we help you execute the hiring plan and optimize the org as you scale. Option 2: A natural next step is Quotas & Target Setting — now that roles and career paths are defined, we can set the right targets for each role. Which sounds more interesting?"

Multi-Project (Dedicated) Path:

Schedule a refinement check-in at handoff:

"On [date ~quarter out], we'll review how the hiring plan is tracking against revenue triggers and see if any org adjustments are needed."

Internal prep (2 weeks before check-in):

Step	What Happens
1. Get pinged	System reminder: refinement check-in in 2 weeks
2. Review metrics	Pull hiring plan progress, revenue vs. triggers, org changes since handoff
3. Decide ownership	Can Architect handle this check-in, or need SME?
4. Prep materials	If SME needed, brief them. If Architect, prep talking points.

At the refinement check-in:

• Review hiring plan execution against original timeline
• Check revenue triggers — any that have fired or are approaching?
• Identify any org changes made since handoff and assess if documentation needs updating
• If minor: Architect handles tweaks to hiring plan
• If major: Scope new project (e.g., full org redesign due to M&A or pivot)

Output: Project archived. Future revenue path established. Ready for next engagement.

---

Deliverables & Assets Summary

Strategic Deliverables:

• Current-State Org Chart (visual) — complete GTM organization mapped with headcount, reporting lines, span of control metrics
• Future-State Org Chart (visual) — target organization design with revenue triggers annotated, new roles highlighted, transition timeline shown
• Gap Analysis Document — structural gaps, overlaps, and prioritized issues with recommendations
• Revenue Trigger Matrix — specific ARR, headcount, and customer count thresholds mapped to org changes

Documentation Deliverables:

• Role Documentation Package — all GTM positions with summary, 5-7 responsibilities, 2-4 KPIs, required competencies, reporting relationships
• Career Ladder Visuals — by job family, showing IC and management tracks with level criteria
• Title Taxonomy — standardized titles mapped to current titles with change management guidance
• Hiring Roadmap Spreadsheet — roles sequenced by trigger, with timing estimates, budget implications, and priority tiers

Enablement Deliverables:

• Training video recordings (org chart walkthrough, hiring roadmap walkthrough)
• Written guides (how to update org chart, how to use role docs, how to execute hiring plan)
• FAQ document (common questions about org design, role definitions, hiring decisions)
• Definition Alignment Document (final version)
• Maintenance Schedule

---

Appendix

What This Document Is

This is the implementation playbook — the step-by-step execution guide an Architect follows to deliver a GTM Org Chart Roles and Hiring Plan project from first contact to project close. See Advisory for project positioning and discovery questions. See Methodology for org design frameworks, benchmarking approaches, and role definition best practices.

What Each Phase Produces

Phase	Output	Gate Criteria
Phase 1: Strategy	Signed-off org design, role definitions, career ladders, hiring plan	All GTM leaders have approved, Finance has approved budget alignment
Phase 2: Engineering	Polished visual org charts, formatted role docs, hiring roadmap spreadsheet	Deliverables match strategy, customer has approved formats
Phase 3: Enablement	Trained leadership and HR/People team with documentation	All training delivered, hypercare complete, team can operate independently
Phase 4: Handoff	Independent customer + archived project	Internal/external handoffs complete, maintenance plan in place, project closed

How to Adapt Per Project Type

This project is strategic-heavy:

Project Profile	Strategy Weight	Engineering Weight	Enablement Weight	This Project
Strategic-heavy	60-70%	10-15%	15-20%	GTM Org Chart & Hiring Plan

Adaptation notes:

• Phase 1 is the core — most effort goes into leadership interviews, gap analysis, role definition, future-state design, and hiring plan development
• Phase 2 is document production only — creating polished visuals and formatted packages, no system configuration
• Phase 3 is important but focused — training three audiences (Leadership, HR/People, Ops) on using the deliverables
• Phase 4 always applies — maintenance schedule is critical because org designs degrade quickly without ongoing attention

---

References

[1] OpsDog - Span of Control: Sales Definition & Benchmarks

[2] Functionly - The Optimal SaaS Company Organizational Structure

[3] LinkedIn Learning - How Career Pathing Leads to Employee Retention

[4] LinkedIn - Employees Who Advance Internally Stay 41% Longer

[5] ResearchGate - Role Ambiguity and Employee Well-Being: The Critical Need for Clear Job Descriptions

[6] Knoetic - Span of Control Benchmarks

[7] SaaStr - What Is The Optimal Structure of an Initial SaaS B2B Sales Team