Gaincue × Canvas Global
Carrier automation,
inside CGL.
A controlled browser layer that runs agreed carrier-portal workflows and writes the result back into CGL as structured data.
Execution brief · September 2026 · four carriers · RM25,000 fixed · valid 30 days
02 · Result
What the system will do.
Log in and hold a session
Authenticates to the carrier and reuses the session while it lives, so logins stay rare.
Enter CGL's data
Fills portal forms from the booking record, not from a person's typing.
Run the workflow
Navigates, looks up, submits, or retrieves, per the agreed workflow.
Extract and write back
References, confirmations, and statuses return to CGL on the right booking or document.
Pause for a person
An unexpected page, an OTP, or a CAPTCHA stops the run and hands back, then resumes.
Leave an audit trail
Every run records what it did and where it stopped, with sensitive values kept out of the logs.
03 · Flow
One run, CGL to carrier and back.
- 01Run triggered in CGL, on demand or on a schedule.
- 02Isolated browser session opens; stored session reused if still valid, otherwise a fresh login.
- 03Navigate to the workflow, fill from CGL's booking data, submit or retrieve.
- 04Extract the result as structured data.
- 05Write it back to the booking or document, then close and log the run.
- !Any unexpected state, OTP, or CAPTCHA pauses the run and hands back to a person.
Each run is isolated and timeout-bounded, and guards against accidental repeat submissions.
04 · How it runs
Cheapest method first. AI only when needed.
Execution hierarchy
- 1 · An existing structured API, where the carrier offers one
- 2 · Deterministic browser and DOM automation
- 3 · Accessibility and page-state analysis
- 4 · Lightweight AI-assisted element resolution
- 5 · Visual or computer-use AI, only where nothing else works
Most runs land at levels 1 to 3, which keeps them fast and inference cost low.
Operating model
- • Server-side runtime in a small container, no operator desktop.
- • One isolated session per run; credentialed access is role-gated.
- • Credentials kept encrypted, outside source code.
- • AI runs on your own account, at your cost.
- • A person is needed only for an OTP, a CAPTCHA, or a flagged exception.
- • Status and run history visible in CGL.
05 · Scope
What the fixed price covers.
The fixed price covers four carriers end to end, each with its agreed initial workflows, selected at kickoff. Everything ongoing, from drift repair to new carriers and extra workflows, sits in the maintenance plan.
| Capability | Included | Maintenance |
|---|---|---|
| Browser runtime and workflow framework | ✓ | — |
| Four carriers, end to end | ✓ | — |
| Agreed initial workflows on each carrier | ✓ | — |
| Auth, sessions, encrypted credentials | ✓ | — |
| AI-assisted element resolution | ✓ | — |
| Results written back into CGL | ✓ | — |
| Logging, retry, human fallback | ✓ | — |
| Additional workflows on any carrier | — | ✓ |
| Carriers beyond the four | — | ✓ |
| Drift repair and portal health checks | — | ✓ |
| CAPTCHA or MFA bypass | Not offered, by design | |
Exclusions are listed in the quotation. Full detail: requirements & scope page →
06 · Investment
RM25,000 fixed. You own it outright.
Fixed price, ex-tax
RM25,000
billed 40 / 40 / 20
Four carriers end to end, each with its agreed initial workflows.
Payment milestones
- CommencementRM10,000
- Staging milestoneRM10,000
- UAT & handoverRM5,000
Maintenance (monthly)
RM1,500/mo
flat monthly
One monthly plan for everything after the build, so nothing arrives as a surprise one-off invoice.
Covers
- ✓Drift repair and portal health checks
- ✓Additional workflows on any carrier
- ✓Adding carriers beyond the four
- ✓Priority support
Running costs (you pay)
Pass-through
not part of the fee
Infrastructure and AI usage you own directly.
Indicative
- ·Runtime host: RM100 to RM300/mo
- ·AI usage: on your own account
- ·Optional proxy: RM200 to RM500/mo
07 · Timeline
4 to 6 weeks. Working software early.
- Phase 0–1 · Wk 1Discovery on the first carrier: portal mapped, workflows confirmed, foundation built.
- Phase 1 · Wk 2–4Carriers built end to end, demonstrating into CGL at the staging milestone.
- Phase 2 · Wk 4–5Resilience: AI element resolution, ambiguous-state detection, retry, human fallback.
- Phase 3 · Wk 5–6Remaining workflows and carriers, regression harness, UAT support, documentation, handover.
Subject to test-account availability, carrier portal stability, and UAT response time.
08 · Next steps
To start, confirm two things.
1 · The four carriers
Selected with you for operational value and technical feasibility.
2 · The named workflows
Agreed per carrier in writing, with test-account credentials supplied.
Then we run the one-week discovery on the first carrier, and build begins on the same basis.
Find us at +60174421238 · info@gaincue.com
gaincue.com · 2026