Who
I kept watching creators and consultants park their whole business behind a vertical stack of blue links.
Linktree-class pages are fine for "here are my URLs." They are a dead end when someone is ready to book a call, leave a review, ask a question, or pay. That visitor opens five more tabs. Intent cools. The operator never sees the near-miss.
GetAt.Me is for the people who already have attention and need a destination that behaves like a small CRM on a single handle. consultants, service-led shops, solo brands, creators who sell time and trust, not just clicks.
If you build MarTech, ship Clerk + Convex stacks, or just hate bolting Calendly + Typeform + Intercom onto a bio link, this is for you.
What
I shipped an interactive landing page at getat.me. Claim a handle. Theme it. Drop links. Then unlock the relationship surfaces as you grow.
Stack facts: Next.js 16.1.6 (Turbopack) on Vercel, Convex for real-time data, Clerk for auth and billing (has() feature gates), Stripe through Clerk Billing, Resend for mail, Sentry + PostHog for the ops trail. Tailwind 4, Radix/shadcn, Phosphor icons. TipTap / markdown editor for posts. @dnd-kit for link reorder. Package version 0.1.0. Public repo under HurleyUS.
Nine themes live in the selector: Mocha, Frappe, Macchiato, Monokai, Tokyo, Tomorrow, One, Rosepine, Dracula. Links reorder by weight. Sections group them. Owners get an analytics dashboard. page views, link clicks, bookings, messages with PostHog and Convex events that ignore the owner so you do not inflate yourself.
Plans from .config/plans.ts: Free starter (no card). Premium at $4.99/mo ($3.99 annual). Pro at $9.99 ($7.99). ProMax at $19.99 ($14.99). Pro is where booking, referrals, live chat, and conversion analytics harden. ProMax is payments, custom availability, rich posts with likes/replies/quote reposts/threads, and the verification surfaces.
Where
The product lives on the open web: getat.me. Profiles at getat.me/{handle}. Owner tools under /{handle}/dashboard and account routes. Marketing shell: features, pricing, FAQ, contact, privacy, terms, plus a small SEO blog cluster comparing link-in-bio options.
Code: github.com/HurleyUS/getat.me. Topics: links, social. Deploy path is Vercel continuous. no GitHub Release tarballs, because this is a hosted SaaS seat, not a desktop binary.
The audience sits next to every creator tool thread that still treats a bio link like a footer.
When
2024-10-27. Create Next App. Three commits. Then a long quiet.
2025-10-30. "forming the profile." Themes (Tomorrow Night, Mocha/Frappe/Macchiato HSL). Clerk catch-all auth routes. Unlimited links gated through Clerk billing features. Convex provider switched to @clerk/nextjs so mutations stop lying about "User not found."
2025-11. Ninety-eight commits in one month. Pricing page and PricingTable styling. Centralized plans config. Free / Premium / Pro / ProMax PlanInfo ladder. Features lander. FAQ, contact, footer, privacy, terms. Homepage hero that says the product out loud.
2026-01-31. Posts grow a social graph. likes, replies, quote reposts, nested threads for ProMax.
2026-02. Analytics dashboard. Click and view tracking for visitors only. Onboarding with live handle availability. Drag-and-drop link reorder. SEO sitemap/robots/manifest. Clerk webhooks for user.updated / user.deleted. Lucide to Phosphor.
2026-03. Brand customization with live preview. QR and social share. Link sections. Next.js 16 and the middleware to proxy migration. Demo showcase profiles. SEO blog pages.
2026-05. Blacksmith CI gates. Convex/Clerk build fallbacks. Sentry project routing.
2026-08-08. X-Robots-Tag: index, follow on Vercel.
2026-09-08. One hundred seventy-seven commits on the clock. PR #43 fixes profile ownership and Clerk billing fulfillment. PR #44 puts Bun on the production build. PR #45 includes the TypeScript packages production installs actually need. HEAD 0b96e39.
That is the journey from empty Next scaffold to a live relationship console with billing that fulfills.
Why
A bio link that only lists URLs trains your audience to leave. I wanted the stay. book the slot, send the referral, open the chat, leave the rating, pay when the work is ready. without exporting the visitor to a scavenger hunt.
So I put the surfaces on the handle, gated them with Clerk plans, synced them on Convex, and kept shipping until ownership and billing fulfillment stopped being a customer-journey cliff.
It is still 0.1.0. Custom domains and deeper analytics sit on the roadmap. That is fine. The document model for a profile already holds links, bookings, messages, posts, and referrals in one place.
What would you put on getat.me/yourname first, the booking calendar, the live chat, or the three links you actually want people to hit this week?