Tango × Thoughtworks · Agentic Reinvention

The Destination

The Agentic Organization.

Becoming agentic is not a technology project. It is a category of company. The destination that gives every modernization decision a purpose.

Stage 01

AI Tourists

Enterprise ChatGPT accounts. Copilot licenses. No systems, no governance, no outcome model.

→

You are here

Stage 02

Agent Builders

Scattered agents, no control plane. The messy middle. Most organizations are stuck here, trying to contain agents instead of harnessing them.

→

Destination

Stage 03

Agentic Native

Agents writing, testing, releasing. Anthropic-class operating model. End-to-end observability, governance, and economics by design.

Three foundations beneath every agent - what Segment 1 proves.

Data readiness

Lineage, quality, and access controls across Core, WatchWire, AgileQuest, and Locatee, so agents can synthesize the data that is Tango's moat.

Agent economics

Token cost is a P&L line item. FinOps, model routing, and cost per outcome, so every agent's margin is known before it scales.

Governance posture

Control plane before agent sprawl. Policy, audit, and human oversight by design, and ASC 842 / IFRS 16 / SOC 2 by default.

The Approach

Three principles govern this engagement.

These are not values on a wall. They shape every commercial, architectural, and team decision in the work that follows.

Build to prove, not advise to plan

Every segment produces functional, demonstrable output against Tango's actual data, constraints, and customer requirements. Strategy is validated through delivery, not presentations.

Tango's reinvention, co-developed

This is Tango's product transformation. Thoughtworks brings agentic platform expertise and production-grade governance to accelerate ADP and agent portfolio development. Tango owns the product vision, the shared data foundation, and the organizational change required to sustain the platform independently.

Capability transfer by design

Thoughtworks builds alongside Tango's founding team from day one. Product, engineering, platform, data. When we leave, your team owns the platform, the operating model, and every artifact.

Workshop signal · April 21 · Dallas

The Roof Reduction Agent surfaced as a high-value candidate alongside Lease Renewal. Final selection lands via the Segment 1 scorecard, with your team, not ours.

Discovery & Validation

Desirability is proven before commitment scales.

Every agent is prototyped, evaluated against synthetic data, and validated with design partners, before any production build commits.

Agent prioritization scorecard

Tango's portfolio is sequenced through a structured scorecard refined in Segment 1. Workshop signal: the Roof Reduction Agent surfaced as a high-value candidate alongside Lease Renewal, final selection lands as the scorecard matures.

Rapid prototyping via AI/works

The first agent gets built as a working prototype on AI/works in Segment 1: core workflow logic, constraint enforcement, escalation triggers. Independent of ADP infrastructure, against synthetic data, in days not weeks.

Customer desirability signal

The prototype goes in front of design-partner contacts to evaluate desirability and inform design and sequencing of the initial agent portfolio. Customer reaction shapes the roadmap, not just the agent.

Validate, then iterate

Segment 2 takes the proven concept into a closed beta on real customer data with 2–3 design partners. Capture feedback, measure outcomes against success criteria, iterate. Production scale only follows validated value.

Objective

Validate ADP target-state architecture, define integration strategy with Track 1's shared foundation, and prototype the first agent (Lease Renewal Agent, or the scorecard's selection in Segment 1) against synthetic data with design-partner feedback. Deliver ELT-ready implementation plan within 30 days. Tango Track 1 owns the shared data foundation; TW provides architectural advisory on the integration/abstraction layer that connects the ADP to Track 1 infrastructure.

Focus

ADP-focused domain immersion & Track 1 integration review

Immerse in ADP-relevant domains: agent-consumable data surfaces, integration points, API contracts across Track 1 middleware
Review Track 1 middleware API progress and data integration readiness as inputs to ADP architecture decisions
Onboard Tango co-development team and establish joint working practices
Establish Track 1 coordination cadence with Hope / Empire leads

Focus

Define ADP architecture & Track 1 integration strategy

AI platform target-state: orchestration, agent framework, control plane, governance, observability, CI/CD, security/compliance
Architectural advisory on Track 1 integration/abstraction layer (Tango Track 1 owns build; TW ensures agent-consumable design)
Refine agent prioritization scorecard; validate first-agent candidate
Synthetic data strategy for agent evaluation

Focus

First-agent prototype & synthetic data evaluation

