Break It First

Tested automation kits

Automations we break on purpose before you run them.

Tested automation kits for small shops and ops teams. Before we show a kit, we break it on purpose with made-up bad data and a crash mid-run. Then we publish what failed and what we fixed.

Free PDF. No email, no sign-up. See the 7 kits

Kits set up on your data from $49. A test run on your own automation from $45. Fixed quote in writing before any work.

  • 7kits shown here
  • 359tests passed
  • 190 of 191planted bugs caught

Totals from the seven kits' own test files. The one that got through is shown below. See the numbers per kit

One kit's logged test runs

run 1
pulled 30, deals created 26, rejected 4
check
shop orders 30 = CRM deals 26 + open rejects 4 -> OK
run 3
no change: 0 created, 0 updated
crash test
after 25 CRM writes; state equals one clean run
Orders-to-CRM sync kit. Made-up orders, mock shop and mock CRM.

Built for small shops and ops teams

  • You sell in one or two online stores and keep orders, inventory and customers in step by hand or by script.
  • Your week runs on CSV exports, spreadsheets and PDF invoices.
  • You already run an automation and do not fully trust it.

What you get

A kit, set up on your data

  • A tested kit, set up on your data after a written brief.
  • Its test report: what we broke, what caught it and what got through.
  • A plain list of its limits.
  • A report or log after every run, so you can check the counts the next day.

A test run on your own automation

  • We run checks from our 12-check sheet on your automation, starting with test data.
  • You get it in writing: what failed, how we made it fail, and what we would fix first.

How a kit is broken

  1. 01

    Attack it.

    We feed it bad data, crash it mid-run and push it past rate limits and time limits. All on made-up data and mock services.

  2. 02

    Plant bugs.

    We change one small thing in its code on purpose, like one retry too many, and run the tests again. If no test fails, a test is missing.

  3. 03

    Publish it.

    What failed, what we fixed, what got through and what we did not test go on the kit's page.

The test loopIllustration

Across 7 kits: 359 tests passed, 190 of 191 planted bugs caught. How we test

Seven kits, broken on purpose

Each card shows the tests the kit passed, the planted bugs it caught and its main limit.

Two-store inventory sync

Keeps two stores on one inventory count and flags oversold orders.

Covers: two online stores and one master count. Oversold orders are listed for you, not cancelled.

24 tests passed28 of 28 planted bugs caught

Both stores are mock APIs. It has not run against a real store or sheet account.

Store product file checker

Checks a product file before import and sends doubtful rows to a person.

Covers: your product file before import. Doubtful rows go to a person, and the checks stop at the file.

66 tests passed20 of 20 planted bugs caught

No live import was run and no store was involved. The checks stop at the file.

Orders-to-CRM sync

Copies shop orders into a CRM, with no duplicates on a rerun.

Covers: new shop orders into CRM deals and contacts, with no duplicates when it runs again.

34 tests passed34 of 34 planted bugs caught

The shop and the CRM are mock APIs. It has not been tested against a real vendor account.

Messy sales export cleaner

Cleans messy sales exports into one workbook. Every rejected row has a reason.

Covers: sales exports in the layouts it knows, cleaned into one Excel workbook with a reason for every rejected row.

28 tests passed25 of 25 planted bugs caught

The rules fit three synthetic layouts. These numbers say nothing about real exports.

Support-ticket script rescue

Our own flawed, AI-style demo script: we test a script that half works and fix what the tests catch.

Covers: one script of yours that runs but gets rows wrong, tested and repaired after a written brief.

18 tests passed19 of 20 planted bugs caught

Mock API, made-up data, no real key.

Spreadsheet sales tracker

Checks every row of a sales sheet. Doubles stay out of the totals.

Covers: every row of one sales sheet, checked by a script inside the sheet, with doubles kept out of the totals.

84 tests passed46 of 46 planted bugs caught

It has not been run on a live Google account.

Free test sheet

Before you trust an automation: the 12-check test sheet

Twelve checks to run before an automation touches real records. Each one says what to do, what a pass looks like and what a failure looks like.

Free PDF. No email, no sign-up.

  1. 01Empty input
  2. 02Messy input
  3. 03Duplicate input
  4. 04Run it twice
  5. 05Break the connection halfway
  6. 06Hit a limit
  7. 07Count the cost of a retry
  8. 08Check who sees the data
  9. 09Find the reviewer and the stop button
  10. 10Plan the undo
  11. 11Read tomorrow what happened today
  12. 12Change the format on purpose

Who you deal with

Questions

What happens to my data?

Our own tests use made-up data and mock services, with no real accounts. We work on your data only after a written brief that says what we touch and why. We start with test data, and we check logs and outputs for keys and personal details before real data goes in.

What if it breaks later?

It can. Every kit has limits, and its page lists them. Each kit writes a report or log of every run, so we can see where it stopped. Send it to us. Your written quote says what a fix after delivery costs, or whether it is included.

Which tools do the kits work with?

CSV exports, Excel workbooks, Google Sheets and text-based PDFs, plus shop and CRM APIs. Most kits are Python scripts. The sales tracker is a script inside a Google Sheet. In our tests, the shops, the CRM and the mail service are mocks we wrote. Connecting a kit to your real tools is part of the written brief.

How does a job start?

You send a short note on what it does and where you think it breaks. We ask a few questions, then send a fixed quote in writing that states the delivery date. Work starts only after you say yes.

What does it cost?

The price is fixed in writing before any work starts. The starting prices are at the top of this page.

Do you use AI?

Built with AI assistance. Reviewed by a person, tested by our own test suites. Every number on this site comes from a kit's own test files.

What happens after you write

  1. You write

    Email us or send a DM on X: what it does and where you think it breaks.

  2. We ask a few questions

    About your tools, your data and what counts as done.

  3. Fixed written quote

    The quote states the price and the delivery date.

  4. Work starts only after you say yes

    Nothing is built before you agree to the quote.

Have an automation you do not trust yet?

Tell us what it does and where you think it breaks. We reply with questions or a fixed quote in writing.

Email [email protected] or send a DM to @breakitfirstlab on X.

Kits set up on your data from $49. A test run on your own automation from $45. Fixed quote in writing before any work.

Or start with the free 12-check test sheet.

Logged across the seven kits

kits
7 shown, each broken on purpose
tests
359 passed -> OK
bugs
190 of 191 planted, caught
Totals from the seven kits' own test files.