How we work
CX Foundry is Principal-led, evidence-first, time-boxed, and fixed-fee. It is designed to get you from real customer conversations to proven OpenAI agents you can take live or translate to another platform.
The full CX Foundry method is public. The commercial engagement is how you get it delivered by a CX Foundry Principal with their judgment, expertise, and AI tools that ensure you get the outcome you want, with the accountability you need. Fast.
The path
Snapshot: find the real opportunity. One to two weeks. We analyze a representative sample of your calls, chats, or transcripts, identify repeated workflows, size the opportunity, and build a working voice AI prototype for the strongest candidate.
Stage 1: prove the agent works. Six weeks. We turn two to three priority workflows into working agent assets, backend tools, test data, simulation runs, and an evidence-based value model.
Stage 2: secure the launch path. Eight weeks. We take the strongest one or two workflows through broader simulation, adversarial testing, policy review, and risk analysis. We deliver a reusable evaluation harness and a small runtime package that can be used to host your agent using OpenAI voice or chat models on AWS, Azure, or GCP.
Run it yourself or translate to a SaaS platform: Take the proven agent, backend tool layer, runtime components, and evaluation harness into your own environment with your team or partner of choice, or use the CX Foundry outputs to configure the same workflow on Parloa, Gemini Enterprise for CX, your existing CCaaS, or another specialist vendor.
CX Foundry itself does not include last-mile telephony routing, production backend integration, live operations, or managed service support. It gives you the evidence, assets, and test harness to deploy and prove those things with confidence, on your own, with another partner, or with Waterfield Tech.
Your role
The work moves quickly because we keep the team small and the inputs clear. Success demands:
- A named business sponsor with budget authority
- A representative sample of customer conversations
- Access to operations, technical, data, security, and compliance stakeholders at the points where their judgment matters
- SOPs, policies, scripts, escalation rules, API documents, schemas, sample payloads, and test data
- Fast decisions when the evidence says a workflow should be narrowed, stopped, or taken forward
Payment model
Our invoicing and payment model is different from a traditional project because the delivery model is different. We reserve a named Principal for a defined slot, use the CX Foundry method and tooling to compress the work, and keep the commercial backstop simple.
Delivery slots can be reserved with a 50% deposit. The remaining 50% is invoiced on stage acceptance. If you don’t accept the stage after a structured review process, the balance is not invoiced; ownership and use rights do not transfer, and the engagement closes for that stage.
Why it works
The model removes the coordination overhead of endless scheduling and rescheduling, scoping and re-scoping. You and your Principal share the same incentive: turn the available evidence into useful work and clear decisions.