Explain to the client about "technical debt"

Rush through things to get version 1 out of the door is an option, but the application may not live up to customer's expectation, and competitors may beat your client before version 2 or 3 can be rolled out (since version 1 wasn't built with quality in mind)

Code generation during build can help keeping code base consistent

Strive to diminish rework

Lean thinking

build quality into the process

Code quality and toyota comparison

You can have a process that embraces change

building relationship with client is very important

tight feedback: have the customer working with you in order to avoid rework and waste

Whether you're writing "production" code or "test" code, you are "coding"; it's part of the craft.

Keep track of time spent doing rework

there's a lot of resources explaining "why" quality matters

Document the symptoms of technical debt.

How to show tech debt to biz users/stakeholders? Bug reports and cycle times can help

ndepend: shows you all metrics about your app