Archives: Documents

1. Purpose

The Headcount Plan Sheet is a central planning document that records all approved positions within the organization for a given financial year or quarter.

It ensures alignment between HR, Finance, and Business Leaders by providing visibility into:

• Hiring needs (role, level, department)
• Hiring timelines (by quarter/month)
• Budgeted compensation & benefits impact
• Status tracking of open vs. filled positions

2. Scope

Applies to:

• All departments (Tech, Design, QA, Sales, Marketing, HR, Operations, etc.)
• All employment categories (full-time, part-time, contract, intern)
• All geographies (onsite, hybrid, remote)
• Planning horizon: Minimum 1 year, updated quarterly

3. Ownership & Custodianship

• HR (Workforce Planning Lead): Maintains and updates the sheet weekly.
• Finance: Validates cost estimates against approved budgets.
• Department Heads: Submit headcount requests, justify needs, and approve timelines.
• CHRO/CEO: Final approval of additions or deletions.

4. Headcount Plan Sheet – Sample Structure with Entries

Position ID

Department

Role Title

Level/Grade

Employment Type

Location

Planned Hire Date

Approval Status

Budgeted CTC (Annual)

Benefits Cost

Total Cost (CTC + Benefits)

Hiring Manager

Recruiter Assigned

Current Status

Notes/Justification

HR-2025-01

Development

Senior Backend Developer

L3 – Consultant

Full-time

Jaipur – Hybrid

Q2 FY25

Approved

₹18,00,000

₹1,20,000

₹19,20,000

Head of Dev

Priya Sharma

In Progress

Scaling backend capacity for new client projects

HR-2025-02

Marketing

Digital Marketing Manager

L2 – Senior Assoc.

Full-time

Remote

Q3 FY25

Pending

₹12,00,000

₹80,000

₹12,80,000

Head of Mktg

Arjun Mehta

Open

Strengthening lead generation & branding efforts

5. Process Workflow (Usage)

The Headcount Plan Sheet is not just a record — it is an active workflow tool.

Each stage ensures alignment between business need, financial approval, and HR execution.

1. Quarterly Demand Submission
   • Department Heads evaluate their team capacity vs. business goals.
   • New role requests (including replacements for attrition) are shared with HR in a structured format.
   • HR consolidates all requests into the Headcount Plan Sheet to avoid duplication and track priorities.
2. Validation
   • Finance cross-checks each proposed role against the annual budget and cost structure.
   • The CHRO reviews alignment with the company’s strategy (e.g., are we scaling sales this quarter or pausing?).
   • Roles that don’t align with business goals or budget are marked On-Hold or Deferred.
3. Approval
   • Once Finance and HR validate, final sign-off is obtained from the CEO/Leadership.
   • Approval status in the sheet changes from “Pending” to “Approved.”
   • This ensures that hiring managers cannot initiate hiring without leadership’s explicit green light.
4. Execution
   • HR translates the approved positions into hiring priorities.
   • Roles are shared with Talent Acquisition (recruiters/agencies).
   • Each role status (Open → In Progress → Offer Made → Closed) is updated live in the sheet for visibility.
5. Tracking & Reporting
   • HR updates role status weekly.
   • The sheet feeds into dashboards that show:
     • How many roles are open vs. filled?
     • Which departments are on track or lagging?
     • Cost utilization vs. budget.
   • Leadership can see progress vs. plan at a glance.

6. Reporting & Monitoring

To make the Headcount Plan a living document, regular reviews are essential.

1. Monthly Summary
   • HR prepares a snapshot report showing:
     • Total planned hires vs. actual hires.
     • Roles are delayed or on hold.
     • Budget spent vs. budget allocated.
   • Shared with CHRO + Finance + Leadership for quick visibility.
2. Quarterly Review
   • Adjustments are made based on real-time business conditions:
     • Attrition: Extra headcount needed if exits are higher than forecast.
     • Project wins/losses: If a new client signs on, urgent roles may be added; if a project is lost, roles may be deferred.
     • Financial shifts: If revenues dip, hiring plans may be frozen or adjusted.
   • This ensures the plan is dynamic and responsive, not rigid.
3. Annual Audit
   • At year-end, HR and Finance conduct a plan vs. actual analysis:
     • How many approved roles were hired?
     • Were cost estimates accurate?
     • Did we over-hire or under-hire in any function?
   • Learnings from the audit are fed into the next year’s headcount planning cycle, improving accuracy.

1.1 Objectives (what this SOP must achieve)

Objective	Why it matters	How it’s enforced
Strategic alignment	Roles exist to deliver business outcomes, not ad‑hoc requests	Mandatory mapping to Job Family & Level; Leadership approval
Cost control	Prevent unplanned payroll creep	Finance budget validation before any approval
Role clarity & consistency	Fair titles, comparable levels across functions	Fit to Role/Level Architecture; HR validation gate
Traceability & compliance	Every change is reviewable and auditable	Central logging in Workforce Budget Sheet; document retention
Speed with discipline	Requests move fast but never bypass gates	Time‑bound SLAs and escalation path

1.2 When this SOP is used (triggers)

• New role creation (full‑time, intern/trainee, contract/fixed‑term).
• Replacement hire for an approved, vacant position.
• Role change (title change, level upgrade/downgrade, job family shift, scope/reporting change).
• Conversion (intern/contract → full‑time, or vice‑versa).
• Off‑cycle exception (urgent business need outside annual/quarterly plan).

Notes

• For bulk or programmatic changes (e.g., annual title standardization), run this SOP as a batch with a single approval pack.

• Role eliminations follow workforce planning & org design processes, not this SOP.

