Lattice does not have a visibility problem, and the models are not rejecting it. They find it and they say yes, though rarely without caveats. The real problem is the label. The models still describe Lattice as a performance specialist rather than the home for a company's HR data, and that label decides which buyers ever hear its name.
The label lives mostly in the models' training memory, which is older than the pages they cite. When the models search, the record they read is written by others. Rivals and third-party sites author almost all the sourcing, while Lattice's own pages barely appear. The cost lands in one place: core HR. Lattice loses that question against nearly every competitor. The stake is growing because buyers' language has flipped. Core HR and payroll terms now draw about 19x the searches of performance terms. Lattice's own homepage claims the HR and payroll category, yet the models never place it there.
Because the belief sits in memory, it moves only at retraining. The fix is to rewrite the record the models read, starting now, so the next training cycle inherits the new story. That means owning the core HR narrative in the pages that get cited, and accepting that the payoff compounds over quarters, not weeks.
AI-generated read of the lab's measurements, as are the explainers under each section's TL;DR; every number is measured on this page.
The index measures which brands the models (ChatGPT, Claude and Gemini) name unprompted; the lab puts one subject under every other prompt condition a buyer creates: aided ("I'm considering Lattice. Would you recommend them?"), forced choice ("Lattice or [competitor]: give a definitive answer"), and grounded (web search on: which sources the models cite). Lattice is an enrolled lab subject, selected by the operator; every prompt template is published in full below, name order rotates to cancel position bias, and these answers never touch the Visibility Score. Methodology →
TL;DR The all-in-one people platform (HRIS, payroll, performance) story has not landed: 47% of the models' answers still call Lattice a talent management suite.
Most answers describe Lattice as a talent management suite, a step above its old reputation but short of its goal. Every one of the 120 aided runs also reveals what the model believes Lattice is, and we sort those descriptions into buckets. *Nearly half of all answers (47%) call Lattice a talent management suite, while the all-in-one people platform story it markets shows up in only 18%. The gap is sharpest at the top: Lattice's own homepage claims the HR and payroll category, yet the index does not rank it there at all. Instead it ranks #1 in performance management, the identity it is trying to outgrow. The label a model reaches for shapes which buyers it recommends the product to*, so a company described as a review tool never makes the shortlist when someone asks for a full HR platform.
The prompt, asked 120 times across four buyer personas and five needs: “I'm [persona] and I need [attribute]. I'm considering Lattice. Would you recommend them? Give me pros and cons.”
TL;DR core-HR and payroll terms out-search performance-management terms about 19 to 1 on Google, and have led for the whole measured window.
US Google monthly search volume, Sep ’22–Aug ’26. Baskets: performance-management terms = “performance management software”, “performance review software”, “employee engagement software”, “okr software”; core-HR and payroll terms = “hris”, “hr software”, “payroll software”, “onboarding software”. The models' dominant label for Lattice tracks the 19x-smaller vocabulary, not the one buyers are moving to.
The same gap, measured a third way: what Lattice's own homepage claims, next to where the index actually ranks it.
Lattice's homepage positions it for HR & Payroll. Ask the models that question and they name Rippling, Gusto and BambooHR, not Lattice.
Why, and what closes it. Models recommend what the web says about a brand, not what its homepage asserts. That is a content and coverage gap, not a product one. Earned mentions and clearer positioning can move it.
Homepage self-messaging · September 2026 ranking · the biggest gaps across the index →
TL;DR 93% of the models' recommendations for Lattice come with conditions; 6% recommend against it outright.
When a buyer names Lattice directly and asks for a verdict, the models almost never give a clean answer. Across 120 of these direct asks, only 1 reply was an unconditional yes, 112 were yeses hedged with warnings, and 7 advised against the product. A qualified recommendation looks like agreement with strings attached, most often warnings that implementation takes real effort and that pricing adds up across separate modules. This matters commercially because every hedge is an opening for a rival name, and the models take it, steering buyers toward alternatives like Rippling and BambooHR. The hedging is also remarkably uniform: the split barely moves across the five buyer needs and four personas tested. No buyer type earns a confident yes, so the caution is baked into how the models see the product rather than tied to any one kind of customer.
| attribute | unqualified yes | qualified | no |
|---|---|---|---|
| AI people operations | 0 | 24 | 0 |
| engagement | 0 | 24 | 0 |
| core HRIS | 0 | 20 | 4 |
| payroll | 0 | 21 | 3 |
| performance and goals | 1 | 23 | 0 |
What the qualifications are about, in order of frequency: Implementation takes real effort · Pricing adds up fast with separate modules · May require additional systems or integrations · Pricing stacks up fast with separate modules. And when the models hedge, they don't hedge into silence: the brands they name alongside or instead of Lattice are Rippling, BambooHR, Workday, Culture Amp. For the unaided version of this measurement, how answers portray Lattice when the buyer never names it, see the sentiment stances on the brand page.
TL;DR Forced to pick between Lattice and a named competitor, the models choose Lattice 53% of the time; the weakest attribute by far is core HRIS (25%).
Lattice wins most of these matchups, but it collapses whenever the question turns to core HR record-keeping. Each run poses a buyer who already knows both brands and demands a single answer, across 420 runs against 10 competitors. On its home turf the results are lopsided: the models pick Lattice 93% of the time for performance and goals and 82% for AI people operations. The crater is core HRIS, and its shape matters. The weakness belongs to the attribute, not to one type of rival, because Lattice loses on it against competitor after competitor. In practice, the models treat Lattice as a strong layer on top of an HR system, not as the system of record itself.
How to read the matrix: green cells favor Lattice, red favor the competitor; hover any cell for the raw run counts. A single cell is only 6 runs, so treat differences under ~25 points as direction rather than precision; the row and column totals (42+ runs each) are the reliable numbers. Brand-name order was rotated on every run and produced identical win rates in both orders, so position bias is measured at zero.
| Size | Use case | All | ||||||
|---|---|---|---|---|---|---|---|---|
| vs | enterprise needs | mid-market needs | startup needs | performance and goals | core HRIS | payroll | AI people operations | |
| | 100% | 100% | 33% | 100% | 83% | 100% | 100% | 88% |
| | 100% | 17% | 17% | 100% | 0% | 0% | 83% | 45% |
| | 0% | 83% | 100% | 100% | 100% | 100% | 100% | 83% |
| | 33% | 83% | 0% | 100% | 0% | 0% | 100% | 45% |
| | 100% | 100% | 0% | 100% | 0% | 0% | 100% | 57% |
| | 33% | 0% | 33% | 100% | 0% | 0% | 50% | 31% |
| | 83% | 50% | 17% | 33% | 67% | 100% | 67% | 60% |
| | 0% | 0% | 100% | 100% | 0% | 0% | 100% | 43% |
| | 0% | 0% | 0% | 100% | 0% | 0% | 50% | 21% |
| | 0% | 100% | 100% | 100% | 0% | 0% | 67% | 52% |
| All competitors | 45% | 53% | 40% | 93% | 25% | 30% | 82% | 53% |
| vs | enterprise needs | mid-market needs | startup needs | performance and goals | core HRIS | payroll | AI people operations |
|---|---|---|---|---|---|---|---|
| 15Five | 6–0 | 6–0 | 2–4 | 6–0 | 5–1 | 6–0 | 6–0 |
| BambooHR | 6–0 | 1–4–1t | 1–5 | 6–0 | 0–6 | 0–6 | 5–1 |
| Culture Amp | 0–6 | 5–1 | 6–0 | 6–0 | 6–0 | 6–0 | 6–0 |
| Deel | 2–1–3t | 5–1 | 0–5–1t | 6–0 | 0–6 | 0–6 | 6–0 |
| Gusto | 6–0 | 6–0 | 0–6 | 6–0 | 0–4–2t | 0–6 | 6–0 |
| HiBob | 2–3–1t | 0–6 | 2–4 | 6–0 | 0–6 | 0–5–1t | 3–3 |
| Leapsome | 5–0–1t | 3–2–1t | 1–5 | 2–4 | 4–2 | 6–0 | 4–2 |
| Paylocity | 0–4–2t | 0–5–1t | 6–0 | 6–0 | 0–5–1t | 0–6 | 6–0 |
| Rippling | 0–6 | 0–6 | 0–6 | 6–0 | 0–6 | 0–6 | 3–3 |
| Workday | 0–6 | 6–0 | 6–0 | 6–0 | 0–4–2t | 0–6 | 4–1–1t |
Each cell: Lattice wins–competitor wins–ties out of 6 runs.
TL;DR In head-to-head answers Lattice wins on “Purpose-built performance management platform”; the models' most common objection is “Weak or immature HRIS and core HR”.
Lattice's biggest strength and its biggest weakness turn out to be two sides of the same reputation. Every forced-choice answer explains its reasoning, and we code those reasons into countable labels: the left column is why Lattice wins, the right is what the models hold against it. When Lattice is the pick, the models most often praise its purpose-built performance platform, named in 10% of all 420 runs, or its native HRIS with unified employee data. When a competitor wins, the leading objection is a weak or immature HRIS, also at 10%, followed by the absence of native payroll and benefits. The pattern is that the models see Lattice as a specialist. That perception wins deals where performance depth matters and loses them where buyers want a full HR backbone, and the fact that the HRIS appears on both lists shows the models themselves are split on whether Lattice's core HR is an asset or a gap.
Percentages are shares of all 420 runs, so a 21% differentiator is one the models reach for in a fifth of every matchup they see.
TL;DR Rippling is the biggest real threat to Lattice, winning 79% of its head-to-head matchups.
Overall win rates hide which rivals actually take the runs Lattice loses, so this section breaks out each competitor's winning argument using the models' own recurring phrases, ordered by how often that competitor wins. The pattern is clear: Lattice loses to platforms that own the underlying HR system of record, not to other performance tools. Rippling wins with AI workflows grounded in system data, while HiBob, which takes 64% of its runs, argues it is purpose-built for mid-market scale with a stronger HRIS foundation. BambooHR wins about half its runs with a similar story about centralized employee data as the base for AI. The two competitor classes win differently: all-in-one platforms like Rippling argue breadth of operational context, while HRIS-first vendors argue depth of the data foundation. Either way, the argument that beats Lattice is that owning the employee data layer makes a better home for AI than a layer that sits on top of it.
The chip on each card is that competitor's win rate against Lattice in this lab (wins out of runs played); the biggest genuine threat reads first.
TL;DR Competitors author 34% of what the models read about Lattice; Lattice itself authors just 1%.
When the models can search the web, Lattice's story gets told almost entirely by other people. Everything above measured what the models believe from training; here we turned search on, asked the same battery again, and recorded which pages they cite. Lattice appears in 79% of these answers, so being found is not the problem. The problem is who wrote the pages doing the grounding. Lattice's own site and docs barely register, while listicles, software directories, review sites, and rival vendors supply nearly all the sourcing. When a competitor authors the page a model cites, that model ends up narrating Lattice in its rival's words.
The most-cited grounding domains:
| domain | answers citing it | how it frames Lattice |
|---|---|---|
| peoplemanagingpeople.com ↗ blog | 35 | page not captured in the description audit |
| hr.software ↗ directory | 29 | legacy framingLattice is a cloud-based talent management suite focused on performance reviews, employee engagement, and compensation planning that operates as a specialized talent overlay integrating with core HR systems. |
| capterra.com ↗ review site | 24 | page not captured in the description audit |
| softwareadvice.com ↗ review site | 20 | page not captured in the description audit |
| heartcount.com ↗ competitor-owned | 17 | legacy framingLattice is a performance management platform that consolidates performance reviews, goal tracking, continuous feedback, and employee engagement surveys into a single system for mid-market companies. |
| calamari.io ↗ competitor-owned | 16 | The page mentions Lattice only in the context of its HRIS shutdown and as a point of comparison for alternative platforms, not as a substantive description of what Lattice is. |
| youtube.com community | 16 | page not captured in the description audit |
| denlook.com ↗ directory | 15 | page not captured in the description audit |
| remotelytalents.com ↗ blog | 15 | people-platform framingLattice is an integrated HR platform that brings together performance management, employee engagement, and career development with AI-powered features for mid-sized to large organizations. |
| research.com ↗ review site | 14 | page not captured in the description audit |
Framing lines are AI-summarized from each domain's most-cited page about Lattice (description audit, run with the same measurement pass).
These are the three numbers that would move first if Lattice's repositioning is landing. The lab re-runs monthly from the same battery, so each is directly comparable measure to measure.
Measured September 21, 2026, alongside the September 2026 snapshot. Models: ChatGPT (gpt-5.4), Claude (claude-sonnet-4-6), Gemini (gemini-3-flash-preview). Grounded runs are a separate measurement surface (web search on) from the sections above, which measure what the models know from training alone. A forced choice is a different measurement than open visibility: a brand can dominate this lab and still be invisible when buyers don't name it. Read the lab and the index together.