Kajabi

When Does It Make Sense To Build Your Own Kajabi Or Circle?

Starien still uses and recommends Kajabi, while building more of its own software and apps. Geoffrey Moffett explains when a hosted platform is worth paying for, when it makes sense to build, and why the best option may be to keep the platform and build the one feature you need.

Geoffrey MoffettDigital Educator / Developer 10 Min Read
In This Article

At Starien, we still use Kajabi. We’re on a good plan, it does what we need, and we regularly recommend it to clients. We’re also building our own software and mobile apps, both for ourselves and for other businesses.

A few years ago, those would have felt like two very different ways to run a business. Today, it’s quite normal for us to keep the courses and checkout on Kajabi, build the public website ourselves, and write a small integration when we want the two to work together.

“I’ve been a Kajabi customer since 2015. If you have a course ready to sell and you want to get it online this weekend, I’d still recommend Kajabi. If you’ve been running a membership for three years and you spend every Monday working around the same problem, I’d want to know what it would cost to fix that one thing.”

Circle, Kajabi, Thinkific and Mighty Networks have made it easier for people to sell courses, run memberships and build communities. Circle and Kajabi in particular have taken a lot of separate jobs and put them under one roof. Plenty of business owners are happy to pay someone to look after that roof. We are too, when the price makes sense.

What’s changed is how much of the building we can now do ourselves.

One feature can change the price of the whole plan

Circle currently advertises Professional at $89 a month, Business at $199 a month and Scale at $419 a month. Those are monthly equivalents on annual billing, before tax. That makes Scale $5,028 a year. Circle’s public pricing page shows the annual rate for Scale, so we’d ask for the current month-to-month price before comparing the two. The $499 month-to-month figure you may see online comes from Circle’s 2025 announcement about its former Enterprise plan.

Circle’s plans have changed over time. In 2025, it announced that Enterprise pricing for new upgrades would rise from $399 to $499 on monthly billing, and from $360 to $419 a month on annual billing. Existing Enterprise customers kept their pricing under that announcement. Circle stopped offering Enterprise in March 2026, and its current line-up includes Scale. Today, Circle lists APIs and its MCP integration on Business, while Scale adds features including webhooks, AI workflows and custom single sign-on.

Kajabi’s pricing history has been different. It says its 2025 announcement was its first price adjustment in roughly a decade. The increase started taking effect for existing customers in January 2026, with exceptions for Founder and Beta Invite plans. We still get good value from the plan we’re on, which is one reason we keep using it.

For a business on Circle, the question might be as simple as this. You’re happy on Business, but you want a webhook to tell your own system when a member signs up. Moving from Business to Scale adds $2,640 a year at the advertised annual rates. Scale comes with plenty of other features. If that one integration is the reason you’re considering it, price the integration on its own before committing to the upgrade.

What the branded app quote buys you

Circle Plus is where Circle lists custom-branded iOS and Android apps, custom app screens, branded push notifications, unlimited admins and Email Hub with 10,000 contacts. The price is set by quote. Circle’s own support documentation refers to Plus contracts above $20,000 a year. That works out to more than $5,000 per quarter on an annualised basis, though the actual invoice schedule and price depend on the agreement. Kajabi publishes a separate app price of $199 a month on Basic and Growth, with the branded app included on Pro.

Part of what Circle Plus sells is someone to handle the work. Circle lists app store submissions and ongoing app store operations alongside the branded app itself. If you want your name on the app and someone else to deal with publishing it, that can be worth a great deal.

When we build an app ourselves, we can decide what members see when they open it. A local community might put events, jobs and business listings before the discussion feed. A training business might open on the lesson a learner was halfway through. We can change which notifications go out, what they say and where they take people. We can publish under the business’s own developer accounts and use its branding from day one. Those decisions matter most when the app is a regular part of how customers use the business.

“I care more about what someone can do in the first 30 seconds than whose logo is on the splash screen. If the useful thing is buried three taps deep, that’s what I want the freedom to change.”

What we’d actually build

The easiest mistake is to take a feature comparison page and turn it into a development brief. A small business rarely needs everything on that page. It usually needs a few things to work especially well.

FeatureWhat we’d build firstWhat the hosted platform already handles
Reporting and analyticsA weekly view of new members, renewals, event bookings and whatever else someone will act on.Dashboards, data collection and standard reports that are ready to use.
GamificationOne or two actions worth recognising, such as completing a course or answering another member’s question.Points, badges and leaderboards you can switch on without developing them.
Custom domains and brandingThe business’s own domain, design and sign-in experience. We’d keep the domain in the client’s account.Setup and hosting. Circle already includes a custom domain on Professional, so a domain alone is a poor reason to rebuild.
Webhooks and APIsThe specific events other tools need, such as a membership renewal updating a CRM or an approved listing appearing on a public website.Documented interfaces that work within the plan’s limits.
Email and push notificationsA welcome sequence, a digest, and notifications people can control. We’d use a specialist service for email delivery.A dashboard that ties campaigns, segments and member activity together.
Mobile apps and admin accessThe screens members use most, with permissions that reflect who actually does the work. We’d start with the web if it meets those needs.A larger set of ready-made features and, on relevant plans, help getting the native apps live and keeping them updated.