Generate synthetic data from domain schemas and business rules
Build first-agent prototype on AI/works, independent of ADP infrastructure
Evaluate vs success criteria; capture design-partner desirability signal
Inform portfolio sequencing

Focus

Implementation plan & design-partner strategy

ELT-ready implementation plan: phased budget, hiring plan, agent portfolio roadmap aligned to release cadence
Design-partner selection criteria & shortlist (3–5 customers)
Track 2 co-development integration plan
AI-First PDLC advisory: quality gates, evaluation-driven development, governance patterns (Tango-led)

Outcomes · Segment 1

An evidence-based foundation for reinvention: ADP architecture, integration strategy, implementation plan, and a working first-agent prototype.

ADP target-state architecture blueprint

Integration/abstraction layer advisory spec

First-agent prototype + evaluation

Agent portfolio roadmap & scorecard

ELT-ready plan (30-day)

Design-partner shortlist

Track 2 co-development integration plan

Seg 2 execution plan

Gate · M1

ELT approval of blueprints, plan, prototype + measurable Segment 2 outcome criteria.

Approval gates initiation of Segment 2 investment. 30-day deliverable from engagement start.

First-agent candidate: Lease Renewal Agent or Roof Reduction Agent (workshop signal). Selection finalized via the agent prioritization scorecard during Segment 1.

Objective

Co-develop the ADP platform slice and control plane. Rebuild the first agent on the ADP and advance it through MVP to production with customer-facing validation via design partners in closed beta. Prototype and advance the second agent to MVP. Track 1 middleware integration is built ADP-side against Tango's middleware APIs.

Focus

ADP platform build & control plane

AI platform build: orchestration, agent framework, CI/CD, security/compliance
Control plane: fleet-wide observability, policy enforcement, cost controls, evaluation, audit trail
ADP-side integration against Track 1 middleware APIs and data integration endpoints
TW acceleration tooling for tactical microservice development on ADP components

Focus

First agent to production & customer validation

Rebuild first agent on ADP from Seg 1 prototype: production-grade workflow logic, Track 1 data integration
Deploy to design-partner environments via Track 1 shared foundation
Closed beta on real customer data with human oversight; iterate to production-grade deployment
Capture outcomes against success criteria for the September board proof point

Focus

Second agent prototype & MVP

Build second agent on ADP: workflow logic, constraint enforcement, escalation triggers
Generate synthetic data for second-agent domain; evaluate against success criteria
Advance second agent to MVP with design-partner feedback

Focus

Design-partner onboarding & engineering practices

Onboard 2–3 design partners; connect data through Track 1 shared foundation
Support Tango-led AI-First PDLC implementation: AIFSD SME advisory through Week 12
Support Tango-led design-partner program coordination and closed beta execution

Outcomes · Segment 2

First agent in production on real customer data, second agent at MVP, ADP slice and control plane operational, 2–3 design partners in closed beta.

Functional ADP platform slice

Control plane operational

First agent in production with design partners

Second agent at MVP

2–3 design partners in closed beta

AI-First PDLC patterns embedded

Board-ready proof point

Seg 3 scale-up plan

Gate · M2

First agent in production demonstrated to Tango ELT and design partners. Second agent MVP reviewed.

Approval of scale-up plan, with elaborated Segment 3 outcome criteria, gates Segment 3 investment.

Objective

Harden ADP and control plane to production scale. Advance agents 2–3 to production, develop agents 4–5 (Workplace Intelligence, Space Optimization/Maintenance, Site Selection) through development and validation to production readiness, and establish a sustainable agent release cadence as a proven Tango-owned capability. Expand design-partner program to 3–5 customers and embed organizational capability for Tango independence. Support Tango-led ≥$1M net new bookings target within FY'26.

Focus

Platform hardening at production scale

Harden ADP for scaled multi-agent production: performance, scalability, multi-tenancy
Harden control plane for fleet-wide operations: security audit, compliance, scale observability
Optimize ADP-to-Track 1 integration layer for production throughput

Focus

Agents 2–3 to production, agents 4–5 to readiness

Advance second agent from MVP to production deployment
Develop agents 3–5: workflow logic, constraint enforcement, synthetic evaluation
Deploy agents 2–3 sequentially to production; advance agents 4–5 through development and validation to production readiness
Each successive agent compounds: reusable framework, proven integration templates, established evaluation infrastructure

