Sales outreach and business operations
Outbox — Private Gmail Outreach Platform
A live, access-controlled Django platform connecting Gmail outreach, contacts, campaign sequences, sending safeguards and response analytics.
Sender connected
Contacts reviewed
Daily cap configured
Interface reconstruction based on the verified live application and source. Display data is illustrative and contains no private outreach records.
- Client
- 365 Spotless
- Build
- Custom campaign automation platform
- My role
- Product architecture, UX/UI, full-stack development and Gmail integration
- Engagement
- Private product design, engineering and Railway deployment
Evidence basis: the live Railway authentication entry and the deployed source revision were matched through production static-asset hashes, route behaviour, models, templates and tests. Interface visuals use fictional display data so no contact, Gmail account, campaign content or OAuth credential is exposed. Client permission covers the Outbox name, logo and product details.
Project context
Building for the buying decision and the work behind it.
Outbox is a private campaign-operations application built for 365 Spotless. It brings contacts, reusable messages, multi-step sequences, connected Gmail senders, launch checks and response signals into one focused workspace. The public Railway URL intentionally opens at an authenticated entry point because the product manages private outreach data.
The project was shaped as operational software rather than a bulk-email interface. Its job is to help an approved user prepare a relevant audience, review the message and sender, respect defined sending limits, stop unnecessary follow-ups after a reply and understand what happened without moving between disconnected spreadsheets and inbox tools.
01
The challenge
What the product needed to make easier.
A responsible outreach workflow has more moving parts than composing an email. Contacts must be imported and deduplicated, audiences must be selected deliberately, personalization data must remain usable, Gmail accounts need secure authorization, and every campaign needs clear limits and readiness checks before launch. Follow-ups also need to stop when a recipient replies, while the operator needs enough history to understand sent, queued, skipped and failed work. Generic tools left these decisions fragmented or hidden behind features that did not match the client’s operating process.
02
The approach
One connected experience, not isolated features.
I designed and built a role-protected Django application around the complete campaign workflow. Contacts can be created individually or imported from CSV with mapped custom fields, then organized through lists, tags or direct selection. A guided campaign builder connects audience, reusable rich or plain-text templates, sequence steps, Gmail sender identities and a final readiness review.
The sending layer applies account and campaign caps, controlled delays, dry-run testing, sender rotation and pause-on-reply behaviour. Gmail access uses OAuth and encrypted token storage. Dashboards and logs expose campaign status, remaining capacity, delivery attempts and reply-rate signals. New accounts remain inactive until an administrator approves them, preserving the product as a private business application even though its login URL is public.
03
Verified scope
Capabilities implemented around the real workflow.
Admin-approved registration and authenticated access to private outreach data
Gmail OAuth connection with encrypted access and refresh-token storage
Contact creation, CSV import, deduplication, custom fields, lists and tags
Campaign audiences selected by lists, tags or individual active contacts
Reusable plain-text and rich HTML templates with personalization variables
Multi-step sequences linked directly to campaign content and timing
Multiple sender identities with controlled rotation and per-account limits
Daily, weekly and monthly caps, randomized delays and dry-run testing
Pause-on-reply follow-ups, sent-email logs and campaign reply-rate signals
Scheduled campaign launches and a readiness checklist before sending
04
The demonstrated outcome
What can be said responsibly.
The result is a live private application that consolidates the implemented outreach workflow inside one maintainable product: audience preparation, campaign construction, reusable content, Gmail sending, safety controls, follow-up sequencing and operational feedback. The deployed application and repository verify these capabilities. This case study does not claim a specific revenue increase, deliverability rate, reply-rate improvement or time saving without an approved measurement baseline.
Inside the private product
One controlled route from audience preparation to responsible follow-up.
These interface diagrams use fictional display data. They represent verified product workflows without exposing contacts, connected Gmail accounts or campaign content.
Build the sequence in context.
Audience, message sequence, sender and launch checks stay connected through a reviewable campaign workflow.
Protect relevance before scale.
Campaigns resolve only active contacts and apply account and campaign limits before messages enter the sending workflow.
Make the next action visible.
Logs, campaign status and reply signals help the operator understand progress while pause-on-reply prevents avoidable follow-ups.
A useful next step
Have a customer journey or internal workflow that has outgrown generic tools?
I’ll help you identify the smallest credible version that can create value.