Circle’s public plan comparison is worth checking against the features your team actually uses. A tool you use once a quarter deserves a different budget from something customers use every morning.

AI credits or your own API?

Circle currently lists 2,500 monthly credits on Professional and Business and 5,000 on Scale, with extra credits listed at $10 per 1,000 on those plans. Circle says its credits cover more than AI-generated text. They can also cover workflow tasks, API calls and agent usage. Kajabi advertises an additional 500 AI credits for $15 a month. Those credit packs measure different things, so the price per credit tells you very little across platforms.

If the built-in AI saves an hour a week, the credit pack may be an easy purchase. If you mainly want AI to draft a newsletter from this week’s events or summarise feedback for your team, a direct integration with a model provider can be cheaper at modest usage. You can choose the model, track the cost of individual jobs and set a spending limit. You can also decide which jobs need AI in the first place. A reminder that goes out every Thursday probably needs a schedule and an email template.

The same goes for MCP, or Model Context Protocol. On our own software, we can give an AI assistant access to a well-defined set of tasks. For example, it could read approved business listings, turn event details into a newsletter draft, or save a blog post to the CMS for someone to review. We can decide who gets access, what they can do and which actions require approval. For client projects, we can also design around the client’s own API account so they can see and manage their usage.

That’s where custom software starts to earn its keep. You can give each person the few tools they need to do the job, then change those tools as the work changes.

Could you run it for $150 a month?

For a modest community, $150 a month or less is a plausible infrastructure target. It’s an estimate we’d test against actual usage. As a starting point, Supabase lists its Pro plan from $25 a month and Vercel lists Pro at $20 a month. That leaves room within a $150 budget for services such as email, monitoring, storage and light AI usage, depending on volume.

A lean app can have its own branding, database, member logins, roles, reporting, webhooks and email integration within that kind of budget. A native branded app may share much of the same backend, while bringing its own development, testing and release work. Heavy video usage, a large mailing list or substantial AI traffic can change the bill quickly.

Circle’s in-platform screen recorder is a good example. Recording directly into a post or course lesson saves time, and those clips count towards your plan’s storage. If you build the feature yourself, you still pay for storage and delivery. You get to choose how much video to keep, where to store it and how to manage the cost.

The fair comparison is the hosted subscription versus the whole cost of running your own software. Include the initial build, maintenance, payment processing, backups, app releases and the time someone spends helping members. If you run a successful membership by yourself, paying a vendor to handle that may be an excellent deal. If you already have technical capacity and keep paying for plan upgrades to get small changes, the numbers may go the other way.

How much would it cost to leave?

This is the question we’d ask before putting courses, payments, email and a mobile app under the same account. Having those things connected makes life easier. It also means a move involves more than copying your website.

Circle and Kajabi both document ways to export subscription records. Kajabi also documents a route for eligible Stripe subscriptions to move into Kajabi Payments without customers re-entering their details. Before a switch in either direction, we’d want to know exactly which customers can keep their existing billing arrangements and what they’ll have to do themselves.

Our first test would be an ordinary renewal. A member’s payment goes through next Tuesday. Does the new system recognise it? Does their course access continue? Does the right email go out? Can they still get into the app? Then we’d look at what happens on a failed payment or cancellation. That tells us more about the cost of switching than the number of rows in a CSV.

On a custom project, we’d ask the same questions of ourselves. Who owns the domain and developer accounts? Can someone else maintain the code? Can the client get their data out? Owning custom software is useful when you can hand it over and keep running it.

Buy it, build it, or do a bit of both

We’d buy when the platform already fits how the business operates and the team would rather spend its time teaching, selling or looking after members. That’s still a strong case for Kajabi and Circle.

We’d build when something central to the customer experience keeps getting squeezed into someone else’s feature set, and there’s technical capacity to own it after launch.

We’d combine the two when the existing setup handles the hard parts well and there’s one obvious thing we could improve. Keep Kajabi for courses and checkout, for example, and build the website or member directory around the business. Or keep Circle for the community and build a reporting tool that answers the questions the team asks every week.

This is where Codex and Claude Code have made the biggest difference for us. We can try a small idea sooner, show it to the people who’ll use it and see whether it deserves more work. TechCrunch has reported on founders and investors making similar build-versus-buy calculations. Thoughtworks makes a distinction we find useful too. Some software handles routine work, and some directly shapes what customers choose you for. The second kind is often where a custom build pays off.

“The next time someone says we’ll have to upgrade to do that, I want to know what ‘that’ is. If it’s a better way to run the whole membership, I’ll look at the plan. If it’s a screen our team needs twice a week, I’ll see what it takes to build the screen.”

That’s where we’ve landed at Starien. We’re happy to keep paying for good software. We’re also building more of the things that make our work, and our clients’ businesses, run the way they want. Before the next upgrade, take the feature you actually need and price it three ways. Get the cost of the higher plan, the cost of adding it separately, and the cost of building and maintaining it yourself. You may find the best decision is a much smaller one than replacing the whole platform.

Filed Under

Kajabi

Share This Post

Written By

Geoffrey Moffett

Digital Educator / Developer

More Articles
More In Kajabi

Back To Top