Need improved t-shirt sizes for Standard Edition

We need to improve our t-shirt sizing for Standard Edition.   We need sizes that allow our sales teams and customers to choose the right architecture to meet their needs.  There are a number of key requirements and reasons that we need this data.

Our sales teams need to steer customers in the right direction.  Ideally, we want as many customers as possible using Standard Edition.   We know that our largest customers will need custom edition.  But, there are many customers with 5000 servers or less and reasonable transaction rates that can probably fit into  a Standard Edition deployment.

Probably the most important t-shirt sizing is to understand the absolute maximum that we can  push a 5 node cluster.   For example, I recently worked with a customer that is expecting 41K spans/second.  Currently we haven't tested with those numbers.    My general recommendation would be to have a target of around 50K spans/second, but to try to push Standard Edition as high as it can go with the current performance characteristics.

Then, we need several other t-shirt sizings for the most common configurations:

• Demo - this is always needed in order to reduce the HW requirements
• Small Single Server - A reasonable environment that can handle a small production workload.   I would assume that the customer won't want more than 28 vCPU and 96 Gig of RAM. But, this needs to take into account the most common additional features (Logging, EUM).  
• Large Single Server -If a customer will willing to devote 40 vCPU and 200+ Gig of memory, how well can it scale?   
• Small 3 node deployment:   This should be configured to be quite small.   We have a number of customers that want a 3 node deployment because they can't get a single VM with enough cores.  For example, I want to do a POC and I want to use synthetics, logging, and automation.  I would need around 20 vCPU.  Some customers can't get a VM with more than 16 vCPU.
• Large 3 node deployment:  This should be a 3 node that pushes the product to the limits.  Maxiumum number MVS and spans/second.   Ideally, close to 40K spans/second
• Large  5 node deployment:  We should strive for higher scale than what we have with the small 3 node.   Most customers that go with 5 node will do it because the 3 node can't meet their scale needs.  How high can I scale a 5 node deployment.  Target should be around 50K spans/second

With each of these t-shirt sizes, there should be an out of the box configuration within Instana.   So, instead of saying Demo or Production, we should have small, medium, large, etc. and the datastores, etc. would be tuned to ensure good performance.