1.3 Expected outputs (deliverables)

Deliverable	Owner	Repository
Approved Role Request (Create/Change) with justification	HR (custodian) / Dept Head (author)	HRIS / MIC Docs Library
Budget validation note (salary band + OPEX impact)	Finance	Workforce Budget Sheet
Leadership decision record (Approve / Reject / Revise)	HR (records)	MIC Decision Log
Updated role master (family, level, title, reporting)	HR	Role/Level Register
Communication to stakeholders (HR, Finance, TA, Manager)	HR	Email/MIC Notice

1.4 Success measures (KPIs & SLAs)

Metric	Target
HR validation turnaround	≤ 5 business days from submission
Finance budget check	≤ 5 business days post‑HR validation
Leadership decision	≤ 5 business days post‑Finance confirmation
First‑time‑right submissions (no rework)	≥ 85%
Policy violations (unapproved hiring)	0 per quarter

1.5 Controls & risk coverage

• Segregation of duties: Request (Dept) ≠ , Validation (HR) ≠ , Budget check (Finance) ≠ , Approval (Leadership).
• Single source of truth: No action without an entry in the Workforce Budget Sheet and Role/Level Register.
• Exception governance: Any off‑cycle approval must cite business impact, cost, and expiry/regularization plan.

1.6 References (binding documents)

• Workforce Planning Governance Policy
• Role/Level Architecture Document
• Headcount Plan Sheet (Template)
• Workforce Budget Sheet (Template)

2. Scope

This SOP applies organization-wide and governs every case where a new role is created or an existing role is modified. It defines the boundaries of what is included, what is excluded, and who it applies to.

2.1 Applicability by Employee Type

• Full-time employees – All permanent roles, regardless of department or location.
• Interns & Trainees – Short-term learning roles that may later be converted into full-time.
• Contract / Fixed-Term Staff – Roles created for project-based or specialized assignments.
• Leadership Roles – Any new Manager, Director, VP, or CxO positions.

2.2 Applicability by Activity

This SOP must be followed whenever:

1. New role creation
   • Creation of a position not previously existing in the org chart.
   • Adding capacity in a new function, team, or job family.
2. Replacement hiring
   • Filling a role that exists in the workforce plan but is vacant due to resignation, termination, or transfer.
3. Role changes
   • Title changes (e.g., “Executive” to “Specialist”).
   • Level upgrades/downgrades (e.g., “Senior Consultant” to “Manager”).
   • Changes in reporting line or functional scope.
   • Cross-job-family movements (e.g., Developer → Project Manager).
4. Conversion
   • Intern or contractor being moved into a full-time role.
5. Off-cycle exceptions
   • Any urgent/unplanned role created outside the annual or quarterly workforce planning cycles.

2.3 Exclusions

This SOP does not apply to:

• Temporary workload allocation (e.g., assigning duties during an absence without changing title/level).
• Role eliminations/redundancies, which are covered under Workforce Planning and Exit/Restructuring policies.
• Freelancer/outsourced vendor engagements, governed by Procurement/Finance policies.

2.4 Mandatory Compliance

• All departments, business units, and leadership teams must follow this SOP.
• No role creation or modification may be implemented outside of this process.
• Any violation will be flagged as a policy breach and escalated to Leadership.

3. Responsibilities

This section defines role-wise accountability in the role creation/change process. Responsibilities follow the RACI (Responsible, Accountable, Consulted, Informed) model to ensure clarity and prevent overlap.

3.1 Department Heads / Hiring Managers

• Responsible for initiating requests with full justification.
• Provide details such as job family, level, reporting line, purpose, and outcomes.
• Ensure requests are aligned to business needs and project deliverables.
• Respond promptly to HR queries during validation.
• Communicate approved changes to their teams once HR confirms.

3.2 Human Resources (HR Department)

• Accountable for administering this SOP and maintaining governance.
• Validate role requests against the Role/Level Architecture and Workforce Planning Governance Policy.
• Ensure consistency in titles, levels, and career paths.
• Return incomplete or misaligned requests for revision.
• Maintain all documentation: Workforce Budget Sheet, Role Register, Approval Logs.
• Escalate non-compliance or violations to Leadership.

3.3 Finance

• Consulted for budget validation on all role requests.
• Review salary bands, benefits, and impact on approved workforce budget.
• Flag variances and recommend corrective action.
• Confirm financial feasibility before Leadership approval.
• Maintain records of cost validations linked to each approved/rejected request.

3.4 Executive Leadership / Leadership Committee

• Accountable for final decision-making.
• Review HR validation and Finance notes before granting approval.
• Approve, reject, or request revision for role creation/changes.
• Grant exception approvals for off-cycle or urgent requests.
• Ensure that role additions align with organizational strategy and long-term workforce planning.

3.5 Employees (Informational)

• Informed when their role is directly impacted by a change (e.g., reporting structure, title adjustment).
• Must be notified formally through HR communication once the change is approved.

3.6 RACI Summary Table

Activity	Department Head	HR	Finance	Leadership	Employees
Initiate role request	R	C	I	I	I
Validate against Role Architecture	C	R/A	C	I	I
Budget validation	I	C	R/A	C	I
Final approval decision	I	C	C	R/A	I
Record-keeping & audit	I	R/A	C	I	I
Communication of approved changes	R	R	I	I	I

4. Procedure

All role creation or change requests must strictly follow the steps below. No role may be created, filled, or modified outside of this process.

Step 1: Request Initiation (Department Head)

