At a glance
The browser-local tools and fictional sample workflow are inspectable. The customer SaaS, tenant controls, integrations, migrations, commercial commitments and customer outcomes remain unverified until the relevant environments and agreements supply evidence.
01 / How to read this
State labels answer different questions.
A capability can exist on the public website without existing in the future customer application. A concept can be visible without being implemented. Read the state, boundary and dated evidence together.
| State | Meaning | Buyer action |
|---|---|---|
| Implemented on this website | Working public-site behaviour with release evidence | Inspect it here; do not generalise it to the SaaS |
| Demonstrated | A sample or local product direction can be inspected | Treat sample records as fictional, not customer proof |
| Planned | An intended capability without current production evidence | Do not include it in a buying decision or tender response |
| Access dependent | Provider, SDK, credentials or environment are still required | Ask for a named integration test before relying on it |
| Application dependent | The protected SaaS must supply the evidence | Require representative tenant, role and failure-path tests |
02 / Implemented website
What the Prism candidate demonstrates.
The local Prism candidate preserves 51 canonical sitemap routes, five browser tools and ten template sets. Each template set includes blank and fictional worked examples in CSV and printable HTML. Local checks cover the build, page metadata and links, tool calculations, responsive page patterns and the preview enquiry flow.
The existing production enquiry contract is retained. In this local preview, form receipts are stored locally and nothing is sent to the Spectra team. Production storage, security headers and delivery must be rechecked at the deployed origin before a release is accepted.
- A stored receipt proves website-database durability, not notification or fulfilment
- Browser-local tools do not submit entered job values through their scripts
- The sample workspace is noindex, uses fictional records and resets
- The Prism marketing pages show their content without an opening animation
03 / Demonstrated workflow
The sample shows continuity, not adoption.
The public product story demonstrates a connected seven-stage sign-job workflow and a reviewable fictional workspace. Its illuminated-fascia, vehicle-graphics and multi-site examples show hand-offs and exceptions; they are teaching scenarios, not customer names, outcomes, endorsements or production usage.
- No anonymous testimonial or invented expert quotation
- No customer adoption, saving, ROI or implementation-duration claim
- No price, availability, service level or support-hours claim
- No ranking, certification or vulnerability-free guarantee
04 / Unverified product
What still needs a representative SaaS environment.
The SaaS application, tenant permissions, franchise controls, integrations, mobile experiences, automation actions and migration service are not proven by this public website. Their acceptance evidence must come from authorised product and provider environments.
- Cross-tenant denial and role-permission tests
- Provider scopes, webhook signatures, retries, revocation and audit history
- Migration rehearsal, reconciliation and rollback
- Backup, restore, monitoring, incident and exit evidence
- Contracted availability, support and data-processing responsibilities
05 / Authority gaps
Market evidence is measured, not declared.
The source handover records Search Console verification and sitemap acceptance on 17 September 2026, when reports were still processing. Current search performance, field Core Web Vitals, customer outcomes and independent operator reviews were not supplied for this redesign.
The research programme explains how future evidence would be collected. Until genuine participation and usable data exist, no result, quotation or market conclusion is claimed.