If I Cannot Export It, I Do Not Own It

There is one question I ask before I build anything on top of a tool.

Can I get my stuff out.

Not can I run a report. Not can I email support and wait nine days for somebody to mail me a spreadsheet. Can I, right now, without asking anyone for permission, take everything I have put into this thing and walk out the door with it in a format I can actually read.

If the answer is no, I do not build on it.

I might still use it. I will not build on it. That is a real difference and it took me too long to learn it.

Renting your reach is one problem. Renting the record is worse.

I have already written about not owning your audience. That is the reach problem. Somebody else decides who sees you, and they can turn that dial down tonight and never tell you they did it.

This is the quieter problem, and it is the one that actually kills businesses.

The record problem is when the work itself lives somewhere you cannot retrieve it from. Your customer list. Your invoices. Your writing. Your photos. Your proof that a thing happened.

Losing reach is a marketing setback. You can rebuild reach. Losing the record is the business, because the record is the only thing that survives an argument.

The export test

Three questions. I run them on everything now, before I put a single hour into it.

One. Can I pull it all out today? Not a summary. Not the last ninety days. All of it, including the old stuff, including the parts they consider theirs.

Two. Is it in a format that still works somewhere else? A CSV is a format. A PDF of a table is not. An export that only reimports into the same company's other product is not an export, it is a leash with a longer chain.

Three. What do I lose if this company is gone in eighteen months? Not if they go out of business. If they get acquired, change their pricing, decide my kind of account is not worth the support burden, or read something I wrote and decide they would rather not be associated with it. That last one is not hypothetical for me.

If a tool fails those three, it is a billboard. Billboards are fine. You just do not put your family in one.

What that looks like in the things I actually build

The site is the clearest example. Every article I have written lives in a database I control, as plain text, in a table I can dump in one command. The design can change. The front end can be rebuilt from scratch. The words do not move, because the words are not stored inside the design.

That sounds obvious until you go look at where most people's writing actually lives.

Same rule everywhere else. With Gideon HQ the whole idea is that what the platform knows about a transaction is visible instead of buried, and a public trust page is a promise you cannot quietly walk back. With RepWatchr the method is published on purpose, because if I will not show you how the record was built you have no reason to believe it. And with SellerProof I made the same call I wrote about here, which is that proof has to be a feature, not a support process.

None of that is clever engineering. It is the same instinct three times. Keep your own copy. Show your work. Assume you will one day have to prove it to somebody who is not on your side.

The unglamorous part

Nobody is impressed by this.

There is no launch post for a backup. No one has ever congratulated a man for having a clean export. The work is boring, it takes an afternoon you would rather spend on something that shows, and the entire payoff is a bad day that never happens.

That is exactly why almost nobody does it.

It is the same reason people skip the pre trip inspection. The truck started fine yesterday. It will probably start fine today. And it does, for years, right up until the morning you actually needed it to.

I do not build for the good day. The good day takes care of itself.

What I would go do this week if I were you

Pick the one tool your business would hurt the most without. Your email list, your books, your customer records, whatever it is.

Go find the export button.

Click it.

Two things happen and both of them are worth the ten minutes. Either you get a file, in which case put it somewhere you control and now you have a floor under you. Or you go looking and there is no button, and you have just learned something important about a company you have been trusting with the thing you cannot replace.

You do not have to leave that tool. I am not telling you to move your whole operation. I am telling you to know, today, on a normal Saturday with nothing on fire, exactly how you would leave if you had to.

That is the whole discipline. Everything else I have built sits on top of it. If you want to see how I set the site up so nobody could take it from me, start here.

So which one is it for you? What is the one tool that, if it locked you out tomorrow morning, you would have no copy of anything?