Case studies.

Client names are withheld as policy. These examples cover working systems, supporting builds and architecture.

Seven systems, and what each one does.

The scope of each piece of work is described below.

01One view of clients, delivery and cash02Daily cash visibility alongside the accounts03Client answers with sources and access controls04Invoice preparation with human approval05A shared AI architecture for seven departments06AI systems inside our own business07A Dubai property market intelligence terminal

One view of clients, delivery and cash

In production

The problem

Client delivery, financial information and account ownership were spread across tools and spreadsheets. Leadership had to reconcile them to understand one account.

The work

We connected the client book, delivery information and financial sources in a shared data layer with consistent definitions and freshness checks.

Where it stands

Leadership can move from the full client book to one account using shared definitions. The client-answer assistant remains in controlled rollout, with source and access checks.

Read the case study

Daily cash visibility alongside the accounts

In production

The problem

Owners needed current cash visibility without waiting for every bank item to reach the monthly accounts.

The work

We connected bank feeds to show cash, money in and out, and runway, with the freshness of the source data visible.

Where it stands

Owners can check cash between accounting closes. The accounting platform remains the source of the official P&L after the bookkeeper closes the month.

Read the case study

Client answers with sources and access controls

Controlled rollout

The problem

People had to search conversations and documents to answer client questions, while keeping each client’s information within the right team.

The work

We connected company conversations to shared knowledge while retaining their original sources and timestamps.

Where it stands

The assistant brings answers and supporting sources together. Access and source checks remain part of the controlled rollout; the person using an answer can inspect the evidence.

Read the case study

Invoice preparation with human approval

Supporting build

The problem

A senior construction operator was constrained by manual invoice processing and a rigid, locked legacy system that could not be ripped out or replaced.

The work

The batch workflow reads and stamps invoices, matches them by exact contract key, and prepares a controlled import file for the existing database.

Where it stands

The workflow stops on ambiguity. The operator retains the final database import, attachment and approval.

Read the case study

A shared AI architecture for seven departments

Architecture designed

The problem

Seven distinct operational departments (Finance, Stock, Imports, Transport, Factory Operations, HR, and Customer Service) were preparing to independently procure and build siloed AI solutions.

The work

We designed a shared layer for the group, identifying which knowledge, connections and access rules the departments could reuse.

Where it stands

The group has a shared architecture and proposed rollout sequence to guide implementation.

Read the case study

AI systems inside our own business

Internal production

The problem

Systems need to work through ordinary operating problems: missing context, interrupted jobs, unclear ownership and mistakes that need review.

The work

We use specialist agents, shared knowledge, persistent queues and human review in our own operation.

Where it stands

Live internal use exposes failures and informs improvements. Those lessons support client work, but do not replace testing inside the client’s systems.

Read the case study

A Dubai property market intelligence terminal

Venture build

The problem

High-value, unstructured property data often sits dormant rather than being leveraged for strategic market advantage or productization.

The work

We connected Dubai property data to a market terminal for area and developer analysis, transaction exploration and reporting.

Where it stands

This active data and reporting engine now powers advanced developer analytics, transaction exploration, and automated market reporting, establishing the foundation for a consumer product in development.

Read the case study

Want to also become AI-native?

You have just seen what one shared layer changes. A 30-minute call tells you what it would look like in your company, and whether it’s worth paying us to build it. If it isn’t, I’ll say so.

Book a 30-minute call

About TwoHundred.ai

TwoHundred.ai helps established businesses adopt and implement AI that moves the P&L. It is run by people who have run businesses, and its engineers work inside your organisation to build, test and run AI with your team. See our case studies or book a 30-minute call.