Digital Workforce System

Case studies

A service business has a ceiling.
A platform does not.

One system we built and still operate, and five companies that were operating businesses first, encoded what they knew, and found out what happens to the ceiling.

Every figure on this page carries a source. Where a number could not be confirmed against a primary or major-trade source, it is not here.

Built by DWS

Twenty people. One business.
Three copies of everything.

A 20-person property brokerage. Four months from first commit. We built it, and we still operate it.

deals closed — 1.7× the leads multiplied by 5.3× the conversion rate

conversations handled per person, in the same working day

1,536

replies moved into the system in thirty days. Nobody was told to switch

15×

search impressions, from a website that had been a cost line

The problem was never capability. Twenty people who knew their market perfectly well were running it out of three separate copies of the same catalogue — 1,995 properties in a master spreadsheet, 1,352 on the website, the rest in somebody’s head. In the month we arrived, customers sent 1,677 messages into the business and the company had a record of zero replies: the team was answering from their own phones, because the software was worse than the phone already in their hand.

285 customers had been promised an answer and never got one — not because anyone forgot, but because only 39 of 3,706 listings had ever been confirmed. That is what scattered tools actually cost: not licence fees, but the standing tax of stopping work to go and ask someone.

What we built for them →

Studied by DWS

A cybersecurity company
proved the thesis on itself.

Proofpoint’s professional services team had the problem every services business has: consultants spending roughly twelve hours a week on work that wasn’t the work. Nine months from first commit to production.

18,300

hours saved annually, across the services team

40%

productivity gain on administrative tasks

30+

custom applications built — not one chatbot

9 mo

from starting the work to running it in production

They found the chat box wasn’t the answer. In their own words, they “quickly identified the limitations of solely having the chat functionality.” The value came from building thirty specific applications against thirty specific workflows — follow-up emails, health-check comparison, renewal justification, custom responses — each one aimed at a task somebody was already doing by hand.

Three things they concluded

On context

“AI is only as smart as we make it.”

Their words. The quality of the data fed in directly determined what came out — so the first phase was documentation, metadata and a vetting process, not a model.

On who does it

“AI thought leaders embedded within our services function.”

Not an external vendor and not a pure engineer. Someone who understands both the technology and the business process, sitting inside the operation.

On staying

“Customization and ongoing management are key.”

They name the time investment explicitly, and the need for dedicated people with expertise in AI, their business, and their processes. The build was the start, not the finish.

They also built a process to document tribal knowledge — the undocumented judgment that lived in people’s heads. That is the same entry point we most often start from, and the reason a services business can be systematised at all.

This is the job, described by somebody else →

Source: Stephen Coverdale and Alessandra Filice (Proofpoint) with Abhishek Maligehalli Shivalingaiah and Ram Krishnan (AWS), “Unlocking the future of professional services: How Proofpoint uses Amazon Q Business”, AWS Machine Learning Blog, 3 September 2025. Figures are Proofpoint’s own, self-reported.

Studied by DWS

Five that made
the transition.

Operating knowledge, encoded. Ordered by how closely each matches the pattern: an internal system, used in production, that outsiders asked for. We did not build these — they are the evidence the road exists.

Acquired 2025

Highwire

Started inside Harvard University. Built to assess contractor risk and cut insurance costs. Contractors asked for it themselves. Spun out in 2008; now covers 60,000+ contractors, acquired by Veriforce.

~$2B valuation

CompanyCam

Started inside White Castle Roofing, Nebraska. Needed job-site photo software, could not find any, hired a local studio to build it.

Opened 2026

Side

Started inside real-estate brokerage operations. Ran its own back office for years, refined the platform in production across 600+ companies, then opened it to the industry.

Series A

Soraban

Started inside an AI-first accounting firm. Built to run their own client intake, then sold to the firms doing the same work.

IPO 2024

ServiceTitan

Started with two contractors’ sons. Built for their parents’ businesses first. Labelled honestly: this one is not an internal-tool spinout in the strict sense.

The pattern

What they share

None set out to build software. Each had an operating problem, solved it for themselves, and then found other businesses asking for the solution.

Two of the five are not internal-tool spinouts and are labelled as such. Mixing borrowed credibility into your own proof is how a case-study page stops being believed.

Why the ceiling moves

The work is the same.
What you can charge for it is not.

A service business sells hours, and hours are finite. It grows by adding people, which adds cost at nearly the same rate it adds revenue. That is a real ceiling, not a failure of ambition.

Service businessPlatform
Revenue scales with headcount
Revenue scales with customers
Each new customer needs more people
The next customer costs a fraction of the last
Margin is capped by what people cost
Margin improves as you add customers
The knowledge lives in those people
The knowledge is encoded and stays
The asset walks out at 6pm
The asset is on the balance sheet
The catch is that getting from one to the other is a different kind of engineering — and it is the part these companies had to do before any of the numbers happened.
How that transition works →

Let’s talk about your business

Ready to stop adding AI
and start building?

No commitment. No pressure. A free twenty-minute conversation where I look honestly at your operation and tell you exactly where AI fits — and where it doesn’t.

  • An honest read on where AI fits your specific operation
  • Which systems make sense to build first
  • A realistic picture of what’s possible — no hype, no generic advice
  • Insights that are yours to keep, whether we work together or not

Or reach out directly: imtiazh@digitalworkforcesystem.com WhatsApp

Chat with Imtiaz Imtiaz Hasan