Adil Soukaini | Full-Stack Developer

Thanks Kamran, "who maintains it in year two" is a better first question than the one I led with. It also makes the hand-over easier: one framework's auth, queues and scheduler are simpler for the next developer to pick up than five libraries wired together by hand. In the post's Driveway Morocco example (a car-rental demo I built in Laravel), adding the Expo mobile app later only meant adding Sanctum tokens to the same backend, with no second server. When you do pick NestJS, do you keep real-time inside the main app or split it into its own service from day one?

Thanks, that's a fair correction, and a better way to put it. Fixed price only hurts when a change has nowhere to go. If the first piece of work is one problem with a written finish line, the change becomes its own small, priced piece of work. That's close to how I quote too: one defined problem first, then the next one. On your question: I think the model usually follows the product's stage. Before launch the work is a defined build, so a fixed price fits. After launch it turns into a steady stream of small fixes and features, and that's where a retainer earns its place. An agency fits in between, when you suddenly need several people at once for a while. The one thing that shouldn't change across those moves is ownership: code, hosting and accounts in the product owner's name, so switching models is a business decision, not a migration project.