The workload, the memory budget it has to fit inside, and what breaks today. That is enough for a useful first reply, and it is more than most forms ask for on purpose.
Pilots, licensing, and technical evaluation all start here. Say which one you are after and the message lands with the person who can answer it rather than the person who books the call.
A reply comes back inside one business day, from someone who has read the message. If a pilot is the right next step, the scope sheet and the qualifying questions come with it.
If you would rather not use a form, write to hello@semgrav.example and it reaches the same place.
The route you pick sets who replies and what comes back with it. Pick the nearest one, we will move it if you land in the wrong queue.
You have a workload and a memory budget, and you want the comparison run on your own traffic. The reply carries the scope sheet and the qualifying questions.
You know where the field belongs and want terms, tiers, and what the licence covers. The reply comes from the people who negotiate it, not from a queue.
You want to interrogate the mechanism before anyone talks commercials: how it is configured, what it is measured against, and where it does not fit.
Not a routing rule. The detail you put in the message is the detail the reply answers, so specifics are worth the extra minute.
You get a reply inside one business day. If the answer needs someone who is heads down that week, we say so and give you the date.
If a pilot is the right next step, the reply carries the scope sheet and the qualifying questions. No deck, no discovery theatre.
If the field is the wrong tool for what you run, we say that instead. It costs us one email and saves you a quarter.
SCOPE: nothing you send is shared outside the people who need to read it, and a pilot conversation moves under NDA before any of your workload detail changes hands.
None of this is required, and a one-line message is still welcome. But a reply can only be as specific as the message it answers, and these four are what turn a first reply into a useful one.
What actually runs: the sessions, the context lengths, and the traffic shape that pushes memory hardest.
The footprint it has to fit inside, whether that was fixed by the hardware or by the bill.
The failure you are trying to remove: a reset thread, a dropped value, a cost curve, a device that cannot hold the day.
What a measured answer would let you decide, and roughly when you need it by.
A shape, not a template. Prose is fine, and rough numbers are better than none.