As eye-popping as the $14 migration is, the most interesting thing here is Claude catching Replit calling a broken feature "working as spec'd." Most orchestration pitches sell speed, but this is the opposite: one model's job is to make the other one stop and finish correctly. (And I love that you now have two models!).
Sad footnote: I consulted for Marketo many moons ago when it was early and leading the drive towards marketing/revenue cycle automation. Statis -> decline -> irrelevance -> disrupted to obsolescence seems to be the "legacy" path here.
First-time reader, first-time commenter . . .
As eye-popping as the $14 migration is, the most interesting thing here is Claude catching Replit calling a broken feature "working as spec'd." Most orchestration pitches sell speed, but this is the opposite: one model's job is to make the other one stop and finish correctly. (And I love that you now have two models!).
Sad footnote: I consulted for Marketo many moons ago when it was early and leading the drive towards marketing/revenue cycle automation. Statis -> decline -> irrelevance -> disrupted to obsolescence seems to be the "legacy" path here.