Design review
The problem list before your customer writes theirs.
Send the design you intend to submit. Three working days later you receive a scored report that names the evidence, the gaps and the open decisions.
01
Illustrative review finding
Know the gap before you commit.
This illustrates the structure of a review finding. It is not a customer result or a completed engineering assessment.
- Requirement
- The customer needs 8 PiB of usable storage.
- Evidence gap
- The capacity calculation exists. Vendor confirmation of usable capacity, workload throughput and the orderable configuration is still missing.
- Consequence
- The bid could commit to capacity or performance that the proposed configuration cannot deliver.
- Decision and owner
- Assign the storage architect to obtain vendor sizing evidence. The bid owner must approve the scope or record the exception before committing.
01
What you send
Send the RFP or requirement set, the topology, the bill of materials, and the rack and power envelope where those exist. Missing inputs remain named unknowns. They are not filled with guesses.
02
What comes back
- A requirement-by-requirement evidence register
- Hard gates and unevidenced claims first
- Architecture, bill of materials and envelope reconciliation
- Named decisions, assumptions and exceptions
- A review meeting to decide what changes before submission
03
The boundary
This is a finding report. It does not warrant, certify or approve a design for submission. NVIDIA or a customer may reject a design for reasons outside the review.
The $5,000 review fee is pro rated against what you buy next. We confirm the credit in your next order. Refund and repeated-review terms remain subject to the signed engagement terms.
04
Start with the submission date
Tell us your submission date and what needs deciding. Before you share confidential files, we agree scope, start date, deployment, support and data-handling terms. The three working days cover the review, starting on the agreed date.
02
Before you buy
What you are buying. What needs agreement.
What does the review fee cover?
A $5,000 review, delivered in three working days from the agreed start date, with an evidence register, gaps and a decision meeting. The fee is pro rated against what you buy next. The next order records the credit; refund and repeat-review terms are agreed in writing.
What do we keep?
The $50,000 standalone licence is perpetual. The $75,000 Bid Pack includes the compiler licence and a package produced with you in ten working days. Knowledge-pack subscriptions and additional services are priced separately.
Where does our data go?
Before you share a confidential RFP, we agree processing location, permitted access, retention and deletion. The hosted demo is a disposable evaluation environment. Use sample inputs there.
What about deployment, packs, updates and support?
Your order names the deployment arrangement, included knowledge packs, update entitlement and support coverage. We confirm these against your environment before you buy. The public demo does not establish your production deployment terms.
Who will we work with?
Matt Hertel is your first contact and replies within two working days. The architecture team has designed compliant architectures for leading hyperscalers and model builders. We agree the reviewer and decision meeting as part of the engagement.
Does repeated bid work justify it?
Illustration only: five designs a year × ten architect-days saved per design × $1,000 per day = $50,000 of architecture capacity. Those are assumptions, not measured Neon savings. Replace them with your bid volume, effort and internal cost. Include pack subscriptions, support and implementation costs in your comparison.
The immediate review decision is narrower: is $5,000 worthwhile to identify the gaps and owners on this bid before you commit?
Discuss your design