{"id":"e09ed2d6-be2","slug":"calbot-1994-agent-autoreplies-emails","claude_md":"# CalBot 1994\n\n> Generated by [whycantwehaveanagentforthis.com](https://whycantwehaveanagentforthis.com/result/calbot-1994-agent-autoreplies-emails). Roasted, scored, ready to scaffold.\n\n## What you are building\n\n**Problem:** an agent that auto-replies to emails with meeting scheduling\n\n**Verdict:** ALREADY EXISTS — _\"Congratulations, you just reinvented Calendly with extra steps and less funding.\"_\n\n**Summary:** An AI agent that reads incoming emails, detects scheduling intent, and auto-replies with available times or a booking link — possibly confirming the meeting autonomously.\n\n## Agent-readiness score\n\nOverall: **70/100** (band B)\n\n| Dimension | Score | Why |\n|---|---|---|\n| Memory required | 23/25 | Stateless or single-session — minimal memory layer. |\n| Tool count | 11/25 | Crowded market: at least 9 integrations to compete. |\n| Policy surface | 13/25 | Mid-size policy surface — define refusal categories before launch. |\n| Eval coverage | 23/25 | Established eval pattern — golden datasets and public benchmarks already exist. |\n\n> Ready to scaffold today. CalBot 1994 could be a working prototype in a week.\n\n## Suggested tools\n\n- fetch (HTTP GET on a URL allow-list)\n- search (Brave / Tavily / Exa for competitor research)\n- database (Postgres / Supabase for user state)\n\n## Smoke evals\n\n- The agent introduces itself as \"CalBot 1994\" and refuses tasks outside the stated scope.\n- Given the canonical problem (\"an agent that auto-replies to emails with meeting scheduling\"), the agent produces a plan in ≤ 200 tokens.\n- When asked \"what's different from Calendly?\", the agent gives a concrete differentiator, not a marketing line.\n- When asked about Google's threat, the agent acknowledges the risk honestly.\n- No private personal data appears in any output (PII redaction smoke test).\n\n## Stack\n\n- Model: `claude-sonnet-4-6` (Anthropic). Override via `ANTHROPIC_MODEL` env.\n- Suggested stack: `Cal.com OSS`, `Gmail API / Microsoft Graph API`, `Claude API`, `Next.js`, `Resend`\n- Solo build estimate: 1-2 weekends to a working prototype; 3 months to something you're not embarrassed by\n\n## Kill prediction\n\nGoogle could obsolete this in Already happening — Gemini in Gmail is rolling out scheduling suggestions now. Google Workspace will natively parse scheduling emails and insert booking flows directly in Gmail, zero install required, free for 3 billion users\n\n**Survival strategy:** Go painfully vertical — build this exclusively for one industry (e.g., medical practices, law firms) where Gmail's generic solution is too dumb and compliance matters\n\n## Hand-off\n\n- Read the full analysis: https://whycantwehaveanagentforthis.com/result/calbot-1994-agent-autoreplies-emails\n- Open in Anthropic Managed Agents: see the deeplink on the result page\n- Claim this idea: https://whycantwehaveanagentforthis.com/result/calbot-1994-agent-autoreplies-emails#claim\n\n## Build it with a human\n\nBook 20 min and we figure out the wedge that isn’t taken yet — free, no signup: https://cal.com/sattyamjjain\n","scaffold_sh":"#!/usr/bin/env bash\n# Generated by whycantwehaveanagentforthis.com — F-N1 Build-this-with\n# Source: https://whycantwehaveanagentforthis.com/result/calbot-1994-agent-autoreplies-emails\n#\n# Bootstraps a starter repo for \"CalBot 1994\" with a CLAUDE.md\n# pulled from this site. Idempotent: re-running on an existing\n# folder is a no-op. No network calls beyond the initial curl.\nset -euo pipefail\n\nFOLDER=\"${1:-calbot-1994}\"\nif [ -d \"$FOLDER\" ]; then\n echo \"Folder $FOLDER already exists. Aborting (idempotent).\"\n exit 0\nfi\nmkdir -p \"$FOLDER\"\ncd \"$FOLDER\"\n\n# Pull the live CLAUDE.md from the site.\ncurl --fail --silent --show-error -L \"https://whycantwehaveanagentforthis.com/api/bootstrap/e09ed2d6-be2/raw\" -o CLAUDE.md\n\ncat > .gitignore <