MailCraft - Pre-Built Email Workflow Engine for Recruiters
Recruiters send the same 12 email sequences on repeat and somehow still do it manually in Gmail like it is 2009. MailCraft is a no-fluff email automation engine with 5 pre-built recruiter workflow templates that deploy in under 10 minutes — no Zapier tax, no n8n PhD required.
Difficulty
intermediate
Category
Business Automation
Market Demand
High
Revenue Score
7/10
Platform
Web App
Vibe Code Friendly
No
Hackathon Score
🏆 7/10
Validated by Real Pain
— seeded from real developer complaints
Recruiters openly describe their email follow-up as a broken mix of manual Gmail drafts and fragile Zapier automations, with no tool offering recruiter-specific workflow logic out of the box.
What is it?
Recruiters on Reddit and HN threads openly admit their email follow-up process is a mess of copy-pasted Gmail drafts, missed follow-ups, and Zapier workflows that break monthly. Existing tools like Mailchimp are built for marketers, not recruiters — they lack candidate-specific logic like stage-based triggers, interview scheduling hooks, and offer/rejection branching. MailCraft ships 5 opinionated recruiter email workflows out of the box: sourcing outreach, interview confirmation, offer letter follow-up, rejection nurture, and referral ask. Each workflow is a visual node editor pre-wired with Gmail/SMTP send, delay timers, and basic conditional logic. Recruiters connect their Gmail, pick a template, customize copy, and their entire pipeline runs on autopilot. Buildable in 2 weeks using React Flow for the visual editor, Resend for email delivery, and Supabase for workflow state.
Why now?
Resend's email API hit production-ready stability in late 2025 making programmatic send-from-own-domain trivially easy, removing the biggest friction point in building recruiter email tools without enterprise SMTP setup.
- ▸5 pre-built recruiter email workflow templates deployable in under 10 minutes (Implementation note: store templates as JSON workflow graphs in Supabase, clone on select).
- ▸Visual node editor built on React Flow showing email steps, delay nodes, and conditional branches.
- ▸Gmail OAuth connect with Resend fallback SMTP so recruiters send from their own domain.
- ▸Workflow run log showing which candidates are at which step with open and reply tracking via Resend webhooks.
Target Audience
Independent and agency recruiters, roughly 200k+ in the US alone, who manage 5-30 open roles simultaneously and live in their inbox.
Example Use Case
Jake, an independent tech recruiter with 15 open roles, sets up the sourcing outreach workflow in 8 minutes, connects Gmail, and watches 3 follow-up sequences run automatically — he closes 2 extra placements per month worth $6,000 in fees.
User Stories
- ▸As an independent recruiter, I want to activate a pre-built outreach sequence in under 10 minutes, so that I stop losing candidates to slow follow-up.
- ▸As an agency recruiter, I want to see which candidates are at which workflow step in real time, so that I can intervene manually when someone goes cold.
- ▸As a recruiter, I want to send automated emails from my own Gmail address, so that reply rates stay high and emails do not land in spam.
Done When
- ✓Template deploy: done when recruiter selects a template, customizes subject line, clicks Activate, and the first scheduled email appears in the run log within 60 seconds.
- ✓Gmail connect: done when user completes OAuth and a test email sends from their own Gmail address visibly in their Sent folder.
- ✓Run log: done when dashboard shows each contact name, current workflow step, and last email open timestamp updating in real time.
- ✓Payment gate: done when free-tier user hits 50 emails and sees upgrade prompt, completes Stripe checkout, and immediately gains unlimited workflow access.
Is it worth building?
$39/month x 30 recruiters = $1,170 MRR at month 2. $39/month x 150 recruiters = $5,850 MRR at month 7.
Unit Economics
CAC: $20 via LinkedIn DM outreach. LTV: $468 (12 months at $39/month). Payback: under 1 month. Gross margin: 88%.
Business Model
SaaS subscription
Monetization Path
Free tier: 1 active workflow, 50 emails/month. Paid $39/month: unlimited workflows and 2,000 emails/month. Upgrade triggered when free limit hit.
Revenue Timeline
First dollar: week 4 via first beta-to-paid conversion. $1k MRR: month 3. $5k MRR: month 8.
Estimated Monthly Cost
Resend: $20, Vercel: $20, Supabase: $25, Stripe fees: ~$20. Total: ~$85/month at launch.
Profit Potential
Full-time viable at $5k-$8k MRR with 130-200 paying recruiters.
Scalability
High — expand to ATS integrations (Greenhouse, Lever), team seats, and white-label for staffing agencies.
Success Metrics
Week 2: 10 beta recruiters running workflows. Month 2: 30 paying users. Month 4: less than 10% monthly churn.
Launch & Validation Plan
Post in r/recruiting asking which email sequences they repeat most — validate 30 responses, identify top 3 workflows, build those first.
Customer Acquisition Strategy
First customer: DM 20 independent recruiters on LinkedIn offering 6 months free in exchange for weekly 15-minute feedback calls. Ongoing: r/recruiting posts, LinkedIn recruiter groups, ProductHunt launch targeting HR tech followers.
What's the competition?
Competition Level
Medium
Similar Products
Outreach.io (too expensive at $100+/month for solo recruiters), Lemlist (marketing-first not recruiter-logic), n8n self-hosted (requires DevOps) — none offer recruiter-specific pre-built workflow templates with zero setup friction.
Competitive Advantage
Recruiter-specific templates out of the box, no Zapier dependency, 10-minute setup vs hours for n8n or Make.
Regulatory Risks
CAN-SPAM and GDPR compliance required — unsubscribe links and data deletion endpoints mandatory before launch.
What's the roadmap?
Feature Roadmap
V1 (launch): 5 templates, React Flow editor, Gmail send, run log, Stripe billing. V2 (month 2-3): reply detection pausing workflow, CSV contact import, Resend analytics dashboard. V3 (month 4+): Greenhouse/Lever ATS webhook triggers, team seats, white-label for agencies.
Milestone Plan
Phase 1 (Week 1-2): schema, workflow engine, 5 seeded templates — done when executor runs a template end-to-end locally. Phase 2 (Week 3): React Flow editor, Gmail OAuth, Stripe — done when first real email sends. Phase 3 (Month 2): beta feedback applied, ProductHunt launch — done when 10 paying users active.
How do you build it?
Tech Stack
Next.js, React Flow, Resend API, Supabase, Stripe, Gmail OAuth — build with Cursor for workflow engine, v0 for node editor UI
Suggested Frameworks
React Flow, Resend SDK, Supabase Edge Functions
Time to Ship
3 weeks
Required Skills
React Flow, Resend API, Gmail OAuth, Supabase Edge Functions for scheduled sends.
Resources
React Flow docs, Resend SDK docs, Gmail OAuth2 setup guide, Supabase cron job docs.
MVP Scope
app/page.tsx (landing), app/dashboard/page.tsx (workflow list), app/workflow/[id]/page.tsx (React Flow editor), app/api/gmail/route.ts (OAuth handler), app/api/workflow/run/route.ts (trigger engine), lib/workflow-engine.ts (step executor), lib/db/schema.ts (workflows, steps, runs, contacts), components/NodeTypes.tsx (email, delay, condition nodes), seed.ts (5 template workflows), .env.example (Gmail client ID, Resend API key, Supabase URL, Stripe key)
Core User Journey
Sign up -> connect Gmail -> pick workflow template -> customize copy -> activate -> watch emails send automatically.
Architecture Pattern
Recruiter triggers workflow -> Supabase Edge Function scheduled run -> step executor reads next node -> Resend API sends email -> webhook updates run log in Supabase -> dashboard reflects live status.
Data Model
User has many Workflows. Workflow has many Steps (nodes). Workflow has many Runs. Run has many RunEvents tied to Contacts.
Integration Points
Gmail OAuth for send-from-own-address, Resend for email delivery and webhooks, Supabase for workflow state and scheduling, Stripe for billing.
V1 Scope Boundaries
V1 excludes: ATS integrations, team seats, A/B testing, custom domain tracking, mobile app.
Success Definition
A recruiter signs up, deploys a workflow template without founder help, and their first automated sequence completes end-to-end with real candidate emails sent.
Challenges
Gmail OAuth app verification takes 2-4 weeks — start the Google Cloud Console application on day one. Distribution is the hard part: recruiters are notoriously loyal to their existing tools, so cold outreach beats SEO for the first 50 customers.
Avoid These Pitfalls
Do not build a custom email editor before validating the template approach — plain text emails outperform HTML for recruiter outreach anyway. Gmail OAuth verification delay can kill launch momentum — apply on day one. Finding first 10 paying customers will take longer than building the product — budget 3x more time for outreach than development.
Security Requirements
Supabase Auth with Google OAuth. RLS on all workflow and run tables scoped to owner. Gmail tokens encrypted at rest. Rate limiting: 30 workflow triggers/min per user. GDPR unsubscribe and deletion endpoint required before launch.
Infrastructure Plan
Vercel for Next.js, Supabase for Postgres and Edge Function cron, GitHub Actions for CI/CD, Sentry for errors — estimated $85/month at launch.
Performance Targets
Expected 30 DAU at launch. Workflow step execution under 2s per node. Email delivery via Resend under 5s. Dashboard load under 2s. No Redis needed at this scale.
Go-Live Checklist
- ☐Security audit complete.
- ☐Payment flow tested end-to-end.
- ☐Sentry error tracking live.
- ☐Supabase monitoring dashboard configured.
- ☐Custom domain with SSL active.
- ☐Privacy policy, terms, and unsubscribe flow published.
- ☐5 beta recruiters ran full workflow.
- ☐Rollback: revert Vercel deployment.
- ☐Launch post drafted for r/recruiting and LinkedIn.
First Run Experience
On first run: 5 pre-built workflow templates are visible in the dashboard with mock run logs showing candidate progress. User can immediately explore the React Flow editor and preview email copy without connecting Gmail. No manual config required: demo mode uses seeded template data and Resend sandbox mode with no real emails sent.
How to build it, step by step
1. Define Supabase schema for workflows, steps, runs, and contacts in lib/db/schema.ts before any UI. 2. Register Gmail OAuth app in Google Cloud Console and submit verification request immediately. 3. Run npx create-next-app with Tailwind and App Router, install React Flow and Resend SDK. 4. Seed 5 workflow template JSON graphs into Supabase via seed.ts. 5. Build the React Flow editor with 3 node types: email, delay, and condition in components/NodeTypes.tsx. 6. Build workflow executor in lib/workflow-engine.ts that walks node graph and queues sends via Supabase Edge Function cron. 7. Build Gmail OAuth handler and Resend fallback in app/api/gmail/route.ts. 8. Add Resend webhook endpoint to update run logs when emails are delivered or opened. 9. Add Stripe $39/month checkout with usage gate at 50 emails on free tier. 10. Verify: activate a seeded workflow template, confirm scheduled emails send via Resend, confirm run log updates, and confirm Stripe payment unlocks full access.
Generated
April 24, 2026
Model
claude-sonnet-4-6
Disclaimer: Ideas on this site are AI-generated and may contain inaccuracies. Revenue estimates, market demand figures, and financial projections are illustrative assumptions only — not financial advice. Do your own research before making any business or investment decisions. Technology availability, pricing, and market conditions change rapidly; always verify details independently.