NeuroForge
Appearance

Use your device setting or keep a preference on this browser.

Contact
Navigate
Support the labTalk to Lloyd

Quick find

Find what you need

Esc

Try a job or topic, such as meeting notes.

    Search learning resources Free lessons, printables and activities.

    10-Day AI Fit Test

    Find out whether AI can do the job.

    For A$5,280 including GST (A$4,800 ex GST), try a useful workflow with examples you approve. We test on an agreed compatible computer or an approved reference machine. Get a local demonstration and a report on what worked, what needs changing and whether to go ahead.

    Ask about the Fit TestSee a report example

    Use the model that fits the job. There’s no obligation to go ahead with a deployment.

    Payment is due in full before work begins. The 10 business days start on a date we agree in writing, once payment is received, approved examples and machine access are ready, and your review is booked.

    Fixed standard scopeA$5,280 including GST
    Elapsed timeUp to 10 business days
    DecisionDeploy · change · stop

    A tangible handover

    This is what the decision looks like.

    The report shows the tested cases, hardware requirements and failures behind its recommendation. You can use it to budget the next stage or decide to stop.

    Taking it further? A$2,400 of the ex-GST Fit Test fee is credited toward a separately agreed private technical-document setup (NF-A1) if both parties sign within 30 calendar days after delivery of the final System Fit Report.

    System Fit ReportIllustrative specimen
    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

    Illustrative report. The cases and results above show the format; an engagement produces its own measured findings.

    What you take away

    Try the workflow on an agreed computer.

    See the workflow on the agreed machine, understand the limits, and leave with the evidence to choose the next step.

    The target, model, cases, failures and recommendation stay together. The signed statement of work may narrow the exact deliverables.

    1. See what works

      A local demonstration with the approved cases and the failures kept visible.

    2. Understand the limits

      A report on the hardware, runtime, data boundary and questions still unresolved.

    3. Choose what happens next

      Decide whether to deploy, make changes or stop. A clear reason to stop is useful too.

    Full handover contents
    • 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

    How it works / Up to 10 business days

    Test it together.

    Bring one workflow, the person who owns the decision and representative cases. We agree what success means before testing begins.

    The engagement succeeds when its result, limits and next action are clear. A larger deployment is a separate decision.

    Is this the right starting point?

    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

    Another path is needed 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
    What we agree before starting
    • 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

    Start requirements

    One repeated non-safety-authoritative workflow, one decision owner, an approved target or reference host, three to ten lawful non-sensitive cases, clear data/network/output limits, and a buyer review inside the delivery window are required before work starts.

    The steps we follow

    1. Define the workflow, current alternative, decision owner, consequence, and stop rule.
    2. Inspect data rights, network, host, memory, storage, power visibility, software, and prohibited uses.
    3. Run the local preflight and record the deployability envelope, unavailable measurements, and blockers.
    4. Demonstrate the practical ceiling on approved customer-relevant cases and retain failures.
    5. Recommend staged deployment, remediation, a model/hardware change, rescope, or stop.
    How you accept the handover
    • 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.
    Scope and terms

    AI System Fit Audit & Local Demo · NF-A0

    Audit and local demonstration only. No production deployment, full-corpus ingestion, bespoke integration, continual learning, certification, penetration test, production SLA, or guarantee of accuracy, savings, deployability, or ERAIS performance.

    What this engagement does not establish

    The offer is a founder-led market test with no observed demand or delivery history. An audit or demonstration does not establish production readiness, broad device support, customer traction, or general ERAIS quality or efficiency.

    Offer source and review record

    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.

    Talk to us

    Would AI actually help?

    Tell us the job you’re trying to make easier and the computer or tools you use. We’ll work out what a useful test would look like.

    Ask about the Fit Test