Pilot design / bounded engagement

Start with one workload and a decision to make

Tell us the task, how you handle it now, which errors matter and where the data may go. Your team and Gyde agree on pass/fail criteria before testing. The review compares models, records request failures and cost evidence, and gives your team a basis to proceed, redesign or stop.

Use the contact form to describe the workload. Do not submit complaint text, statements, account numbers or other sensitive records.

01What to bring

Start with descriptions, not sensitive files.

01

The task

Describe the process, your current method, the result you need and errors you cannot accept.

02

How it will be used

Share a rough request volume, response-time need, integration owner and tolerance for interruptions.

03

Your rules

Name the target geography, preferred environment, permitted 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.

Your team and Gyde fill in these targets before testing. The blank cells are decisions to make, not default targets.

Set thresholds before the run.
MeasureTarget to agreeEvidence owner
Task quality and severe errorsDomain reviewer
p95 latency and served-request rateOperations owner
Location and egress evidenceSecurity owner
Cost per accepted resultBudget owner

04What you receive

Leave with a model comparison and an operating record.

01

Model comparison

Results on the agreed test cases, scoring rules, serious error types and a recommendation.

02

Deployment record

A map of where data went, the agreed rules, the operating owner and a rollback plan.

03

Decision record

Successful and failed requests, estimated and billed costs kept separate, open risks and a 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.

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.