We ship when it is ready, not when it is promised.
This is what we are working on, what is next on the line, what we have parked, and what we have decided we will not build. Dates are intentionally absent. The credible commitment is the direction, not the calendar.
This quarter
In-flight + just-shipped.
Per-tier API + cron quotas, end-to-end
ShippedStarter / Pro / Business / Scale tiers each enforce their own request, briefing, watchlist, and analysis (due-diligence / battlecard / compare) budgets, honoured on both the API and the nightly cron. Alert delivery is tier-agnostic by design. Pricing page is the source-of-truth and the backend honours it.
Disaster recovery posture (restore drill + verification cron)
ShippedDaily off-host pg_dump uploads + a daily 04:00 UTC backup-verification cron that fails loudly if a backup is missing or corrupt + a quarterly restore drill into an isolated database, run on an automated timer.
Loading and empty states across the whole dashboard
ShippedEvery dashboard page renders a skeleton while loading and a typed empty state with a contextual CTA when there is no data, so no surface ever opens on a blank screen.
Public changelog + RSS
In flightThe changelog page and RSS feed are live; entries publish with every release, so the record reflects exactly what has shipped.
WCAG 2.2 AA hardening sweep
In flightSkip-links jump to <main>, focus management on modals, axe-core in CI on every PR, color-contrast verification of the full token palette.
Pre-launch stability gate + production load test
In flightA 14-day stability watch across signal collection, enrichment, digests, and alert delivery, plus a load test at 100x baseline traffic.
Next on the line
We have decided to do these. Order may shift.
External penetration test + remediation
NextEngage a qualified third party for a black-box + grey-box test against the production stack. Public remediation summary in the changelog.
SOC 2 Type I report
NextAutomated evidence collection has been running for months. We will land the Type I report and start the Type II observation window.
Help center migration to Mintlify
Next~30 articles will go live at docs.pulsesignal.co with proper search, versioning, and Mintlify-native code samples.
Native Slack + Teams app listings
NextPublished in the Slack App Directory and Microsoft Teams App Store with OAuth installation flows and per-channel routing.
Storybook + visual regression on every primitive
NextEvery UI primitive gets a documented story and an automated visual diff on every change, so regressions are caught before they ship.
Later
Parked, with intent.
WebAuthn / passkeys
LaterA modern alternative to authenticator-app codes, queued after the SOC 2 evidence cycle stabilises.
Localisation beyond English
LaterLikely de / fr / es / pt / ja / ko, scheduled when the first international paid customers land. Translated legal pages will land with each locale.
Native mobile app (React Native via Expo)
LaterYear-2 roadmap. The installable PWA covers offline access for now.
Reverse-ETL destinations (Hightouch / Census)
LaterNative exports to Snowflake / BigQuery / Databricks are ahead of this; reverse-ETL is the connector layer.
Affiliate + partner programmes
Later20% recurring for first-year affiliates via Rewardful / Tolt; agency partner programme alongside.
Decided no
Just as important as what we are building.
Roadmaps that only list ambitions are not roadmaps. These are the things we have consciously decided against, so you know what we will not become.
Decision-as-a-Service / scoring individuals
Decided noWe do not score, rank, or take adverse decisions on natural persons. Our signals describe companies and roles, not individual employability or creditworthiness.
Selling raw scraped data as a dataset
Decided noPulseSignal is a product, not a data broker. We do not sell raw datasets or contact information for outbound spam.
AMP for marketing pages
Decided noGoogle deprioritised AMP. Modern Core Web Vitals work covers the same ground without the platform lock-in.
Influence this roadmap
Tell us what is missing.
The fastest way to move something onto this page is a concrete workflow story: “every Monday I do X by hand because PulseSignal does not surface Y.” Send those to hello@pulsesignal.co or file a feature request on GitHub. We read everything.