The prior audit ran on 2026-05-21T12:00:00. 5 days later, this re-audit re-runs the identical 150-query panel and measures what changed.
Same buyer queries every cycle — unchanged. This is the longitudinal ruler.
+6.6pp means "percentage points gained." Green = improvement, red = regression.
p<0.05 = statistically significant. Above = directional (trend is there, sample too small).
When the platform set changes, we isolate platforms present in both cycles — the honest apples-to-apples comparison.
Each newly-visible query traced to the shipped page. attributed / partial / none.
Carried Resolved Re-investigate New — every Part C item carries a thread.
Platform changes, model updates, extraction gaps — always disclosed.
"Consistent with" — never "caused by." Evidence chain: deployed → cited → visible.
What moved, why it moved, and what it means. Start here.
The change reading: what moved between cycles, and whether the movement is signal or noise.
Panel verdict: significant (McNemar p = 0.0259, b = 8 regressions, c = 21 improvements)
Every prior plan item with shipping status and outcome.
| Prior item | Source | Prior status | Carryover outcome | Visibility Δ | Reason |
|---|---|---|---|---|---|
l2_001 | l2_001 | pending | Flagged for review (lineage-lost) | — | gap absent from UPR with no corroborating signal — possible re-cluster or instrument drift; routed for human review |
l2_002 | l2_002 | pending | Carried forward | — | not yet deployed and the gap is still present — carry forward |
l2_003 | l2_003 | pending | Carried forward | — | not yet deployed and the gap is still present — carry forward |
l2_004 | l2_004 | pending | Carried forward | — | not yet deployed and the gap is still present — carry forward |
l2_005 | l2_005 | pending | Carried forward | — | not yet deployed and the gap is still present — carry forward |
l2_006 | l2_006 | pending | Carried forward | — | not yet deployed and the gap is still present — carry forward |
l2_007 | l2_007 | pending | Carried forward | — | not yet deployed and the gap is still present — carry forward |
l2_008 | l2_008 | pending | Flagged for review (lineage-lost) | — | gap absent from UPR with no corroborating signal — possible re-cluster or instrument drift; routed for human review |
l2_009 | l2_009 | pending | Flagged for review (lineage-lost) | — | gap absent from UPR with no corroborating signal — possible re-cluster or instrument drift; routed for human review |
l2_010 | l2_010 | pending | Carried forward | — | not yet deployed and the gap is still present — carry forward |
The cross-cutting read. Per-dimension detail in Part B.
These findings inform Part C — The Next Plan below.
Baseline measurement sections, delta-annotated. Click any section to expand.
Each section becomes a collapsible card with a one-line delta summary. Click any card to expand the full baseline measurement detail underneath.
| Ordinal | Completed | Visibility | HI win rate | SOV | Queries |
|---|---|---|---|---|---|
| 0 | 2026-05-07T12:00:00 | — | — | — | — |
| 1 | 2026-05-20T12:00:00 | — | — | — | — |
| 2 | 2026-05-21T12:00:00 | — | — | — | — |
| 3 | 2026-05-26T20:00:08 | — | — | — | — |
| 4 | 2026-05-26T20:52:38 | — | — | — | — |
Where Insynctive appears and where it doesn't — across personas, buying jobs, and platforms.
[TL;DR] Insynctive is visible in 17% of buyer queries and wins 44% of those. The primary challenge is getting visible in the first place. High-intent queries run higher at 22%.
Insynctive's 16.7% overall visibility (25/150 queries) understates its late-stage competitive strength — a 38.9% conditional win rate (7/18 visible high-intent queries) — but the 88.6% early-funnel absence (39/44 queries) means most buyers reach the Comparison stage with a mental shortlist that excludes Insynctive entirely.
| Dimension | Combined |
|---|---|
| All Queries | 16.7% |
| By Persona | |
| Benefits Account Manager | 6.7% |
| Broker Principal | 33.3% |
| CFO Employer | 13% |
| HR Director Employer | 5.9% |
| HRIS Benefits Admin | 10.7% |
| Tpa Operations Lead | 30% |
| By Buying Job | |
| Artifact Creation | 0% |
| Comparison | 24.2% |
| Consensus Creation | 16.7% |
| Problem Identification | 25% |
| Requirements Building | 0% |
| Shortlisting | 32% |
| Solution Exploration | 12.5% |
| Validation | 8.3% |
[Data] Overall visibility: 16.7% (25/150 queries). High-intent visibility: 22% (18/82 queries). High-intent conditional win rate: 38.9% (7/18 visible queries).
Early-funnel invisibility: 88.6% (39/44) — Requirements Building: 100% (16/16); Solution Exploration: 87.5% (14/16); Problem Identification: 75% (9/12). By buying stage: Shortlisting 32% (8/25); Comparison 24.2% (8/33); Validation 8.3% (2/24). By persona: Broker Principal 33.3% (10/30); TPA Operations Lead 30% (6/20); CFO 13% (3/23); HRIS Admin 10.7% (3/28); HR Director 5.9% (2/34); Benefits Account Manager 6.7% (1/15).
[Synthesis] The 16.7% overall visibility rate obscures a stage-structured pattern: Insynctive performs competitively at Comparison and Shortlisting (24.2% and 32% visibility respectively) but is functionally absent at the three earlier stages where buyers form their category understanding. The persona split sharpens this further: broker principals and TPA leads (the channel-facing personas) see Insynctive in 33.3% and 30% of queries respectively, while HR directors and benefits account managers (the employer-facing evaluators who initiate most employer-side RFPs) encounter it in only 5.9% and 6.7% of queries. Improving employer-facing early-funnel presence — through content that answers requirements-building and problem-identification queries — would expand the top of the pipeline and compound the late-stage win rate.
30 queries won by named competitors · 48 no clear winner · 44 no vendor mentioned
Sorted by competitive damage — competitor-winning queries first.
| ID | Query | Persona | Stage | Winner |
|---|---|---|---|---|
| ⚑ Competitor Wins — 30 queries where a named competitor captures the buyer | ||||
| ins_045 | "Best benefits administration platforms for mid-market employers handling open enrollment for 300+ employees on multiple plans" | HR Director Employer | Shortlisting | Rippling |
| ins_050 | "Best HCM suites for mid-market employers that want benefits, payroll, and HR consolidated under one contract" | CFO Employer | Shortlisting | Rippling |
| ins_051 | "Top benefits administration platforms with deep ADP Workforce Now integration for 250-person employers already on ADP" | HRIS Benefits Admin | Shortlisting | Employee Navigator |
| ins_052 | "Benefits platforms a 30-broker agency can stand up for new clients in days rather than weeks" | Benefits Account Manager | Shortlisting | Employee Navigator |
| ins_053 | "Top benefits platforms with strong premium reconciliation tools for account managers carrying 75 employer groups" | Benefits Account Manager | Shortlisting | Employee Navigator |
| ins_056 | "Benefits administration platforms with strong ad-hoc reporting for HRIS administrators at 400-person companies" | HRIS Benefits Admin | Shortlisting | Rippling |
| ins_058 | "Benefits administration platforms that integrate with payroll without forcing a full HCM rip-and-replace project" | Broker Principal | Shortlisting | Employee Navigator |
| ins_059 | "Mobile-friendly open enrollment tools for mid-market employers that handle carrier-specific forms automatically" | HR Director Employer | Shortlisting | Employee Navigator |
| ins_060 | "Best HR platforms for self-service I-9, W-4, and benefits document signing at a 200-employee company" | HR Director Employer | Shortlisting | Rippling |
| ins_065 | "Top benefits administration platforms with strong payroll integration that don't force a full HCM switch" | CFO Employer | Shortlisting | Employee Navigator |
Remaining competitor wins: Employee Navigator ×12, Selerix ×4, isolved ×2, Rippling ×1, Benefitfocus ×1. 48 queries with no clear winner. 44 queries with no vendor mentioned. Full query-level data available in the analysis export.
| ID | Query | Persona | Stage | Winner |
|---|---|---|---|---|
| ins_066 | "Benefits administration platforms with reliable EDI feeds across medical, dental, vision, and ancillary carriers" | Benefits Account Manager | Shortlisting | Rippling |
| ins_069 | "Best benefits platforms that play well with existing HRIS, payroll, and 401k systems for mid-market employers" | HRIS Benefits Admin | Shortlisting | Employee Navigator |
| ins_070 | "Employee Navigator vs Ease — which one should a 100-broker agency build its book on now that they're under one roof?" | Broker Principal | Comparison | Employee Navigator |
| ins_071 | "Employee Navigator vs BerniePortal for a benefits brokerage onboarding 30 employer groups a year" | Benefits Account Manager | Comparison | Employee Navigator |
| ins_072 | "PlanSource vs Selerix for a 600-employee company focused on premium reconciliation accuracy" | HR Director Employer | Comparison | Selerix |
| ins_073 | "Employee Navigator vs PlanSource for a TPA with 80 employer groups — which one scales better operationally?" | Tpa Operations Lead | Comparison | Employee Navigator |
| ins_074 | "How do PlanSource and Selerix compare on ADP Workforce Now integration depth and sync reliability?" | HRIS Benefits Admin | Comparison | Selerix |
| ins_076 | "isolved vs PlanSource for a 350-person company that wants benefits and payroll handled in the same platform" | CFO Employer | Comparison | isolved |
| ins_078 | "Employee Navigator vs BerniePortal for a mid-market employer keeping legacy on-prem HR systems in place" | HRIS Benefits Admin | Comparison | Employee Navigator |
| ins_079 | "Employee Navigator vs Selerix — broker book defensibility Comparison for an agency post-consolidation" | Broker Principal | Comparison | Selerix |
| ins_083 | "Reporting and analytics Comparison: Employee Navigator vs PlanSource for a benefits administrator at a 400-person employer" | HRIS Benefits Admin | Comparison | Employee Navigator |
| ins_084 | "Compare Employee Navigator, BerniePortal, and PlanSource for a 50-broker agency expanding into mid-market accounts" | Broker Principal | Comparison | Employee Navigator |
| ins_085 | "Benefitfocus vs PlanSource for a CFO comparing benefits platforms on cost predictability and contract flexibility" | CFO Employer | Comparison | Benefitfocus |
| ins_087 | "Ease vs BerniePortal for SMB-focused brokerages — pros and cons after the Employee Navigator acquisition" | Broker Principal | Comparison | Employee Navigator |
| ins_089 | "Pros and cons of BerniePortal versus Employee Navigator for a benefits account manager carrying 60 employer groups" | Benefits Account Manager | Comparison | Employee Navigator |
| ins_090 | "Selerix vs bswift for an enterprise-leaning TPA running a multi-tenant deployment across 40 employer groups" | Tpa Operations Lead | Comparison | Selerix |
| ins_091 | "How do Employee Navigator and PlanSource compare on the employee open enrollment experience for a mid-market employer?" | HR Director Employer | Comparison | Employee Navigator |
| ins_092 | "Implementation speed: Employee Navigator vs PlanSource for a brokerage onboarding new employer groups quickly" | Broker Principal | Comparison | Employee Navigator |
| ins_093 | "Employee Navigator vs isolved on configurability for a mid-market employer with multi-state operations and union populations" | HRIS Benefits Admin | Comparison | isolved |
| ins_134 | "Case studies of brokerages doubling group count without doubling account-manager headcount through better platforms" | Broker Principal | Consensus Creation | Employee Navigator |
| ins_003 | "How do HR teams catch carrier billing errors before they pile up at year-end reconciliation?" | HR Director Employer | Problem Identification | No Vendor Mentioned |
| ins_004 | "What does it actually cost a 500-person company to keep paying premiums for terminated employees nobody caught?" | CFO Employer | Problem Identification | No Vendor Mentioned |
| ins_005 | "Tradeoffs CFOs weigh between an all-in-one HCM suite and a best-of-breed benefits platform for a 400-person company" | CFO Employer | Problem Identification | No Clear Winner |
| ins_006 | "Why does open enrollment still take six weeks for mid-market employers, and what's actually driving the time?" | HR Director Employer | Problem Identification | No Clear Winner |
| ins_007 | "Why is new-client onboarding taking weeks when our brokerage thought it would take an afternoon?" | Broker Principal | Problem Identification | No Vendor Mentioned |
| ins_008 | "Why do HRIS, payroll, and ben admin systems keep disagreeing about who is enrolled in what plan?" | HRIS Benefits Admin | Problem Identification | No Vendor Mentioned |
| ins_009 | "How are benefits account managers cutting down on the same five enrollment questions employees keep asking?" | Benefits Account Manager | Problem Identification | No Vendor Mentioned |
| ins_010 | "Common ways mid-market employers fall behind on I-9 and ACA compliance and only find out at audit" | HR Director Employer | Problem Identification | No Vendor Mentioned |
| ins_012 | "Hidden costs of running benefits and payroll on separate platforms for a 350-person mid-market employer" | CFO Employer | Problem Identification | No Vendor Mentioned |
| ins_013 | "Modern cloud HRIS vs keeping our legacy on-prem system, what are real options for mid-size companies that can't gut everything?" | HRIS Benefits Admin | Solution Exploration | No Clear Winner |
| ins_015 | "How do TPAs typically build multi-employer benefits platforms — proprietary build, white-label, or piecemeal integration?" | Tpa Operations Lead | Solution Exploration | No Clear Winner |
| ins_016 | "Unified HCM suite versus a separate ben admin platform plus payroll integration, when is each the better economic choice?" | CFO Employer | Solution Exploration | No Vendor Mentioned |
| ins_017 | "Different approaches to running open enrollment for a mid-market employer — broker-led, fully self-service, or hybrid?" | HR Director Employer | Solution Exploration | No Clear Winner |
| ins_018 | "Best ways to keep ADP Workforce Now in sync with a separate benefits administration platform without manual rekeying" | HRIS Benefits Admin | Solution Exploration | No Clear Winner |
| ins_019 | "Manual carrier bill reconciliation vs automated tools — how do brokerages typically catch terminated-employee charges?" | Benefits Account Manager | Solution Exploration | No Vendor Mentioned |
| ins_020 | "Software, outsourced compliance partner, or internal team — what works best for I-9, ACA, and HIPAA at a 300-person company?" | HR Director Employer | Solution Exploration | No Vendor Mentioned |
| ins_021 | "Multi-tenant SaaS versus single-tenant deployments for benefits platforms, what should a TPA actually care about?" | Tpa Operations Lead | Solution Exploration | No Vendor Mentioned |
| ins_022 | "Benefits and payroll integration approaches — point-to-point, middleware, or full HCM consolidation, real tradeoffs?" | CFO Employer | Solution Exploration | No Vendor Mentioned |
| ins_023 | "Configurable HRIS platforms versus rigid SaaS HR tools — what happens when you have multi-EIN groups and union populations?" | HRIS Benefits Admin | Solution Exploration | No Vendor Mentioned |
| ins_025 | "Decision-support tooling for employees during open enrollment — vendor-built versus broker-led education programs" | Benefits Account Manager | Solution Exploration | No Clear Winner |
| ins_026 | "EDI feeds versus API connections for sending enrollment data to medical and dental carriers, real pros and cons" | HR Director Employer | Solution Exploration | No Vendor Mentioned |
| ins_027 | "How do brokerage agencies usually reduce platform lock-in risk after their primary tech vendor gets acquired?" | Broker Principal | Solution Exploration | No Vendor Mentioned |
| ins_028 | "Service providers offering benefits without payroll vs full HCM — what's the right move for a 50-employer-group TPA?" | Tpa Operations Lead | Solution Exploration | |
| ins_029 | "Key requirements for evaluating open enrollment software for a 400-person mid-market employer running multiple medical plans" | HR Director Employer | Requirements Building | |
| ins_032 | "Questions a CFO should ask benefits administration vendors about TCO, contract terms, and PEPM pricing transparency" | CFO Employer | Requirements Building | |
| ins_034 | "Compliance requirements checklist for evaluating HRIS platforms — I-9, ACA, HIPAA, and what else mid-market employers should pin down?" | HR Director Employer | Requirements Building | No Vendor Mentioned |
| ins_035 | "Technical questions to ask a ben admin vendor about ADP Workforce Now integration depth and bi-directional sync cadence" | HRIS Benefits Admin | Requirements Building | No Clear Winner |
| ins_036 | "Must-have features for a benefits platform handling carrier EDI feeds and bill reconciliation across 100+ employer groups" | Benefits Account Manager | Requirements Building | No Vendor Mentioned |
| ins_037 | "What does a brokerage need to evaluate when picking a platform that will handle new client onboarding for the next five years?" | Broker Principal | Requirements Building | No Vendor Mentioned |
| ins_038 | "Reporting requirements for a benefits administrator who needs ad-hoc enrollment and deduction reports without filing IT tickets" | HRIS Benefits Admin | Requirements Building | No Vendor Mentioned |
| ins_039 | "Self-service requirements for an HR platform — what should employees be able to do without ever calling HR?" | HR Director Employer | Requirements Building | No Clear Winner |
| ins_040 | "Vendor risk assessment criteria for a TPA picking a benefits platform that will be the foundation for the next decade" | Tpa Operations Lead | Requirements Building | No Vendor Mentioned |
| ins_041 | "Financial controls a CFO should require when evaluating benefits administration platforms for a mid-market manufacturer" | CFO Employer | Requirements Building | No Vendor Mentioned |
| ins_042 | "Configurability requirements for an HRIS supporting multi-EIN, union, and seasonal workforces at a mid-market employer" | HRIS Benefits Admin | Requirements Building | No Vendor Mentioned |
| ins_043 | "Should a benefits brokerage prioritize a payroll-included platform or a benefits-led platform — what criteria actually matter?" | Broker Principal | Requirements Building | No Clear Winner |
| ins_044 | "What document workflow features should mid-market HR directors require for paperless onboarding and open enrollment?" | HR Director Employer | Requirements Building | No Clear Winner |
| ins_049 | "Benefits administration software that automatically reconciles carrier bills against active enrollment for a 500-employee company" | HR Director Employer | Shortlisting | No Clear Winner |
| ins_057 | "Benefits platforms that catch overpaid premiums and improve cost predictability for mid-market CFOs at 600-person companies" | CFO Employer | Shortlisting | No Clear Winner |
| ins_061 | "Configurable HRIS options for multi-EIN organizations with mixed union and non-union workforces in healthcare" | HRIS Benefits Admin | Shortlisting | No Clear Winner |
| ins_064 | "Benefits enrollment platforms with embedded decision support and cost estimators for employees at mid-market companies" | HR Director Employer | Shortlisting | No Clear Winner |
| ins_067 | "HR platforms with strong I-9, ACA, and document automation for mid-market employers in regulated industries" | HR Director Employer | Shortlisting | No Clear Winner |
| ins_075 | "BerniePortal vs Ease for SMB-heavy brokerages — feature gap analysis for an agency with 60 employer groups" | Benefits Account Manager | Comparison | No Clear Winner |
| ins_077 | "PlanSource vs Businessolver — open enrollment experience Comparison for a 750-person mid-market employer" | HR Director Employer | Comparison | No Clear Winner |
| ins_080 | "Carrier connectivity Comparison for medical, dental, and voluntary benefits — Employee Navigator vs Selerix" | Benefits Account Manager | Comparison | No Clear Winner |
| ins_081 | "PlanSource vs bswift for a TPA that needs fast multi-employer deployment and scalable carrier feeds" | Tpa Operations Lead | Comparison | No Clear Winner |
| ins_082 | "Businessolver vs PlanSource decision support — which one actually helps employees pick the right plan during open enrollment?" | HR Director Employer | Comparison | No Clear Winner |
| ins_086 | "PlanSource vs Businessolver — which handles ACA reporting and audit prep better for a mid-market employer?" | HR Director Employer | Comparison | No Clear Winner |
| ins_094 | "isolved People Cloud vs Employee Navigator — single-vendor HCM versus broker-led benefits administration" | CFO Employer | Comparison | No Clear Winner |
| ins_101 | "Compare Businessolver, PlanSource, and Employee Navigator on open enrollment workflow flexibility for mid-market" | HR Director Employer | Comparison | No Clear Winner |
| ins_103 | "Employee Navigator implementation problems for mid-size brokerages — what do reviews actually say?" | Broker Principal | Validation | No Clear Winner |
| ins_104 | "Ease customer complaints since the Employee Navigator acquisition, especially around roadmap and support" | Broker Principal | Validation | No Clear Winner |
| ins_105 | "BerniePortal limitations for mid-market employers with multi-EIN structures and complex eligibility rules" | HRIS Benefits Admin | Validation | No Clear Winner |
| ins_106 | "Hidden costs of PlanSource that mid-market employers don't expect at year two and beyond" | CFO Employer | Validation | No Clear Winner |
| ins_107 | "PlanSource open enrollment problems — what do reviews say about the employee experience and broker hand-off?" | HR Director Employer | Validation | No Clear Winner |
| ins_108 | "Selerix implementation timeline issues for TPAs scaling from 20 to 60 employer groups quickly" | Tpa Operations Lead | Validation | No Clear Winner |
| ins_109 | "Employee Navigator ADP integration issues — what do HRIS administrators report after going live?" | HRIS Benefits Admin | Validation | No Clear Winner |
| ins_110 | "Common Employee Navigator complaints from HR teams about carrier bill reconciliation and discrepancy handling" | HR Director Employer | Validation | No Clear Winner |
| ins_111 | "BerniePortal weaknesses for brokerages serving mid-market clients with complex billing and reporting needs" | Benefits Account Manager | Validation | No Clear Winner |
| ins_112 | "Employee Navigator reporting limitations for benefits administrators who need true ad-hoc reports without exports" | HRIS Benefits Admin | Validation | No Clear Winner |
| ins_113 | "isolved benefits-administration weaknesses — what's the catch when you bundle benefits with payroll?" | CFO Employer | Validation | No Clear Winner |
| ins_114 | "Businessolver implementation risks for a 600-employee mid-market company without enterprise-scale resources" | HR Director Employer | Validation | No Clear Winner |
| ins_115 | "Common BerniePortal complaints from benefits account managers handling everyday employer group support" | Benefits Account Manager | Validation | No Clear Winner |
| ins_116 | "PlanSource implementation problems for TPAs running multi-tenant deployments across 30+ employer groups" | Tpa Operations Lead | Validation | No Clear Winner |
| ins_117 | "Employee Navigator configurability issues for mid-market employers with non-standard workflows and approval chains" | HRIS Benefits Admin | Validation | No Clear Winner |
| ins_118 | "PlanSource decision-support shortcomings during open enrollment — where employees end up picking the wrong plan" | HR Director Employer | Validation | No Clear Winner |
| ins_119 | "Benefitfocus implementation timeline complaints from broker partners and mid-market employers" | Broker Principal | Validation | No Clear Winner |
| ins_122 | "Selerix carrier connectivity problems — what do account management teams complain about most?" | Benefits Account Manager | Validation | No Clear Winner |
| ins_123 | "bswift implementation risks for a mid-market TPA without dedicated enterprise integration resources" | Tpa Operations Lead | Validation | No Clear Winner |
| ins_124 | "Risks of staying on Employee Navigator and Ease post-acquisition for an independent mid-size brokerage" | Broker Principal | Validation | No Clear Winner |
| ins_125 | "PlanSource API limitations for benefits administrators building custom payroll and 401k integrations" | HRIS Benefits Admin | Validation | No Clear Winner |
| ins_126 | "Businessolver open enrollment complaints — what mid-market HR directors warn other buyers about" | HR Director Employer | Validation | No Clear Winner |
| ins_128 | "How to make the business case for a white-label benefits platform to a brokerage's partner group and board" | Broker Principal | Consensus Creation | No Clear Winner |
| ins_129 | "Justifying a configurable benefits platform investment to a CFO at a mid-market employer — what numbers move the needle?" | CFO Employer | Consensus Creation | No Vendor Mentioned |
| ins_130 | "Quantifying the cost of manual open enrollment for a 400-person employer to build the savings argument" | HR Director Employer | Consensus Creation | No Vendor Mentioned |
| ins_132 | "Typical payback period for switching from Employee Navigator or PlanSource to a more configurable platform" | CFO Employer | Consensus Creation | No Clear Winner |
| ins_133 | "Risk-based business case for upgrading I-9 and ACA document automation tooling at a 500-person company" | HR Director Employer | Consensus Creation | No Vendor Mentioned |
| ins_135 | "Three-year TCO Comparison for a benefits platform plus ADP versus a full HCM suite at a 350-person mid-market employer" | CFO Employer | Consensus Creation | |
| ins_136 | "How to argue internally for replacing a legacy benefits platform that no longer integrates cleanly with payroll" | HRIS Benefits Admin | Consensus Creation | |
| ins_137 | "Strategic argument for why mid-market brokerages should diversify off Employee Navigator and Ease post-merger" | Broker Principal | Consensus Creation | |
| ins_138 | "Building the executive case for moving a TPA off a legacy ben admin platform onto multi-tenant configurable software" | Tpa Operations Lead | Consensus Creation | |
| ins_139 | "Draft an RFP for a benefits administration platform for a 500-employee mid-market employer with strong open enrollment, ACA compliance, and ADP integration requirements" | HR Director Employer | Artifact Creation | |
| ins_140 | "Create a vendor scorecard comparing Employee Navigator, BerniePortal, and PlanSource for a 100-broker agency evaluating white-label fit" | Broker Principal | Artifact Creation | |
| ins_141 | "Build a 3-year TCO model for a benefits administration platform plus ADP Workforce Now versus a full HCM suite at a 400-person company" | CFO Employer | Artifact Creation | |
| ins_142 | "Write evaluation criteria a TPA can use to assess multi-tenant benefits administration platforms onboarding 50+ employer groups annually" | Tpa Operations Lead | Artifact Creation | |
| ins_143 | "Create a security and compliance questionnaire for evaluating benefits administration platforms in healthcare and financial services" | HRIS Benefits Admin | Artifact Creation | |
| ins_144 | "Draft an RFP focused on premium bill reconciliation, carrier connectivity, and data accuracy for a mid-market employer's benefits platform replacement" | HR Director Employer | Artifact Creation | |
| ins_145 | "Create a vendor Comparison matrix focused on implementation speed, broker UI, and white-label customization for benefits agencies serving mid-market clients" | Broker Principal | Artifact Creation | |
| ins_146 | "Draft technical evaluation criteria for ADP Workforce Now integration depth — what fields, what cadence, what error handling?" | HRIS Benefits Admin | Artifact Creation | |
| ins_147 | "Build a side-by-side scorecard for PlanSource, Employee Navigator, and isolved on cost predictability and contract flexibility for a mid-market CFO" | CFO Employer | Artifact Creation | |
| ins_148 | "Write a buyer's checklist for evaluating employee decision-support tools embedded in mid-market benefits enrollment platforms" | HR Director Employer | Artifact Creation | |
| ins_149 | "Create a vendor risk and platform-defensibility scorecard for a TPA evaluating Employee Navigator, PlanSource, and Selerix" | Tpa Operations Lead | Artifact Creation | |
| ins_150 | "Draft a reporting requirements document for a benefits platform at a 400-person mid-market employer with weekly executive reporting needs" | HRIS Benefits Admin | Artifact Creation |
Queries where Insynctive is mentioned but a competitor is positioned more favorably.
| ID | Query | Persona | Buying Job | Winner | Insynctive Position |
|---|---|---|---|---|---|
| ins_001 | "What are mid-size benefits brokerages doing now that their main ben admin platform is getting acquired?" | Broker Principal | Problem Identification | No Clear Winner | Brief Mention |
| ins_002 | "How are TPAs scaling employer onboarding without hiring an account manager for every new group?" | Tpa Operations Lead | Problem Identification | No Clear Winner | Brief Mention |
| ins_014 | "Build our own broker portal vs license a white-label benefits platform, what's the actual cost difference for a 200-group agency?" | Broker Principal | Solution Exploration | No Clear Winner | Mentioned In List |
| ins_024 | "Fastest ways for a benefits brokerage to stand up new employer groups in a single platform without a custom build" | Benefits Account Manager | Solution Exploration | Employee Navigator | Strong 2nd |
| ins_047 | "Configurable HRIS options for a mid-market company keeping its existing payroll and ERP systems in place" | HRIS Benefits Admin | Shortlisting | Rippling | Mentioned In List |
| ins_054 | "Best HRIS platforms for a mid-market employer with strict ACA reporting and I-9 compliance requirements" | HR Director Employer | Shortlisting | Rippling | Brief Mention |
| ins_055 | "White-label HR and benefits platforms for TPAs that don't want to be locked into a broker-mediated distribution model" | Tpa Operations Lead | Shortlisting | Selerix | Mentioned In List |
| ins_063 | "Alternatives to Employee Navigator and Ease for mid-size brokerage agencies that want a defensible product roadmap" | Broker Principal | Shortlisting | Rippling | Mentioned In List |
| ins_088 | "How does Employee Navigator handle ADP Workforce Now sync for a multi-EIN organization with 600 employees?" | HRIS Benefits Admin | Comparison | Employee Navigator | Brief Mention |
| ins_096 | "How does Insynctive compare to Employee Navigator on premium reconciliation for a 500-employee company?" | HR Director Employer | Comparison | Employee Navigator | Strong 2nd |
| ID | Query | Persona | Buying Job | Winner | Insynctive Position |
|---|---|---|---|---|---|
| ins_098 | "Insynctive Hub vs Employee Navigator on ADP Workforce Now integration for mid-market employers already on ADP" | HRIS Benefits Admin | Comparison | Employee Navigator | Strong 2nd |
| ins_099 | "Why are brokers comparing Insynctive against Ease post-acquisition, and what's the actual feature gap?" | Broker Principal | Comparison | No Clear Winner | Mentioned In List |
| ins_102 | "Benefitfocus vs Employee Navigator for a brokerage thinking about switching to agency-branded portals" | Broker Principal | Comparison | Employee Navigator | Listed |
| ins_120 | "Insynctive customer reviews from brokerages and mid-market employers — what do they actually say?" | Broker Principal | Validation | No Clear Winner | Mentioned In List |
| ins_121 | "Insynctive limitations a CFO should know about before signing a multi-year contract for a 500-person company" | CFO Employer | Validation | No Clear Winner | Mentioned In List |
| ins_127 | "ROI of automated premium bill reconciliation for a 600-employee mid-market employer — typical payback period?" | CFO Employer | Consensus Creation | No Clear Winner | Brief Mention |
| ins_131 | "Case studies of TPAs cutting employer onboarding from weeks to days after moving to a multi-tenant platform" | Tpa Operations Lead | Consensus Creation | No Clear Winner | Mentioned In List |
Who’s winning when Insynctive isn’t — and who controls the narrative at each buying stage.
[TL;DR] Insynctive wins 7.3% of queries (11/150), ranks #4 in SOV — H2H record: 9W–10L across 8 competitors.
SOV rank 4 of 10 (30 mentions) and a 4W-5L-11T H2H record vs Employee Navigator show Insynctive is a peer-level competitor when visible — not an afterthought — but the early-funnel visibility gap means fewer buyers ever reach the Comparison moment where Insynctive performs competitively.
| Company | Mentions | Share |
|---|---|---|
| Employee Navigator | 77 | 30.4% |
| Rippling | 40 | 15.8% |
| Selerix | 36 | 14.2% |
| Insynctive | 30 | 11.9% |
| Benefitfocus | 22 | 8.7% |
| BambooHR | 17 | 6.7% |
| isolved | 15 | 5.9% |
| Paycor | 13 | 5.1% |
| PrismHR | 2 | 0.8% |
| Namely | 1 | 0.4% |
When Insynctive and a competitor both appear in the same response, who gets the recommendation? One query with multiple competitors generates a matchup against each — so H2H totals will exceed the query count.
Win = primary recommendation (cross-platform majority). Loss = competitor was. Tie = neither or third party.
For the 125 queries where Insynctive is completely absent:
Vendors appearing in responses not in Insynctive’s defined competitive set.
[Data] High-intent win rate (conditional, wins/visible): 38.9% (7/18 visible high-intent queries). High-intent win rate (unconditional, wins/total): 8.5% (7/82 total high-intent queries). SOV rank: 4th of 10 companies (30 mentions, 11.9% share of 253 total mentions).
Top SOV competitors: Employee Navigator (77 mentions, 30.4% share), Rippling (40, 15.8%), Selerix (36, 14.2%). H2H records — vs Employee Navigator: 4W-5L-11T (20 co-appearing queries); vs Selerix: 2W-3L-7T (12 queries); vs Rippling: 0W-2L-6T (8 queries); vs isolved: 1W-0L-1T (2 queries).
[Synthesis] SOV rank 4 of 10 reflects Insynctive's presence in the category but trails the top three competitors substantially in mention volume. The H2H record vs Employee Navigator (4W-5L-11T across 20 co-appearing queries) reveals a peer-level competitive relationship: the platforms tie on 11 of 20 queries where both appear, meaning AI systems frequently present them as comparable alternatives — a positioning that is commercially valuable if Insynctive can be present earlier in the buyer journey. Note the metric distinction: H2H win rate measures pairwise matchups (when both appear in the same response), while the 8.5% unconditional win rate (7/82 high-intent queries) measures how often Insynctive wins regardless of whether any competitor appears.
Insynctive's H2H performance confirms product-level competitiveness; the unconditional win rate confirms that low early-funnel visibility — not competitive weakness — is the primary commercial constraint.
What AI reads and trusts in this category.
[TL;DR] Insynctive had 18 unique pages cited across buyer queries, ranking #4 among all cited domains. 10 high-authority domains cite competitors but not Insynctive.
59 citation instances across 18 unique pages and a domain rank of 4th confirm Insynctive's citation engine is working but structurally concentrated; the 30+ content pages excluded from the sitemap are not yet contributing to this footprint, and 10 third-party citation opportunities remain untapped.
Note: Domain-level citation counts (above) tally instances per individual domain. Competitor-level counts (below) aggregate across all domains owned by a single vendor, which may include subdomains.
Non-competitor domains citing other vendors but not Insynctive — off-domain authority opportunities.
These domains cited competitors but did not cite Insynctive pages in the queries analyzed. This reflects citation patterns in AI responses, not overall platform presence.
[Data] Total unique pages cited: 18. Citation instances for insynctive.com domain: 59 citation instances across all queries. Client domain rank: 4th.
Third-party citation gap: 10 missing third-party Validation instances. Platform spread: ChatGPT leads Claude by 7pp and Gemini by 2pp across all 150 queries tested.
[Synthesis] 18 unique pages carrying 59 citation instances means Insynctive's citation load is heavily concentrated on a small page set — the existing /compare and /resources pages that AI crawlers have discovered. With a domain rank of 4th and 10 third-party citation gaps outstanding, the citation foundation is functional but structurally limited. The 30+ content-library pages excluded from the sitemap are not contributing to this footprint at all; fixing the sitemap gap is the mechanism most likely to distribute citation signals across the full content library and compound the existing domain authority without requiring new content creation.
Three layers of recommendations ranked by commercial impact and implementation speed.
[TL;DR] 18 priority recommendations (plus 2 near-rebuild optimizations) targeting 139 gap queries (122 invisible, 17 positioning gaps). 5 L1 technical fixes + 1 verification checks, 10 content optimizations (L2), 2 new content initiatives (L3).
24 recommendations prioritize L1 infrastructure first — the sitemap fix (sitemap_excludes_resources_library) alone unblocks AI crawler access to Insynctive's strongest 30+ content pages — then 10 L2 content optimizations, then 8 L3 NIO recommendations that create the two Comparison-format pages competitors currently win by default.
Reading the priority numbers: Recommendations are ranked 1–18 across all three layers by commercial impact × implementation speed. Within each layer, items appear in priority order. Gaps in the sequence (e.g., L1 shows 1, 2, then 12) mean higher-priority items belong to a different layer.
Configuration and infrastructure changes. Owner: Engineering / DevOps. Timeline: Days to weeks.
| Priority | Finding | Impact | Timeline |
|---|---|---|---|
| #1 | Sitemap excludes the entire /resources content library, including all Comparison pages | High | < 1 day |
| #11 | /hr-solutions-product-overview is ~150 words of body content despite being the primary nav 'Product Lines' destination | Medium | 1-3 days |
| #12 | Every URL in pages-sitemap.xml shares the same lastmod, making the freshness signal unreliable | Medium | < 1 day |
| #13 | Heading hierarchy on main nav pages is weaker than on the resources library | Medium | 1-3 days |
| #14 | JSON-LD schema markup could not be assessed; recommend manual verification | Medium | 1-2 weeks |
Items requiring manual review before determining if action is needed.
| Priority | Finding | Impact | Timeline |
|---|---|---|---|
| #18 | Meta descriptions, canonical tags, and OG tags could not be assessed; recommend manual verification | Low | < 1 day |
Click any row to expand full issue/fix detail.
Existing pages that need restructuring or deepening. Owner: Content Team. Timeline: Weeks.
The /carrier-integrations page does not state Insynctive's specific carrier count by benefit type (medical, dental, vision, ancillary, voluntary) — buyers asking 'must-have features for EDI across 100+ employer groups' find no carrier count claim to evaluate, while Employee Navigator's content leads with specific carrier totals (600+ carriers) that AI systems extract and cite as the benchmark answer. The /carrier-integrations page does not include a Comparison of EDI vs API connectivity approaches with real-world tradeoffs — buyers asking 'EDI feeds versus API connections for enrollment data — real pros and cons' find no Insynctive answer, leaving the solution exploration moment to generic technical content or competitor pages that do address this question. The /carrier-integrations page contains no competitive Comparison section addressing Selerix's carrier connectivity limitations — buyers at Validation stage asking 'Selerix carrier connectivity problems' find no Insynctive-authored content that names this competitor's failure modes, which is the citation opportunity to position Insynctive as the credible alternative.
Queries affected: ins_026, ins_036, ins_066, ins_080, ins_122
The /premium-benefits-administration page is structured as a product pitch rather than an educational resource — buyers asking 'why does open enrollment still take six weeks for mid-market employers' find a page describing Insynctive's capabilities rather than a page that explains the root causes of OE delays and positions Insynctive as the solution. The buyer's problem-identification question goes unanswered. The /premium-benefits-administration page does not provide an evaluation framework for OE software — buyers asking 'key requirements for evaluating open enrollment software for a 400-person employer' find no checklist or requirements specification, making this page useless for requirements-building stage buyers who need a structured evaluation tool. The /premium-benefits-administration and /employee-benefits-decision-support pages combined do not address the decision-support Comparison query 'Businessolver vs PlanSource decision support — which actually helps employees pick the right plan' — Insynctive has decision-support capabilities but no Comparison-format content positioning it against Businessolver, which is the default named answer for these queries.
Queries affected: ins_006, ins_017, ins_025, ins_029, ins_039, ins_044, ins_045, ins_059, ins_064, ins_082, ins_107, ins_118, ins_126, ins_130
The /compare/employee-navigator-alternatives page positions Insynctive as a forward-looking alternative but contains no analysis of why brokerages are reconsidering Employee Navigator now — the page reads as aspirational pitch rather than responding to the acquisition-driven anxiety driving these queries. The /compare/employee-navigator-alternatives page does not address BerniePortal's known limitations for mid-market employer groups (complex billing, ad-hoc reporting, multi-EIN structures), leaving Comparison-stage buyers who ask about 'BerniePortal for 60 employer groups' with no Insynctive answer. The /compare/employee-navigator-alternatives page presents no head-to-head evidence on broker book defensibility — no data on client retention rates, no specific platform migration case, no quantified onboarding speed Comparison — the exact claims that broker principals require at the Validation and consensus stages.
Queries affected: ins_070, ins_071, ins_084, ins_087, ins_103, ins_104, ins_124
The /hris-vs-hcm page frames the HRIS vs HCM decision conceptually but does not provide CFO-facing financial decision criteria — buyers asking 'tradeoffs CFOs weigh between an all-in-one HCM suite and a best-of-breed benefits platform' find no TCO analysis, PEPM pricing Comparison, or financial scenario model on this page, leaving the CFO's actual decision framework unanswered. The /hris-vs-hcm page does not include a compliance requirements checklist for HRIS platform evaluation — buyers asking 'compliance requirements checklist for evaluating HRIS platforms — I-9, ACA, HIPAA, and what else mid-market employers should pin down' find no structured checklist on this page, which is exactly the format requirements-building buyers need and that competitor educational content provides. The /hris-vs-hcm page does not address isolved People Cloud or Rippling by name as the primary competing options in the payroll-consolidated HCM category — buyers asking 'isolved vs PlanSource for a 350-person company' or 'isolved People Cloud vs Employee Navigator' never find Insynctive because the page doesn't insert itself into the specific platform Comparison buyers are conducting.
Queries affected: ins_005, ins_010, ins_016, ins_020, ins_028, ins_034, ins_043, ins_050, ins_076, ins_094, ins_114
The /integrated-data-hub-api-solutions page describes Insynctive's integration hub in general terms but does not list specific payroll systems Insynctive connects to — buyers asking 'best platforms that play well with existing HRIS, payroll, and 401k systems' find no payroll partner list to evaluate, while Employee Navigator's integration page leads with '83 payroll partners' as a specific, citable claim. The /integrated-data-hub-api-solutions page contains no CFO-facing framework for evaluating integration TCO and contract terms — buyers asking 'questions a CFO should ask benefits administration vendors about TCO, contract terms, and PEPM pricing' find no structured question set on this page, leaving them to use whatever framework competitor content provides. The /integrated-data-hub-api-solutions page does not document isolved or PlanSource API limitations — buyers at Validation stage asking 'isolved benefits-administration weaknesses when you bundle benefits with payroll' or 'PlanSource API limitations for custom payroll integrations' find no Insynctive-authored answer, missing a competitive differentiation opportunity.
Queries affected: ins_008, ins_012, ins_022, ins_032, ins_058, ins_065, ins_069, ins_113, ins_125, ins_129
The /benefits-billing-reconciliation-guide does not quantify the cost of the problem it solves — buyers asking 'what does it actually cost a 500-person company to keep paying premiums for terminated employees nobody caught' find no dollar figure or percentage-of-payroll benchmark on this page, which is the first data point a CFO requires before authorizing a vendor evaluation. The /benefits-billing-reconciliation-guide contains no financial controls framework for CFO evaluation — buyers asking 'financial controls a CFO should require when evaluating benefits administration platforms' find no structured checklist on this page, leaving them to default to vendor Comparison sites that do provide this format. The /benefits-billing-reconciliation-guide does not directly compare Insynctive's reconciliation accuracy or error-detection methodology to Employee Navigator's, despite the /compare/insynctive-vs-employee-navigator page being linked from this area — buyers comparing 'Employee Navigator vs PlanSource for reconciliation' never see Insynctive claim a reconciliation advantage.
Queries affected: ins_003, ins_004, ins_019, ins_041, ins_049, ins_053, ins_057, ins_072, ins_085, ins_110, ins_132
The /white-label-benefits-administration-for-brokers page describes Insynctive's white-label capabilities in general terms but provides no implementation timeline data — buyers asking 'Implementation speed: Employee Navigator vs PlanSource for onboarding new groups' find no specific Insynctive claim to evaluate against the 'days rather than weeks' promise. The /white-label-benefits-administration-for-brokers page has no case study modules with specific agency size data (broker group count before/after, headcount ratios, onboarding time reduction) — leaving consensus-creation buyers ('How do brokerages double group count without doubling headcount?') without the quantified evidence they need to build a board-level business case. The /white-label-benefits-administration-for-brokers page does not address vendor risk assessment criteria that TPAs applying a 10-year platform selection framework require — specifically: data portability, acquisition/exit scenarios, SLA commitments, and roadmap transparency — making it unable to compete on the 'long-term platform foundation' queries where bswift and Selerix win by having enterprise-facing content.
Queries affected: ins_052, ins_073, ins_075, ins_079, ins_081, ins_090, ins_092, ins_108, ins_116, ins_119, ins_123, ins_128, ins_131, ins_134
The /integrations/adp-workforce-now page does not specify bi-directional sync cadence, field coverage, or error-handling methodology — buyers asking 'technical questions about ADP Workforce Now integration depth and bi-directional sync cadence' find no specific technical claim on this page, while Employee Navigator's ADP integration content leads with specific sync frequency and field-level coverage data. The /integrations/adp-workforce-now page contains no Comparison of Insynctive vs Employee Navigator on ADP WFN integration depth — buyers asking 'PlanSource vs Selerix on ADP integration depth and sync reliability' (a Comparison where Insynctive could insert itself as a named alternative) find no Insynctive answer because the page describes Insynctive's integration only, not how it compares to the platforms buyers are already evaluating. The /integrations/adp-workforce-now page contains no documentation of common ADP integration failure modes and how Insynctive handles them — buyers asking 'Employee Navigator ADP integration issues — what do HRIS administrators report after going live' find no Insynctive-authored answer, missing the opportunity to turn a Validation-stage competitor query into an Insynctive citation.
Queries affected: ins_018, ins_035, ins_051, ins_074, ins_109
The /reporting-analytics page does not specify which report types HRIS administrators can run without filing IT tickets — the key differentiator buyers ask about ('ad-hoc enrollment and deduction reports without IT tickets') is a specific capability claim the page must make explicitly to be cited for requirements-building queries. The /reporting-analytics page does not document Employee Navigator's reporting limitations despite the /compare/insynctive-vs-Benefitfocus-vs-Selerix-reporting Comparison being linked from this area — buyers asking 'Employee Navigator reporting limitations for benefits administrators who need true ad-hoc reports without exports' find no Insynctive answer, and Employee Navigator is the primary Comparison competitor for reporting queries (wins ins_083 by default). The /reporting-analytics page and the /document-automation-process-management page do not present a unified picture of HR self-service for document workflows — buyers asking 'best HR platforms for self-service I-9, W-4, and benefits document signing' must navigate to a separate URL, reducing the probability that AI systems extract both capabilities when answering self-service HR questions.
Queries affected: ins_038, ins_056, ins_060, ins_067, ins_083, ins_112
The /flexible-hris-solutions page describes HRIS configurability in general terms but does not document specific use cases for multi-EIN organizations, union populations, or seasonal workforces — buyers asking 'configurability requirements for an HRIS supporting multi-EIN, union, and seasonal workforces' find no evidence that Insynctive has addressed these specific organizational structures. The /flexible-hris-solutions page does not compare Insynctive's configurability against Employee Navigator's or BerniePortal's known limitations for complex employers — buyers asking 'BerniePortal limitations for mid-market employers with multi-EIN structures' or 'Employee Navigator configurability issues for non-standard workflows' find no Insynctive-authored answer that inserts the platform into this competitor Comparison. The /flexible-hris-solutions page does not address the legacy-to-cloud migration question — buyers asking 'modern cloud HRIS vs keeping our legacy on-prem system — real options for mid-size companies that can't gut everything' find a cloud HRIS sales pitch rather than a structured Comparison of migration approaches that would serve buyers in genuine legacy-cloud evaluation.
Queries affected: ins_009, ins_013, ins_023, ins_037, ins_042, ins_061, ins_078, ins_089, ins_093, ins_105, ins_115, ins_117
Net new content addressing visibility and positioning gaps. Owner: Content Strategy. Timeline: Months.
Open enrollment workflows register 0% AI visibility across all 12 queries tested for this feature (0/12), making it Insynctive's most complete blind spot despite being a core product capability. The three queries in this cluster all share the same diagnostic: the Comparison buying job requires a Comparison-format page, and no such page exists for open enrollment experience, so AI systems either default to Employee Navigator (ins_091) or name no winner — never Insynctive. HR directors comparing open enrollment platforms form their finalist list at this Comparison stage; absence here means Insynctive is never considered for that seat. A dedicated open enrollment experience Comparison page creates the first citation-ready surface for this buying moment across all three major AI platforms.
ChatGPT (high): Comparison-format queries with named competitors are among ChatGPT's highest-citation query types; the 'Employee Navigator vs PlanSource on open enrollment' framing maps directly to the structured Comparison answers ChatGPT generates. ChatGPT's freshness weighting (cited pages updated within 30 days) means a dated Comparison page with a specific lastmod would be prioritized over undated feature pages. Claude (medium): Claude's platform visibility is 7pp lower than ChatGPT across this audit (platform_delta: 7pp gap, claude lower), suggesting Claude draws from a broader and more conservative source set for Comparison queries. A well-structured Comparison page with factual depth and balanced analysis would earn citation, but Claude may also draw from G2 and review aggregators rather than a single Insynctive-owned page. Gemini (high): Gemini's Luminous Sources pattern favors structured data with comprehensive coverage and clear entity relationships. A Comparison page with FAQPage schema markup (question-as-H2 structure already used on /compare/* pages) and explicit entity names (platform names, feature names, employer size ranges) aligns directly with Gemini's citation model. Gemini trails ChatGPT by only 2pp in this audit, suggesting similar content receptivity.
ACA compliance and audit prep represent a veto-holding requirement for HR directors at mid-market employers in regulated industries — and the Comparison buying job for this topic produces zero Insynctive presence because no Comparison-format page exists for compliance capabilities. Insynctive's compliance feature area shows 14.3% visibility overall (1/7 queries), but the single Comparison-stage compliance query (ins_086) is routed to L3 because existing compliance pages are classified as blog, case study, or feature pages — none as Comparison pages. An HR director asking ins_086 and finding only Businessolver and PlanSource compared concludes that compliance is not an Insynctive differentiator, which is false. A dedicated compliance Comparison page converts Insynctive's I-9, ACA, and HIPAA capabilities into a cited Comparison advantage at the highest-stakes moment of the evaluation.
ChatGPT (high): Compliance queries with named regulatory frameworks (ACA, I-9, HIPAA) are high-specificity query types that ChatGPT answers with structured comparisons; a Comparison page using regulatory terminology as heading text and citing specific compliance features would match ChatGPT's citation pattern for this query class. Claude (medium): Claude handles compliance topics carefully and often cites authoritative third-party sources (DOL, IRS, SHRM) alongside vendor Comparison pages; a well-sourced compliance Comparison page would be cited, but Claude's broader source preference means off-domain citations (SHRM, compliance trade press) compound significantly with the on-domain page for this topic. Gemini (high): Compliance regulatory entities (ACA, I-9, HIPAA, DOL) are well-defined entities in Gemini's knowledge graph; a structured Comparison page with explicit entity references, FAQPage schema, and comprehensive regulatory coverage aligns with the Luminous Sources DOM pattern observed in this audit and maximizes Gemini citation probability.
All recommendations across all three layers, ranked by commercial impact × implementation speed.
sitemap-geo.xml (the file referenced from robots.txt) and its two child sitemaps (pages-sitemap.xml, pricing-plans-sitemap.xml) list only 20 URLs covering the primary Wix-managed pages. The /resources content hub at /resources surfaces 30+ additional articles that are not in any sitemap: 6 platform Comparison pages under /compare/* (Insynctive vs Employee Navigator, vs Benefitfocus+Selerix, vs Businessolver, Employee Navigator Alternatives, Multi-Tenant vs Employer-Direct, Standalone HRIS vs Integrated), feature deep-dives (/carrier-integrations, /reporting-analytics, /employee-benefits-decision-support, /compliance, /integrations, /integrations/adp-workforce-now, /white-label-benefits-administration-for-brokers, /benefits-administration-for-brokers, /for-service-providers, /employee-onboarding, /benefits-billing-reconciliation-guide), educational/blog content (/hr-document-automation, /i9-compliance-guide, /compliance-at-50-employees, /i9-compliance-in-onboarding, /hris-buyers-guide, /hris-vs-hcm, /hris-for-mid-market), data-integration articles (/data-integration-hub/why-payroll-benefits-sync-fails, /data-integration-hub/payroll-benefits-integration-approaches), calculators/templates (/resources/benefits-platform-tco-calculator, /resources/internal-business-case-benefits-platform, /resources/Chief Financial Officer-guide-benefits-platform-analytics), and a case study (/case-studies/enterprise-document-automation-fleet-compliance). These pages are reachable only through the /resources index page or sidebar nav links.
3 of the 4 L3 gap queries target open enrollment experience comparisons where Insynctive's existing pages are classified as feature, landing_page, or product type — not the Comparison page type the buying_job requires. The routing system's AFFINITY OVERRIDE confirms the root cause: content exists but in the wrong format, making a dedicated Comparison page creation (not a page edit) the minimum viable fix.
The /carrier-integrations page does not state Insynctive's specific carrier count by benefit type (medical, dental, vision, ancillary, voluntary) — buyers asking 'must-have features for EDI across 100+ employer groups' find no carrier count claim to evaluate, while Employee Navigator's content leads with specific carrier totals (600+ carriers) that AI systems extract and cite as the benchmark answer.
1 Comparison-stage query on ACA compliance and audit prep is routed to L3 because Insynctive's compliance-related content (blog posts, case studies, feature pages) does not include a dedicated compliance Comparison page against Businessolver and PlanSource. The AFFINITY OVERRIDE routing confirms this is a content type gap: Insynctive has compliance content, but not in Comparison format.
The /premium-benefits-administration page is structured as a product pitch rather than an educational resource — buyers asking 'why does open enrollment still take six weeks for mid-market employers' find a page describing Insynctive's capabilities rather than a page that explains the root causes of OE delays and positions Insynctive as the solution. The buyer's problem-identification question goes unanswered.
The /compare/employee-navigator-alternatives page positions Insynctive as a forward-looking alternative but contains no analysis of why brokerages are reconsidering Employee Navigator now — the page reads as aspirational pitch rather than responding to the acquisition-driven anxiety driving these queries.
The /hris-vs-hcm page frames the HRIS vs HCM decision conceptually but does not provide CFO-facing financial decision criteria — buyers asking 'tradeoffs CFOs weigh between an all-in-one HCM suite and a best-of-breed benefits platform' find no TCO analysis, PEPM pricing Comparison, or financial scenario model on this page, leaving the CFO's actual decision framework unanswered.
The /integrated-data-hub-api-solutions page describes Insynctive's integration hub in general terms but does not list specific payroll systems Insynctive connects to — buyers asking 'best platforms that play well with existing HRIS, payroll, and 401k systems' find no payroll partner list to evaluate, while Employee Navigator's integration page leads with '83 payroll partners' as a specific, citable claim.
The /benefits-billing-reconciliation-guide does not quantify the cost of the problem it solves — buyers asking 'what does it actually cost a 500-person company to keep paying premiums for terminated employees nobody caught' find no dollar figure or percentage-of-payroll benchmark on this page, which is the first data point a CFO requires before authorizing a vendor evaluation.
The /white-label-benefits-administration-for-brokers page describes Insynctive's white-label capabilities in general terms but provides no implementation timeline data — buyers asking 'Implementation speed: Employee Navigator vs PlanSource for onboarding new groups' find no specific Insynctive claim to evaluate against the 'days rather than weeks' promise.
The 'Product Lines' link in the primary nav routes to /hr-solutions-product-overview. The page renders four product-line headers (Document Automation, Comprehensive Benefits Administration, Human Resource Information Management, Insynctive Integrated Hub) plus an H1, but body content is roughly 150 words total — a few sentences per product line. Each product line links to its own deeper page, but the hub itself does not carry the substantive treatment an LLM would cite when answering 'what does Insynctive sell.' content_depth scores 0.2 for this page. The /our-clients hub (also linked from primary nav) has the same shape: ~400 words, generic broker pitch.
All 19 entries in pages-sitemap.xml carry an identical lastmod value of 2026-05-08. This is a Wix-generated stamp emitted at site re-publish, not an actual modification date for the individual pages. The /pricing-plans-sitemap.xml entry shows 2026-05-07. The same uniform-date pattern was observed in this client's prior re-audit (run-2026-05-20-1).
Resources-library pages (/compare/*, /resources/*, /carrier-integrations, /compliance, /reporting-analytics) use descriptive noun-phrase H2s that read as standalone passage labels (e.g., 'How Insynctive's Carrier Feeds Catch Errors Before the Invoice Arrives,' 'Compliance Capability Comparison: Insynctive vs PlanSource vs Businessolver'). The Wix-managed commercial pages use generic or stylistic H2/H3s — /features has 'Digitize / Secure / Automate / Comply' as standalone H2s; /pricing-plans/list uses 'PEPM' three times as H2; /flexible-hris-solutions mixes descriptive and label-style headings. The /demo page has its H1 phrase split across an H1 line and an H2 line ('Modernizing HR Operations with' / 'Customizable, Automated Solutions').
The fetch tooling used for this analysis returns rendered markdown rather than raw HTML, so JSON-LD <script type='application/ld+json'> blocks are not visible in the captured content for any of the 46 inventoried pages. Schema_coverage is therefore recorded as null across the inventory.
The /integrations/adp-workforce-now page does not specify bi-directional sync cadence, field coverage, or error-handling methodology — buyers asking 'technical questions about ADP Workforce Now integration depth and bi-directional sync cadence' find no specific technical claim on this page, while Employee Navigator's ADP integration content leads with specific sync frequency and field-level coverage data.
The /reporting-analytics page does not specify which report types HRIS administrators can run without filing IT tickets — the key differentiator buyers ask about ('ad-hoc enrollment and deduction reports without IT tickets') is a specific capability claim the page must make explicitly to be cited for requirements-building queries.
The /flexible-hris-solutions page describes HRIS configurability in general terms but does not document specific use cases for multi-EIN organizations, union populations, or seasonal workforces — buyers asking 'configurability requirements for an HRIS supporting multi-EIN, union, and seasonal workforces' find no evidence that Insynctive has addressed these specific organizational structures.
The fetch tooling returns rendered markdown and strips <head> metadata. We cannot confirm whether each inventoried page has a unique meta description, an accurate canonical tag, or complete OG/Twitter card markup. The site has a www-host preference (the canonical hostname used throughout is www.insynctive.com) but kg.client.domain is the bare 'insynctive.com' — the canonical tag should resolve any ambiguity for AI crawlers.
All three workstreams can start this week.
[Data] 24 total recommendations: 6 L1 technical fixes (5 diagnostic findings + 1 verification check), 10 L2 content optimizations (addressing 135 gap queries), 8 L3 NIO recommendations (targeting 4 gap queries requiring new Comparison-format content). Total items addressed: 145. Highest-priority L1: sitemap_excludes_resources_library (high severity, effort < 1 day, scope: 30+ currently excluded pages).
Gap breakdown: 122 invisibility gaps, 17 positioning gaps, 139 total query-level gaps.
[Synthesis] L1 executes first regardless of commercial priority because the sitemap fix (sitemap_excludes_resources_library) unblocks AI crawler access to the 30+ pages that all L2 optimizations target — improving content on undiscovered pages produces no citation gain. L2 is the highest-volume work but lowest structural risk: remediating existing pages that already attract some buyer traffic but underperform for AI extractability. L3 creates the two Comparison-format content types (open enrollment experience Comparison and ACA compliance Comparison) that no existing page can supply, targeting the buying stage where Insynctive currently cedes Comparison authority to Employee Navigator and Businessolver by default.
Gap coverage note: 99 of 139 gap queries (71%) are assigned to an L2 or L3 action item. 40 gap queries remain unrouted — these may represent edge-case queries that don’t cluster neatly or fall below the LLM’s grouping threshold.
Lineage-tagged. Every item carries its thread across cycles.
Carryover summary: carried: 7 · inherits_lineage: 7 · lineage-lost: 3 · new: 17 · ambiguous: 0
Every item carries a lineage tag. Resolved items appear in the A.2 scorecard, not here — Part C is only actionable work.
L1-001 — sitemap-geo.xml (the file referenced from robots.txt) and its two child sitemaps (pages-sitemap.xml, pricing-plans-sitemap.xml) list only 20 URLs covering the primary Wix-managed pages. The /resources content hub at /resources surfaces 30+ additional articles that are not in any sitemap: 6 platform comparison pages under /compare/* (Insynctive vs Employee Navigator, vs Benefitfocus+Selerix, vs Businessolver, Employee Navigator Alternatives, Multi-Tenant vs Employer-Direct, Standalone HRIS vs Integrated), feature deep-dives (/carrier-integrations, /reporting-analytics, /employee-benefits-decision-support, /compliance, /integrations, /integrations/adp-workforce-now, /white-label-benefits-administration-for-brokers, /benefits-administration-for-brokers, /for-service-providers, /employee-onboarding, /benefits-billing-reconciliation-guide), educational/blog content (/hr-document-automation, /i9-compliance-guide, /compliance-at-50-employees, /i9-compliance-in-onboarding, /hris-buyers-guide, /hris-vs-hcm, /hris-for-mid-market), data-integration articles (/data-integration-hub/why-payroll-benefits-sync-fails, /data-integration-hub/payroll-benefits-integration-approaches), calculators/templates (/resources/benefits-platform-tco-calculator, /resources/internal-business-case-benefits-platform, /resources/cfo-guide-benefits-platform-analytics), and a case study (/case-studies/enterprise-document-automation-fleet-compliance). These pages are reachable only through the /resources index page or sidebar nav links.
L1-011 — The 'Product Lines' link in the primary nav routes to /hr-solutions-product-overview. The page renders four product-line headers (Document Automation, Comprehensive Benefits Administration, Human Resource Information Management, Insynctive Integrated Hub) plus an H1, but body content is roughly 150 words total — a few sentences per product line. Each product line links to its own deeper page, but the hub itself does not carry the substantive treatment an LLM would cite when answering 'what does Insynctive sell.' content_depth scores 0.2 for this page. The /our-clients hub (also linked from primary nav) has the same shape: ~400 words, generic broker pitch.
L1-012 — All 19 entries in pages-sitemap.xml carry an identical lastmod value of 2026-05-08. This is a Wix-generated stamp emitted at site re-publish, not an actual modification date for the individual pages. The /pricing-plans-sitemap.xml entry shows 2026-05-07. The same uniform-date pattern was observed in this client's prior re-audit (run-2026-05-20-1).
L1-013 — Resources-library pages (/compare/*, /resources/*, /carrier-integrations, /compliance, /reporting-analytics) use descriptive noun-phrase H2s that read as standalone passage labels (e.g., 'How Insynctive's Carrier Feeds Catch Errors Before the Invoice Arrives,' 'Compliance Capability Comparison: Insynctive vs PlanSource vs Businessolver'). The Wix-managed commercial pages use generic or stylistic H2/H3s — /features has 'Digitize / Secure / Automate / Comply' as standalone H2s; /pricing-plans/list uses 'PEPM' three times as H2; /flexible-hris-solutions mixes descriptive and label-style headings. The /demo page has its H1 phrase split across an H1 line and an H2 line ('Modernizing HR Operations with' / 'Customizable, Automated Solutions').
L1-014 — The fetch tooling used for this analysis returns rendered markdown rather than raw HTML, so JSON-LD <script type='application/ld+json'> blocks are not visible in the captured content for any of the 46 inventoried pages. Schema_coverage is therefore recorded as null across the inventory.
L1-018 — The fetch tooling returns rendered markdown and strips <head> metadata. We cannot confirm whether each inventoried page has a unique meta description, an accurate canonical tag, or complete OG/Twitter card markup. The site has a www-host preference (the canonical hostname used throughout is www.insynctive.com) but kg.client.domain is the bare 'insynctive.com' — the canonical tag should resolve any ambiguity for AI crawlers.
L2-006 — The /compare/employee-navigator-alternatives page positions Insynctive as a forward-looking alternative but contains no analysis of why brokerages are reconsidering Employee Navigator now — the page reads as aspirational pitch rather than responding to the acquisition-driven anxiety driving these queries.
L2-007 — The /hris-vs-hcm page frames the HRIS vs HCM decision conceptually but does not provide CFO-facing financial decision criteria — buyers asking 'tradeoffs CFOs weigh between an all-in-one HCM suite and a best-of-breed benefits platform' find no TCO analysis, PEPM pricing comparison, or financial scenario model on this page, leaving the CFO's actual decision framework unanswered.
L2-008 — The /integrated-data-hub-api-solutions page describes Insynctive's integration hub in general terms but does not list specific payroll systems Insynctive connects to — buyers asking 'best platforms that play well with existing HRIS, payroll, and 401k systems' find no payroll partner list to evaluate, while Employee Navigator's integration page leads with '83 payroll partners' as a specific, citable claim.
L2-009 — The /benefits-billing-reconciliation-guide does not quantify the cost of the problem it solves — buyers asking 'what does it actually cost a 500-person company to keep paying premiums for terminated employees nobody caught' find no dollar figure or percentage-of-payroll benchmark on this page, which is the first data point a CFO requires before authorizing a vendor evaluation.
L2-010 — The /white-label-benefits-administration-for-brokers page describes Insynctive's white-label capabilities in general terms but provides no implementation timeline data — buyers asking 'Implementation speed: Employee Navigator vs PlanSource for onboarding new groups' find no specific Insynctive claim to evaluate against the 'days rather than weeks' promise.
L2-015 — The /integrations/adp-workforce-now page does not specify bi-directional sync cadence, field coverage, or error-handling methodology — buyers asking 'technical questions about ADP Workforce Now integration depth and bi-directional sync cadence' find no specific technical claim on this page, while Employee Navigator's ADP integration content leads with specific sync frequency and field-level coverage data.
L2-016 — The /reporting-analytics page does not specify which report types HRIS administrators can run without filing IT tickets — the key differentiator buyers ask about ('ad-hoc enrollment and deduction reports without IT tickets') is a specific capability claim the page must make explicitly to be cited for requirements-building queries.
L2-017 — The /flexible-hris-solutions page describes HRIS configurability in general terms but does not document specific use cases for multi-EIN organizations, union populations, or seasonal workforces — buyers asking 'configurability requirements for an HRIS supporting multi-EIN, union, and seasonal workforces' find no evidence that Insynctive has addressed these specific organizational structures.
NIO-002-ON-1 — Create /compare/open-enrollment-experience as a new comparison page: structure as an H1 question ('Which benefits platform delivers the best open enrollment experience for mid-market employers?'), then a feature-row comparison table (Employee Navigator, PlanSource, Businessolver, Insynctive) covering mobile experience, carrier-specific form automation, OE timeline benchmarks, and employee decision-support tools. Include a dated 'Last updated' stamp and real carrier names throughout to maximize AI citation readiness. Register the URL in sitemap-resources.xml and add FAQPage schema markup.
NIO-002-ON-2 — Add an H2 section titled 'Open Enrollment Experience: How Insynctive Compares to Employee Navigator and PlanSource' to the existing /employee-benefits-decision-support page — include a 3-4 row comparison table on decision-support tooling, employee self-service capabilities, and OE completion rate benchmarks. This creates a second citation surface for comparison-stage queries while the new dedicated page is in content review.
NIO-002-OFF-1 — Pursue structured inclusion in G2 and Capterra category comparison grids for 'Benefits Administration Software: Open Enrollment' — AI systems frequently cite G2 comparison matrices for feature-specific buying queries. Update Insynctive's G2 profile with quantified open enrollment feature data (carrier count, OE setup time, employee self-service rate) to feed into AI-cited comparison answers.
NIO-002-OFF-2 — Pitch 3-5 HR practitioner publications (SHRM, HR Dive, Employee Benefits News) a byline on 'Why Mid-Market Open Enrollment Still Takes Six Weeks — and How Automation Changes the Math,' authored by an Insynctive subject matter expert. Third-party citations from category-authority publications compound with the on-domain comparison page to build a multi-source citation footprint that increases AI confidence in Insynctive as a comparison-stage answer.
L2L3-003 — The /carrier-integrations page does not state Insynctive's specific carrier count by benefit type (medical, dental, vision, ancillary, voluntary) — buyers asking 'must-have features for EDI across 100+ employer groups' find no carrier count claim to evaluate, while Employee Navigator's content leads with specific carrier totals (600+ carriers) that AI systems extract and cite as the benchmark answer.
NIO-004-ON-1 — Create /compare/insynctive-vs-businessolver-compliance as a new comparison page: H1 framing around a buyer decision ('PlanSource vs Businessolver vs Insynctive for ACA Compliance and Audit Prep — Mid-Market Comparison'), followed by a 4-column compliance capability matrix (ACA reporting, I-9 automation, HIPAA audit trail, DOL/IRS documentation, penalty exposure reduction). Add a 'Questions to ask your compliance vendor' FAQ section using question-as-H2 formatting to qualify for FAQPage schema. Include a dated lastmod and link to the /i9-compliance-guide and /compliance pages as supporting evidence.
NIO-004-ON-2 — Add an H2 section 'ACA Compliance Comparison: Insynctive vs PlanSource vs Businessolver' to the existing /compliance page, structured as a 3-column capability matrix. This second citation surface can intercept comparison-stage compliance queries while the dedicated comparison page is in content review, and it ensures the /compliance page — currently classified as a feature page — gains a comparison-format section that AI systems can extract.
NIO-004-OFF-1 — Contribute a compliance-focused byline or data brief to HR compliance trade outlets (SHRM HR Compliance, HR Compliance Expert, SHRM Executive Network) on 'ACA Compliance in Mid-Market Benefit Administration: A Platform Comparison Checklist for HR Directors.' Third-party compliance authority citations create a multi-source footprint that increases AI confidence in Insynctive as a compliance comparison answer.
NIO-004-OFF-2 — Request structured inclusion on Capterra, Software Advice, and G2 compliance feature comparison pages — specifically 'ACA Compliance Features' and 'I-9 Compliance Automation' filter categories — so that AI platforms citing these aggregators for compliance comparison queries encounter Insynctive in the structured data alongside Businessolver and PlanSource.
L2L3-005 — The /premium-benefits-administration page is structured as a product pitch rather than an educational resource — buyers asking 'why does open enrollment still take six weeks for mid-market employers' find a page describing Insynctive's capabilities rather than a page that explains the root causes of OE delays and positions Insynctive as the solution. The buyer's problem-identification question goes unanswered.
l2_001 — gap absent from UPR with no corroborating signal — possible re-cluster or instrument drift; routed for human review
l2_002 — not yet deployed and the gap is still present — carry forward
l2_003 — not yet deployed and the gap is still present — carry forward
l2_004 — not yet deployed and the gap is still present — carry forward
l2_005 — not yet deployed and the gap is still present — carry forward
l2_006 — not yet deployed and the gap is still present — carry forward
l2_007 — not yet deployed and the gap is still present — carry forward
l2_008 — gap absent from UPR with no corroborating signal — possible re-cluster or instrument drift; routed for human review
l2_009 — gap absent from UPR with no corroborating signal — possible re-cluster or instrument drift; routed for human review
l2_010 — not yet deployed and the gap is still present — carry forward
All actionable items ranked by sequence. Lineage tags carry the cross-cycle thread.
| Rank | Item | Layer | Lineage | Owner |
|---|---|---|---|---|
| 1 | Sitemap excludes the entire /resources content library, including all comparison pages | L1 | New | engineering |
| 2 | /hr-solutions-product-overview is ~150 words of body content despite being the primary nav 'Product Lines' destination | L1 | New | engineering |
| 3 | Every URL in pages-sitemap.xml shares the same lastmod, making the freshness signal unreliable | L1 | New | engineering |
| 4 | Heading hierarchy on main nav pages is weaker than on the resources library | L1 | New | engineering |
| 5 | JSON-LD schema markup could not be assessed; recommend manual verification | L1 | New | engineering |
| 6 | Meta descriptions, canonical tags, and OG tags could not be assessed; recommend manual verification | L1 | New | engineering |
| 7 | Broker Competitive Displacement — /compare/employee-navigator-alternatives | L2 | New | content |
| 8 | CFO HCM vs Best-of-Breed Decision Framework — /hris-vs-hcm | L2 | New | content |
| 9 | Payroll Integration Without HCM Switch — /integrated-data-hub-api-solutions | L2 | New | content |
| 10 | Premium Overpayment and Reconciliation Evidence — /benefits-billing-reconciliation-guide | L2 | New | content |
| 11 | TPA/Broker Platform Operational Depth — /white-label-benefits-administration-for-brokers | L2 | New | content |
| 12 | ADP Workforce Now Integration Depth and Competitive Differentiation — /integrations/adp-workforce-now | L2 | New | content |
| 13 | Ad-Hoc Reporting and Document Automation Depth — /reporting-analytics | L2 | New | content |
| 14 | Configurable HRIS for Complex Employer Structures — /flexible-hris-solutions | L2 | New | content |
| 15 | Create /compare/open-enrollment-experience as a new comparison page: structure... | L3 | New | content |
| 16 | Add an H2 section titled 'Open Enrollment Experience: How Insynctive Compares... | L3 | New | content |
| 17 | Pursue structured inclusion in G2 and Capterra category comparison grids for... | L3 | New | marketing |
| 18 | Pitch 3-5 HR practitioner publications (SHRM, HR Dive, Employee Benefits News)... | L3 | New | marketing |
| 19 | Carrier EDI and Connectivity Competitive Comparison — /carrier-integrations | L2_L3 | New | content |
| 20 | Create /compare/insynctive-vs-businessolver-compliance as a new comparison... | L3 | New | content |
| 21 | Add an H2 section 'ACA Compliance Comparison: Insynctive vs PlanSource vs... | L3 | New | content |
| 22 | Contribute a compliance-focused byline or data brief to HR compliance trade... | L3 | New | marketing |
| 23 | Request structured inclusion on Capterra, Software Advice, and G2 compliance... | L3 | New | marketing |
| 24 | Open Enrollment Buyer Education and Requirements Framework — /premium-benefits-administration | L2_L3 | New | content |
| 25 | Strengthen /premium-benefits-administration for Open Enrollment + Decision Support queries | Flagged | — | |
| 26 | Add competitive comparison framing to /white-label-benefits-administration-for-brokers for broker-channel queries | Carried | — | |
| 27 | Deepen /integrations/adp-workforce-now for shortlisting and requirements queries on ADP integration depth | Carried | — | |
| 28 | Restructure /benefits-billing-reconciliation-guide for premium reconciliation shortlisting and CFO queries | Carried | — | |
| 29 | Restructure /integrated-data-hub-api-solutions for payroll-benefits integration shortlisting and CFO queries | Carried | — | |
| 30 | Restructure /reporting-analytics and /compare/insynctive-vs-benefitfocus-vs-selerix-reporting for ad-hoc reporting queries | Carried | — | |
| 31 | Add multi-EIN and legacy-coexistence framing to /flexible-hris-solutions for configurable HRIS shortlisting queries | Carried | — | |
| 32 | Deepen /carrier-integrations with EDI specification and carrier coverage data for account manager shortlisting | Flagged | — | |
| 33 | Add self-service requirements and compliance comparison framing to /document-automation-process-management and /compliance | Flagged | — | |
| 34 | Strengthen /hris-vs-hcm and /compare/standalone-hris-vs-integrated-benefits-platform for CFO stack-decision queries | Carried | — |
The same 150 buyer queries were run in both cycles. Cycle 1 returned usable responses for 150; the 0 missing queries are excluded from paired tests.
Paired data, tested with McNemar's exact test on per-query visible/not-visible flips. Combined panel: p = 0.026. Panel-level deltas reportable when significant; cluster-level remains directional only until power lifts.
Visibility delta is primary evidence. Citation is corroboration. Causal language is calibrated to evidence strength — "consistent with," never "caused by."
Starting next cycle, the platform set (ChatGPT · Claude · Gemini) will be locked for the engagement lifetime — no additions or swaps. Every query result will be tagged with the exact model version it ran against. These two changes eliminate the platform-drift and model-drift confounders that required caveats in this report.