10-Day AI Fit Test / formal engagement NF-A0

Know what fits before you fund the rollout.

For A$4,800 ex GST, test one useful workflow on the target hardware and approved data. Leave with a working local demo, visible failures, and a deploy, change, or stop decision.

Test a workflow See a report example

Formal offer: AI System Fit Audit & Local Demo · model-neutral · no obligation to deploy.

Fixed standard scopeA$4,800 ex GST

Elapsed timeUp to 10 business days

DecisionDeploy · change · stop

A tangible handover

This is what the decision looks like.

The report ties the recommendation to the actual workflow, machine, cases and observed limits—not a polished demo on unrelated infrastructure.

Proceeding? A$2,400 is credited toward NF-A1 when the next deployment stage is signed within 30 calendar days.

DecisionDeploy with changes

Target: Existing 32 GB workstation
Candidate: Qualified local model
Cases: 8 / 10 passed illustrative
Failure: Source mismatch retained on case 07
Recommendation: Repair the source set before staged deployment

Example report shape—not a customer result or a promise that this workflow will pass.

What you receive

A decision pack—not another proof of concept.

The evidence, failures and next-step recommendation travel together. The signed statement of work may narrow the exact list.

01System Fit Report covering the decision, current alternative, target host, approved boundary, observed limits, unresolved risks, and recommendation
02Local Demo Pack with the agreed cases, outputs, failures, exact target identity, and demonstration limits
03Hardware and Runtime Envelope separating what was measured, what remains unknown, viable model/runtime classes, and when different hardware is required
04Data and Accountability Boundary naming permitted information, prohibited use, decision ownership, evidence retained, and stop authority
05Fixed staged-deployment option, prerequisite-remediation plan, or explicit no-bid/stop record

A good fit when

A buyer deciding whether a local AI deployment is technically and economically worth funding
A valuable workflow constrained by data location, hardware, connectivity, power, latency, or provider dependence
A team that wants visible demo outputs and failures on its own target or an approved reference machine
An organisation prepared to accept deploy, change, remediate, rescope, or stop

Not the right starting point when

Autonomous or safety-authoritative decisions, live OT/SCADA/control integration, or public production exposure
Classified, export-controlled, patient-identifiable, credential, or otherwise unauthorised material
A request for regulatory, legal, privacy, security, safety, or engineering certification
An exact field device that cannot be accessed or qualified inside the agreed scope

How it works / Up to 10 business days

Agree the test. Run it. Make the call.

The workflow, cases, target environment, decision owner and stop conditions are agreed before the result is known.

01Define the workflow, current alternative, decision owner, consequence, and stop rule.
02Inspect data rights, network, host, memory, storage, power visibility, software, and prohibited uses.
03Run the local preflight and record the deployability envelope, unavailable measurements, and blockers.
04Demonstrate the practical ceiling on approved customer-relevant cases and retain failures.
05Recommend staged deployment, remediation, a model/hardware change, rescope, or stop.

What we need from you

One repeated, valuable, non-safety-authoritative workflow and its economic owner
One customer-controlled target host or approved reference machine
Three to ten representative, lawful, non-sensitive test cases
Known data, network, connectivity, output, and prohibited-use boundaries
Permission to retain enough non-sensitive evidence to reconstruct the decision

A useful answer can be no

The customer chooses the next step.

The engagement succeeds when the tested boundary, evidence, failures, limits and next action are clear—not only when the workflow passes.

Handover is complete when

The decision owner confirms that the report accurately records the tested target, approved boundary, demonstration, limitations, and recommendation.
The local demonstration pack preserves the agreed cases, outputs, failures, target identity, and stated measurement limits.
The hardware and runtime envelope distinguishes measured findings from unresolved questions and unavailable telemetry.
The customer selects proceed, remediate, change model or hardware, rescope, or stop.

The result stays tied to what we tested

Clear evidence. Clear boundary.

The target, model, configuration, cases, limits and recommendation remain attached to the decision.

Before you enquire

Common questions.

Is this a production deployment?

No. It tests fit and produces a small customer-relevant demonstration plus the evidence needed to decide whether a larger deployment is justified.

Does the audit require a native ERAIS model?

No. NeuroForge can use the best-fit qualified local or open-weight model. ERAIS is used only where its current capabilities and evidence methods add value.

Can the right answer be not to deploy?

Yes. A documented stop or hardware-change decision can prevent a much larger failed implementation and is successful delivery.

Can you assess a field or embedded device?

Only under an exact-device scope. Embedded, mobile, robotics, drone, intermittent-power, and non-x86 environments are valuable qualification paths, not included standard support claims.

Formal scope remains available

Bring one workflow worth testing.

Describe the workflow, target machine, data boundary and the result that would make you deploy, change—or stop. Do not send protected material in the first message.

Test a workflow