• The Department Head raises a formal request using the prescribed Role Request Form / Headcount Plan Sheet.
• Mandatory fields include:
  • Job Family and Level (as per Role/Level Architecture),
  • Role title, reporting line, and purpose,
  • Expected outcomes / key accountabilities,
  • Justification (business need, project requirement, attrition replacement, or new capability).
• Replacement requests must also include the name of the outgoing employee and anticipated transition timelines.
• The request is submitted to HR through the designated HRIS / MIC workflow.

Step 2: HR Validation (HR Department)

• HR reviews the request within 5 business days to ensure:
  • Alignment with Role/Level Architecture (no duplication or misclassification),
  • Consistency of title, scope, and level,
  • Compliance with the Workforce Planning Governance Policy.
• If the request is incomplete or misaligned, HR returns it to the Department Head with feedback for correction.
• HR logs validated requests in the Workforce Budget Sheet for tracking.

Step 3: Budget Validation (Finance)

• HR forwards validated requests to Finance within 2 business days.
• Finance reviews cost implications within 5 business days, including:
  • Salary band validation against approved pay ranges,
  • Total workforce cost impact (salary + benefits + statutory costs),
  • Variance against the current Workforce Budget Sheet.
• Finance records its decision (Approved / Rejected / Requires Revision) and returns it to HR.

Step 4: Leadership Approval (Executive Leadership)

• HR consolidates HR + Finance notes and presents the request to Leadership.
• Leadership must provide a final decision (Approve / Reject / Revise) within 5 business days.
• Off-cycle or urgent requests must include explicit justification and may only be approved as exceptions.
• Leadership’s decision is final and binding.

Step 5: Documentation & Record-Keeping (HR)

• Once approved, HR must:
  • Update the Role/Level Register with the new or changed role,
  • Update the Workforce Budget Sheet with cost details,
  • File all supporting documents (request form, validation notes, approval decision) in the HRIS / MIC Documentation Library.
• Rejected requests must also be documented, with reasons for rejection.

Step 6: Communication

• HR communicates the decision to:
  • Department Head (for next steps),
  • Finance (for cost tracking),
  • Recruitment team (if new hiring is required).
• If the change impacts existing employees (e.g., promotion, reporting line change), HR issues a formal notification letter / email to the employee concerned.

Step 7: Escalation (if required)

• If a request is delayed or rejected at any stage, the Department Head may escalate through HR to Leadership.
• Any deviation from this procedure must be documented and explicitly approved by Leadership.

5. Timelines

To ensure efficiency and prevent delays, all activities under this SOP are bound by strict timelines. Departments, HR, Finance, and Leadership must comply with the following Service Level Agreements (SLAs):

5.1 Standard SLAs

Stage	Activity	Owner	SLA (Max)	Notes / Escalation
1	Request initiation	Department Head	As per workforce planning cycle	Must use prescribed form; incomplete requests not accepted.
2	Validation of role request	HR	5 business days	Requests pending >5 days escalate to HR Head.
3	Forward to Finance	HR	2 business days (after validation)	Delays flagged in Workforce Budget Sheet.
4	Budget validation	Finance	5 business days	If not closed in 5 days → escalate to Finance Head.
5	Consolidation & submission to Leadership	HR	2 business days (after Finance note)	Must attach HR & Finance validation notes.
6	Final approval decision	Leadership	5 business days	Off-cycle exceptions may require special Leadership review.
7	Documentation update	HR	3 business days (post-approval)	Role/Level Register, Workforce Budget Sheet, and archives updated.
8	Communication to stakeholders	HR	2 business days (post-approval)	Departments, Recruitment, Finance, and impacted employees informed.

5.2 Exception SLAs

• Off-Cycle Requests: Must be reviewed on a priority basis and closed within 10 business days end-to-end.
• Urgent Business Needs: Leadership may fast-track approval within 48 hours if justified in writing.

5.3 Monitoring & Reporting

• HR shall publish a Quarterly SLA Compliance Report to Leadership, highlighting:
  • % of requests closed within SLA,
  • Cases delayed and reasons,
  • Escalations raised.

6. Records & Compliance

6.1 Documentation Requirements

For every role creation or change request, HR must maintain a complete record consisting of:

• Role Request Form (new or change request with justification).
• Validation Notes (HR review outcome, alignment to Role/Level Architecture).
• Finance Validation Note (budget confirmation or variance flagged).
• Leadership Decision Record (approval, rejection, or revision).
• Communication Log (emails or letters sent to Department Heads, Recruitment, Finance, or employees).

6.2 Central Repository

• All records must be stored in the HRIS / MIC Documentation Library under version control.
• Each request must be tagged with a unique request ID for tracking.
• Rejected requests must also be archived with reasons.

6.3 Retention

• Role request records shall be retained for a minimum of five (5) years, or longer if required by statutory or legal compliance.
• Records related to leadership-level roles (Manager and above) must be retained for seven (7) years due to higher governance sensitivity.

6.4 Audit & Monitoring

• HR will conduct semi-annual audits of the Role/Level Register and Workforce Budget Sheet to verify:
  • All filled roles were created/changed through this SOP,
  • No deviations or unapproved hiring occurred,
  • Documentation completeness (forms, approvals, validations).
• Findings will be shared with Finance and Leadership, along with corrective action recommendations.

6.5 Compliance Enforcement

• Non-compliance with this SOP will be considered a policy breach under the Workforce Planning Governance Policy.
• Any unauthorized hiring or role change will be escalated directly to Leadership for corrective action.
• Repeated violations may trigger disciplinary action against the responsible Department Head or Manager.

7. Related Documents

This SOP must be read and applied in conjunction with the following policies, frameworks, and templates to ensure consistency and compliance:

