AVEOS
Prepare US supplier teams for AVEOS launch
Amezay uses the US public surface to capture launch demand, state-aware company context, and the first buyer-facing evidence workflows your team wants live. The request goes into AVEOS launch planning while UK stays the active commercial anchor.
Move from company setup to submission-ready delivery in one operating flow
US launch planning surface
Use the public US page to register company context, state-aware setup needs, and the first evidence workflow your team wants live.
State-aware company foundation
Keep entity form, home state, operating identifiers, and supplier ownership visible in one US home record before target-market overlays are expanded.
Operating company record
Control company identity, ownership, teams, and market scope from one shared workspace.
Submission-ready evidence packs
Assemble reusable evidence packs for tenders, onboarding, and buyer review without rebuilding the same file set.
Review and alert flow
Track expiries, approvals, and external request-backs before they slow delivery.
1. Identity and company
Create the account, attach the company, and define who owns each evidence area.
Keep one GBP commercial baseline ready for every AVEOS country launch.
One-time setup
GBP 8,000. Covers initial setup, company baseline alignment, workspace activation, and the first live operating lane.
Annual operating fee
GBP 20,000 per year. Includes 5 users and migration for up to 20 historical tender entries.
Payments and scope
PayTR credit-card checkout (GBP only) and bank transfers obey the single GBP pricebook so TRY-based collection is disallowed while higher scope stays review-led.
Request AVEOS launch access in United States
Request AVEOS launch access in United States
Leave your company context, buyer market, and the first evidence or DDQ workflow you want AVEOS to cover in United States. The request enters the pre-registration and launch planning queue with the active country and language context.
Run one supplier evidence operation instead of rebuilding every request
Supplier Profile Core
Keep company profile, ownership, contacts, and buyer-facing identity data consistent.
Evidence Vault
Store versioned documents, policies, certificates, insurance, and readiness evidence.
Questionnaire Engine
Reuse answers across DDQs, onboarding forms, and recurring procurement requests.
Trust Room
Share curated evidence packs with time-boxed, reviewable external access.
Narrow enough to sell. Broad enough to grow into the full platform.
US launch planning surface
Use the public US page to register company context, state-aware setup needs, and the first evidence workflow your team wants live.
State-aware company foundation
Keep entity form, home state, operating identifiers, and supplier ownership visible in one US home record before target-market overlays are expanded.
Operating company record
Control company identity, ownership, teams, and market scope from one shared workspace.
Submission-ready evidence packs
Assemble reusable evidence packs for tenders, onboarding, and buyer review without rebuilding the same file set.
Review and alert flow
Track expiries, approvals, and external request-backs before they slow delivery.
Start in the UK and sell across every active AVEOS country
Move from company setup to submission-ready delivery in one operating flow
1. Identity and company
Create the account, attach the company, and define who owns each evidence area.
2. Evidence foundation
Upload documents, categorize them, and keep expiry-sensitive records up to date.
3. Buyer delivery
Run packs, answer questionnaires faster, and open controlled trust rooms for review.
What teams need before each submission, onboarding, and review cycle
Is the US public surface the main commercial anchor today?
No. UK remains the primary commercial anchor. The US page currently collects launch demand, company context, and the first workflows that should go live.
Can US teams keep one home entity record?
Yes. AVEOS keeps the real US home entity and adds target-market overlays only where foreign buyer requirements need them.
Does the US entry stay market-specific?
Yes. The US public surface stays focused on American supplier operations, state-aware company setup, and launch-planning detail while still connecting to AVEOS-active buyer markets.
Where do users actually work?
After sign-in, users operate in the shared AVEOS workspace at us.amezay.com/account-dash/en.
The contracting company officer accepts the AVEOS commercial and operational service terms for this country package.
This notice explains how AVEOS handles account, organisation, evidence, access, audit, billing, and support data.
This notice explains organisation-level data handling, controller-processor boundaries, and cross-border service operations.