01
Business and quality
Process, current baseline, output schema, example types and unacceptable errors.
Pilot design / bounded engagement
Start with one workload and a decision to make
Bring one task, a current baseline, examples of unacceptable errors and the data boundary. Gyde and your team set quality, latency, operating and cost thresholds before controlled traffic starts. The pilot ends with a recorded go/no-go decision.
Use the contact form to describe the workload. Do not submit complaint text, statements, account numbers or other sensitive records.
GYDE / INFERENCEILLUSTRATIVE PILOT FLOW
DESIGN PATH / BUYER-SPECIFIC
01WorkloadTask + test cases
02ModelQualified candidate
03PolicyAllowed route
04ServingApproved capacity
05EvidenceOutcome + cost
Decision: proceed, redesign or stop
01Discovery inputs
Start with descriptions, not sensitive files.
02
Operating shape
Approximate traffic band, latency need, integration owner and failure tolerance.
03
Boundary
Target geography, preferred environment, approved providers, data permissions and budget owner.
02Pilot stages
Each stage needs evidence or approval to continue.
Timing is agreed after discovery. The customer approves data use and pass/fail rules before testing; infrastructure spend follows the agreed approval policy.
01Discovery / joint→︎
02Offline evaluation / Gyde→︎
03Approved setup / joint→︎
04Traffic and failure test / Gyde→︎
05Go/no-go review / customer
03Acceptance scorecard
Set thresholds before the run.
These are blank fields for the buyer and Gyde to agree. No default target is implied.
| Measure | Agreed threshold | Evidence owner |
|---|---|---|
| Task quality and severe errors | Domain reviewer | |
| p95 latency and served-request rate | Operations owner | |
| Location and egress evidence | Security owner | |
| Cost per accepted result | Budget owner |
04Review package
Leave with a model comparison and an operating record.
01
Model decision
Frozen comparison, scoring rules, error slices and recommendation.
02
Deployment record
Data-flow diagram, policy record, operating owner and rollback plan.
03
Measured outcome
Success and failure accounting, estimated and billed cost separated, open risks and go/no-go review.
05Qualification gate
Stop if the evidence cannot support a decision.
If data permission, provider capacity or evaluation quality cannot meet the agreed threshold, the team records the constraint and stops or redesigns the pilot before expanding it.
?Buyer questions
Questions to settle before a pilot.
Answers reflect the current prototype and scoped engagement approach.
What data do you need first?
Start with a description of the process, schema, error types, rough volume and data boundary. Representative records are discussed only after an approved handling path is in place.
Can we pilot in our cloud?
A customer-cloud profile can be scoped. Packaging, network, identity, region, provider access and operational ownership have to be designed and accepted in your environment.
What counts as a pass?
The buyer and Gyde set quality, severe-error, latency, availability, boundary and cost criteria before the run, using a frozen evaluation set and a clear baseline.
Who pays for GPUs?
The pilot agreement names the bill payer and approval policy. Card-billed supplier use in current operations requires manual approval.
Gyde Inference pilot
Start with a workload you can measure.
Describe the task, data boundary and decision you need to make. We will scope the test and operating conditions together.
Discuss a workload Do not submit sensitive records through the marketing form.