Can I vibecode Amie?

KINDA · weekend project

price $28.84/moyou'd save $346.08/yrbuild time multi-daycategory 📅 schedulingreplaced by 0 people

The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Amie, combine calendar, tasks, contacts, and scheduling in a polished daily interface. The hard boundary is native polish, sync, calendar providers, mobile apps, and integrated communications, plus calendar integrations and reliability.

the prompt

Build a personal replacement for Amie in an empty repository.
Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, Google Calendar OAuth, and Resend; do not offer alternative stacks.
The core loop is: read one calendar, combine tasks and contacts in a daily view, publish availability, create conflict-safe bookings, and send confirmations and reminders.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Implement one account with configurable working hours, buffers, minimum notice, and booking horizon.
Connect Google Calendar using OAuth and store refresh tokens encrypted at rest.
Calculate availability in UTC and render it in the visitor's detected timezone.
Reserve slots transactionally, create calendar events, and prevent concurrent double booking.
Send confirmation, cancellation, and reminder email with signed management links.
Add an admin booking list, event-type editor, audit log, and calendar reconnect flow.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out Microsoft and Apple calendar support.
Deliberately leave out team round-robin routing.
Deliberately leave out payments, CRM workflows, and enterprise controls.
Finish by running the tests and listing the exact commands used.

$ open in your agent (prompt prefilled, you press enter) or copy it raw · this prompt is generated from the build plan · improve it via PR

why people still pay

People still pay for Amie because people pay because one double booking or missed invite can cost more than years of subscription fees. The recurring cost buys OAuth refresh, webhooks, timezone databases, race conditions, reminders, deliverability, privacy, and uptime, not just the visible interface.

what you lose

xnative polish, sync, calendar providers, mobile apps, and integrated communications

xmultiple calendar providers

xteam routing and round-robin

xpayments

xtimezone edge-case maturity

prior art · use these instead of building, if you'd ratherCal.comMature open-source scheduling platform with calendar integrations and booking workflows.↗

share on X ↗"I just replaced Amie ($28.84/mo) with one prompt"

the numbers

Amie pricing

plan	monthly	annual (per mo)	what you get
free	$0/user	$0/user	25 meeting-note credits one time; unlimited Google/Apple calendar connections and to-do lists; basic AI
pro	$28.84/user	$23.07/user	Unlimited meeting notes, bot-free recording, chat with notes and AI scheduling
business	$57.67/user	$46.14/user	Pro features plus custom templates/branding and ATS/CRM integrations
enterprise	custom	—	Custom security, support, deployment and enterprise controls

free tier25 meeting-note credits one time, unlimited Google/Apple calendars and to-do lists, and basic AI

billingmonthly + annual (-20%); 7-day paid trial; subscriptions auto-renew

hidden costsTeam subscriptions are per seat and mid-cycle additions are prorated. VAT/taxes may be added, standard purchases are generally non-refundable, and USD cost moves with EUR/USD. Free meeting-note credits do not renew.