LW GLOBAL CONNECT — AI-READABLE IMPLEMENTATION BRIEF
Version: 2026-08-31
Owner context: LW Technologies
Status: Private review POC; not production

PURPOSE
Create a premium, business-first connectivity experience for LW Technologies. The public-facing demo should make the customer journey tangible while the live architecture is evaluated separately.

DECISION ALREADY MADE
- Roamless is demo-only.
- Roamless must not be treated as the live provider or carried into the production architecture by default.
- The live shortlist should center on Gigs and credible competing telecom infrastructure providers.
- No provider, pricing, coverage, provisioning model, billing arrangement, support boundary, customer-ownership model, or white-label scope is confirmed by this POC.

DEMO ROLE
- Use the public Roamless destination to demonstrate the referral/customer journey.
- Keep the handoff clearly labeled as a demo/reference route.
- Do not represent the demo as a signed partnership, affiliate relationship, confirmed offer, or production integration.
- Public reference: https://www.roamless.com/

LIVE PLATFORM SHORTLIST TO DILIGENCE
1. Gigs — public materials describe an operating system for embedded telecom, with Connect, Payments, Operator, Dashboard, and API products. Public references: https://gigs.com/ and https://docs.gigs.com/
2. eSIM Go — public materials describe own-brand digital mobile services, a wholesale eSIM API, affiliate eSIM solutions, and a pay-as-you-grow platform. Public reference: https://esimgo.com/
3. 1GLOBAL — public materials position the company around enterprise telco solutions, eSIM, tech and travel, IoT, compliance, and mobile-operator partnerships. Public references: https://www.1global.com/ and https://www.1global.com/partnerships/
4. Telna — public materials list API-first Connect, Connect Flex, Network API, eSIM, and management tools for global cellular connectivity. Public reference: https://www.telna.com/

These are candidate categories surfaced from public marketing/product pages, not a ranking and not a statement that any provider has agreed to work with LW Technologies. Validate current capabilities directly with each provider before relying on them.

REQUIREMENTS BEFORE A LIVE DECISION
A. Market and network
- Launch countries and expansion sequence
- Network access, roaming behavior, speed policies, throttling, and outage handling
- Consumer, business, travel, or IoT scope

B. Product and provisioning
- eSIM and/or physical SIM support
- Activation, install, lifecycle, suspension, cancellation, and replacement flows
- Supported devices and operating systems
- Data, voice, SMS, phone numbers, add-ons, and plan controls

C. Billing and settlement
- Wholesale rates, margins, minimums, taxes, refunds, chargebacks, and settlement cadence
- Who is merchant of record and who owns payment data
- Catalog, pricing, discounting, and reporting controls

D. API and integration
- API/SDK scope, sandbox, authentication, versioning, rate limits, and webhooks
- Provisioning and plan lifecycle endpoints
- Monitoring, logs, status visibility, incident communication, and data export

E. Compliance and ownership
- KYC/identity requirements and regulatory roles by market
- Privacy, data processing, retention, and customer-consent responsibilities
- Customer relationship, terms, acceptable-use, and brand ownership

F. Support and operations
- First-line and escalation ownership
- Service levels, ticketing, outage response, refunds, and service recovery
- Account administration, fraud handling, and customer communications

LIVE PRODUCT BOUNDARY
- The live service, if pursued, should be LW-branded and provider-backed rather than an LW carrier/MVNO implementation unless a later brief explicitly changes that boundary.
- The provider decision must be based on verified requirements and negotiated terms, not the demo provider.
- A later phase may evaluate hosted checkout, API, SDK, co-branding, or white-label scope; none is currently confirmed.

NON-GOALS FOR THIS POC
- No carrier network, MVNO, eSIM provisioning, billing, CRM, support desk, or customer account backend
- No live lead capture; the form is demo-only and does not transmit or store data
- No production deployment, domain/DNS change, provider signup, vendor outreach, or external support request
- No claim of Roamless, Gigs, eSIM Go, 1GLOBAL, Telna, or any other signed relationship

RECOMMENDED NEXT SEQUENCE
1. Confirm service audience, markets, devices, and data/voice/SMS requirements.
2. Turn the requirements above into a weighted provider scorecard.
3. Request current capability, commercial, compliance, and support details from shortlisted providers.
4. Select a live platform only after fit and ownership are documented.
5. Build a sandbox integration and test provisioning, billing, support, and failure paths.
6. Only then define a production launch plan.

HOW AN AI ASSISTANT SHOULD USE THIS
Treat this file as the source-of-truth brief for the current review POC. Preserve the demo/live separation. Mark unknowns as unknowns. Do not invent pricing, coverage, terms, credentials, integrations, or provider commitments. When proposing work, distinguish static prototype changes from live telecom implementation.