Requirements and scope

Which carriers are covered

The fixed price covers four carriers, selected with you at kickoff for operational value and technical feasibility. We map each portal on a short discovery, then build it end to end. Carriers beyond the four are added under the maintenance plan.

How many workflows

An agreed initial workflow or two on each carrier, for example a lookup and retrieval flow plus one form-based flow. We agree the exact list per carrier in writing before the build starts. Additional workflows are added under the maintenance plan.

One-time codes (OTP or MFA)

We never bypass them. The automation pauses at the code prompt, hands control back to a person who enters the code, then continues. That handover is built in from the start. The best-fit carriers are the ones that let a session stay logged in, so the handover is rare.

CAPTCHA

We do not solve or bypass CAPTCHA. If a carrier gates a step behind one, the run hands back to a person to complete it and resumes. We will not build anything that defeats a carrier's security controls.

Credentials

In an encrypted store outside the source code, never in the repository or a config file. Access is role-gated through CGL's existing permissions, and the automation only reads what it needs for an agreed workflow.

Where it runs

On a controlled browser runtime on your or our infrastructure, in a small container, not a desktop someone has to leave switched on. Each run gets a fresh, isolated session, and an authenticated session is reused where the carrier allows it.

What AI is used, and its cost

The AI is a light assistant, not the driver. Deterministic browser logic does the work; AI only resolves an element when the page markup is ambiguous, and flags an unexpected page state. That keeps inference use low. AI usage runs on your own AI account and is billed to you directly, so it is not part of the fee.

When a carrier redesigns its site

The 30-day warranty covers defects in what we delivered. A redesign, a new anti-bot measure, or a new CAPTCHA requirement is outside it and is repaired under the maintenance plan. Carrier sites change, and those changes are a running cost, not a one-off build item.

How new carriers or workflows are added

Under the maintenance plan. Once the platform is built, adding a workflow on a carrier we already drive, or bringing on a carrier beyond the four, is scheduled as maintenance work rather than a fresh one-off project.

What comes back into CGL

Structured results: statuses, references, confirmations, and extracted data written into the booking or document it belongs to, following CGL's existing conventions. Every run leaves an audit trail, with sensitive values kept out of the logs.

Do we buy anything new

No new licence from us. AI usage runs on your own AI account. You may also need a small runtime host and, if a carrier blocks datacentre traffic, a proxy. Those infrastructure costs are listed separately and excluded from the fee.

How the work is staged

Phased, with a working demonstration at the staging milestone, which is also where the second payment falls due. You see working software before the largest tranche of the build, and if a carrier proves infeasible after discovery we tell you before committing the rest of the budget.

Who owns it

You do. It is built into your CGL application and your repository, on the same stack you already own, with no lock-in to a third-party automation service.