{"id":4093,"date":"2026-08-06T03:52:51","date_gmt":"2026-08-06T03:52:51","guid":{"rendered":"https:\/\/tucumandevelopers.com\/index.php\/2026\/08\/06\/my-first-paying-customer-failed-4-times-quality-is-not-a-final-check\/"},"modified":"2026-08-06T03:52:51","modified_gmt":"2026-08-06T03:52:51","slug":"my-first-paying-customer-failed-4-times-quality-is-not-a-final-check","status":"publish","type":"post","link":"https:\/\/tucumandevelopers.com\/index.php\/2026\/08\/06\/my-first-paying-customer-failed-4-times-quality-is-not-a-final-check\/","title":{"rendered":"My First Paying Customer Failed 4 Times: Quality Is Not a Final Check"},"content":{"rendered":"
\n
<\/div>\n

The interesting part is the last field. The first three fields are engineering. The last one is product definition surfacing as an enum \u2014 if the pipeline cannot return one of those three answers, the boundary, the authority, or the failure state is still missing.<\/p>\n

<\/a> What the recovery run surfaced <\/h2>\n

Recovering the customer meant retrying the same project in production. I deliberately did not blind-loop. Each production attempt targeted exactly one defect that was already reproduced, regression-tested, independently reviewed, and deployed \u2014 and a terminal failure returned to diagnosis.<\/p>\n

That controlled sequence surfaced four independent defects in the retry chain itself:<\/p>\n

    \n
  1. A database claim contract that drifted.<\/strong> The new retry type was accepted at creation but rejected at claim time \u2014 the schema said yes, the claim function said no.<\/li>\n
  2. An exact-text validator that false-flagged adjacent CJK spans<\/strong> because of unconditional newline joins. Two legitimate Chinese characters touching across a line break looked like a corruption.<\/li>\n
  3. A fixed 120s provider deadline<\/strong> that could not cover a ~67-minute source across two sequential providers. The deadline was tuned for short audio and simply did not scale.<\/li>\n
  4. A false-ready result<\/strong> whose final cue ended early while ~930s of trailing speech remained \u2014 caught by independent acceptance before any export or email.<\/li>\n<\/ol>\n

    Each one went through the same loop: reproduce \u2192 a failing regression test (RED) \u2192 minimal fix \u2192 independent review \u2192 controlled deploy \u2192 production verification. No step was “let’s try and see.”<\/p>\n

    <\/a> The customer was never wrong <\/h2>\n

    Japanese audio + Chinese translated script is not an edge case invented to embarrass a QA suite. It is a standard subtitle production workflow. The first-generation product never answered the question “what is the script, and what is its relationship to the audio?” \u2014 so the implementation answered it with the cheapest assumption.<\/p>\n

    This is the actual root cause: not a developer who wrote a bad check, but a product that had not defined its input boundary. The cheapest time to define a product boundary is before the first paying customer. The second cheapest is right after they teach you where it was missing.<\/p>\n

    <\/a> Recovery was also engineering <\/h2>\n

    For the affected customer, the recovery process left immutable evidence at every step:<\/p>\n

      \n
    1. Containment.<\/strong> Affected projects entered a neutral “I am reviewing this, no action needed” state. UI, APIs, exports, and email paths all fail closed.<\/li>\n
    2. Usage correction.<\/strong> The mistakenly reserved 67 minutes were restored via an append-only record.<\/li>\n
    3. Compensation.<\/strong> A non-expiring +60 minute service-recovery credit, additive to the plan, visible separately, and impossible to duplicate.<\/li>\n
    4. Delivery.<\/strong> An independently reviewed 660-cue result was attached through an append-only receipt \u2014 zero new charges, all seven export formats verified, and the SRT byte-identical to the approved artifact.<\/li>\n
    5. Notification.<\/strong> One combined email \u2014 apology, root cause, result link, compensation \u2014 sent exactly once and confirmed delivered.<\/li>\n<\/ol>\n

      The operating principles: compensation precedes notification, an email failure never revokes compensation, historical failures are never automatically replayed, and every action leaves a verifiable receipt. Compensation was deliberately bounded \u2014 not an open-ended habit.<\/p>\n

      <\/a> Where I stand <\/h2>\n

      Here is where TimedSubs<\/a>, the script-first subtitle tool, stands after this incident:<\/p>\n

      Shipped:<\/p>\n