yesreply - Monetize Your Email Inbox, Guarantee Your Responses
What inspired us to build YesReply?
We've all been there. You craft the perfect cold email. You hit send. Then... nothing. You refresh your inbox obsessively, wondering:
Did they even see it? Did it land in spam? Am I being ignored?
The anxiety is real. For every cold email you send, there are 999 others competing for the same person's attention. That busy VC gets 500 emails a day. That startup founder you admire? Their inbox is a warzone. Your message—no matter how valuable—drowns in the noise.
The Problem We Witnessed
We watched talented founders send hundreds of cold emails to investors, only to get ghosted. Not because their ideas were bad, but because attention is the scarcest resource in the digital age, and there's no market for it.
Meanwhile, those same VCs and experts want to help—they're just overwhelmed. They have:
- No system to filter signal from noise
- No incentive to prioritize the right messages
- No way to monetize the time they spend reading unsolicited outreach
Current solutions don’t give experts the flexibility to engage on their own terms. They’re often expected to respond immediately, sacrificing valuable time just to keep up. yesreply changes that — we let recipients decide when and how they respond. They can manage conversations at their own pace, without pressure, while still being rewarded for their attention
The Solution That Changed Everything
That's when it hit us: What if attention had a price tag?
Not to gatekeep, but to create alignment. If someone values your expertise enough to pay for it, and you're fairly compensated for your time, suddenly the game changes:
- Senders get guaranteed responses
- Recipients earn money from their inbox instead of drowning in it
- Everyone wins
We built yesreply to kill two birds with one stone—a platform where distinguished professionals get paid to communicate, and determined senders get the recognition they desperately need.
No more ghosting. No more anxiety. Just clear, incentivized, professional communication.
What does yesreply even do?
Your inbox is your most valuable asset. yesreply helps you monetize it.
Set your rate. Share your link. Get paid for every email you read—it's that simple. We've built a paywall for professional attention where busy experts earn money and serious senders get guaranteed responses.
Here's the Magic:
** For Senders:**
- Pay $0.20 upfront when you hit send
- Recipient earns that immediately
- When they reply within 48 hours, you're charged the remaining amount (up to $6.80)
- Funds land directly in their Stripe account
** For Recipients:**
- Set your email rate ($2-$6)
- Earn $0.20 for every email received
- Reply within 48 hours → Get the full amount
- Don't reply? Sender gets automatic refund
Built-in Protection:
- Spam protection via dynamic blacklisting
- Quality enforcement through whitelisting trusted senders
- 48-hour guarantee with automatic refunds
- No wasted time or money
yesreply isn't just email—it's a marketplace for attention where everyone wins.
How we built it
We moved fast and built smart.
Frontend Stack
React.js ├── Lightning-fast UI ├── Gmail-style email threading ├── Real-time analytics dashboard ├── Smooth, minimalist design └── Dark/Light mode support Backend Architecture
FastAPI (Core API) ├── User management ├── Email CRUD operations ├── JWT authentication └── Real-time data processing Payment Infrastructure
Stripe Integration ├── Stripe Connect (OAuth wallet linking) ├── Payment Intents (split payment handling) ├── Manual capture mode ($0.20 upfront) └── Automatic refund system (48-hour window) Email Pipeline
Email Processing Flow AWS SES (receives email) ↓ Cloudflare Worker (intercepts) ↓ RabbitMQ (message queue) ↓ Backend Server (processes) Architecture handles thousands of emails per second without breaking a sweat.
AI Intelligence Layer
Google Gemini API ├── Email summarization (2-3 sentence TLDRs) └── Meeting Scheduling Result: Busy professionals read less, earn more.
Data & Infrastructure
Storage & Caching ├── PostgreSQL (users, transactions, scores, blacklists) ├── Redis (hot data caching) └── Docker (containerized for scalability) The Result?
A production-ready platform that feels like magic but runs on solid engineering.
Challenges we ran into
1. Stripe Connect Complexity
The Challenge:
- Understanding the differences between Standard, Express, and Custom Stripe Connect accounts
- Implementing OAuth flow correctly with state management
- Designing the payment flow to ensure every component serves its purpose
What Made It Hard:
- Multiple redirect URIs and authorization codes
- Webhook verification and test mode quirks
- Balancing user experience with payment security
Our Solution:
- Chose Standard Connect for maximum flexibility
- Implemented two separate Payment Intents (one for $0.20 upfront, another for remainder)
- Created comprehensive error handling for OAuth failures
2. Prioritizing Relevant Communication
The Challenge:
- How do we prevent spam while allowing legitimate outreach?
Our Solution:
- Dynamic blacklisting for unwanted senders
- Whitelisting for trusted contacts
3. Email Infrastructure
The Challenge:
- AWS SES doesn't simply "forward" emails
- Handling MIME parsing, attachments, SPF/DKIM
- Preventing abuse at scale
Our Solution:
- Cloudflare Workers as programmable edge layer
- RabbitMQ ensures zero message loss under load
- Comprehensive spam and abuse detection
Accomplishments that we're proud of
What We Achieved:
Built a complete MVP in a hackathon timeframe
Production-ready infrastructure that can scale to thousands of users
Real payments working with actual Stripe Connect integration
AI-powered intelligence that genuinely improves user experience
Solved a real problem we personally experience
Why It Matters:
We didn't just build a hackathon demo—we built a minimalistic, user-centric application that achieves all the goals we laid out during the planning phase. Every feature serves a purpose. Every interaction is intentional.
This isn't vaporware. yesreply works today.
What we learned
Technical Learnings:
Simplicity wins — Functionality and empathy matter more than technical over-engineering
Constraints breed creativity — Limited time forced us to ruthlessly prioritize
OAuth is hard but worth it — Solid payment infrastructure enables future iteration
AI shines when focused — Narrow, specific use cases (summarize + rank) > trying to boil the ocean
Team Learnings:
Efficient collaboration under tight deadlines — We leaned into our strengths and moved like a single organism
Ship beats perfect — Technical debt is fine for MVPs. Refactor later.
Ambitious ideas need grounded execution — Big vision + pragmatic milestones = working product
Most importantly, we learned how to turn an ambitious idea into a real, working product that people can actually use today.
We're laser-focused on feedback. We want to hear:
- What would make you actually use this?
- What features are missing?
- What's confusing or unclear?
- What concerns do you have?
We Want Your Feedback
We're extremely excited to hear from amazing minds who can critically evaluate our project.
Log in or sign up for Devpost to join the conversation.