Pulse Briefing
Traditional media monitoring showed what people said about your brand. Pulse shows how AI systems understand, mention and recommend it.
Briefing data
This open preview uses recorded sample results, so you can see the report style without connecting private data or running a new scan.
Showing recorded sample results.
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
Point-in-time AI visibility comparison for the selected sample brand and peer set
AI Model Summary
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.
Create a prospect snapshot
Enter a prospect, choose the scan depth and market, then turn the result into internal BD cards, graphics and a PPTX draft. Start with a quick scan; use full scan when the first result is thin or the prospect matters.
Snapshot command center
Use this area to create a first BD view, then decide whether to improve sources, prepare share-safe wording or export reviewed drafts.
Pulse separates public proof checks from sampled AI answer examples, then shows what staff should review next.
Turn the Snapshot into a conversation starter
Internal BD View stays staff-only. Prospect Share View is a reviewed, plain-language extract after source, claim and owner review.
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
Prospect packs support initial emails, follow-ups, proposal teasers and repitches. Use them for PRecious team preparation until approved partner access and shared approval history are ready.
Internal pitch handoffs
Use these to prepare PRecious follow-ups: the conversation angle, supporting sources, points to verify and the next action before anything is shared outside the team.
Saved locally for the current browser. Use the notes for proposal preparation; shared archive and approval history come later.
Explain the workspace for BD follow-up
Use the selected workspace context to turn findings into business implications, proof gaps, client questions and recommended next actions.
Uses approved Pulse context. If the assistant service is unavailable, this panel shows prepared guidance instead.
Choose a prompt to interpret the workspace.
Ask Pulse will return a finding, business implication, proof gap, question to ask the client, what not to claim, evidence used, confidence and recommended next step.
Save useful Ask Pulse answers for follow-up notes. Nothing is sent, posted or written to CRM from this panel.
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
Workspace profile, markets, sources and report preferences for the selected brand.
Workspace profile
Brand, competitor, market and source details used across scans and reports
Editable setup areas
These settings control how this workspace is described, measured and reported
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/API health, source and dataset controls. Operational setup comes first; launch evidence, version history and roadmap details stay at the end.
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.
Current Access
Current people, roles, workspace access and last-login readback. Public signup and client login stay closed.
Current Access is a read-only overview. Use Refresh access after saving the owner/admin key; use View access list for the pop-up view.
Workspace Activity Log
Admin-only timeline of access, reports, exports, requests and scan/usage events for the selected workspace.
Use the owner/admin key, then refresh activity. This log is read-only and does not enable public signup, CRM writes, checkout or external sends.
Request Access Queue
Review public access requests and record GO, HOLD, REWORK or REJECT. Decisions create receipts only; they do not create accounts or workspaces.
Use this queue for reviews until email alerts are configured. Decisions are owner-review receipts only; public signup, automatic workspace creation, checkout, CRM and external sends stay closed.
Source review approvals
Name the people who can approve source-learning suggestions before anything is stored or applied.
Apply queue remains disabled until storage, review owners, server write owner, retention and external wording owner are approved.
Controlled Demo Guardrails
Champion-only demos, client selection rules, regulated-sector holds and feedback discount requirements from the RC1 baseline approval.
Pulse Champions & certification
| Person | Status | Mock demo | Certified by | Allowed scope |
|---|
Client selection eligibility
Feedback discount quality gate
Regulated-sector holds
Healthcare, finance, banking, insurance, digital health, medical and pharma accounts need SLT selection before live reports or client demos.
This panel is an internal operating guardrail. It does not open public signup, public workspace creation, checkout, CRM writes, external sends or production OAuth expansion.
Access Role Boundaries
Who can operate platform, staff, client and partner access layers before client login opens.
This is an internal access model. It does not open client login, partner access, public signup or public workspace exposure.
Auth Execution Cockpit
Credential-owner path for one controlled invite or magic-link execution.
Public signup, client login and public durable writes remain closed while this gate is being cleared.
RC Readiness Summary
Compact go/no-go view before the controlled-pilot release candidate.
Do not cut rc.1 until Auth execution, membership readback, private API matrix, GA4 journey proof, owner review, hosted smoke and LarsOS go/no-go pass.
Create Workspace
Create the client workspace shell, client record, owner membership, invite status and billing posture together. Public signup and client login stay closed.
Public signup remains closed. Brand, competitor, market and language setup still happens in Profile Workspace Settings until the client workspace switcher is connected to durable profiles.
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
Review internal proof-pack handoffs only when preparing BD follow-up or owner approval
Show proof-pack archive and review gates Collapsed by default because this is evidence review, not day-to-day platform setup.
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
Detailed RC evidence board for launch owners. Keep it collapsed unless checking launch gates.
Show RC evidence board and launch-readiness detail For launch owners only. Public signup, client login, pricing and public claims remain held.
RC evidence board is read-only. It shows what still blocks controlled pilot readiness before any public/client activation.
Hosted evidence capture is internal-only. It collects launch-readiness proof while guarded RC submission remains token-blocked.
RC evidence closure is internal-only. It defines the exact proof packet needed before guarded RC submission can be attempted.
This panel is internal-only. Public promotion, public claims, pricing, signup, sends, partner access and public report links remain blocked.
Profile Workspace Settings
Workspace 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 & Evidence Review
Check search/source-provider readiness and attach source candidates for review when live discovery misses known proof
Optional source candidates for review Use this for known source URLs that live scans might miss, then review claim fit before use.
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.