geoSurge <> Google Cloud commercial record

One year-plus of goodwill, restarts, handoffs, and no executable partnership.

This page compiles the email and meeting history behind geoSurge's response to Google Cloud's latest offer. It shows a long-running attempt to make GCP work, and why geoSurge is now engaging consultants to plan a migration path away from GCP.

15+ moCommercial discussions since March / April 2025.
8+Google stakeholders involved across handoffs and restarts.
£30-45kMonthly GCP spend discussed in 2026, with growth expected.
$150kFinal credits proposed against a $500k one-year commitment.

Negotiation Position

The issue is both commercial and operational: the proposed economics are weak, and the process has reduced confidence that Google can execute as a strategic partner.

geoSurge engaged in good faith. The company repeatedly gave Google strategic context, product demos, usage details, fundraising context, AI workload detail, and executive time.

Google repeatedly restarted discovery. Each stakeholder transition created another round of context-setting rather than producing a concrete, executable commercial package.

The latest offer is not strategic. A $500k one-year commitment with $150k credits released only after 25% and 75% spend milestones is not front-loaded support and is materially inferior to AWS.

geoSurge is now preparing migration options. The current path is to engage consultants to plan a move away from GCP unless Google materially changes the economics and operating cadence immediately.

Google offer $500k one-year commitment; $150k credits in two $75k tranches after spend milestones; additional requests for AWS billing data.
Google process Multiple owners, handoffs, repeated requests, role changes, slow internal approval paths, and recurring re-explanation of the same business context.
AWS position Commercially and operationally stronger, with a clearer path to support migration and reduce near-term cloud burn.
geoSurge response Proceed with migration planning unless Google returns with a materially better, front-loaded, executive-backed package.

Interactive Timeline

Filter by stakeholder to see how ownership shifted and how geoSurge repeatedly responded to changes by re-explaining context, providing more data, and keeping Google in the process.

Mar / Apr 2025
EmailOpening

Commercial discussions begin with Google Cloud.

geoSurge starts discussions with James Massey around GCP support and the AI-first startup program. The early conversation frames Google as a potential strategic infrastructure partner, not just another cloud vendor.

Evidence details
Email threads show discussion around a $350k credit path, follow-ups, forms, and escalation. This was the first point where Google had the opportunity to convert interest into an executable partnership.
24 Apr 2025
MeetingCredits

Google discusses $350k credits and custom partnership potential.

On a recorded call, James explains a request for $250k in year one and $100k in year two, with potential to build something custom if usage requires more support.

Evidence details
The call included discussion of Vertex, Gemini, Claude and DeepSeek through Vertex, GPU limitations, and larger strategic structures. geoSurge raised the possibility of a much larger multi-year commitment if Google could support front-loaded growth.
May / Jun 2025
DelayFollow-up

Momentum stalls after the initial credit and custom-deal conversations.

geoSurge follows up repeatedly after the initial engagement. The expected next steps, including senior introductions and clearer commercial terms, do not materialize quickly.

Stakeholder impact
From geoSurge's perspective, the company had already invested executive time and shared enough context for Google to act. Instead, the process drifted and created the first loss of confidence.
16-23 Jun 2025
HandoffRestart

James changes roles; Mike Adebiyi is introduced.

Google explains that there have been changes, and Mike is brought into the relationship. The practical effect is a reset: geoSurge has to re-explain the commercial context and urgency.

Evidence details
In the June 23 meeting, Mike says James moved into a different role and that he is taking over. geoSurge states that Google has dropped the ball and that infrastructure decisions have been held while waiting for Google.
23 Jun 2025
MeetingRe-discovery

geoSurge re-explains the opportunity and the lost time.

Mike asks to hear the story directly. geoSurge explains that it has already been waiting around three months, that decisions are being delayed, and that Google has moved backwards into discovery instead of forwards into execution.

Evidence details
geoSurge describes a VC-backed company, one of the largest rounds in Europe, looking for a meaningful custom proposal with front-loaded support. Mike says he can create a proposal and send it that evening.
26 Jun 2025
In-personStrategic pitch

