“meeting scheduler agent”
CalPocalypse 9000
“Congratulations, you've reinvented Calendly. Your parents must be so proud.”
An AI agent that autonomously finds, proposes, and books meeting times by reading calendars, inferring preferences, and handling the back-and-forth negotiation between participants.
This is possibly the most competed-over productivity problem in SaaS history. Calendly, Cal.com, Reclaim.ai, Motion, and Clockwise have collectively raised hundreds of millions of dollars attacking this exact problem. The AI-native angle is the only wedge left, and even that's being eaten by Reclaim and Motion already.
Generates a shareable PNG image of this verdict card entirely in your browser — nothing is uploaded. Choose portrait (1080×1350, for stories and status) or landscape (1200×630, matches the link preview), then download.
Viability Analysis
Pros & Cons
What's going for it
What's against it
Who You're Up Against
Open Source Alternatives
When Will Big AI Kill This?
Most Likely Killer
Timeline: 12-18 months
How They'll Do It
Google Duet AI inside Google Calendar will handle natural language scheduling natively — 'Schedule a meeting with my team next week when everyone's free' — no third-party tool needed, already rolling out
Your Survival Strategy
Go vertical. Own one industry (recruiting, therapy, legal) so deeply that Google's generic solution feels like a butter knife at a surgery
Confidence
If You're Crazy Enough to Build It
Solo Dev Time
3-4 weeks for MVP, 6 months to be embarrassed by Reclaim's feature list
Team Size
1 dev who will question their life choices, 1 designer to make it look less like Calendly, and a therapist on retainer
Estimated Cost
$500-$2,000/month in API costs at scale; $0 if you fork Cal.com and add an LLM layer
Tech Stack
Agent-Readiness Score
Ready to scaffold today. CalPocalypse 9000 could be a working prototype in a week.
- Memory ↗24/25
Stateless or single-session — minimal memory layer.
- Tools ↗11/25
Crowded market: at least 9 integrations to compete.
- Policy ↗13/25
Mid-size policy surface — define refusal categories before launch.
- Evals ↗23/25
Established eval pattern — golden datasets and public benchmarks already exist.
DETERMINISTIC SCORE — DERIVED FROM EXISTING ANALYSIS, NO SECOND LLM CALL
⚡ Ship it anyway
The version that survives
The bot says you're late. Fine. Here's the one version of this that isn't dead on arrival — if you're stubborn enough to build it.
The wedge that isn't taken
Build exclusively for async-first, multi-timezone remote teams — focus on eliminating the meeting entirely first, book it only as a last resort.
Test this before you write a line of code
That users want AI to schedule FOR them autonomously — most people actually want control and just hate the email back-and-forth part.
The honest cost — and who should walk away
6 months and $15K minimum to be competitive. If you're not obsessed with calendar UX specifically, walk away — this vertical eats generalists alive.
Think the wedge holds? ↓ Pressure-test it live before you sink a weekend into it — 20 min, free, no signup.
🔥 Second opinion
Verdict says don’t. Want a second opinion from the human who built the roaster? 20 min, free.
We'll pressure-test the wedge above together — is that differentiator really still open, does the riskiest assumption survive contact, what to build first. No signup, no slides.
Book 20 min — freeFree · no signup on this site, ever.
👋 Rather not book a call?
Leave your email and I'll take a real look.
A human (the person who built the roaster) reads it and emails you back — whether it's worth building, what to skip, and the fastest V0. No signup, no list.
By sending, you're asking me to email you about this idea. That's the only thing it's used for — no list, no spam, unsubscribe by just replying.
How this was generated
Production-readiness odds
Worth pursuing — but expect the production gap to be the long pole, not the prototype.
ANCHORED TO OUR OWN READINESS RUBRIC — NO EXTERNAL STAT CITED
🛡 Safety considerations
What these mean →Heuristic, not exhaustive. Surfaces the 3 biggest categories an operator should think about for this idea. Hover any chip for the mitigation pointer.
⚖ Governance checklist
7 controls applyThings to have in place before you ship. Pairs with the OWASP-style risk chips above — that catalog answers “what could go wrong?”, this one answers “what should you have ready?”
Audit trail of every tool call
criticalPersist a structured per-call log of inputs, outputs, and decisions for at least the legal retention window. Without this, post-incident review is impossible.
Role-based access control on the agent surface
criticalDifferent users, different scopes. The agent should never default to "admin can do everything." Pair with per-task capability scoping.
Tenant / workspace isolation
criticalA multi-tenant agent must never leak data across tenants in either direction (inputs OR cached intermediate state).
Secrets management
highTokens and API keys live in a vault, not in env vars on a CI runner. Rotate on a documented schedule, not "when something happens."
Eval coverage on every release
highA frozen eval suite that runs on every model / prompt change. "It worked when I demoed it" is not a release gate.
Per-user / per-tenant rate limits
mediumAgent loops are pathologically expensive when wrong. Cap tokens-per-session, tool-calls-per-session, and dollars-per-day before launch.
Pin model versions; track the changelog
mediumA silent provider-side model upgrade can shift behavior overnight. Pin to a versioned model ID; subscribe to the provider changelog.
OUR INTERNAL TWELVE-CONTROL SYNTHESIS — STANDARD SOC 2 / ISO 27001 / GDPR FAMILIES APPLIED TO LLM AGENTS
🛠 Build this with Claude Code
Skip the boilerplate. Start from a working spec.
We've packaged this idea into a CLAUDE.md + scaffold.sh starter — the problem statement, agent-readiness sub-scores, suggested tools, and smoke evals, all deterministic and ready to drop into a fresh repo. Open it in Claude Code, or copy the markdown into any IDE.
Don't have Claude Code yet? View the bootstrap preview · grab the JSON bundle · or embed the readiness badge.
Got another problem that needs an agent?
Roast My Problemwhycantwehaveanagentforthis.com