Application portfolio · Deployment Strategist · HappyRobot

How I'd work as a Deployment Strategist at HappyRobot.

A deployment works when the strategist and the engineer own one outcome together.

I've been the strategist next to an engineer, and the builder next to domain experts.
This page shows how I'd bring that to an FDE partnership, from the first discovery call to the next deployment.

01 · Why HappyRobot, and why now01 / 08

Continuous intelligence, with a human touch.

The line in the manifesto that stayed with me was "a negotiation worker that has mastered the psychology of your suppliers." It stayed with me because I already augment my own work with AI: it takes in more data than I can, and it keeps learning. I want to bring that same productivity and impact to customers. Machines handle the 99%, and people decide on execution.

The timing matters too. HappyRobot's Series C names telecommunications as an expansion sector, alongside insurance, energy and utilities, and airlines. It funds enterprise integrations, infrastructure to deploy agents at scale, and growth in engineering, deployment and go-to-market teams.[1]

Each round has been roughly three times the last
HappyRobot funding by round, US$ millions
View data
RoundDateUS$ MLead
Series ADec 202415.6a16z
Series BSep 202544Base10 Partners
Series CAug 2026150Prysm Capital, co-led by Eurazeo
Sources: Fortune, Staffing Industry Analysts, Pulse 2.0 [2][3][4]
70+ → 150+
enterprise customers, Sep 2025 to Aug 2026 [5][6]
5×
business growth since the Series B, per the company [6]
4–12 weeks
typical time for initial agents to go live [1]

02 · Past partnerships02 / 08

Two wins, and what I changed after each.

Depth · one engineer

Cricket World Cup solution

A customer engineer and I took on four large clients at once. I designed a tiering strategy and SLA to capture the full revenue, brought sales, policy, legal and GTM along, and built alongside my engineer so all four went live on time and stayed supported through deployment.

$4M
incremental revenue within the tournament
Breadth · many countries

Global FMCG client

The account was worth almost $60M across the region, over 20 projects, and my markets were almost 30% of it. I stepped in to scope work in another country. I delivered, but it was my first time across multiple countries, and I didn't have the full context. The next time, stepping in for an Engagement Manager two levels above my role, I planned with regional teams from the start and built a learning framework.

~$60M
regional account, 20+ projects
~30%
of it from my markets
Cricket World CupGlobal FMCG client
The gap I sawIt wasn't built in modules, so it couldn't travel to other countries and industriesI scoped without the full context of the regional landscape
What I changedDesign for reuse from day one; bring GTM in earlyPlan with regional teams first; learn the environment and our own goals before scoping
Where it shows up hereThe Debrief step: capture what worked so the next deployment starts further aheadThe account prep in section 04: my learning framework, applied

I act on feedback continuously, implement changes quickly, and tie each one to impact.

03 · Partnering with an FDE03 / 08

A strong partnership, built to deliver shared impact.

The Deployment Strategist job description asks for discovery, scoping, prototyping, program management and a product feedback loop. The Forward Deployed Engineer postings ask for building, integrating, tuning prompts, voices and transcribers, and improving from customer feedback.[7][8] So I'd split the lead by stage, and share the result.

I lead the ends of a deployment; the FDE leads the middle; we scope together
Who leads each stage of a deployment, with the other partner's role
Deployment Strategist leadsFDE leadsShared

Clearing the way

  • Customer updates handled before they reach the build
  • Escalations and scope changes managed up front
  • Customer context shared, so nothing is rediscovered

Building side by side

  • Prototypes shaped with the FDE from the first sketch
  • Test cases from real calls, shared before the build starts
  • Their code stays theirs; I help where they ask

Staying in sync

  • A weekly 30-minute check-in on one shared page
  • A quick debrief together after every customer session
  • One scorecard we own and review together

04 · A worked example04 / 08

A first telecom customer, served from Madrid.

I picked a hypothetical Spanish telecom operator, an unnamed archetype with several million mobile and fibre subscribers across more than one brand. Three reasons:

Four operators hold 98% of Spain's mobile lines
Share of mobile lines by operator, July 2026, %
View data
OperatorShare, %
MasOrange40.60
Movistar26.13
Vodafone18.72
Digi12.71
Other virtual operators1.84
Source: CNMC data via Mobile World Live [13]. A small buyer pool means one reference customer matters a lot.
Nearly half a million numbers changed operator in one month
Net mobile number portability by operator, July 2026, lines (491,629 ports in total)
Net gainNet loss
View data
OperatorNet lines
Digi+44,206
Movistar+19,414
Vodafone−2,296
Other virtual operators−4,583
MasOrange−56,741
Source: CNMC data via Mobile World Live [13]. Every support call is also a retention moment.

The five D's for one account, tied to HappyRobot's own work

A scoped pilot line can go live in about three months, in line with HappyRobot's benchmarks
Planned weeks per stage, with the lead partner and a quality gate at the end of each stage
Deployment Strategist leadsFDE leadsShared◆ Gate
Week numbers are my hypotheses. Benchmarks: initial agents typically live in 4–12 weeks [1]; Naturgy took 3 months from proof of concept to production [9]. Starting now, only a narrow first line, such as the after-hours outage line, could be live by 28 December 2026: the deadline is a reason to start, not the finish line.
StageWhat we doTied toGate
DiscoverExecutive and operations sessions; call reasons by volume; systems inventory; Ley 10/2025 gap checkNaturgy reviewed about 30 vendors, so expect a bake-off [9]Sponsor agrees on use case 1 and how we'll measure it
DesignImpact vs effort; ROI model; human handoff policy; prototype on a mock of their systemsNaturgy's proof of concept ran on a mock environment [9]Customer commits to production
DevelopIntegrations; prompt, voice and transcriber tuning; tests on router serials and customer IDsEncompass fixed model-number capture with validation layers [14]Acceptance tests and compliance sign-off
DeliverAfter-hours outage line, then a share of daytime calls, then one full brandEncompass piloted one brand, then expanded [14]Two stable weeks at full volume
DebriefValue review; use case 2 (technician scheduling); notes the next team can reuseThe telecom page lists field-crew scheduling as a use case [15]Use case 2 signed