geoSurge presents the product, AI workload, and why Google should win.

In person, geoSurge demos its GEO product, explains million-query scale, data value, model workload, and why Google's stack is strategically attractive. The ask is clear: shared risk, front-loaded compute support, GTM help, and partnership.

Stakeholder impact
Google acknowledges the desire to build a real partnership and says the team needs to digest. geoSurge again responds constructively to Google's process by providing more detail and strategic framing.
11 Jul 2025
Senior meetingStrategic review

Senior Google stakeholders are brought in.

James Rosenthal, Emily Ford, Mike Adebiyi, Fabian Desnoes and others join a broader conversation. geoSurge again explains the company, funding, product, strategic dataset, compute needs, token needs, and why Google is well placed to support the business.

Evidence details
James Rosenthal introduces his role across global partnerships and strategic companies. Google discusses possible internal demand, licensing, corp dev, equity investment, GTM, and pulling in the right teams. geoSurge sends the fundraising deck afterward.
14 Jul 2025
DebriefNon-standard deal

Google acknowledges the deal would need senior approval.

Mike explains that a two-year free compute structure is unlikely, that only a small number of startups would receive this kind of long-term deal, and that VP-level approval may be required.

Stakeholder impact
The conversation shifts from strategic intent to internal approval complexity. geoSurge attempts to make the structure workable by discussing rolling credit batches, calibration, open caps, and long-term commitment.
Jul / Aug 2025
Technical supportQuota

GPU quota and capacity discussions move in parallel.

geoSurge raises quota and GPU requirements for its project. Fabian clarifies that quota does not guarantee capacity and asks about reservations, Dynamic Workload Scheduler, and related options.

Stakeholder impact
This reinforces that geoSurge's need was practical and immediate, not theoretical. The company needed a cloud partner able to make compute access and commercial support executable.
Mar / Apr 2026
Re-engagementSpend clarity

geoSurge re-engages after moving more usage onto Vertex AI.

After adopting Vertex AI based on Google's recommendation, geoSurge has a clearer GCP spend profile and asks to reopen the commercial discussion. Monthly spend is now described as roughly £30k-£45k and growing.

Evidence details
This removes one of Google's earlier objections: unclear spend. geoSurge comes back with actual GCP usage and renewed willingness to make Google work.
1 May 2026
MeetingAnother reset

Gabby Rothman-Shaw joins; geoSurge explains the full history again.

Gabby is introduced as an Account Director focused on hyperscale startups. geoSurge explains the love/hate history with Google, the prior promises, role changes, AWS support, current Vertex migration, and the need for front-loaded value.

Stakeholder impact
Despite the increased spend clarity and repeated strategic context, Google still cannot provide a concrete ballpark on the call and asks for more information to take internally.
May / Jun 2026
Data requestAWS CUR

Google asks for AWS billing data in a specific format.

Mike requests AWS Cost and Usage Report data. geoSurge explains that extracting and packaging this is not a good use of the team's time. Mike initially says this is the only way he knows to proceed, then later sends CLI steps.

Evidence details
geoSurge replies that the discussion started a year earlier, that unclear spend was the old blocker, and that current GCP spend is now clear. The request for still more data becomes a symbol of process failure.
24 Jun 2026
OfferCurrent email

Google sends the current offer through Elliott.

The proposal is a $500k one-year commitment with $150k of GCP credits in two $75k installments, released after 25% and 75% spend milestones. Google again asks for AWS billing details.

Negotiation readout
After more than a year of goodwill, stakeholder time, product demos, technical context, and repeated re-engagement, this is not a strategic proposal. It is a weak transactional offer, inferior to AWS and insufficient to stop migration planning.

Stakeholder Map

The repeated stakeholder movement is central to the response: every handoff required geoSurge to restate context while Google delayed a concrete commercial answer.

JM

James Massey

Initial Google Cloud contact

Discussed AI-first credits, $350k support path, possible custom strategic structure, and senior introductions. Momentum slowed before a clear executable offer appeared.

MA

Mike Adebiyi