Focus

Design-partner expansion & GTM

Expand design-partner program to 3–5 customers
Outcomes-led sales playbook, competitive positioning, pricing
Thought leadership and analyst briefings
Value proof via won new bookings within FY'26

Focus

Capability transfer & org enablement

PM practices, engineering restructuring, cross-functional patterns
Progressive ownership transfer; Tango leads sprints by end
Phase 2 recommendations

Outcomes · Segment 3

A production-grade agentic platform, 3 agents in production, agents 4–5 at production readiness, Tango-led, design-partner-validated.

Production-grade ADP and control plane

3 agents in production with design partners

Agents 4–5 at production readiness

Agent release cadence transferred to Tango

3–5 design partners active

GTM enablement playbook

Won bookings within FY'26

Tango platform team operating independently

Gate · M3

Tango ELT evaluates production platform, full agent portfolio, design-partner results.

Decision: transition to fully independent operations (deploying agents 4–5 to production internally), or extend into Phase 2 for production deployment of agents 4–5, portfolio expansion beyond the initial 5, and scaled customer migration.

Status

Phase 2 is not part of this engagement.

It is an optional path forward Tango ELT can choose at the M3 gate. Scope, duration, and commercial structure are defined jointly at that point, grounded in Segment 3 outcomes.

If elected

What it could cover

Harden initial 5-agent portfolio in production
Develop additional agents beyond the initial portfolio
Scale customer migration toward GA

How it's shaped

Defined at the M3 gate

Scope & duration set based on Segment 3 evidence
Design-partner outcomes inform agent priorities
Tango's hiring trajectory determines co-build balance
Commercial structure negotiated separately

Commercial Vehicle

A commercial model built for the work itself, not the work as imagined.

Fixed-fee for outcomes. Gated segment commitments. Each milestone gate is both an acceptance checkpoint and a scope elaboration point, so commercial specificity scales with what we actually learn.

Gated

Three segments. Each segment requires the prior gate's outcomes to be approved before investment commits.

Fixed-fee for outcomes

Not time and materials. Each segment is priced against defined outcomes and measurable success criteria.

Progressive elaboration

Segment 1 outcomes are fully defined at start. Segment 2 and 3 outcomes are baselined as a deliverable of the preceding segment.

M1 in 30 days

An ELT-ready implementation plan within 30 days of engagement start. Architecture, plan, first-agent prototype results.

Outcomes that matter to Tango

This is not a services proposal. It is a reinvention bet.

Every segment is measured against the outcomes Tango's own ELT proposal laid out: reposition the market narrative, unlock the acquisition moat, and get ahead of the AI-native upstarts before they expand beyond their initial niches.

Reposition the market narrative

From "legacy IWMS" to "AI-first workplace platform." Re-open deals Tango is currently losing to AI-native entrants like VergeSense, Density, and Facilio. Win the category-shift buyers like Apple and NVIDIA.

Protect the $70M base

The shared foundation layer lets existing customers benefit from AI capabilities without a forced platform migration. Continuity for today's customers while the new platform matures.

Unlock the acquisition moat

WatchWire, AgileQuest, and Locatee finally compound instead of fragmenting. Lease + occupancy + energy data, in one agent, is what no point-solution can match.

Hedge the investment

Shared foundation delivers value even if agentic adoption takes longer than planned. The data work is load-bearing either way, agents are the upside, not the whole bet.

The Portfolio Tango Identified

Five candidate agents.

The agent concepts Tango identified, the portfolio we'd prioritize, sequence, and prototype together in Segment 1. Click any to read its description.

Outcome Arc

Credibility in 6. Validation in 12. Scale in 24.

Tango's own outcome arc, broader than the 30-week engagement window. The TW engagement closes around month 7 with a production-grade platform and 3 agents in production; month 12 and beyond is Tango executing on what we built.

6 mo

Establish credibility and speed

ADP slice operational. First agent in production with design partners on real customer data. Second agent at MVP. 2–3 design partners in closed beta. Market signal that Tango is no longer a legacy player.

12 mo

Validate and demonstrate

3 agents in production, agents 4–5 at production readiness, 3–5 design partners active. Tango platform team operating independently on proven patterns. Project Hope and Project Empire substantially complete. Market narrative shifted.

