Google Cloud Commercial and Professional Services Sweden

Arrive

Enterprise Knowledge Search

Arrive needed to work across fragmented post-merger HR, CRM, project, and messaging systems without waiting on a long ETL program, because information silos were slowing RFP work, onboarding, and day-to-day collaboration.

Cut RFP research time from hours to minutes
Enabled development of an AI retrieval layer in two weeks
a similar process would have taken up to four hours

Reported impact

Business outcome

Arrive built its AI retrieval layer in two weeks, cut RFP research from hours to minutes, improved onboarding and cross-team collaboration, and created a scalable alternative to separate AI add-ons across each legacy system.

  • Customer Experience
  • Productivity Improvement
  • Scalability
  • Speed to Market

Solution

Arrive used Gemini Enterprise and Gemini Enterprise Agent Platform to build Aria, an AI retrieval and orchestration layer that sits across siloed internal systems created by multiple acquisitions. Instead of migrating all data first, the company configured Aria to query live backend sources across HR systems, CRM platforms, project tools, messaging systems, and other internal repositories, then return grounded answers through a single conversational interface. Gemini handles the natural-language reasoning, Agent Search points requests toward verified internal sources, and prompt engineering bridges inconsistent schemas so the model can interpret disparate data structures correctly. The team monitors performance with automated logging and employee feedback as new companies and systems are brought into the environment. This design let Arrive deliver a production virtual agent in two weeks and turn hours of manual RFP and onboarding research into minutes.

Data flow

Employees ask Aria natural-language questions, Gemini interprets the request, the agent layer queries live HR, CRM, project, and messaging systems, Agent Search grounds the response in verified internal sources, and the answer is returned through a single conversational interface while logs and feedback tune performance over time.

Solution architecture

5 components · 3 layers
  1. Compute
    • Gemini Enterprise Provides the governed enterprise AI layer that sits across Arrive's siloed systems.
    • Gemini Interprets complex queries and generates grounded responses from fragmented internal data.
  2. Serving
    • Agent Search Directs the model toward verified internal data sources to reduce hallucinations.
    • Google Maps Supports Arrive's longer-term plan to add richer geospatial mobility insights.
  3. Orchestration
    • Gemini Enterprise Agent Platform Provides the foundational orchestration platform for Aria and its live system access.

Architecture clues

  • Agent Search is used to ground answers in verified internal data sources.
  • Aria queries live systems instead of waiting for a multiannual ETL migration.
  • Performance is monitored with automated logging and employee feedback.
  • Prompt engineering is used to normalize inconsistent HR schemas.

Evidence from the source

Enabled development of an AI retrieval layer in two weeks
We used Gemini Enterprise Agent Platform, which provided the foundational platform, and combined it with Gemini's advanced natural language capabilities.
a similar process would have taken up to four hours
the team used Agent Search to point the model towards verified internal data sources
using Gemini Enterprise to build an AI-driven orchestration layer that sits across siloed systems and surfaces answers in real time.
Transparency Evidence & methodology 75/100 reference value · 77% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value75/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence77%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Google Cloud

    Arrive customer story

    First-party
    https://cloud.google.com/customers/arrive-ai
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • Sitemap last modified Jun 26, 2026 · Google Cloud · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
  • Unverified extracted date Jun 26, 2026 · Google Cloud · Unknown Legacy extracted date without source-page confirmation.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.

Related

Similar use cases

See all like this