Google Cloud Commercial and Professional Services Toronto, Ontario, Canada

SearchKings

Sales Automation

SearchKings had a small team supporting thousands of advertising customers and needed a way to automate repetitive campaign-analysis work without losing the personalized service that differentiates the agency.

Cut manual search term review time from 30 to five minutes with Gemini
We have a little over 100 employees but thousands of customers.
we need to run tens of thousands of performance reports every day

Reported impact

Business outcome

SearchKings cut negative-keyword review time from 30 minutes to five, automated campaign-analysis work at scale, and kept personalized service intact for thousands of customers with a team of just over 100 employees.

  • Customer Experience
  • Productivity Improvement
  • Revenue Growth
  • Scalability

Solution

SearchKings built its internal operating system, Ease, on Google Cloud so account managers could move from manual campaign maintenance to faster, AI-assisted decision-making. The company initially used Google Kubernetes Engine for flexibility, then shifted more of the platform to Cloud Run and Cloud SQL so a lean development team could take advantage of serverless simplicity, autoscaling, and faster deployment. Gemini 3.1 Flash and Gemini 3.1 Pro power tools such as Negative Keyword Suggestion, which ingests campaign context like geography and customer vertical, recommends which search terms to exclude, and keeps a human reviewer in the loop before changes are applied. Around that core, Google Workspace and Firebase support collaboration and earlier product development, while Gemini CLI helps developers in daily work. This architecture lets SearchKings run tens of thousands of reports every day and serve thousands of customers with just over 100 employees.

Data flow

Campaign and performance data enters the Ease platform, where Cloud Run-hosted services and a Cloud SQL-backed data layer feed Gemini models that analyze context such as geography and customer vertical, generate keyword and workflow recommendations, and return suggestions that account managers approve before acting on them.

Solution architecture

8 components · 3 layers
  1. Compute
    • Google Kubernetes Engine (GKE) Provided the original flexible environment for building SearchKings' AI platform.
    • Cloud Run Runs the production application in a serverless model that reduces maintenance overhead.
    • Gemini 3.1 Flash Handles faster recommendation and analysis tasks within the campaign-optimization workflow.
    • Gemini 3.1 Pro Handles deeper recommendation and analysis tasks within Ease.
    • Gemini CLI Helps developers work faster inside the Google-based development environment.
  2. Storage
    • Cloud SQL Supports the structured data layer behind Ease.
  3. Serving
    • Google Workspace Supports internal collaboration across the agency's Google-based operations.
    • Firebase Supported early platform development and introduced the team to the broader Google ecosystem.

Architecture clues

  • Ease combines CRM, campaign management, performance monitoring, and financial operations in one system.
  • Gemini suggestions are reviewed by humans before being accepted or rejected.
  • SearchKings migrated from a more GKE-heavy setup toward Cloud Run and Cloud SQL for simplicity and autoscaling.
  • The company is extending the platform toward customer-facing agentic AI experiences.

Evidence from the source

Cloud Run was a perfect fit for us because it abstracted away a lot of the maintenance.
Cut manual search term review time from 30 to five minutes with Gemini
The team reviews those suggestions and either approves or rejects them, keeping a human in the loop but reducing time spent to an average of five minutes.
We have a little over 100 employees but thousands of customers.
We use Google Cloud solutions. We use Workspace. Our developers use Gemini CLI.
Transparency Evidence & methodology 90/100 reference value · 79% 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 value90/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 impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • 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 specificity10/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

    SearchKings customer story

    First-party
    https://cloud.google.com/customers/searchkings
    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

  • First archived Jun 10, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Jul 30, 2026 · Google Cloud · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.