Inside Mewayz · The build

Exporting is
the promise.

M
The Mewayz team
From the founder's desk
May 17, 2026 · 6 min read

In Settings → Account, two clicks down, there's a button. It says Export everything & close account. Click it once, confirm, and a few hours later you get an email with a download link. Inside the zip: every contact, every deal, every invoice, every project, every ticket, every employee record, every file you uploaded — in formats the next tool can read. CSV for the structured data, JSON for the relationship graph, PDFs for the documents.

Most platforms hide this button. We argued about it for a week, then put it on the second screen of the settings menu, in the same size as every other button. We made sure the engineer who shipped it didn't add any "are you really sure" interstitials beyond the basic confirm.

Every product talks about trust. Almost none of them let you leave.

Why the export button is the product.

The unstated promise of an all-in-one platform is enormous. We are asking customers to put their CRM, their accounting, their HR records, their support history, their inventory, and twelve other things into a single vendor's database. If that vendor disappears — bankruptcy, acquisition, pricing change, change of heart — the customer is in real trouble.

The standard industry answer to this risk is "we won't disappear, trust us." That's not an answer. The customer can't audit our cap table or our hiring plan. They can only audit the door we left open.

A clean, fast, complete, free export is the only durable form of vendor trust. Everything else is marketing.

1 click
From inside the product, to a portable copy of everything

What we had to actually do.

It is much easier to write this essay than to ship the button. Three things had to be true engineering-wise:

  1. Every module had to emit a standard schema on export. CRM contacts → vCard plus CSV. Accounting → CSV per ledger, plus a CSV journal. HR → BambooHR-compatible CSV. Tickets → Zendesk-compatible CSV. Projects → Asana-import-friendly CSV. We wrote translators for the formats the customer is most likely to import into next.
  2. The relationship graph had to come with it. A CRM without its links to invoices, projects, and tickets is useless. We export a separate relationships.json that re-stitches the records on the other side, with a documented schema.
  3. It had to be free, fast, and complete. No "premium support add-on." No 14-day SLA. Most exports finish in under fifteen minutes. The longest we've seen, for a six-year-old agency on the white-label tier, was ninety minutes.

None of this was technically novel. All of it was a sustained refusal to take the cheap path. The cheap path is to make the export real but inconvenient — present, in the docs, technically accurate, practically unusable. We have seen that pattern in every category. We did not want to be in that pattern.

Doesn't this hurt retention?

The honest answer: we don't think so, and we wouldn't change it if it did.

We don't think so because retention isn't about whether the door is locked. Retention is about whether the customer wakes up on a random Tuesday and feels good enough about the product to not go shopping for a replacement. Locks make people resent you. Resentment is the leading indicator of churn, three quarters out. Switching cost as a retention strategy works for exactly as long as it takes for one of your customers to write a blog post about how hard it was to leave.

The principle
The best customer is the one who knows they can leave at any time and chooses not to. The worst customer is the one who wants to leave and can't. Pretending those are the same customer is the original sin of SaaS.

And we wouldn't change it if it did hurt retention, because we are explicitly trying to win in a category — small-business platforms — where the alternative is twelve vendors holding twelve hostage chunks of the customer's data. We can't make that argument while quietly being the thirteenth.

The harder version of this commitment.

Easy: export the data. Harder: tell the customer where to put it next. Hardest: actually help them get there.

We're not at the hardest version yet. We do publish a short doc — "If you're leaving Mewayz, here's what we'd switch to and how" — that names specific products for each module and the format they accept. We update it twice a year. It costs us roughly one engineer-day each cycle. It is, by miles, the most-emailed-to-us page we run.

Some of the people on that page do leave. Most of them don't. A surprising number have come back a year later, and the conversation when they do is unrecognizably different from the standard "win-back" call. They know what's outside. We don't have to pitch them. They are choosing the bundle again, with their eyes open, and the relationship from that point forward is essentially unbreakable.

— The Mewayz team
May 17, 2026 · 6 min read · From mewayz.com/blog
Share this essay

Stay because
you want to.

Start free — no card required →
Full export available from day one