Contact
Describe the workload. We will tell you what it actually needs.
An engineer reads every enquiry that arrives here. Not a lead-scoring queue, and not an account manager who will pass it on. Tell us the job, the shape of the data and the date it has to run, and the first conversation can be a technical one.
The Constraint We Design Around First
A vague enquiry can only get a vague answer.
Nobody can size a cluster from the words "we need more compute". Three numbers change everything: how the job decomposes, how the data is shaped, and when it has to be running. Give us those and we can be useful on the first call.
Send us the brief
Where We Are
Three offices, and engineers who travel to the room.
Design reviews go better in front of a whiteboard, and commissioning goes better in front of the rack. We will come to your site, your data centre, or your facility manager's office.
Sydney
Level 00, 000 Example StreetSydney NSW 2000, Australia
Head office. Engineering, storage and networking practices.
Melbourne
Level 00, 000 Example StreetMelbourne VIC 3000, Australia
Research and media compute. Closest to the eResearch and post-production work.
Canberra
000 Example AvenueBarton ACT 2600, Australia
Government and defence engagements, including cleared personnel.
Sydney · Melbourne · Canberra
Visits to secured facilities need notice for clearance checks. Tell us the site and the date and we will start that process rather than promising a walk-in.
After You Hit Send
Four steps, and none of them is a nurture sequence.
The fourth step is sometimes a recommendation not to buy anything from us. That has happened often enough to be worth saying on the contact page.
Acknowledgement, with a name attached
You get a reference and the name of the engineer who now owns the enquiry, the same business day. Some briefs sit outside what we do. We say so immediately, rather than booking a discovery call to find it out slowly.
A thirty-minute technical triage call
An engineer, and whoever from your side actually runs the jobs. We ask where the time goes today: queue wait, I/O stall, single-thread limits, licence ceilings, or a human step between runs. That distinction decides whether the answer is more nodes, a faster storage tier, a scheduler policy change, or nothing at all.
A written scoping note with the method shown
Five to ten business days later you receive a short document: our reading of the constraint, the assumptions we have made, the measurements still missing, and what we would benchmark to close them. Assumptions are listed separately from findings on purpose, so you can attack ours.
A design and price, or a reasoned no
If the work suits us, you get an architecture, a bill of materials, a commissioning plan and a price, with the operating cost over four years beside the capital figure. If it does not, you get the reasoning and, where we can, a pointer to who would do it better. Both outcomes are free.
Who Picks Up
Every enquiry type has a named destination.
Published so you can hold us to it. If a target below is missed, telephone and say so — that is a process failure on our side, not an imposition on yours.
| Enquiry type | Goes to | Target first response | Bring this |
|---|---|---|---|
| New project | Solution architect for the practice you selected | 1 business day | Job script, dataset size, deadline |
| Workload assessment | Performance engineering | 1 business day | Current wall-clock times and a profile if you have one |
| Managed services | Operations lead, plus the NOC shift manager | 1 business day | As-built documentation, or permission to produce it |
| Partnership | Practice principal for the overlapping area | 3 business days | Where our scopes meet, and where they compete |
| Careers | Engineering hiring panel | 5 business days | Something you built, and what you would change about it |
| Media | Communications, with an engineer for technical questions | 1 business day | Your deadline, stated plainly |
| Existing client support | NOC, 24/7/365 — telephone for anything degraded | Per your service agreement | Site identifier, hostnames, recent changes |
Tender and panel responses are handled by the practice principal named on the panel instrument, not by a bid team writing to a template. That is slower to start and considerably faster to evaluate.
Before You Write
The procurement questions, answered first.
Contracting, confidentiality and lead time, so you are not spending the first call on them. If your question is not here, it is probably the one worth asking.
Yes, and we would rather sign yours than argue for ours. Send it with the enquiry and we will return it executed or redlined, usually within two business days. The only clauses we routinely negotiate are perpetual terms with no expiry and residual-knowledge provisions broad enough to stop our engineers working in the same field afterwards.
If even the existence of the project is sensitive, send one line and a contact name. We will move the detail onto a channel you nominate, including an air-gapped briefing if that is what your classification requires.
Often, and it is worth checking before you write a new approach to market. Tell us which arrangement your organisation buys under — a whole-of-government panel, a state arrangement, a university consortium, or a prime you already contract with — and we will confirm whether we can be engaged through it directly or must come in as a subcontractor.
Where we are not listed, we will say so plainly rather than encouraging a procurement path that will not survive an audit.
Design and assessment work starts within two to three weeks of a signed engagement. Hardware is the variable that ruins schedules: accelerators and high-radix switches have run to long and volatile lead times, and any date we give you carries the vendor's allocation risk, not ours alone.
So we quote two dates. The one we control — design, staging, integration, burn-in, acceptance testing — and the one the supply chain controls. If your deadline is fixed by a grant milestone or a broadcast date, say so in the first message. It changes the architecture, because we will design around parts that can actually be delivered in time rather than the parts we would prefer.
Yes, with a limit worth stating. Design, benchmarking and architecture review we do anywhere, remotely or on site. New Zealand and the Pacific we treat as part of our normal delivery region.
Where we are cautious is 24/7 operations. Our NOC shifts are worked in Australia, so a site many hours outside Australian Eastern time gets slower human response at exactly the wrong hour. We will tell you that before you sign rather than after, and in some cases we will recommend a local operations partner with our design documentation handed over properly.
Sovereignty cuts the other way too. Some of our work cannot leave Australia, and for those engagements we cannot offer offshore delivery at any price.
The triage call and the written scoping note are free. Paid work begins when we have to run something: a benchmark on loaned or hired hardware, a filesystem bake-off against your real data, a profiling engagement inside your environment. We quote that as a fixed-price piece of work with a defined deliverable before any of it starts.
Benchmark results belong to you, including the ones that argue against the design we proposed. We will also hand over the method, so your team can rerun it after we leave.