Are you genuinely asking?

As 80% of enterprise software is CRUD with a bit of sprinkling of user authorization and tenant customisation. But subtly different for every business domain. It's mainly what properties the models and validations have that are different.

When you add a new module or whatever most of the code you have to write is rote code.

And sonnet can handle that crap just fine, you just point it at a similar example in the code, it picks up your userContext convention, how you're doing i18n, etc. and you're done.

I like saying that enterprise code is often shallow but wide. I must have written at least 4 purchase order systems in my career that are all completely different but almost exactly the same.

Add new route to API that displays additional information we need, work out query for it, update controllers/models/whatnot. No need for top model for that.

Write a detailed plan using a more expensive model and implement it using the cheaper one.

How much are you saving once the more expensive model already has all the context loaded and ready to go?

There is caching to consider. Switching models throws away the cached tokens.

"rote" is the wrong framing, the real point is that however sophisticated your task it a lot of it will probably consist of problems they have a good solution already in the training set.

One task I've found this useful for is writing example code. Release admin (updating version numbers, etc) as well.