Setup, workflows,
outputs, safeguardswithout the marketing fluff.
This guide explains how SignalizeAI works in practice: how to get started, when to use single-page prospecting versus batch workflows, what the output means, and how privacy and access are handled.
Guide coverage
What you can find in the docs
Format
Product docs
Focus
Prospecting + outreach
Scope
Single, batch, and saved workflows
Start here before you think about edge cases
These steps establish the normal use path. If the basics are unclear, the rest of the documentation will feel more complicated than it needs to.
Install the extension
Add SignalizeAI to Chrome or Firefox and keep it pinned so it is available when you are reviewing public business sites.
Open a public company page
Use a homepage, product page, or pricing page where the business clearly explains what it sells and who it serves.
Run a quick website check
SignalizeAI reads visible page content on demand and converts it into a sales-focused brief instead of generic metadata.
Decide what happens next
Generate outreach, save the prospect, open it on the website, or keep moving through batch prospecting.
Choose the right mode for the job
Each workflow fits a different stage of research. Use the cues below to decide when to run one-off checks, when to scale with batches, and when to keep results for ongoing follow-up.
Quick website check
Use this when you need a fast read on one account before outreach, discovery, or qualification.
Use when: you are evaluating a single company page in real time
Expect: a short brief in seconds from public, visible page content
Output: summary, target customer signal, value proposition, readiness cues, and suggested outreach direction
Batch prospecting
Use this when manual tab-by-tab review is too slow and you need consistent prospect data across a list.
Use when: running prospecting sprints, territory sweeps, or list validation
Expect: queue-style processing from pasted URLs or CSV inputs
Output: standardized per-domain briefs with optional outreach and follow-up generation for fast comparison and triage
Saved prospects
Use this when prospecting spans multiple sessions and you need a reusable record across the extension and website.
Use when: tracking accounts over days, revisiting outreach, or handing context to teammates
Expect: stored runs with status, outreach emails, follow-ups, search, filtering, bulk delete, and optional export
Output: a reusable working set you can reopen in the website prospect page or manage inside the website saved prospects workspace
What each run is trying to tell you
SignalizeAI output is meant to be actionable for sales and research, not just descriptive. The fields below are the main pieces of context the product surfaces.
Business summary
A concise explanation of what the company appears to do and how it presents itself.
Target customer
The likely buyer segment inferred from messaging, offer structure, and page context.
Value proposition
The most obvious product or service angle surfaced from the public copy.
Best persona recommendation
The role most likely to care about the problem or budget signaled by the site.
Suggested outreach
A goal, outreach angle, and AI-generated outreach emails built from the prospect data.
Follow-up emails
Additional follow-up messages generated after the opening outreach so the prospect can move from first touch to sequence.
Readiness signal
A directional indicator for how ready the account appears for outreach and why.
Exportable working set
When supported, saved prospects can become a reusable set for filtering, export, website prospect views, the `/prospects` workspace, and follow-up.
Understand which workflows are available
This section explains which product capabilities exist and how they generally fit. Billing, subscription changes, and live plan comparison belong on the pricing page.
Quick website check
Available to all usersThe core single-page workflow for active-tab prospecting, immediate context generation, and outreach direction.
Batch prospecting
Plan-dependentUsed when you need to process multiple domains at once and generate prospect data or outreach across a list.
Saved prospects
Plan-dependentSaved prospect capacity, organization features, `/prospects` workspace tools, and export access vary by plan. Website prospect pages are available for saved prospects.
Built for on-demand prospecting, not passive tracking
SignalizeAI turns public website content into prospect data on demand rather than monitoring general browsing.
The extension does not collect form inputs, cookies, or private account data.
API keys stay server-side and requests are rate-limited.
Saved prospects are optional and tied to the authenticated user account.
Users can remove saved prospects through the product interface.
activeTab
Access the current tab only when you request prospect data.
tabs
Read the active page URL for prospect context.
scripting
Inject the extraction script into the page on demand.
storage
Store preferences and local extension state.
sidePanel / sidebar_action
Render the SignalizeAI UI inside the browser side panel or sidebar.
host permissions
Allow secure requests to SignalizeAI services, Supabase, and user-requested prospect targets.
Fix common problems without leaving the page
Most issues come down to unsupported pages, weak source pages, or account and access mismatches. Start here before escalating.
Nothing happens when I run a check
Refresh the page and retry on a public website. Browser-protected tabs, PDFs, and restricted pages do not allow content scripts.
The output feels too thin
Try a stronger page source such as the homepage, product page, or pricing page where the business explains itself clearly.
Batch prospecting is unavailable
Batch prospecting is not a universal feature. Check plan access if the workflow is not available in your account.
Saved prospects are missing
Confirm you are signed in to the same account used when the prospects were created.
Outreach or follow-ups are missing
Open the saved prospect again and generate them from the current view. Saved prospects keep outreach and follow-ups once they are generated.
Need direct help?
Use Discord for fast product questions, GitHub for code visibility, and privacy documentation when the question is specifically about data handling.