The first one is open
We do not have a customer case study yet, and we are not going to manufacture one. DTCD is released and pre-revenue: the first contractor to run it on a live project gets to decide whether their story is told at all.
Plenty of early-stage software fills this space with a composite customer, an unnamed “regional contractor,” or a quote nobody said. We would rather show you an empty page and the exact structure the first real one will follow — so when it appears, you can tell it is real.
What a DTCD case study will contain
Named, or anonymous if that is what the contractor prefers. Nothing gets published without written permission, and permission can be withdrawn.
Type of work, duration, and the traffic-control complexity — lane closures, flagging, mobile operations, night work.
How the daily diary was actually handled: who wrote it, when, from what, and what it cost in supervisor time.
What changed in the field workflow, and what did not. Including the parts that did not fit.
Time saved, records produced, quantities tracked, disputes avoided or resolved — measured, not estimated, and only what the contractor can stand behind.
In the contractor's words, approved by the contractor, including any caveats they want in it.
What we will not do
- Publish a composite or fictional customer
- Use a logo without written permission
- Quote someone from a conversation they thought was private
- Report a metric we cannot show the working for
- Require case-study participation as a condition of a pilot or a founding rate
Meanwhile, here is what we can show you
Real output instead of testimonials: the sample closure diary and sample invoice DTCD generates, the live work-zone feeds running right now, the 50-state requirement research, and the 105-matter litigation review with its sources and limitations published.
Be the first one
Run DTCD on one project for two weeks. If it earns a case study, we will ask. If it does not, we want to hear that even more.