# Company workforce Observed headcount footprint, hiring-and-attrition motion in the series, department mix, and people-match coverage when your ICP supplies role filters. _Data source — Company workforce signals Propensify detects: observed headcount footprint, series trajectory and period shocks, department mix, and people-match coverage when filters apply._ HTML: https://propensify.io/data-sources/company-workforce Markdown: https://propensify.io/data-sources/company-workforce.md We measure mix and trajectory here. Leader names and stories live on Website signals; how work feels is Employee voice. - **Also read:** [Website signals](https://propensify.io/data-sources/website-signals) — leader names and stories on the team page - **Also read:** [Employee voice](https://propensify.io/data-sources/employee-voice) — how work feels, not the headcount series ## Presence is a gate. Motion is prioritization. ### Presence Whether we observe usable headcount for the company — or an honest empty / unusable return. ### Motion How the series moves — sustained growth or contraction, below peak, stalls, recoveries, and period shocks — plus department and people texture. ## How workforce evidence stacks Three layers — bind observed headcount, read the trajectory, then see department concentration and motion — plus role-match coverage when filters apply. 1. **Footprint** — Observed / none usable 2. **Trajectory** — Growth → below peak + events 3. **Department motion** — Mix + growth / contraction - **Always useful:** Observed vs no usable observation. - **Series motion:** Primary trajectory + texture + period events. - **Org texture:** Department dominance / thin shares / growth / contraction. ## Headcount footprint First question: do we have a usable observed headcount for this company? Exactly one footprint outcome for this lane. No usable observation is not proof of zero employees. ## Footprint States - **Headcount observed:** At least one LinkedIn-visible employee observed — not confirmed payroll. - **No usable observation:** No usable observed headcount in this return — not proof the company has no employees. ## Headcount trajectory How total observed headcount moved across the history window. Observed series change — not a confirmed hiring or layoff program. Texture can coexist with a primary trajectory. ## Primary trajectory At most one primary shape for the series — sustained growth, sustained contraction, or current level below a prior peak. _Growing → below peak_ - **Sustained growth:** Material increase across history without sustained reversal. - **Sustained contraction:** Material decrease without sustained recovery — observation, not a layoff verdict. - **Below prior peak:** Current observed headcount materially below a prior observed peak. ## Trajectory texture Stall, recovery, and volatility patterns that can appear alongside a primary trajectory. _Stall → recovery → volatile_ - **Plateau / stall:** Recent headcount largely flat after earlier movement — coverage or true stall. - **Recovery arc:** Decline to a trough then material recovery — not proof of renewed buying. - **Oscillation / volatility:** Repeated direction changes with high churn vs net — weak on small bases. ## Period events Adjacent-period shocks rolled up from the series — read with trajectory context. A single burst usually needs broader trajectory context. Contractor cycling is a niche proxy, not strategy proof. ## Event Cards - **Headcount burst:** At least one adjacent-period material total increase under signal thresholds. - **Headcount cliff:** At least one adjacent-period material total decrease under signal thresholds. - **False dawn:** A material burst mostly reversed in a short window — observation instability. - **Band crossing:** Observed employee-count range bucket changed between adjacent snapshots. - **Contractor cycling:** Unclassified headcount alternates with consistent amplitude — niche proxy only. ## Department mix & motion Where observed headcount concentrates — and which function families grew or contracted. Pattern types fire per department in the observed mix — taxonomy and coverage bias are possible. ## Department Cards - **Department dominance:** A named department is a large share of observed headcount. - **Low function share:** A monitored department is thin in the mix — not proof the function is absent. - **Department growing:** A function family increased materially vs its baseline window. - **Department contracting:** A function family decreased materially vs its baseline window. ## People coverage When your ICP supplies title, seniority, or department filters, we can see whether people matches land in the returned search page. Page sample under filters — not a full org chart. No matches ≠ no such employees exist. Illustrative mix texture when matches return — page-local counts, not a census. ## People States - **People matches:** At least one person returned under the filtered search. - **No people returned:** Empty result for this filtered search — not proof no such employees exist. - **Title query hit:** At least one match under a non-empty title query — match quality varies. - **Seniority mix:** Returned-page people share seniority values — not a company-wide census. - **Department mix:** Returned-page people share department values — taxonomy, not payroll org chart. ## People Chips - Executive - Manager - IC - Engineering - Sales - Marketing - HR - IT ## What it looks like in a verified fit Workforce evidence lands as findings on the account — with the same Fit and Signals score grammar as the product. Harborline Systems ## Findings - **Headcount observed** - **Sustained growth** - **Department growing** ## Boundaries & method - Headcount is LinkedIn-visible observation — not confirmed payroll. - No usable observation ≠ the company has no employees. - Trajectory movement is observed series change — not a confirmed hiring or layoff program. - Below a prior observed peak is not proof of distress intent. - Recovery arc ≠ renewed buying intent. - Bursts and cliffs need trajectory context; false dawn is observation instability. - Contractor cycling is a niche proxy — not proof of a contractor strategy. - Department shares use observed taxonomy — coverage bias possible; low share ≠ function absent. - People results are a filtered page sample — not a full org census. - No matches for a filtered search ≠ no such employees exist. - Title match quality varies — not a confirmed role inventory. - We do not invent headcount volume bands (large / mid / small) from observed counts. - Firmographic size bands and public job openings are sibling guides — not substitutes for this series. ## Want company workforce signals on your verified fits? We’ll map footprint, trajectory, department motion, and people coverage to your ICP and show how they look on real accounts. - [Get 10 vetted companies →](https://propensify.io/#lead) - [Book a call](https://propensify.io/book-a-call) Part of https://propensify.io/data-sources. Full set: https://propensify.io/data-sources.md.