> I worry that if I start taking fixed-fee projects the incentive to make good software will be gone (the faster I deliver, the better). There's no incentive fo

> I worry that if I start taking fixed-fee projects the incentive to make good software will be gone (the faster I deliver, the better). There's no incentive for documenting things, writing tests, creating a CI/CD pipeline or any of that. These things simply become nice-to-haves that will not matter once you deliver the project and cash yourself out. If you're setting this stuff up when you're doing hourly billing, are you not explaining to the client why it's worth the time in the long run? Just do the same for fixed price quotes. There must be some value to the client or you probably wouldn't think of doing it. > While this is sort of true, I also find that hourly work gives you more freedom to approach the work with a "craftsmanship" mindset. We all know good work takes time. I feel the opposite with hourly. In the worst case, you're having to ask permission before billing hours on something (like setting up CI) and then having your timesheets scrutinised. This takes up time itself and slows everything down. With fixed price, the client doesn't have to worry about tracking your hours and just lets you get on with it.