What if we are not ready to buy anything?

That is a normal starting point and worth saying openly. Plenty of enquiries are people testing whether an approach is sound before writing a business case. We will answer the technical question without treating it as a pipeline event. If the honest answer is that your existing platform is adequate for another few years, you will get that answer.

Can we send a requirements document instead of filling in the form?

Yes. Use the form to introduce the requirement and attach or reference the document from there, so it arrives with context rather than on its own. Tender packs, architecture diagrams and inventory exports are all useful. Strip anything sensitive first. If a document cannot leave your environment, describe its contents and we will work from that.

One route in

Tell us the problem in your own words, and we will tell you whether we are the right people for it.

The enquiry form is the channel we monitor. It reaches the people who would scope the work rather than a general mailbox.

Send Your Enquiry Request an Assessment

If your requirement is outside what we do, we will say so in the first reply rather than book a meeting to find out.

What to include in your enquiry

None of this is mandatory. Each item removes a round trip.

The problem, not the product. "Our PACS archive is out of support and the vendor has stopped supplying media" tells us more than a request for a quotation on a named library.
What is forcing the timing. An audit finding, an expiring support contract, a facility move and a budget cycle each change what a sensible answer looks like.
New build or replacement. Whether you are adding a tier to a working estate or replacing something that has failed determines whether migration is part of the conversation.
Roughly how much data, and how fast it grows. An order of magnitude is enough at this stage. Precise figures belong in scoping.
Where the site is. Country and whether it is a data centre, a hospital floor, a broadcast facility or a remote installation.
Who else is involved. Records, security, procurement and the incumbent integrator often hold half the constraints.

Please do not send credentials, configuration exports containing personal data, or anything covered by an internal classification you would rather not email. Describe it instead and we will agree a safer route.

How enquiries are routed

Enquiries divide into three kinds, and each goes to a different place.

Enquiry	Where it goes	Typical first reply
Technical scoping, architecture, feasibility	Storage architect	Questions, or an offer to run an assessment
A known requirement needing a configuration	Configuration desk	Confirmation of what still has to be pinned down before anything is costed, via configuration and pricing
Reseller, distributor or project partnership	Partnerships	A short conversation about coverage and scope, see partner with us

Two things will not come back by return. We do not issue prices without a validated configuration, because availability and firmware compatibility change what is actually buildable. We also do not confirm delivery timescales in a first reply. Both come after the checks described on the configuration page.

If you are still deciding which of the five solution areas applies, say what worries you and we will point you at the right one.

Frequently asked questions

Not a reliable one. A figure produced from a model number alone tends to be wrong on interfaces, capacity headroom, rack and power fit, or software licensing. We would rather ask six questions and issue something you can put in front of finance. If you already know the shape of the system, the configuration request page lists what makes that quick.