Kajabi runs the businesses of hundreds of thousands of creators on $200–400/month plans, but it will not let them take their own data with them. There is no public API, the contact list shows only a fraction of the fields it actually stores, and the one built-in export is a slow CSV that gets emailed to you and expires in three days. Plenty of people end up copy-pasting rows by hand.

The brief had two layers. Build the export Kajabi withholds — cleanly and safely, inside a dashboard we do not control and must not break. And build it so the same fix can ship for the next locked-in platform, and the one after that, without starting from scratch each time.

An overlay, not an integration

Kajabi has no API to connect to, so Sidecar does not try. A Manifest V3 content script injects a small export bar directly above Kajabi’s own tables — People, Sales, Analytics — inside the dashboard the user is already logged into. The whole UI lives in a Shadow DOM, so the host’s styles can’t break it and it can’t break Kajabi.

The real product is a reusable engine

The valuable part isn’t the Kajabi extension — it’s @sidecar/core: a shared engine for mounting, Shadow-DOM widgets, settings, a centralized selector registry with a self-check, scraping, export, and ExtensionPay licensing. A whole new target is roughly six thin files — config, selectors, manifest and entry points — layered over that core. Kajabi is the flagship; Teachable, Thinkific and an email-billing cluster ride the same rails.

Resilient to a host you don’t control

Every selector for a platform lives in one registry behind a self-check and a kill-switch, so when Kajabi ships a DOM change the extension degrades safely instead of silently exporting garbage. The targets are validated on a live account, never guessed — Kajabi’s contact table is a table.sage-table that sits outside the page’s main element, exactly the kind of detail you only learn by checking.

Full export — the Pro feature that earns its price

Kajabi’s list shows six columns; the other nine — phone, mobile, address, city, state, country, zip, tags and custom fields — live on each contact’s profile page. Full export fetches each profile in the user’s own logged-in session, parses the server-rendered fields, and assembles all fifteen with bounded concurrency. Instant and on-device, versus Kajabi’s slow, emailed, three-day-expiry file.

Privacy as a hard constraint — and a real business model

Everything runs in the browser: no servers, no analytics, no data off the device — the only network calls are to the user’s own Kajabi pages. Free one-click CSV is the hook; Pro ($5/mo or $39 lifetime) unlocks JSON and Full export, gated by ExtensionPay on top of Black Hart’s existing Stripe. Each platform ships as its own Chrome Web Store listing, with scoped permissions and isolated payouts.

Shipped the flagship — Sidecar for Kajabi — built, validated on a live Kajabi account, and submitted to the Chrome Web Store, with the reusable engine behind it ready for the next platform.

• A Manifest V3 extension that injects a one-click export bar over every Kajabi table — People, Sales and Analytics.
• Free CSV; a Pro tier adding JSON and Full export, which recovers all 15 contact fields from the 6 the list shows.
• @sidecar/core — a shared engine (selectors + self-check, kill-switch, scraping, export, licensing) that turns a new target into roughly six files.
• ExtensionPay + Stripe billing at $5/mo or $39 lifetime, with per-extension store listings and isolated payouts.
• A Black Hart–themed marketing, support and privacy site, plus a full set of Chrome Web Store assets, submitted for review.
• Six platforms mapped on the roadmap: Kajabi → Teachable → Thinkific, then an email-billing cluster.

Honest status: the flagship is submitted and awaiting Chrome Web Store review. The bet isn’t a single extension — it’s the engine that turns each approval into a repeatable, privacy-first product line.