Professional Services

The public guide remains free. These paid scopes are for people and teams who want hands-on help, a controlled reproduction, or evidence for a specific system.

All work remains evidence-led. Payment does not buy a positive conclusion, hidden edits, or removal of accurate negative results.

Setup Rescue

Introductory fixed price: EUR 199

For an owner who has a Strix Halo system but is stuck between BIOS settings, Linux, GPU access, Ollama, llama.cpp, model formats, or quantization choices.

The scope includes:

• Pre-session review of one machine, one operating system, and one primary local-AI goal.
• One remote session of up to 90 minutes.
• A known-good path or a clearly documented blocker.
• A short written follow-up with the commands, versions, and next steps used.

It does not include an operating-system reinstall, hardware repair, data recovery, unattended administration, or a guaranteed performance number.

Independent Reproduction Sprint

Starting price: EUR 950

For a model publisher, runtime team, developer, reviewer, or vendor that wants an independent Strix Halo reproduction of one clearly scoped claim or route.

A normal sprint includes:

• One agreed model or artifact, backend, and primary question.
• A written test plan before execution.
• Exact hardware, software, command, model, and quantization metadata.
• Cold or warm controls where they materially affect the result.
• Repeats, raw logs, structured results, caveats, and failed-path notes.
• A concise findings report with claim-to-evidence links.

Public publication is optional and must be agreed before the work starts. If a paid result becomes public, the relationship and scope are disclosed. Private results do not become public benchmark claims without written permission and a separate evidence review.

OEM Buyer-Path Pilot

Starting price: EUR 2,500 plus access to the target system

For an OEM, system vendor, reviewer, or developer-relations team that wants a reproducible path from a retail AI PC to working local AI.

A normal pilot covers:

• One named system and operating-system path.
• BIOS, firmware, memory, driver, and runtime capture.
• Two agreed runtime paths and up to three named workloads.
• Setup interventions, failures, restart persistence, and capability checks.
• A public or private technical report, depending on the agreed scope.
• Raw evidence and factual review, without vendor editorial control over the conclusions.

The goal is to reduce buyer and support friction: make the system easier to evaluate, configure, reproduce, review, and recommend.

Custom Local-AI Proof Of Concept

Custom work can cover a private local model, API, retrieval workflow, coding assistant, serving route, or deployment decision. These projects are quoted after a short technical intake because hardware access, privacy, data, licensing, and success criteria vary substantially.

How To Request A Scope

Email hogeheer499@gmail.com with the subject:

Strix Halo service request: [setup / reproduction / OEM pilot]

Include the fields in SERVICE_INTAKE.md. Do not email passwords, API keys, private model weights, personal data, or confidential logs before a secure handling method and scope have been agreed.

The request is reviewed first. Work starts only after the scope, deliverables, schedule, price, confidentiality, publication status, and payment terms are confirmed in writing.

Commercial And Editorial Boundaries

• Prices are introductory starting prices in euros. Applicable VAT and invoice treatment are confirmed before payment.
• Purchasing time or a report does not guarantee that an issue can be fixed or that a target speed, quality score, or compatibility result will be reached.
• Additional work outside the agreed scope requires approval.
• Client data and credentials remain the client's responsibility. Back up important data before any remote session.
• Vendors may correct factual errors. They do not receive editorial control over independent public conclusions.
• Sponsored, loaned, gifted, affiliate, and early-access work is disclosed according to VENDOR_DISCLOSURE.md.