copywriting

At our previous jobs, we kept losing data during database migrations. Not once, and not at only one company. `[NEED: one specific incident. What was lost, how you found out, how long recovery took, what it cost. Even one sentence of real detail will do more than the rest of this section combined.]` Every time, the fix was the same: a postmortem, a longer checklist, and a promise to be more careful on the next one. After enough of those, we decided the problem was the tooling and started building a better one. ### Section 2: What we built [Product] is a migration tool for developers who run migrations against production databases. `[NEED: 2 to 3 sentences on the mechanism. How does it protect data? Verification step, dry run, automatic rollback, row-level diffing? Name the actual feature and what it catches.]` `[NEED: who it's for and who it isn't. Databases supported, team size, stage. Saying what you don't support yet reads as honest and helps the right visitors self-qualify.]` ### Section 3: Who you'll be talking to There are three of us. `[CONFIRM: if true] When you write to support, you're writing to someone who helped build [Product].` `[NEED: names, roles, and one line each. Prefer something real about each person over a title, such as the migration each one is least proud of.]` ### Final CTA **Run your next migration with [Product]** [CTA button text] `[NEED: matches hero CTA]` `[NEED: one plain line of risk reversal if one exists, e.g. "Free to start. No card required."]` --- ### Annotations - **Headline:** It states the cause and the product in one plain sentence. It passes the swap test, since no competitor can claim your founding reason. - **Story section:** This is the longest section on purpose, because it's the only part of the page only you can write. The placeholder for a real incident is the most important `[NEED]` on the page. A concrete, true detail will carry more weight than anything I could write around it. - **Tone:** Professional but human here means first-person plural, plain verbs, and no hype. I skipped a "mission and values" section because with three people and one clear origin story, it would only add filler. - **What I left out:** There are no claims like "zero data loss" or "trusted by X teams." Nothing in the brief supports them. ### Headline alternatives - **A:** Three people who lost data in migrations one too many times. *Slightly more personality, slightly less clear about what the product is.* - **B:** Database migrations shouldn't cost you data. *Shortest option, but it's a claim any competitor could make. Use it only if the product mechanism backs it up.* ### Meta content - **Title:** About [Product] | Database Migration Tool Built by Developers Who Lost Data - **Description:** [Product] is a three-person team building a database migration tool, started after data loss during migrations at our previous jobs. ### Declined claim and what would unlock it I didn't write anything like "Safer migrations" or "Prevents data loss" as a headline claim. The brief says why you built the tool but not what it does to prevent loss. Send me the mechanism (and, ideally, a test result, a customer quote, or a before/after from a real migration), and I'll turn that into a proper claim.