>I've never seen "less bugs" on a product comparison sheet, for example. Those show up, your sales department just uses the more formal names for the actual c

>I've never seen "less bugs" on a product comparison sheet, for example. Those show up, your sales department just uses the more formal names for the actual customer demands that “less bugs” encodes. That will look like some combination of • “We have an SLA for an annual 99.9xx% uptime and average sub x00 latency!” (so if a bug causes significant annual reduction in service, your business gets penalized), • ”We guarantee regulatory compliance!” (so if a bug or business use causes regulatory issues, it’s your ass on the line), • “We guarantee 24/7 same day chat or email support!” (so if a bug causes an outage, they have a warm body they can yell at, demand an explanation for their customers, and ask questions) • “We guarantee backups, data redundancy, and worldwide data replication!” (so if a bug blows up one of your data centers somewhere, or the intern fat-fingers an accidental deletion of the production user database, the customer doesn’t even notice something went wrong) • “We guarantee API backwards compatibility or a service maintenance guarantee until 20xx!” (So you’re forced to fix bugs, and the bug isn’t ‘your PM team might try to #KilledByGoogle’ the service you invested in building infrastructure on.) Teams that believe in the health, care, and security of their design are far better equipped to offer the above valuable terms to customers to gain competitive business advantage, and teams with bad engineering hygiene are likely to be scared off.