This page reflects the codebase, not a marketing wishlist. Everything under "Shipped" builds, persists data, and has a working signup → admin → API path. Everything under "Known limitations" is a real gap we'd rather name than hide. We don't publish dated promises — what gets built next is decided as we go.
Contacts, deals, pipeline, invoices, customer portal, an agent action surface, and a daily situation email. Signup persists a tenant; the admin shell is auth-gated; invoices take card payments through Stripe Checkout. AI draft replies and customer status lookups are wired.
Lead capture and triage — public intake form, AI form generation, lead qualification, automations, a quote flow, and Stripe billing with a webhook. Signup persists a tenant; the admin is auth-gated; there's a follow-up cron.
Client portal and project workspace — projects, milestones, approvals, client requests, and an agent action layer. Signup persists a tenant; the admin is auth-gated; seed templates ship a usable first project per business type.
Booking — services, availability, a public booking page, a consent flow, and Stripe billing. Signup persists a tenant; the admin is auth-gated.
Products-first homepage, /products hub, per-product /pricing, /developers orientation, and this roadmap — all on one editorial design language.
Per-tenant manifests, a typed action dispatcher, a cross-product directory at /api/whatcanido/registry, plus llms.txt and a sitemap so AI crawlers can find every tenant. Builds clean; routes verified in the production build.
CRM invoices charge through the platform's Stripe account today, not a per-tenant Connect account. Money reaches the team, but via the platform. Per-tenant Connect is the obvious next step.
Contacts and leads are added by hand or through the API. Bulk import from a spreadsheet isn't built — migrating off another tool means scripting against the API for now.
Every tenant has one owner. There's no team-seat model yet — no invites, no per-member permissions, no assigning a contact to a specific teammate.
CRM, LeadKit, ProjectKit and Bookio each carry their own theme. The marketing site is unified; the products aren't yet sharing one token + component system.
Inbound email and DMs don't funnel into the products. Leads arrive via forms and the agent API; an inbound-email pipeline isn't built.
Spotted something we've mislabelled? Tell us at hello@whatcanido.dev — and watch the changelog for ship notes.