Changelog — ClientSniper

v2.5 — September 2026

Starter and Growth plans now include a free sending domain — registered in your name and set up automatically, no DNS work.
Send outreach from your own Gmail in about a minute, as an alternative to Resend.
Add your logo once and it appears under every outreach email.
Domain setup now detects your DNS provider, links you straight to the right page and verifies automatically.
New "Get ready to send" checklist on the dashboard.
Starter outreach templates now appear in your chosen language.
Fixed credit top-ups occasionally not appearing after payment.

Launched the Sales Rep Portal, giving reps their own dashboard for tracking referrals.
Added sales rep application and admin approval flow.
Improved lead discovery search relevance for niche business categories.
Fixed an issue where saved searches occasionally failed to load filters correctly.
Various minor dashboard UI polish and copy fixes.

Added new outreach email templates for local service businesses (trades, hospitality, healthcare).
Improved dashboard load performance, cutting average load time on the leads table significantly.
Added CSV export for lead lists.
Fixed a bug causing duplicate leads to appear after refining a search filter.

Introduced website quality scoring to help prioritise leads most likely to need a rebuild.
Added bulk actions for tagging and archiving leads.
Laid initial groundwork for future CRM integrations.
Fixed timezone display inconsistencies in the activity log.

Reworked the lead discovery search UI for faster filtering by location and industry.
Added support for annual billing plans.
Improved outreach template editor with variable insertion (business name, city, etc).
Fixed several mobile layout issues on the dashboard.

Major rebuild of the lead discovery engine for broader coverage and faster results.
Introduced credit-based plan tiers replacing the old flat-search model.
Added account settings redesign, including payment method management.
Numerous stability and bug fixes following the migration to the new backend.