Every value-creation engagement deploys against the same underlying toolkit. Built once, deployed many times, owned by us. The companies that build alongside OneX pull from this stack — and we tell them honestly when a piece doesn't exist yet.
A pure augmentation engagement may use only Kaizou and a TTF squad. A full transformation typically pulls DouJou + Kaizou + two or three providers.
Not roadmap items. Not vaporware. These are the platforms we deploy beneath every engagement — already in production across the portfolio.
A 5-layer AI infrastructure stack that deploys directly inside a customer's own cloud environment — AWS, Azure, or GCP. Customer data never leaves their infrastructure. The AI runs on the customer's compute, against the customer's identity provider, governed by the customer's policies. Architecturally compliant with Schrems II, NIS2, and the EU AI Act on day one.
The unified workspace for engineering, product, and design teams that we operate across every OneX engagement. Built on S+3 agile — structured planning gates, definition-of-ready checkpoints, acceptance criteria before any work begins. Cycles instead of endless backlogs. Real-time co-editing of specs and tickets. Contextual time tracking that surfaces where throughput actually leaks.
Each provider is a focused capability we've worked with, vetted, and deploy through. Where OneX carries volume discounts with providers, we pass them through to portfolio companies at cost.
Data scientists and AI engineers between France and India. Specialists in retrieval-augmented generation, cloud-to-AI migration, chatbot development, and production LLM integration. The team you deploy when DouJou needs to be customized for a specific portfolio company's data.
Performance tracking, predictive analytics, custom dashboards. The provider we deploy when a portfolio company needs to build the data infrastructure that makes its AI work — and the analytics layer that proves it.
Flexible staffing and engineering squads. Time-and-material engagement, rapid deployment, customized teams. When a portfolio company needs delivery capacity beyond what its current team can produce, TTF is the engine.
Comprehensive data cleaning, tagging, annotation, and AI model training. The provider that prepares raw portfolio-company data into the kind of dataset DouJou can actually train against. Retail, security, satellite imagery specialism.
Marketing content creation for portfolio companies that need to ship a brand alongside the product. Blog content, landing pages, sales collateral, lifecycle email — the GTM content layer that most operating funds outsource and most consultancies bill for.
Not every portfolio company's needs map cleanly onto this toolkit. When something is missing — a regional operator, a specialist regulatory advisor, a domain we don't have credible bench in — we say so. Then we either source it through the broader operator network, or tell you it's not the right engagement for us.
The honest answer is more useful than the polished one.
Willow.co uses DouJou (AI infrastructure inside Willow's cloud) and Kaizou (execution discipline for the engineering augmentation team). The expansion-sales motion is run inside Willow's existing coach network — no provider needed there.
Sarouty uses DouJou (AI-powered property search and recommendation), Kaizou (execution discipline for the rebuild), TTF (engineering squad for the platform build), and MyDataMachine (cleaning and structuring the legacy Sarouty data plus building the regional property datasets for Algeria, Tunisia, Mauritania).
Visible (Verizon) predated DouJou as a productized platform — but used the exact architectural pattern that DouJou is the codification of. The human-AI hybrid service architecture (US Patent 12,056,644 B2) is what DouJou now ships as infrastructure, available on day one.
Tools without operators are shelfware. The OneX engagement is the operators using the toolkit on a specific portfolio company's specific problem. If you have one of those — bring it.