1. Workforce Planning Governance Policy – Defines overall governance, approval flows, and workforce planning cycles.
2. Role/Level Architecture Document – Provides standardized job families, levels, and progression paths.
3. Headcount Plan Sheet (Template) – Standard format for initiating new role requests.
4. Role Change Request Form (Template) – Used for requesting modifications to existing roles.
5. Workforce Budget Sheet (Template) – Tracks approved headcount and financial impact.
6. Succession Matrix (Template) – Used to validate role criticality and identify backups.
7. Performance Management Policy – Ensures role changes and promotions align with fair evaluation practices.

Introduction & Ownership

Purpose of This SOP

This Standard Operating Procedure (SOP) outlines how Ideal Customer Profiles (ICPs) and Buyer Personas are developed, maintained, and operationalized across the business. These definitions serve as the strategic foundation for all demand generation, outbound prospecting, lead qualification, and messaging alignment efforts.

An accurately defined ICP and persona framework ensures:

• Marketing targets the right audience with the right message.
• Sales engages only qualified accounts that meet conversion criteria.
• Customer Success can anticipate goals and friction points post-sale.
• Product, strategy, and leadership teams remain aligned with market fit.

Scope of the SOP

This document applies to:

• Strategic targeting decisions.
• Operational filters in prospecting tools and ad platforms.
• Sales and marketing messaging frameworks.
• Lead qualification, scoring, and segmentation models.

It does not cover:

• Daily prospecting research (covered in the Sales SOP)
• Campaign execution or lead routing logic (covered in the Marketing/Sales SOPs)

Ownership & Responsibilities

Function	Responsibilities
Sales Leadership (Primary Owner)	Owns ICP definition based on win/loss data, deal qualification patterns, and buyer behavior. Oversees updates and version control.
Marketing Team (Collaborators)	Provides feedback from audience engagement (ads, campaigns, organic). Ensures personas align with content and campaign strategy
Customer Success (Optional Input)	Offers post-sale feedback on customer goals, usage patterns, and friction points.
RevOps / CRM Admin	Supports technical implementation of ICP filters and persona tags in CRM and scoring models.

Update Cadence

• Minor persona adjustments may be made quarterly based on campaign or engagement insights.
• Full ICP reviews are conducted bi-annually or following major business strategy shifts.
• All changes must be versioned, reviewed, and redistributed across Sales, Marketing, and CS teams.

ICP vs. Persona – Definitions & Use Cases

Why This Distinction Matters

A common failure in Sales and Marketing alignment stems from conflating Ideal Customer Profiles (ICPs) and Personas. Though interconnected, these two serve distinct strategic and operational functions.

Clear separation ensures:

• Sales teams prospect accounts that match strategic business goals. •
• Marketing targets people within those accounts with relevant messaging. •
• Product and CS teams understand both the organization’s fit and the individuals’ motivations.

Definitions

Term	Definition	Key Focus
ICP (Ideal Customer Profile)	A description of the company that is the best fit for your solution/service. It includes firmographics, techno-graphics, and strategic alignment.	Company-level fit
Persona (Buyer/Influencer)	A detailed profile of the individual decision-makers or influencers within the ICP. It focuses on roles, responsibilities, goals, and pain points.	Human behavior & decision roles

Use Cases by Department

Function	Uses ICP For…	Uses Persona For…
Sales	Filtering prospect lists, qualifying accounts, prioritizing outreach	Crafting email sequences, call scripts, and objection handling
Marketing	Building campaign audiences, segmenting ads, aligning content	Developing messaging, content strategy, and TOFU/BOFU offers
Customer Success	Understanding post-sale risk, account scaling potential	Managing stakeholder expectations, personalization during onboarding
RevOps / CRM	Scoring and routing logic, lead segmentation	Tagging contacts, enabling personalization fields in automation

When to Use What

Situation	Use ICP	Use Persona
Building a Prospect List	✅	❌
Creating a cold email script	❌	✅
Designing and campaign targeting	✅	✅
Segmenting CRM records	✅	✅
Planning a discovery call question bank	❌	✅
Running a closed-won account analysis	✅	✅ (Optional if notes are strong)

Data Sources for ICP & Persona Development

Purpose of This Step

This section defines the specific data sources—and the exact data points—that must be analyzed to create and update both the Ideal Customer Profile (ICP) and associated Buyer Personas. The goal is to remove guesswork and ensure that all targeting decisions are grounded in real performance indicators.

Who Executes This Step

Role	Responsibility
Sales Strategy / Sales Enablement	Leads the data review process for ICP and persona validation
RevOps / CRM Admin	Pulls and structures the relevant data sets
Marketing Analyst	Provides insight from campaign and engagement data
Customer Success Lead	Supplies feedback from onboarding and retention patterns

– Data for ICP Definition (Company-Level)

These data points directly support firmographic, technographic, exclusion, and strategic fit filters for
defining your ICP.

Data Source	Specific Fields to Pull	Why It Matters	Where to Use It
CRM – Closed-Won Deals (Past 12–24 Months)	Industry, Company Size, Region, Deal Size, Sales Cycle Length	Shows real conversion patterns	Define firmographic boundaries for high- probability accounts
CRM – Closed-Lost Deals	Loss reason, industry, deal size, competitor involved	Identifies weak-fit segments	Build exclusion rules or identify risk segments
Churn Reports (From CS or RevOps)	Account size, industry, onboarding notes, renewal loss reasons	Reveals post-sale misalignment	Flag high-risk sectors from ICP
Expansion/Upsell Data	Average revenue increase by segment or vertical	Shows which verticals grow best	Prioritize ICP segments with LTV upside
Delivery Fit Trends (From CS/Project Teams)	Project timeline accuracy, scope changes, stakeholder alignment, success feedback.	Identifies where delivery was smooth, value was clear, and collaboration was strong—indicates strategic ICP fit.	Prioritize company types (size, industry, decision structure) that enable successful long- term delivery.
Competitor Intelligence	Which accounts use competing platforms	Used for displacement opportunities	Supports technographic mapping & outreach positioning

