Maintain an itil_practices column as a JSON array of practice names per platform. Vendors publish ITIL coverage on their pricing pages and renewal docs; refresh the array quarterly. The per-platform page and every pair page render the same grid from the same column, so updates propagate everywhere on the next cache cycle without per-page editing.

Yes. Use price_per_agent and price_per_asset columns and conditional rendering through selector mapping. ServiceNow Neurons and other asset-priced platforms render both numbers; pure per-agent platforms render one. The same logic applies on per-platform and pair pages from the same source columns.

A starting_price column accepts "Quote based" as a string value. The tag mapping renders whatever the cell contains. A typical_band column can hold an estimated range ("$100-$200/agent/mo for enterprise") for buyers wanting context without forcing vendors to publish numbers they don't list publicly.

Yes. Run two page groups with different templates scoped by org_size, one emphasizing SMB ease-of-setup and the other emphasizing enterprise governance and ITIL coverage depth. Both read from the same master sheet with filters, keeping updates centralized while letting layout match the audience's evaluation criteria.

Maintain integrations as a JSON array column on each row. Vendors publish marketplace counts and feature integration lists; refresh quarterly or on major release announcements. List mapping renders the same connector list on the per-platform page and the side-by-side integration grid on pair pages.

Edit the row to reflect the new vendor (Ivanti and others have absorbed multiple ITSM products). The slug stays for SEO continuity. If the product is fully retired, drop the row and the URL stops generating; pair pages that referenced it stop generating too. Set a 301 redirect on the dropped slug to a similar platform to preserve link equity.

Yes. The pairs sheet has its own verdict column written per pair, distinct from the per-platform verdicts. Selector mapping injects the pair-specific verdict alongside the joined platform data. This keeps ServiceNow-vs-Jira pages substantive rather than templated, which is what ranks for high-intent ITSM evaluation queries.

Add price_usd, price_eur, and price_gbp columns and use selector mapping with conditional rendering keyed on locale. Generate region-specific page groups at /service-desk/eu/{slug}/ if your audience splits regionally, with the same master sheet driving all regions through different column selections on each page group.