Pulse Briefing
Traditional media monitoring showed what people said about your brand. Pulse shows how AI systems understand, mention and recommend it.
Briefing Data Mode
Local demo uses the seeded briefing dataset. Lite and PRemium run live AI visibility checks for the active brand.
Showing local demo data.
Tesla, Deepal, BMW, GAC Aion
ASEAN 6 · English, Chinese, Thai, Vietnamese, Indonesian, Malay, Filipino
How your brand compares with competitors in AI-generated answers.
How clearly AI systems can connect the brand to usable sources and reference links.
Tone of AI-generated brand descriptions across positive, neutral, and negative signals.
Change badges compare the current demo snapshot with the previous 30-day baseline.
Competitive Benchmarking
Latest AI visibility benchmark across the Admin competitor set
AI Model Readout
AI mentions, source support and recommendation status by configured model family
Authority and recommendation drill-down Open for corroboration, perception triangle and buyer-journey detail.
Will AI Recommend The Brand?
Checks whether the brand is only visible or survives shortlist and recommendation prompts.
Evidence, research and methodology Open for narrative ownership, research QA and the Pulse operating model.
Evidence Pipeline
Supporting QA view for source gaps, prompt tests and the next research job.
Validate the strongest claims before turning them into client-facing recommendations.
What This Means
Plain-language interpretation for PR, communications and marketing teams.
Your brand is visible in some AI responses, but the strength of source support and category association determines whether that visibility can turn into recommendations.
Visibility Risks
Issues that can reduce AI discovery, recommendation quality or market confidence.
Recommended Actions
Practical PR, content and SXO work that can close visibility and authority gaps.
Create a client-ready output
Use the fast buttons for leadership outputs; open the builder only when you need a fuller report or appendix.
Request a Pulse demo through PRecious
For now, demo requests and commercial enquiries go through the PRecious contact page so the existing HubSpot workflow captures the lead.
No direct Pulse signup yet. Requests go through the PRecious contact page so the existing HubSpot workflow captures the lead.
Business Development Snapshots
Proposal and prospecting outputs for PRecious teams. Keep these separate from normal client dashboards and client report-builder flows.
PRecious-only revenue enablement first
BD packs are sales tools for initial emails, follow-ups, proposal teasers and repitches. Keep them internal to PRecious until partner workspaces, API service accounts, rate limits, audit logs and white-label boundaries are ready.
Internal BD proof-pack handoffs
Use these to turn a Pulse diagnostic into a safe PRecious follow-up: what to discuss with the prospect, which evidence supports it, what caveats apply and what cannot be claimed yet.
Runtime/browser storage is enough for sales-safe demo handoff. Supabase is required before multi-user archives, approvals or external sharing.
Snapshots for proposals and prospecting
Agency-facing outputs for pitches, repitches and first meetings. Keep these separate from normal client reporting.
Turn AI visibility gaps into PR actions
Use this screen to move from the audit findings into earned media, thought leadership, content and SXO work that can make the brand easier for AI systems to mention and recommend.
Recommended PR Actions
Suggested PR, content and SXO actions based on the active brand profile, monitored competitor set and visibility gaps
Uses the active profile and competitor set from Admin.
Evidence basis for action ideas
Each idea shows the source basis, confidence and output format so findings can become an action plan, content brief, prompt pack item, source-gap task or campaign brief seed.
Connect AI visibility to traffic, leads and outcomes
Use this screen to plan attribution once GA4, HubSpot and source tracking are configured. It links AI citations and referral paths to sessions, contacts and conversion evidence.
GA4 Referrals by Day
Preview trend for the GA4 tracking plan; not live reporting until GA4 and UTM rules are connected
HubSpot Conversions by Day
Preview trend for the CRM attribution plan; not live reporting until HubSpot matching is connected
Individual setup required
Impact Attribution is a PRemium module. GA4, HubSpot, source attribution, UTM rules, consent settings, and reporting definitions need to be configured separately for each client before these numbers should be treated as live reporting.
Test real questions, then inspect answers and sources
Use this screen to see whether AI systems mention the brand, recommend it, cite useful sources and describe it consistently for stakeholder-style questions.
AI Query Check Mode
Demo uses local answer styles. Lite and PRemium run the selected question through live AI model connectors.
Showing local demo simulation.
Stakeholder Query Bank
Select a common buyer or stakeholder question, or enter your own.
Uses the active profile and competitor set from Admin.
Browser Prompt Validation
Separate user-experience lane for prompts tested in actual AI browser sessions.
Use this for observed ChatGPT, Gemini, Claude, Perplexity or agent/browser answers. API connector results stay separate.
Demo uses four local answer styles; live modes use the AI models configured in Admin.
Default: last 6 months for relevance plus source depth.
Market Lens
Scan a brand, validate peers, inspect sources and turn the gaps into actions.
Public demo guardrails can limit scans to Lite, English and top connectors.
Run, validate, act
Discovery, visibility, peer validation and recommended actions happen in one flow.
No AI authority check yet
Enter any brand or domain to generate a quick working view of AI mentions, search presence, category association and competitor context.
See what the brand is associated with
Use this screen to understand which topics, proof points, problems and buying situations AI systems connect to the brand, then spot positioning gaps before they become recommendation gaps.
Category Association Mode
Choose source, brand focus and peer set for the association map.
Showing local demo associations.
Competitors configured in Admin appear here.
Category Association Map
Hover over nodes to see association strength, context and source links
Turn findings into client-ready guidance
Use PR Advisory Chat to interpret the visibility checks, connect findings to PRecious services and draft practical recommendations for PR strategy, earned media, content, SXO and reputation work.
PR Advisory Mode
Choose whether the advisor uses the local demo script or live model connectors.
Local rule-based copilot.
Settings
Client-safe setup for the active profile: brand scope, competitors, markets, languages, approved evidence sources, report preferences and retest cadence.
Workspace Profile
What client editors should be able to review or edit without touching platform operations
Client-Safe Controls
Settings that belong here instead of Master Admin
Access & Package
Current role, package and what this workspace can do
Platform Admin Access
PRecious-only platform controls stay outside client workspace settings
Master Admin controls platform setup; client-safe changes move into Settings
Use Master Admin for operator-only setup, access, model, source and dataset controls. Client-facing workspace configuration should appear as Settings once authentication and durable storage are connected.
Workspace & Dataset Governance
Current data boundary, durable-store readiness and what belongs in Master Admin versus Client Settings
Client pilot data must move from browser/runtime state into workspace-scoped durable storage before production use.
Billing Preparation
Invoice-first package assignment, pilot usage counters and audit/export handoff for future billing
Pilot counters only: scan credits and exports are local/demo usage signals for invoice planning, not live payment data. JSON is for audit handoff; CSV is for invoice spreadsheet handoff.
Invite-only Pilot Workspace
Create a controlled access and billing record for an approved pilot. Brand, competitor, market and language setup still happens in Profile Workspace Settings until durable workspace storage is active.
Public signup remains closed. To add competitors or markets for the pilot, use Profile Workspace Settings on the active profile. These invite records prepare controlled invoice-first pilots until Supabase Auth and durable workspace storage are enabled.
Production Foundation Readiness
Auth & Enforcement Readiness plus Render environment, Supabase storage/Auth, invite acceptance, durable membership readback and client-login guardrails
Use staging enforcement first. Production client login stays closed until Render, Supabase, membership storage, invite acceptance, readback and audit events are all ready.
Signup Readiness Gate
Production checklist for keeping open self-serve signup closed until platform controls are ready
Controlled demos and invite-only invoice-first pilots can continue. Open signup needs every gate ready and explicit launch approval.
Pulse-Live Channel Gate
External promotion readiness for PRecious, GA+AI, RevGrowth, SEA Connect, KEK and future partners
Downstream teams can build held assets now. Active external Pulse-backed promotion waits for Pulse-live clearance.
Snapshot Request Queue
Captured BD interest, CRM handoff and launch-readiness storage status
Runtime request queue is enough for private demos. Supabase is required before public multi-person request handling.
Proof-Pack Archive
Internal sales-safe proof-pack handoffs and external-ready guardrail status
Proof packs remain internal review records until evidence labels, caveats, source review and durable storage are cleared.
Workspace Evidence & Output Readiness
Bundle A/B/C bridge: saved evidence ownership, source mix, commercial usage context and report-output regeneration readiness
Use this before treating any Authority Snapshot, report, proof pack or campaign brief as a controlled-pilot output. Runtime fallback is not production durability.
Launch Readiness Acceleration
Bundle F: hosted proof-pack smoke, durable readback, BD handoff export, source-action queue, LarsOS readout, access boundary and usage preflight
This panel is internal-only. Public promotion, public claims, pricing, signup, sends, partner access and public report links remain blocked.
Profile Workspace Settings
Client-safe profile, competitor, market and evidence settings used across scans and reports
Production Integration Path
What needs to change before this becomes multi-user and live-data ready
Host the app on Vercel, Netlify, Cloudflare Pages, or an internal PRecious domain. Add login before exposing client data.
Use a backend service account with the Google Analytics Data API. The browser should call your backend, not Google directly.
Create a private app or OAuth app, store tokens server-side, and expose only aggregated lead/conversion data to this UI.
Move this browser-stored dataset into a database such as Supabase/Postgres, Airtable, Google Sheets, or HubSpot custom objects.
Master AI Model Setup
Define Lite top 4 and switch AI model families on or off across the app
Lite mode uses the selected top 4 AI models. PRemium uses every enabled model. Disabled models are hidden from selectors and skipped in live scans.
Model & API Operations
Connector checks and model availability
Model checks run from Admin when stale or when triggered manually.
The app flags newer recommended models but does not silently switch major model families without review.
Source Providers & Approved Evidence
Check source-provider readiness and optionally attach approved URLs that Pulse can use as fallback evidence for the active profile
Optional manual evidence fallback Use this only for approved source URLs that live scans might miss.
Approved fallback sources are stored with the active profile. They are useful for demos and evidence QA, but they do not replace live third-party source discovery or durable workspace evidence storage.
App Version & System Monitors
Release tracking, app responsiveness and cost-control monitors
Version syntax: Major.Minor.Patch. Major = bigger release, Minor = medium feature change, Patch = small fix or copy/UI adjustment.