– Data for Persona Definition (Contact-Level)

This supports role-based messaging, decision flow mapping, and qualification logic for individuals within the ICP.

Data Source	What to Analyze	Why It Matters	Persona Insight Unlocked
Discovery & Demo Call Logs	Common objections, priorities by role, concerns	Shows what each persona cares about	Pain point narratives and value messaging
Call Transcripts / AI Summary Tools	Language used by buyers (e.g., tech-heavy vs. strategic)	Helps shape messaging tone	Buyer communication style
Campaign Engagement Reports	Open/click/download by job title or function	Shows what content works for whom	Persona-based content interest
Form Submissions & Webinar Registrations	Titles and departments interacting with campaigns	Maps funnel stage vs. function	Role-based intent behavior
CS Feedback (Post-Sale Onboarding)	Who attends onboarding, who raises flags	Reveals hidden influencers or gatekeepers	Expands or refines persona map

– Additional Contextual Sources (Optional, But Powerful)

Source	Use Case
LinkedIn Profile Mining (via Sales Navigator)	Understand org structure, reporting chains, decision-making roles
G2 / Capterra Reviews	Reveal role-based frustrations with competitors (e.g., “HubSpot is too complex for small teams”)
Public Funding Data (Crunchbase, Pitchbook)	Indicates whether a company is investing in growth, hiring, or tech

Critical Principle

Do not generalize from single deals.

Only use patterns that appear consistently across at least 20–30 deals unless backed by strong strategic shifts.

Output of This Step

Output	Description
ICP Fit Framework (updated)	Uses hard data to define who qualifies as a Tier 1/2/3 target account
Persona Reference Cards	Role-based summaries with key insights and behavior
Red Flag List (Negative ICP)	Accounts or roles to deprioritize based on poor historical conversion or churn
Data-backed Playbooks	Supports future creation of targeting filters, outreach templates, and scoring logic

Step-by-Step ICP Development Process

Step 1: Define ICP Criteria Buckets

Start by establishing the 4 primary criteria buckets used to evaluate company fit.

ICP Filter	What It Represents	Example Values
Firmographic	Company characteristics	Industry, Company Size, Revenue, HQ Location
Technographic	Tools/tech they use	CRM system, Marketing stack, ERP, cloud infrastructure
Behavioral/Intent	Signals of active interest or tech maturity	Website visits, Job postings, funding rounds, ad engagement
Strategic Alignment	Internal relevance to your solution	Problem fit, use case, risk tolerance, compliance needs

👉 These are not optional filters—they are required data inputs to ensure ICP decisions are measurable and consistent.

Step 2: Analyze Closed-Won Accounts to Define Thresholds

Pull a list of all won deals in the last 12–24 months and identify what firmographic and strategic patterns they share.

Criteria	How to Extract It	Tools Used
Industry Segments	Analyze top 10 closed-won accounts by vertical	CRM, Pivot tables
Revenue Range	Match revenue to deal size and sales cycle length	ZoomInfo, Crunchbase
Company Size	Segment by employee count to match service complexity	LinkedIn, Apollo
Region	See which countries/states show highest win rates	CRM filters, Geo-mapping

✅ Outcome: Your baseline ICP profile is grounded in historical performance, not subjective targeting.

Step 3: Refine ICP Using Conversion, Retention, and Revenue Behavior

Now that you’ve defined the structural filters for your ICP (firmographic, strategic fit, etc.), this step helps refine the ICP by analyzing actual account behavior across your deal lifecycle. We want to ensure your ICP only includes segments that are proven to convert, retain, and expand—so that your GTM teams invest time only in high-probability, high-potential companies.

Without this step, your “ideal” customer is based on assumptions—not outcomes.

Why This Step Matters

Area of Impact	What Happens Without This Step
Sales Efficiency	SDRs chase accounts that look good but don’t convert
Forecast Accuracy	Pipeline is filled with long shots instead of predictable wins
Customer Fit	CS teams spend time fixing misaligned accounts
LTV Growth	Marketing attracts accounts that churn early or never expand

How to Execute This Step

This step is broken into 5 sub-steps that each analyze one aspect of revenue health.

Sub-Step 1: Analyze Conversion Predictability

Task	Execution
Segment closed-won deals by vertical, size, revenue band	Use CRM pivot tables or filters
Track demo-to-close, proposal- to-close, and qualification-to- demo rates	Funnel report view or deal tagging
Flag segments that perform 2x better than average	Mark as Tier 1 in ICP notes

Sub-Step 2: Map Sales Cycle Length by Segment

Task	Execution
Pull average sales cycle time per segment	Use deal stage duration fields in CRM
Find segments where 80%+ of deals close within 30–45 days	Define cycle boundaries in your ICP

Flag segments that drag beyond 60 days with <40% win rate

Exclude or mark as Tier 3 fit

Sub-Step 3: Evaluate Post-Sale Retention & Expansion

Task	Execution
Pull renewal and upsell data by segment	Use CS/Billing data and CRM revenue logs
Look for:
12-month renewal rates
% of accounts that expand	Tag segments as “High LTV ICP Zones” if both are strong

Sub-Step 4: Identify Delivery Fit & Scope Stability

