Founder note
Why I'm building Koplanit
Founder, Atlanta
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
Build log
What we're shipping
Honest founder notes — most recent first. No metrics that don't exist yet.
Every persona now leaves with something useful
We were sending people a polite “thanks, we’ll be in touch” after they signed up. That’s a holding room, not a product. This week the waitlist ships real artifacts: hosts get a printable Event Starter Plan, vendors see how hosts will discover them, supporters get a 4-variant share kit, investors get a compact snapshot. Concierge Beta is live — 5 early hosts I’ll personally help set up their event. Every confirmation email now has a personal /waitlist/me/{token} link so you can return to your plan anytime. The goal: the waitlist IS the first version of the product, not a placeholder.
Admin filters per persona; founder bio shipped
When you’re triaging dozens of leads a week, “Hosts | Vendors | Investors | Supporters” matters. The admin table now filters by persona, with score chips for hot/warm/cold so the cohort I should call this week pops to the top. Also pushed this /founder page — a credible human face for the brand, no marketing voice. If you got the admin email and clicked through, this is where I decide who I’m reaching out to first.
Persona picker, ?as= deep-links, co-planner invites
People planning events, people who want to support us, vendors trying to reach hosts, investors wanting to follow the build — they all needed different things on signup. The waitlist now branches at step 0 with a persona picker that routes each path to a tailored form. Hosts who arrive via ?ref= (a friend’s invite) become co-planners on submit, with the relationship persisted so admin can render share trees later. ?as=vendor deep-links straight to the vendor form so we can run channel-specific campaigns without confusing visitors.
Atlanta first. Local launch, then city by city.
A lot of seed-stage marketplaces try to launch nationally and watch demand and supply imbalance. We’re starting in one city. Atlanta — because it’s where I can hand-walk early hosts through their event personally, recruit vendors in person, and learn which event types create repeat behavior before deciding whether to expand. The goal isn’t to be in 50 cities. The goal is to be the planning layer that actually works for one city’s event scene first, with real proof, before we generalize.