About Services Tools Blog Contact us

Investor Alert List

A public signup for investor release alerts, with an anti-bot check, a private list, sender access, unsubscribe and a spreadsheet export.

  • Email Automation & Analytics
  • Mining and exploration
  • Website
  • Productised
  • Hybrid
  • 2026

The problem

Investors want release alerts, and an open form gets filled by bots. Giving a colleague access, or pulling out the names, took a manual pass each time. So the list was slow to use and hard to trust.

What it does

A visitor enters an email address, and the signup stores it after a Cloudflare check and notifies the company. In the private admin, staff can list, add, delete and export subscribers, and send access is granted to the people who send an update. A subscriber who has unsubscribed drops out of the export.

Outcomes

  • Alerts have a single list tied to the site.
  • Bots are rejected before a row is stored.
  • Senders can be given access without handing over the database.
  • The export leaves out unsubscribed addresses.

Simplified mockup

Interactive preview with sample data. Nothing is sent to a server.

Release alerts

Site footer

Drill notices and results, by email. A blank address is refused before a row is stored.

Signup
Ready when you are

Subscribers

7

6 active · 1 unsubscribed

Private list
NameEmailTownStatus
Priya Shah[email protected]York Active
Owen Hart[email protected]Leeds Active
Louise Penrose[email protected]Bath Active
Callum Reid[email protected]Bristol Active
Naomi Ellis[email protected]Norwich Unsubscribed 2 Sep 2026
Hugh Barratt[email protected]Exeter Active
Freya Cole[email protected]Sheffield Active

Send access

Senders can post a release. They cannot export the list or open the database.

People who can send
Louise Penrose owner Callum Reid send
Grant
Progress
Choose a person

CSV export

On the list
6 active · 1 unsubscribed
Left out of the file
Naomi Ellis, unsubscribed 2 Sep 2026
Export
Unsubscribed rows stay on the desk and drop out of the file

How it works

  1. Validate the address and the anti-bot check.
  2. Store the subscriber and email a notification through Mailgun.
  3. Grant send access to named staff.
  4. Flag an unsubscribe and leave that person out of the export.
  5. Download the remaining names as a spreadsheet file.

Pipeline

flowchart LR
  A[Signup] --> B[Cloudflare]
  B --> C[Store]
  C --> D[Notify]
  D --> E[Access]
  E --> F[Export]
  C --> G[Unsubscribe]