Task	Execution
Review onboarding docs, CSATs, and CS debriefs	Look for timeline delays, scope creep
Interview Delivery & CS leads	Ask: “Which segments run smoothly, and why?”
Flag segments where projects close on time and within scope	Use these to define your Delivery-Aligned ICP

Sub-Step 5: Spot Risky Behavioral Patterns

Task	Execution
Analyze call logs, AE/CS notes	Look for ghosting, approval delays, indecision
Create a “Behavioral Red Flag Sheet”	Match these to high-churn or lost-deal segments
Exclude segments with 3+ recurring risk traits	List as “Negative ICP Behavior Triggers”

Where This Data Comes From

Sub-Step	Data Source	How to Pull	Who Owns It
Conversion Rates	CRM – Funnel Reports	Stage-to-stage conversion tracking	Sales Ops / Strategy
Sales Cycle Health	CRM – Deal Stage Durations	Average time-in-stage by segment	RevOps
Retention & Expansion	CS Tools / Billing Data	Renewal %, upsell rate by segment	CS Lead, RevOps
Delivery Fit	Project Notes, CSAT Logs	Scope change logs, onboarding timelines	Delivery / CS Leads
Risk Behaviors	SDR/AE/CS Notes	CRM comments, deal feedback, recordings	Sales Strategy Team

📌 Use at least 12–18 months of historical data. Validate patterns with CS & Sales feedback—not just metrics.

Final Output of This Step

Output	Description
Segment-level Performance Scorecards	Each vertical or segment now carries a score for:→ Conversion, sales efficiency, retention, delivery fit
Clear Exclusion Criteria	Segments with long sales cycles + poor post-sale performance are removed from ICP
Updated ICP Filters	Only segments with proven behavior-based reliability are retained in your Tier 1 & Tier 2 ICP scope

Step 4: Define Negative ICP Characteristics Based on Strategic Risk

Purpose of This Step

While many companies focus on “who to go after,” a strong ICP is equally defined by who you should actively avoid.

This step identifies segments that may appear attractive on the surface (industry fit, size, growth) but create strategic misalignment, low ROI, or operational risk.

The goal isn’t to blacklist companies—it’s to protect your team’s time, sales efficiency, and customer success capacity by disqualifying bad-fit accounts before they enter the funnel.

Why This Step Matters

Area of Impact	Without Negative ICP Filters
Sales Efficiency	SDRs waste time chasing low-fit accounts that never qualify or convert
Delivery Stability	Misaligned clients create scope creep, post-sale tension, and missed milestones
Customer LTV	Accounts with high churn potential reduce revenue per effort

Team Morale

Reps, CS, and delivery burn out dealing with toxic, slow, or mismatched clients

How to Execute This Step

You’ll build your Negative ICP Exclusion Filters using 4 core categories.

Category 1: Financial & Operational Misfit

Criteria	Indicators
Low budget tolerance	Consistent pricing pushback, budget hesitation at discovery stage
Unstable org structure	Frequent leadership turnover or missing core decision-makers
Extreme early-stage companies	No PMF, unclear roadmap, “we’re figuring it out” energy
Overly cost-sensitive or transactional buyers	Ask for discounts early, focus only on price

✅ Action: Pull this from sales notes, qualification stage feedback, and delivery finance issues.

Category 2: Strategic Misalignment

Criteria	Indicators
Wrong vision or goals	Company’s growth strategy doesn’t align with your service outcome
One-time project need	No long-term partnership potential or roadmap
Doesn’t value innovation	Stuck in legacy mindset, sees digital transformation as “optional”
Tactical mindset mismatch	Focuses only on execution, resists strategy involvement

✅ Action: Get this via discovery calls, CS feedback, or content disinterest patterns.

Category 3: Delivery Risk Factors

Criteria	Indicators
Poor onboarding behavior	Lack of responsiveness, late approvals, missed kickoff meetings
Scope chaos	Constant spec changes, multiple stakeholders out of sync
Compliance blockers	Long security review cycles, legal red tape that slows momentum
Tech rigidity	Non-negotiable legacy systems, no integration flexibility

✅ Action: CS + Delivery team debriefs, onboarding checklists, project post-mortems

Category 4: Cultural & Behavior Red Flags

Criteria	Indicators
Ghosting during sales	Goes dark after proposal or demo repeatedly
Power imbalance	“We’re the client” energy—disrespects your process or team
Over-collaborative committees	Too many voices, no decision owner, constant re-alignments
Low internal prioritization	“Let’s pick this back up in 3–6 months” repeatedly

✅ Action: Use AE call notes, deal retrospectives, and lost deal feedback

Where This Data Comes From

Source	How to Use It
Lost deal reason tags	Track disqualification patterns over time
CS onboarding notes	Patterns of late delivery, approvals, scope issues
Sales/CS team interviews	Capture red flags that don’t show up in metrics
Churned account reviews	What red flags were missed during qualification?
Discovery transcripts	Early-stage tone and attitude indicators

Build a Negative ICP Sheet

Structure it like this for team usage:

Red Flag Category	Indicator	If Present…
Financial Misfit	Pushback on price before value is explained	Disqualify unless strategic reason
Delivery Risk	No PM assigned, founder- led chaos	Flag for CS bandwidth review

Strategic Misalignment	“We just want a website” mindset	Exclude from mid/enterprise scope
Cultural Red Flag	Disrespects onboarding timeline	Assign lowest priority, flag for CS escalation

Final Output of This Step