The full account prep, with the regulatory, market and competitor context, is in my learning framework, applied to a telecom client.

05 · Measuring it05 / 08

One north star, owned by both of us.

North star: verified value from AI workers running in production, per account. A demo shipped doesn't count.

StageLeadKPIs
DiscoverStrategistQualified use cases per account; % with a sponsor and a measured baseline
DesignSharedDays from discovery to first demo; % of prototypes that become a commitment
DevelopFDEMilestones on time; test-set task success
DeliverFDEResolution without a human; escalation reasons; calls answered within 3 minutes
DebriefStrategistRealized ÷ projected value; days to use case 2 signed; % of the build reused next time
GuardrailsSharedAccounts per FDE; time to resolve a customer escalation; drift caught before the customer sees it

Three headline metrics for the telecom account

Legal
95%+
calls answered within 3 minutes, every hour of the week. Baseline found in discovery.
Cost
Set in pilot
in-scope calls resolved without a human. Encompass reports 60–70% on its scope [14].
Churn
Agreed after baseline
connectivity faults fixed or correctly booked on the first call.

All targets are hypotheses to calibrate with the customer.

06 · My first 30 days06 / 08

Learn the business. Shadow. Earn trust.

I onboard the way I'd deploy: agree on a baseline, act, then measure before moving on.

Monday check-inAgree the one or two highest-impact goals for the week and write down the baseline.
→
ActLearn, shadow, build or propose, depending on the week.
→
Friday measureImpact made, coverage gained, and whether to move on or go deeper.
Week 1
Learn the business, the platform and the people
  • Case studies, pricing models, how a deal reaches deployment
  • Build a first agent workflow on the platform
  • Coffee with someone in every function: "What could I take off your plate?"
  • Rebuild one deployment's economics from scratch, then compare
Week 2
Shadow live deployments
  • Shadow two FDE–strategist pairs at different stages
  • Ask each FDE how they like to work
  • Listen to 50+ real calls and tag why each escalated, checked by an FDE
  • Spend time with the customer's front-line agents
Week 3
Build alongside
  • Own one small, real task through to measurement
  • Rebuild a published use case and run it through tests first
  • Draft a discovery guide and ask a strategist to mark it up
  • Celebrate a teammate's ship out loud, specifically
Week 4
Synthesize and give back
  • Put the telecom thinking in front of the team to be torn apart
  • Co-lead one discovery session
  • Hand over a "first 30 days" doc and the call-pattern library for the next hire
  • Offer an AI-literacy session for non-technical teammates
Coverage by day 30Target
Deployment stages observed5 of 5
Sectors seen live2 or more
Real calls heard and tagged (resolved, escalated, failed)50+
Functions met 1:1All six: FDE, strategist, sales, product, customer success, operations
Contribution shipped into a live deployment1

07 · How I put this together07 / 08

A structured approach to a deployment partnership.

Applied to HappyRobot and a hypothetical Spanish telecom operator, from public information only.

The process

Business mindset and planning

I started from the learning framework I built after my first multi-country engagement, across three areas:

  • Environment and competition
  • Joint value proposition
  • Stakeholders on both sides
Using my own learning framework

Research from primary sources

  • HappyRobot's case studies, job postings and Series C announcement
  • CNMC market data, Ley 10/2025 and the EU AI Act
  • Every figure checked against the page it came from
Using public sources only

AI as a working partner

I used AI agents to research, draft and stress-test each section, the same way I'd want customers to use HappyRobot: the agent takes in the data, and I make the calls.

Using AI research and drafting agents
Deliverables
Partnership modelWho leads each of the five stages, with the FDE, and the scorecard we share
Telecom account prep10-section analysis of the market, regulation, competitors and stakeholders
Deployment planFive stages over about three months, each tied to HappyRobot's own case studies
30-day onboardingWeekly check-in, act and measure, with coverage targets

08 · What else I bring08 / 08

Deployment, plus the business side.

Since Google, I’ve learned how companies enter markets, build partnerships and run day to day, from an MBA and from working inside my family’s company.

Deploying solutions

Scoped, built and scaled alongside customer engineers, owning up to 16 clients and $160M at once.

Google

Business foundations

Market entry and new business development, alongside a master’s in computer science.

IMBA + MS Computer Science, IE

Running the business

Hands-on work in HR and people operations, strategy, joint partnerships and sales.

Family company, during the MBA
How I’d hope to contribute
In every deploymentDoing the core job well, from discovery to production alongside an FDE, with some understanding of how a customer’s operations and people teams work day-to-day.
As the team growsI’d be glad to share what I’ve learned about market entry and partnerships, and from living in the United States, Singapore, Manila, and now Madrid.
As new sectors open upMy time in sales, partnerships, and people operations could help me work closely with the business teams through deployment and strategy.