Why I'm building Koplanit

Most event planning still happens across texts, spreadsheets, notes, screenshots, DMs, and memory. That works until more people, vendors, guests, and decisions get involved — and then everyone is one missed thread away from something falling through.

I've been on every side of that. The host trying to keep twelve plates spinning. The co-planner who got a screenshot and now isn't sure if a decision was made. The vendor who only learned the date had moved when a guest mentioned it. The friend trying to figure out whether to bring a gift, and to where.

For the last decade I've run digital marketing operations at Amazon Web Services, Oracle, Travelport, and YP — the kind of work where keeping coordination tight across vendors, agencies, regions, and tools is the job. Plenty of campaigns fall through the cracks the same way personal events do: a decision that lived in one person's head, a vendor brief that drifted in a 200-message thread, a date that moved and never quite propagated. I built Koplanit because the same coordination layer that would fix that at work would fix it for every real-world event I've ever helped plan.

Koplanit is the planning layer I wished existed: one shared space for the people, vendors, guests, and details behind a real event. Not another task list. Not another notes app. A coordination layer that quietly handles the “who's doing what by when” so the host can spend their energy on the parts that actually make the event memorable.

We're starting in Atlanta — where I've lived and worked through most of those years — with a focused launch small enough that I can personally walk early hosts through their event. If you're planning something soon and want a hand, that offer's real. If you're a vendor, an organizer, or someone who knows a host who needs this, the waitlist below routes each path differently so we can tailor what happens next.

I read every reply. If you've got feedback, an introduction, or a hard question — send it.

— Founder, Koplanit