DEV Community: Adrian Witaszak

What leaves with me? The question nobody asks a platform before they sign

Adrian Witaszak — Fri, 31 Jul 2026 07:58:45 +0000

Every SaaS evaluation I have watched runs the same way. Someone opens a spreadsheet, lists the features, weights them, argues about price, and picks. Two years later the same person is stuck on the tool they picked, and not one cell in that spreadsheet is why.

They are stuck because leaving turned out to be expensive, and nobody priced it on the way in.

I build a creator platform, so I see this from the wrong side of the table. Creators arrive at us carrying data from somewhere else, and the shape of what they carry tells you exactly how much their old platform respected them. Some arrive with a clean file. Some arrive with a PDF invoice list and no email addresses. One arrived with a screenshot.

This post is about what a real exit looks like, why it is usually missing, and what I think you should ask before you commit anything you care about to somebody else's database.

Export is not one feature, it is four

"Can I export my data?" is close to a useless question. Almost every platform says yes, and almost every yes means something different. Break it into four.

Identity. Do you get working contact details for your users, or do you get internal IDs? A platform that hands you user_84719 and a display name has technically exported your users and practically given you nothing. If you cannot contact a person after you leave, that person was never your relationship.

Money. Do you get the history? Who paid, how much, in what currency, on what date, on what plan, and where a subscription is in its cycle. Without it you cannot reconcile, cannot answer a tax question about last year, and cannot migrate an active subscription without asking every single customer to re-enter a card. That last one is where most migrations quietly die. Asking 400 people to re-subscribe is how you find out that only 250 of them were paying attention.

Content. Do you get the source, or the rendering? An export of your posts as HTML with absolute URLs pointing back at the platform's CDN is not an export, it is a hostage note with nice formatting. Check whether images come with it, and whether the paths still resolve.

Addresses. What happens to URLs people already have. Bookmarks, links in old newsletters, search results that took two years to earn. If those go to a 404 or, worse, to a page advertising the platform, you did not move, you restarted.

A platform can do the first one well and the fourth one terribly. Most do.

Why this gets built badly

It is tempting to read a bad export as malice. Sometimes it is. More often it is three ordinary engineering facts stacked on top of each other.

The first is that export is nobody's feature. It has no acquisition story, no retention story, and no dashboard. When it competes for a sprint against something a prospect asked for on a call, it loses, and it will keep losing every quarter forever unless someone protects it.

The second is that export is where your data model's sins become visible. If subscription state lives partly in your database and partly in Stripe, and the reconciliation only happens inside a webhook handler that has been patched nine times, then a truthful export requires you to define what a subscription actually is. Teams put that off. I have put that off.

The third is genuinely hard. Some of what a user thinks of as "their data" is not solely theirs. A comment thread involves other people. An email address you hold under one privacy policy does not automatically transfer under another. A payment method belongs to the processor, not to you or to them. There are real questions here, and they make a convenient hiding place for the two problems above.

What I would actually ask

If you are evaluating anything you plan to depend on, these five questions take ten minutes and tell you more than a feature matrix.

Show me an export file. Not the docs page. An actual sample, with the columns visible. If support has to ask engineering, you have your answer.
Is it self-serve? An export that requires a support ticket is a chokepoint, and chokepoints get slower exactly when relationships get worse.
What is the API story on the way out? Read access to your own historical data, without a plan upgrade, is the difference between a migration and an archaeology project.
What happens to my URLs? Ask specifically whether you can keep a custom domain and point it elsewhere, or whether your addresses are subdomains you are renting.
Has anyone actually left? Ask them to describe a migration off their platform. A vendor who can walk you through it calmly has built for it. A vendor who has never thought about it will improvise, and you will hear that.

Notice that none of these are about features. They are about whether the company has decided, structurally, that you are allowed to go.

Being honest about my own side

It would be easy to end here with a pitch. I would rather be useful.

DukieX is the thing I build. It puts a creator's posts, memberships, community, products, courses and livestreams in one Space, so that a person who buys a course is already a member rather than a row in a second system, and so the operator writes to their members from inside the same place the memberships live. On the paid plans the Space runs on the creator's own domain, which is the part that matters most for question four above, because a domain you control is the only address that survives you changing your mind.

Here is where we are not the answer. We have no discovery network. Nobody browses DukieX and finds you, which is a genuine reason to stay on Substack or Skool if that is where your growth comes from. Our courses are not a full LMS: no quizzes, no certificates, no drip scheduling, no progress tracking, so if you are teaching a cohort that needs assessment, a dedicated course platform beats us and I would rather say so than have you find out in month two. We publish the rest of that list, including the places competitors beat us on price, at https://dukiex.com/vs

The reason I put those in writing is the same reason I wrote this post. A platform that will not tell you where it is weak is unlikely to tell you how to leave.

The version of this you can act on today

You do not need to be evaluating anything to get value out of this. Go and export from whatever currently holds your users, right now, and open the file.

If you get working email addresses, payment history and content you could actually republish, you are in a good position and you should stop worrying about it.

If you get less than that, you have not discovered a crisis. You have discovered a number: how much it would cost you to change your mind. Knowing that number is worth more than any feature comparison, and it takes about two minutes to find out.