24 mo

Scale and differentiate

New AI platform generally available with full initial portfolio. Customers migrating through the shared foundation. New acquisition driven by AI value proposition. Competitive losses declining.

~17 months post-engagement · Tango-led

What You'll Own

Every artifact compounds. Every artifact is Tango's.

Each segment leaves Tango with a concrete asset, not a deliverables binder. Thoughtworks retains rights to its own platforms; everything produced for Tango belongs to Tango.

Segment 1 · 4 weeks

An evidence-based foundation

ADP target-state architecture blueprint
Integration/abstraction layer advisory spec for Track 1 consumption
First-agent prototype evaluated on synthetic data with design-partner desirability signal
First-agent requirements with implementation plan and success criteria
Agent prioritization scorecard and portfolio development roadmap
ELT-ready implementation plan (30-day deliverable) including ADP development roadmap and agent portfolio sequencing
Design-partner selection criteria & shortlist
Track 2 co-development integration plan
Segment 2 execution plan with measurable outcome definitions

Segment 2 · 12 weeks

A functional, end-to-end platform slice

Functional ADP platform slice (orchestration, agent framework, CI/CD, security/compliance)
Control plane configured and operational (governance, observability, cost controls)
First agent in production on real customer data with design partners
Second agent at MVP, evaluated against synthetic and early real data
2–3 design partners onboarded and in closed beta
Board-ready proof point via agent in production with customer feedback
AI-First PDLC patterns embedded in ADP workflows (Tango-led)
Segment 3 scale-up plan grounded in design-partner evidence

Segment 3 · 14 weeks

A production-grade agentic platform

Production-grade ADP (performance, scalability, multi-agent operational)
Production-grade control plane (security, compliance, fleet-wide governance)
3 agents in production with design partners
Agents 4–5 at production readiness
Agent release cadence proven and transferred to Tango
3–5 active design partners driving GTM signal and revenue
Market positioning and value proof assets (Tango-owned)
Value proof via Tango-won new bookings within FY'26
Tango platform team operating independently on proven patterns
Phase 2 recommendations: agents 4–5 production deployment, portfolio expansion beyond initial 5

Team Archetypes

A senior-weighted team, organized by capability, not headcount.

A lean, senior-weighted onshore team scaling from 3.45 to 7.45 FTE across 30 weeks. All Thoughtworks roles are US-based, co-developing with Tango's founding AI platform team from Day 1.

Strategic Leadership

Segments 1–3 · Onshore

Engagement vision, ELT alignment, implementation plan ownership, milestone readouts. Owns design-partner strategy and GTM enablement. Includes delivery transformation leadership for the AI-First operating model and waterfall-to-agile transition.

AI Platform Engineering

Segments 1–3 · Onshore + Offshore

ADP architecture, AI platform target-state design, agent architecture, agentic workflows, LLM integration, control plane configuration. Provides architectural advisory on Track 1 integration/abstraction layer (Tango owns the build). Co-develops with Tango engineers with progressive ownership transfer.

Data Foundation

Segments 1–3 · Onshore + Offshore

Cross-product data model, integration patterns, data readiness, governance, scalable foundations for agent context and reporting. Schema reconciliation across Core, WatchWire, AgileQuest, Locatee. Tapers as the foundation stabilizes.

Quality & Evaluation

Segments 2–3 · Offshore

Agent evaluation rigor: synthetic data validation, agent outcome measurement, evaluation harness ownership, design-partner beta measurement. Secondary coverage of traditional QA alongside Tango's QA function.

AI/works + Agent/works Specialists

Segments 1–3 · Onshore

Technical oversight of AI/works (reverse engineering, prototyping, forward engineering acceleration) and Agent/works (control plane reference architecture, observability, governance). Embedded across teams and workstreams.

Tango Co-Build Counterparts

Segments 1–3 · Tango-supplied

Product Owner, CRE Domain SME, Product Designer / UX Lead, QA Engineer, and 5–6 Platform Engineers. Co-development from day one ensures the platform is Tango's to operate, not just Tango's to receive.

On-Ramp Profile

A senior-heavy start. A delivery-heavy peak.

3.45

Seg 1 · Wks 1–4

→

7.45

Seg 2 · Wks 5–16

→

7.2

Seg 3 · Wks 17–30

