Import
Lead lists pulled directly from Google Drive under OAuth 2.0, so no credentials are handled by the app and no CSV is emailed around.
SaaS & automation platform
Outreach tooling has always lived on the desktop. GMassPulse puts the whole loop — import a lead list, compose a personalised campaign, schedule follow-ups, and watch opens arrive in real time — on a phone, without shrinking a dashboard down to fit.

The problem
Context
Sales and outreach work happens between meetings, in transit, in the gaps — but the tooling assumes you are sitting at a desk with a wide screen and an hour to spare.
What kept breaking
Follow-ups were manual and therefore inconsistent. Reporting arrived in batches, so by the time you knew a campaign was underperforming it had already finished sending. And the moment a prospect opened an email — the one moment when a reply actually lands — nobody was watching.
The real requirement
Not a mobile port of a dashboard. A product where the live activity stream is the primary surface, because on a phone the thing worth showing is what is happening right now.
The approach
The dashboard is a scoreboard, not a spreadsheet. Everything else in the product exists to feed it or to act on what it shows.
Lead lists pulled directly from Google Drive under OAuth 2.0, so no credentials are handled by the app and no CSV is emailed around.
Campaign composition with spin-syntax variation, so every recipient receives a genuinely distinct message rather than an obvious template.
A live activity feed streaming sends, opens, and clicks across every active campaign simultaneously, with a lifetime scoreboard above it.
Automated sequences triggered by recipient behaviour, plus a manual override to fire an individual targeted message the moment it matters.
Inside the app
Real screenshots across the full campaign lifecycle — import, compose, send, track, and follow up. Recipient addresses in the tracking feed are blurred for privacy.








Engineering highlights
Real-time tracking stream
Open and click events arrive continuously and out of order across multiple concurrent campaigns. Rendering that as a calm, readable feed on a phone screen — rather than a flickering wall of rows — was more of a state-management problem than a display one.
OAuth without credential handling
Google OAuth 2.0 on top of Supabase means the app is granted scoped access rather than ever holding a user's password. Drive import runs through the same grant, so lead lists never leave the user's own Google account boundary before being read.
Deliverability engine
Sending is rate-controlled and paced rather than dumped, and message bodies vary per recipient. Both exist for the same reason: bulk-identical, burst-sent mail is what spam filtering is designed to catch, and reputation is far easier to protect than to repair.
Automation with a manual override
Sequences run on their own, but every automated step can be interrupted by a human acting on a live signal. Full automation is efficient; the reply usually comes from the one message a person chose to send at exactly the right moment.
Scope at a glance
Technology
More case studies
Three-app Kotlin Multiplatform delivery platform with dual video proof of delivery, expanding-radius dispatch, and server-enforced cash reconciliation.
Three-role snow removal management platform with live dispatch mapping, map-based area measurement, photo verification, and Stripe escrow payments.
Every case study and product demo in one place, across logistics, field service, education, events, and SaaS.
Start the conversation
Automation, live data, third-party API integration, OAuth — if the product only exists as a desktop dashboard today, there is usually a sharper mobile-first version of it.