Houses vs Blueprints

Cross-posted from AI Marketing for Storytellers.

So there’s people out there right now, with the sudden and unexpected demise of Fable, saying that you shouldn’t build with frontier models, because it’s ‘rented land’ and it all can be taken away.

That’s precisely the wrong lesson to take from this experience.

The right lesson is to use it fast and hard for blueprints.

I still have Arachne, my glorious translation software, running on Claude 4.6.

Why?

Because honestly, I didn’t have time to test 4.8 during the 6 weeks it was out, and then Fable happened, and here we are.

But — I already know that 4.6 is solid.

And I got all of Unspice — my ‘does audiobook editing to turn your audiobooks PG-13 for Youtube, etc’ built with Fable — and it totally continues to work now because it wasn’t meant to run on Fable.

I 100% agree that you shouldn’t use frontier models to keep your apps running — although, prior to Fable being yanked, my reasoning would’ve been that they were likely too expensive.

But when presented with the opportunity to use a frontier model to create blueprints that optimize the use of other models?

Should you be using them?

Abso-fucking-lutely.

And anyone who tells you otherwise is wrong.

xo!
Cassie