[LarryMade2]

If you are paid by the job and not the hour, and you don't have any expectation of supporting the product, using a framework would be most tempting. It gets it done quick, looks acceptable, you'll get paid and move on.

Now if you are long term or expected to support, then you have to weigh the additional work of supporting the framework along with the app. The app you know; the frame work, while well supported now, may not survive web 3.0 or whatever. And if that happens you probably have a more complex migration than if you had built it all in the first place.

I've seen stuff developed on earlier Drupal DB now languishing because the effort it will take to update (and it wasn't really all that great in the first place, so it will be double work for them to update and re-factor).