Head Count Growth Rate

Give it a LinkedIn company identifier, get back how headcount has moved over time.

What it does

• Tracks the growth rate of a company’s employee headcount over time.
• Returns a time-series trend, not a single number.
• Accepts a LinkedIn id, a full LinkedIn URL, or a company name as the identifier.
• For a point-in-time count — total or by department — use headcount_by_department instead. Same 2-credit price, different question.

Growth is a buying signal. A company that added 40% headcount this year has new teams, new tools and new budget. A company that shrank does not.

Parameters

How to use it

How has headcount changed over time at linkedin.com/company/stripe?

Get the headcount growth rate for these 30 companies and sort them fastest
growing to slowest. Report credits used.

For each, tell me both the current headcount and the trend. I want companies
that are mid-sized AND growing, not just large.

Example prompts

Best prompting practices

• Use trend words. “Over time”, “growth rate”, “trend” route to this tool. “How many” routes to headcount_by_department.
• Filter at search time when you can. find_companies has min_headcount_growth_percent_1m/_3m/_6m/_12m built in. Returning 50 companies from that search is 15 credits; 50 separate lookups here is 100.
• Prefer the LinkedIn URL or id over the name. Names are ambiguous across subsidiaries and regions.
• Read direction, not just magnitude. Flat is a different conversation from declining. Ask your client to state which.
• Cap the batch. “Stop after 30 and report credits used.”

Output

{
  "identifier": "linkedin.com/company/stripe",
  "growth_rate": [
    { "period": "6m", "percent": 12.4 },
    { "period": "12m", "percent": 23.1 }
  ]
}

Credits and limits

2 credits per call, flat. Run check_credits (free) before a large batch.

Related tools

Next steps

• All MCP tools — the full catalogue with credit costs
• Signals & ABM — workflows that turn growth signals into outreach triggers

Keep learning

Two courses take these tools past the reference page — clustered by GTM job, then chained into workflows.