Output	Description
Negative ICP Sheet	A documented set of account traits that trigger low-priority or disqualification
CRM Exclusion Rules	Filters or tags that flag exclusion (e.g., “Too Small”, “Pricing Pushback”, “Low Strategic Fit”)
Playbook Sync	SDRs and AEs know how to flag red flags early and when to stop outreach or escalate internally

Step 5: Tier & Score Your ICP Based on Strategic Fit

Purpose of This Step

Once you’ve defined your ICP’s structural traits (firmographics, opportunity signals), validated behavioral patterns (conversion, retention), and excluded risk-prone segments—this step helps you segment and score your ICP into tiers.

You’re no longer guessing who your ideal customers are—you now prioritize them by their strategic fit and commercial upside.

Why This Step Matters

Strategic Impact	Without This Step
🎯 Focus	Sales & Marketing waste equal energy on Tier 3 as they do on Tier 1
💰 ROI	You spend effort on accounts that never grow or renew
📈 Scale	SDRs don’t know who to pursue first, and AE bandwidth gets wasted
🤝 Alignment	Sales, Marketing, CS all talk to “the ICP,” but not in a tiered, practical way

How to Execute This Step

You’ll now apply scoring weights to all ICP criteria to tier-fit your segments into Tier 1 (Priority Fit), Tier 2 (Viable), and Tier 3 (Low-Fit / Conditional).

Define Your ICP Scoring Buckets

Scoring Area	Description	Notes
Firmographic Fit	Industry, company size, revenue, geo	Base-level filters
Opportunity Indicators	Digital readiness, hiring activity, transformation appetite	Strategic urgency
Conversion Predictability	High close rate, short sales cycle	Reduces friction
Retention & Expansion	High renewal & upsell trends	Long-term upside
Delivery Fit	Smooth onboarding, low chaos	Operational alignment
Behavior Risk	Ghosting, indecision, approval delays	Pulls down overall score

Assign Weights Based on Business Priorities

Criteria	Weight (%)	Why
Firmographic Fit	25%	It’s foundational, but not enough alone
Opportunity Signals	20%	Aligns with current GTM motion (e.g., AI, cloud shifts)
Conversion History	20%	Ensures pipeline ROI
Retention & Expansion	20%	Focus on long-term revenue, not one-time wins
Delivery Compatibility	10%	Reduces post-sale headaches
Behavior Risk	-5% to -15%	Acts as a penalty for red flags

Weights can be adjusted per team maturity, sales capacity, or service evolution.

Scoring Execution

Task	Execution
Build a spreadsheet or ClickUp table	Add each target segment (e.g., “Mid- Market FinTech – AU”)
Score each segment from 1–5 per category	Use internal deal analysis + team input
Apply weights to calculate total ICP score	Keep a scoring guide in your playbook

Map final score into Tier 1 / 2 / 3 brackets

Set clear boundaries (e.g., Tier 1 = 85+, Tier 2 = 65–84, Tier 3 = 40–64)

Example Output

Segment	Firmographic	Opportunity	Conv. Rate	Retention	Delivery	Risk	Score	Tier
SaaS – 50–200Employees – AU	5	4	5	4	4	0	88	T1
Manufacturing – 10–50Employees – US	3	2	3	2	3	-1	61	T2
Agencies – <10 Employees – IN	2	1	1	1	2	-2	38	T3

Where This Scoring System Is Used

Function	Use Case
Sales Strategy	Prioritize outbound segments and SDR time
Marketing Ops	Campaign budget allocation by Tier
RevOps	Lead routing & CRM logic customization
GTM Planning	Headcount distribution, territory planning
Reporting	Tier-wise conversion and LTV tracking

Final Output of This Step

Output	Description
ICP Scoring Sheet	Spreadsheet or table that maps all segments to score+ tier
Tiered ICP Playbook	Clear rules for how to treat T1 vs T2 vs T3 (e.g., resource priority, AE assignment, SLAs)
CRM Scoring Sync Plan	RevOps ensures CRM fields/tags reflect ICP tier for each account

Buyer Persona Development

This section outlines the structured, intelligence-driven approach to developing, operationalizing, and maintaining Buyer Personas—the individual roles and behavioral profiles of stakeholders involved in purchasing decisions within ICP accounts.

Unlike Ideal Customer Profiles (which define which companies to target), Buyer Personas identify who within those companies drives or influences buying behavior, and how.

Why Buyer Personas Matter

Personas are not fictional avatars or general audience types. They are decision-specific, role-based, and engagement-validated profiles built from:

• Real deal behavior (won and lost)
• Campaign interaction data
• Discovery call intelligence
• Post-sale delivery friction

They exist to:

Strategic Purpose	Execution Outcome
Identify the real decision-makers	Ensure outreach and discovery focus on those with influence or veto power
Understand what each stakeholder values and resists	Personalize messaging and handle objections proactively
Map stakeholder behavior across the full buyer journey	Anticipate friction points from outreach to onboarding
Build multi-threaded engagement strategies	Strengthen pipeline health and reduce single-threaded deal risk

Personas must be continuously updated based on campaign, sales, and CS inputs—not static assumptions.

Step-by-Step Development Process

Buyer Personas should not be based on generic assumptions like “CTOs want innovation” or “Marketing Managers care about brand.” Instead, they must be grounded in real behavioral patterns, deal experiences, objections raised, and engagement data.

This section outlines the data sources used to build, refine, and validate buyer personas for Memorres’ GTM strategy.

Internal Data Sources