The checklist I wish creators used before picking an all-in-one platform

Adrian Witaszak — Sun, 19 Jul 2026 08:14:58 +0000

Full disclosure up front: I build one of these platforms (DukieX), so read everything below knowing where I stand. The checklist still holds whether you end up with us, Ghost, Kajabi, or a WordPress stack you assemble yourself.

The pitch for consolidating a creator business into one platform is easy: fewer subscriptions, fewer logins, no more copying customers between tools by hand. The risk is just as real: you are about to put your whole business inside someone else's product decisions. These are the questions that actually separate the good moves from the regretted ones.

1. Can you leave with your audience?

The single most important question. Ask it before price, before features. Can you export your member list, with emails and payment history, and walk away tomorrow? If the answer is buried, assume it is no. An all-in-one platform you cannot leave is not a platform, it is a landlord.

2. Does the data actually flow between the modules?

"All-in-one" often means one invoice for six products that still do not talk to each other. The test is concrete: when someone buys a product, does the community module know? When a membership lapses, does access change everywhere at once? If the modules do not share a member list, you have bought your old stack again in a single bill.

3. What happens to the fee as you grow?

Flat platform percentages look harmless at small revenue and become your largest cost at scale. Whatever platform you evaluate, model the fee at the revenue you want, not the revenue you have. Some platforms charge more as you earn more. A few do the opposite. The difference compounds for years.

4. Whose name is on the front door?

If your shop lives at yourname.platform.com, every visitor is learning their brand, not yours. Custom domain support, and email that sends from your domain, is the difference between building your asset and building theirs.

5. Where does the money actually settle?

Stripe-based platforms generally pay out predictably and let you keep the payment relationship. Marketplace-style platforms sometimes hold funds, bundle payouts, or sit between you and disputes. Boring plumbing, until it is not.

6. What is genuinely worse than your current stack?

The honest one. A dedicated tool that does one thing will usually do that one thing better than any bundle. If your entire business is a single ebook, a Gumroad link beats every all-in-one on the market, mine included. Consolidation pays when the seams between tools are costing you real time and lost customers, not before.

I wrote this list because it is the same six questions I keep answering about DukieX, and the same six I would ask a competitor. We publish comparison pages at dukiex.com/vs that answer them for us and for the platforms we compete with, including the places where a rival is still the better choice.

One Space for the whole creator business: dukiex.com. Built by Charlee X.

Creators don't have a tooling problem. They have an integration problem.

Adrian Witaszak — Wed, 08 Jul 2026 07:18:32 +0000

Spend an afternoon with anyone running a paid audience and you will hear the same story told six different ways. The membership lives on one platform. The shop is somewhere else. The community sits in a third app. The email list is in a fourth. Payments and payouts route through a fifth. A spreadsheet holds the whole thing together, because nothing else will.

Each of those tools is fine on its own. Some are excellent. The problem is not any single product. The problem is the space between them.

The stack tax nobody quotes you

When people add up the cost of running a creator business, they count the subscriptions. Membership tool, store, email platform, community app, scheduling, maybe a course host. It is easy to land between 200 and 350 a month before a single sale.

The subscriptions are the cheap part. The expensive part is you. You are the integration layer. You copy a new member from the community app into the email tool. You reconcile a refund in the store against the membership that should have been revoked. You notice, three weeks late, that a churned subscriber still has access to everything because two systems never spoke.

Engineers have a word for this. It is glue code. Creators just call it Tuesday.

Attention is rented, and so is the plumbing

There is a deeper version of the problem. On most of these platforms you do not own the relationship with your audience. You can have fifty thousand followers and not fifty email addresses. The platform owns the graph, the algorithm decides who sees you, and the terms change without a vote.

So you rent attention on the front end and duct-tape tools on the back end. Neither of those is an asset you control.

What we decided to build

I work on DukieX. The bet is simple: give a creator one branded Space they own, where the pieces already fit.

In one place: a community with posts and discussion, digital and physical products with real checkout, membership tiers, bookings for paid one-to-ones, and livestreaming. Same login, same customer record, same payout. When someone buys a product, cancels a membership, or books a call, the rest of the Space already knows. There is no glue code because there are no seams to glue.

There is AI wired through the modules too, but as support rather than the headline. It drafts a product description or summarises a livestream, and you approve it. That is not the pitch. The pitch is that your business stops living in six browser tabs.

Being honest about where we are

I would rather you trust this post than be impressed by it, so here is the honest version.

Shipping still uses mock carriers today, not live rates. The biggest built-in audience for a newsletter is still Substack, and if discovery is your whole game, that matters. If your community is thriving on Discord, ripping it out is not worth it for most people. We keep a set of comparison pages that say out loud where the other tool still wins, because a signup that churns in a month because we oversold is worse than no signup at all.

What we do believe is that the seams between tools are where creators quietly lose money and time, and that closing those seams is worth doing properly.

If that is the problem you are living with, the honest comparison is at dukiex.com/vs, and the product is at dukiex.com.

DukieX lets creators run their whole business from one branded Space they own. Start free at dukiex.com.

DukieX is built by CHARLEE X, a studio making software for web, mobile, and AI. More at charleex.com.