Took over after James changed roles

Restarted discovery, joined product and partnership meetings, discussed non-standard structures, later requested AWS CUR data and sent CLI steps.

JR

James Rosenthal

Senior strategic partnerships

Joined the July 2025 senior meeting, discussed potential strategic angles including internal Google teams, licensing, corp dev, and broader Alphabet access.

EF

Emily Ford

Senior Google participant

Joined strategic discussion where Google asked for the case behind deeper investment and explored whether geoSurge's product could matter to Google teams.

FD

Fabian Desnoes

Technical / quota support

Handled GPU quota and capacity questions, clarifying that quota and actual capacity were separate and that reservations or workload scheduling might be needed.

GR

Gabby Rothman-Shaw

Account Director, hyperscale startups

Joined the 2026 re-engagement, heard the full history, positioned Google as more strategic than AWS, but still required more internal review and data.

EM

Elliott / Amber

Latest commercial email

Sent the June 2026 proposal framing the relationship as strategic while offering economics that geoSurge considers weak and inferior to AWS.

Failure Patterns

These are the recurring themes that support a firm response and justify beginning migration planning.

Owner churnGoogle moved from James to Mike to senior stakeholders to Gabby to Elliott, with no single accountable owner carrying the deal through to execution.
Repeated discoverygeoSurge repeatedly re-explained the same company, workload, spend, funding, product, and urgency instead of moving toward a final offer.
Data escalationEven after GCP spend became clear, Google asked for AWS billing data in a specific CUR format, creating more operational burden for geoSurge.
Weak economicsThe final $150k credit offer on a $500k commitment is not front-loaded and does not match the strategic narrative Google repeatedly used.

Draft Reply

A direct email response that points to the timeline, states the loss of trust, and makes clear that migration planning is underway.

Hi Elliott,

Thank you for the note and for sharing the proposed structure.

I want to be very direct: this offer is not remotely competitive, and it does not reflect the history of our discussions with Google. After more than a year of engagement, a $500k one-year commitment with $150k of credits released only after spend milestones is materially inferior to what AWS is offering us. It also does not solve the problem we have been explaining to Google since the beginning.

I am sharing the attached timeline because I want the record to be clear. We have engaged with Google in good faith for a long time. I have repeatedly tried to keep GCP in the conversation internally, despite AWS being easier for us commercially and operationally. But the process with Google has been fragmented, slow, and increasingly difficult to trust.

Since March / April 2025, we have gone from James Massey to Mike Adebiyi, then to James Rosenthal, Emily Ford and Fabian Desnoes, then to Gabby Rothman-Shaw, and now to you and Amber. Each transition has required us to restate the same context: who we are, why our workload matters, why Google is strategically well placed to support us, what we are spending, what we expect to spend, and why we need front-loaded support rather than a transactional vendor relationship.

We have had calls, product demos, senior meetings, quota discussions, fundraising context, Vertex AI migration discussions, and repeated requests for additional data. We moved more usage through Vertex AI, gave Google a clearer view of our current GCP spend, explained our expected growth, and continued to make the case internally for Google.

The result, after all of that, is still a weak transactional proposal and another request for AWS billing detail.

At this point, the problem is no longer just commercial. We have lost confidence in Google's ability to execute as a partner. The stakeholder changes, shifting priorities, repeated re-discovery, and continuing requests for more information have made it very hard to trust that Google can move at the pace we need.

We are now engaging consultants to help us plan a migration away from GCP. That is not the outcome I wanted. I have spent significant internal political capital trying to make Google work. But based on the process so far and the offer now on the table, I cannot credibly recommend Google as the right infrastructure partner for geoSurge.

AWS is offering us a materially better path, both commercially and operationally. Google's current offer is not in the same category.

If Google wants to remain in the conversation, the offer needs to change materially and immediately. It needs to reflect the strategic nature of the opportunity, the time we have already invested, our current and expected scale of spend, and the fact that AWS is actively giving us a stronger reason to migrate.

Otherwise, I think we should stop spending cycles here.

Best,
Francisco