Source	What to Extract	Why It’s Valuable
Discovery Call Summaries	Pain points by role, language they use, red flags	Reveals what each stakeholder cares about and how they think
Objections During Sales Cycles	Common pushback by job title (e.g., budget, security, UX scope)	Helps define pre-emptive messaging and objection handling
Call Recordings / Transcripts (Fireflies, Gong, etc.)	Decision flow, trust barriers, priorities per persona	Captures nuance: tone, friction points, what gets ignored
Customer Success Feedback	Which personas cause friction post-sale (over-control, scope creep)	Helps identify good vs. risky buyer types for each service
Closed-Won Notes	Who championed the deal, who delayed it, who owned the final decision	Reveals internal decision map and deal drivers by persona
Lost Deal Reasons (By Role)	What caused blockers or drop- offs by title	Validates persona-specific deal risks

Campaign / Engagement Data

Source	What to Track	Why It’s Valuable
Email Campaign Stats	Open/click rates by title	Tells you which personas care about what topics
Webinar Attendance & Drop-Off	Who stayed vs. who left early	Signals interest level by function
Lead Magnet Downloads	Who downloaded which whitepapers/guides	Aligns content relevance to persona intent stage
Ad Performance by Role (LinkedIn, Meta)	CTR and CPL by title or function	Shows where to invest more budget per persona

Qualitative Source

Source	What to Ask / Capture	Why It Matters
Sales Team Interviews	Which personas are the most decisive vs. difficult	Frontline insight you won’t get from analytics
Client Onboarding Debriefs	What each persona expected vs. experienced	Bridges sales-to-delivery alignment gaps
Surveys / CSAT by Role (if available)	Satisfaction by stakeholder type	Helps define post-sale friction sources or persona mismatch

Final Guidance:

• Do not rely on one source. Persona insight must be multi-source validated.
• Use both quantitative (behavioral engagement) and qualitative (field notes, interviews) inputs.
• Prioritize pattern recognition over anecdotes—don’t build personas around one noisy deal.

Step-by-Step Persona Development Process

(Inside Buyer Persona Development section)

🎯 This section converts raw research into structured, usable personas.

Step 1: Identify High-Impact Roles in Buying Committees

Start by listing roles that consistently appear in your deals (both won and lost), such as:

• CEO / Founder
• CTO / Head of Product
• Ops Lead / Delivery Manager
• Procurement / Legal
• Project Manager / Business Analyst

Tip: Focus on roles that affect decisions—not just job titles that appear in CRM.

✅ Output: A shortlist of key decision-makers, champions, blockers, and influencers per segment.

Step 2: Collect Role-Specific Behavior & Pain Points

For each role identified:

• Review discovery notes, deal recordings, and CS feedback
• Extract actual behaviors:
  • What questions they ask
  • What objections they raise
  • What goals they care about
  • What blocks them from deciding

Don’t write: “CTOs want scalability.”

Write: “CTOs asked 3 times if we can support 10K users and offered a sandbox trial model.”

✅ Output: Raw field intelligence mapped to each buyer role

Step 3: Define Each Role’s Decision Influence

Map each role to its actual decision impact:

Role Type	Influence
Economic Buyer	Approves deal; usually appears late
Technical Validator	Influences feasibility or integration approvals
Champion	Pushes deal forward, engages first
Legal / Compliance	Can delay or derail if not aligned early
End User	Doesn’t decide but influences delivery success & feedback

✅ Output: Clear documentation of who controls what during the buying journey

Step 4: Map Goals, Triggers, and Objections

For each persona, define:

Field	Description
Primary Goals	What outcomes they are responsible for (e.g., “reduce dependency on spreadsheets”)
Pain Points	Problems they vocalize (e.g., “team spends 12 hours/week reconciling data”)
Buying Triggers	Events that cause them to search for a solution (e.g., “internal audit failure, team growth”)
Objections	What they fear or resist (e.g., “vendor lock-in”, “too much dev time”)

✅ Output: Strategic messaging + discovery structure customized per role

Step 5: Document Buying Behavior Across Stages

Capture how each persona behaves across these journey stages:

Stage	Behavior
Awareness	What content do they engage with? What problems do they self-identify?
Consideration	What questions do they ask? What comparisons do they make?
Decision	What drives their final commitment? Who else do they consult?
Onboarding	What expectations do they bring into delivery?

✅ Output: End-to-end behavioral flow to inform sales playbooks, content strategy, and delivery readiness

Persona vs. ICP – Clear Differentiation

🎯 Why This Matters

One of the most common reasons for poor targeting, mismatched messaging, and inconsistent pipeline quality is the confusion between ICP and Buyer Persona.

This section clarifies the strategic difference between the two, and when to use each.

📌 ICP vs. Buyer Persona – Comparison Table

Aspect	ICP (Ideal Customer Profile)	Buyer Persona
Focus	Company-level fit	Individual decision-maker behavior
Used For	Defining which companies to target	Understanding who to speak to inside those companies
Data Type	Firmographics, revenue, geography, tech readiness, strategic fit	Job roles, goals, challenges, objections, buying influence
Who Uses It	Sales Strategy, Marketing Ops, RevOps	SDRs, AEs, Marketing Content, Delivery Leads
Examples	“Mid-market SaaS companies in AU with 50–200 employees and digital maturity”	“CTO focused on scale, fears vendor lock-in, wants API-first solutions”
Where It Applies	Lead scoring, audience filters, CRM segmentation, MQL routing	Messaging strategy, email templates, discovery call scripts, ad copy

📎 When to Use What

Scenario	Use ICP or Persona?
Filtering cold leads in CRM	✅ ICP
Writing email sequence for technical buyer	✅ Persona
Building a LinkedIn ads audience	✅ ICP (company filters) + Persona (job title)
Creating objection handling playbook	✅ Persona
Designing service packages for mid-market segment	✅ ICP (to understand structure and budget range)