Indicative FTE counts only. Composition flexes to the work as scope is elaborated at each gate. Tango co-development resources are sized separately and confirmed at engagement start.

Thoughtworks Tooling

Two proprietary platforms. Embedded in how we deliver.

AI/works accelerates how we deliver. Agent/works runs in your stack as the control plane for your agents, with favorable terms if Tango participates as a design partner.

Reverse engineering (CodeConcise) accelerates Segment 1 codebase and domain understanding, extracting structured specifications and knowledge graphs from Tango's existing estate to compress immersion timeline.
Rapid prototyping powers the Segment 1 first-agent prototype, enabling working agent evaluation against synthetic data, independent of ADP infrastructure.
Forward engineering (TWist) accelerates tactical microservice development on ADP platform components: orchestration services, agent framework modules, and CI/CD pipeline infrastructure.

AI/works is embedded in our delivery methodology. All outputs are Tango-owned.

A/w

Agent/works

Composable agent governance & control plane

Licensed as the control plane for Tango's ADP and agent portfolio. Production governance, observability, cost controls, evaluation, and audit trails. All running in Tango's stack from Day 1.
Favorable licensing terms if Tango elects to act as a design partner. The design-partner relationship gives Tango influence over the Agent/works roadmap and preferential commercial terms.
Integration architecture, configuration scope, and rollout plan are defined during Segment 1 and delivered at M1 as part of the implementation plan.

ASC 842

IFRS 16

SOC 2

Thoughtworks retains IP rights to both platforms. All engagement-produced artifacts and code are Tango-owned.

Governance & Risk

Lightweight cadence. Transparent escalation. Risks managed from Day 1.

Four governance tiers, calibrated by altitude. The top risks are named and mitigated in the contract, not buried in an appendix.

Level

Cadence

Participants

Purpose

Operational

Daily

Platform squad + TW team

Co-sourced collaboration, progress, blockers

Track 1 Coordination

Weekly

TW Team Leads + Hope/Empire leads

Shared dependency alignment, extraction progress, risk escalation

Steering

Bi-Weekly

Tango + TW leadership

Performance, RAIDs, ways-of-working, escalations

Executive

Monthly

Tango ELT + TW leadership

Milestone readouts, gate approvals, go-forward decisions

Top Risks 4 High, 3 Medium · named and mitigated +

High Impact

Track 1 middleware / Project Empire dependency

Mitigation

Stored procedure extraction is Tango-led (Project Empire). TW designs the ADP to consume Track 1 middleware APIs and extracted services, not raw ADF artifacts. Dependency tracked explicitly from Segment 1 via weekly Track 1 coordination; critical-path visibility surfaced at steering.

High Impact

Compressed timeline, 3 agents to production in 30 weeks

Mitigation

Senior-weighted onshore team and prototype acceleration compress Seg 1–2 delivery. Each successive agent reuses proven ADP framework, control plane, and evaluation infrastructure. Agents 4–5 advance to production readiness in Seg 3; production deployment defers to Phase 2 if Track 1 data domains or Tango co-development capacity constrain the cadence. Scope adjustable at each milestone gate.

High Impact

Track 1 integration readiness gates agent deployment

Mitigation

Track 1 middleware and data integration are already underway (first slice demoed). Weekly coordination cadence monitors API availability, data domain coverage, and interface contract stability. ADP designed to decouple from Track 1 delivery timeline where possible via synthetic data and interface abstraction.

High Impact

Tango co-development hiring timeline

Mitigation

4–6 Tango platform engineers are required from Seg 2 but many are not yet hired. Delayed hiring directly impacts Seg 2–3 delivery velocity. Mitigation: hiring plan confirmed and tracked as part of Seg 1 implementation plan; staffing progress reviewed at M1 gate; Seg 2 scope may be adjusted at M1 if co-development capacity falls materially below 4 FTE.

Medium Impact

Design-partner recruitment stalls

Mitigation

Selection criteria defined in Segment 1 with Tango sales leadership. Minimum viable design-partner profile established early. Fallback: agents proven on synthetic data with real-data validation deferred. Tango GTM and Design Partnership Lead drives recruitment from Seg 2.

Medium Impact

Agent 4–5 production readiness delayed

Mitigation

