These get a little boutique, but if you want to attract and close large enterprise/regulated customers, I'd extend a few of yours: - Build your application to

These get a little boutique, but if you want to attract and close large enterprise/regulated customers, I'd extend a few of yours: - Build your application to suit many customers or one. Large customers love to have their instance run in a dedicated account. - Open source your operations. Large customers love to see logs/operational activity from their environments (e.g. cc: cloudtrail/config/cloudwatch logs to customer, this assumes dedicated account) - Open source your security. Be prepared to ship guardduty, config rules, etc to your customer (this assumes dedicated account). Also, since we're focusing on AWS here - Build your application to support hybrid cloud customers. Expose it through private link, VPC connections, transit gw, firehose, api gateways, VPC lambdas, whatever is appropriate for your architecture. - Leverage IAM as much as possible for authentication/authorization. Not AWS-specific but implement SSO and assume customers will require numerous instances of your service when developing your user account model. - Leverage KMS as much as possible to protect data at rest, and support customer CMKs. There are more but I'll stop here.