Production readiness for agents 4–5 depends on ADP framework maturity, Tango co-development capacity, and Track 1 data domain coverage. Each successive agent reuses proven patterns, reducing marginal cost. If Track 1 data domains are not ready by mid-Seg 3, development can proceed against synthetic data with production deployment deferred to Phase 2.

Medium Impact

LLM cost and availability at production scale

Mitigation

Multi-agent portfolio at production scale across heterogeneous CRE domains drives meaningful LLM inference costs. Control plane cost controls and observability provide fleet-wide cost management. Model governance architecture (defined in Seg 1) supports provider flexibility and fallback strategies.

Critical Dependencies

What Tango supplies. What we track from Day 1.

Six items sit on the critical path. Each is named, owned, and surfaced at the right governance tier, so a dependency slip becomes a steering conversation, not a Segment 3 surprise.

Project Empire extraction progress

Stored-procedure extraction directly gates shared foundation integration timeline. Weekly Track 1 cadence established in Segment 1 to maintain critical-path visibility.

Design-partner legal agreements

Customer availability and legal/data-sharing agreements must be in place before the closed beta in Segment 2.

Data infrastructure readiness

Data warehouse maturity (Redshift consolidation) and API availability assessed in Segment 1. Material gaps may require scope adjustment at M1.

Tango co-development capacity

Delivering 3 agents to production and agents 4–5 to production readiness requires sustained Tango co-development capacity (4–6 engineers exclusively deployed to Track 2) across multiple concurrent workstreams. Shortfall may defer agents 4–5 into Phase 2.

Track 1 data domain coverage for agent portfolio

Agents 3–5 (Workplace Intelligence, Space Optimization/Maintenance, Site Selection) need data domains beyond lease data: occupancy, energy, maintenance, facilities. Track 1 data foundation must extend to these by mid-Segment 3. Coverage gaps may re-sequence agents within the release cadence.

ELT gate decision cadence

Milestone gate decisions must land within one week of readout to maintain engagement momentum and team continuity. Built into the executive cadence.

Prerequisites

Three things we assume in place by engagement start.

Tango authorizes formation of the dedicated AI platform team (founding group + product lead) concurrent with or prior to Segment 1 kickoff
Project Hope and Project Empire continue in parallel under Tango ownership

Timely access to all product codebases, data stores, infrastructure, and documentation across Core, WatchWire, AgileQuest, Locatee, and E&S
Required AI/ML tooling, cloud infrastructure, and sandbox environments procured and available by Segment 2 build initiation

Design-partner customers are identified and willing to participate within Segment 2 timeline; Tango sales leadership drives recruitment with TW advisory support
All engagement artifacts owned by Tango; TW retains rights to pre-existing IP (AI/works reference architecture, Agent/works source code, methodologies)

Next Steps

Three steps from this site to a signed engagement.

A simple sequence. No surprises. Commercial and legal start in parallel only after we are aligned on the work itself.

Tango reviews this site (before our session)

Walk the narrative and the prototype with the team you'd want in tomorrow's alignment conversation. Capture questions and pushback so we can address them live.

Alignment conversation, Wednesday April 29, 2:00–2:30 PM ET

Already on the calendar. A working session to mutually align on the engagement approach: principles, segment shape, gate criteria, co-build model, and the agent portfolio shortlist. The goal is a shared point of view, not a sales meeting.

Kickoff commercial & legal in parallel

Once aligned on approach, we run pricing and contracting tracks in parallel, so M0 kickoff is days away, not months.

Once we kickoff, you have an ELT-ready implementation plan within 30 days, before any Segment 2 commitment is made. That is the smallest, fastest unit of evidence we can offer.

This site is for Tango leadership review.

Agentic Reinvention.

This is not Thoughtworks' point of view. It is the consensus.

The Agentic Organization.

Three principles govern this engagement.

Desirability is proven before commitment scales.

From kickoff to production-grade in 30 weeks.

A commercial model built for the work itself, not the work as imagined.

This is how Segment 1 actually works.

This is not a services proposal. It is a reinvention bet.

Every artifact compounds. Every artifact is Tango's.

A senior-weighted team, organized by capability, not headcount.

Two proprietary platforms. Embedded in how we deliver.

Lightweight cadence. Transparent escalation. Risks managed from Day 1.

What Tango supplies. What we track from Day 1.

Three steps from this site to a signed engagement.