How Washington D.C. Built a Digital Government: One Platform at a Time — Part 1: From Fragmentation to Flow
Explore the series:
Part 2: Marketplace for Inspections
Part 3: Real-Time Permits and Inspections
Part 4: Building Government Services People Can Actually Use
On a construction site in Washington D.C., delays don’t just slow progress. They cost money. When inspections are postponed or approvals are stuck in review, projects can lose over $100,000 per day. For developers, contractors, and city officials alike, these inefficiencies were not abstract problems, but daily realities.
For a contractor on-site, this didn’t just mean delays, but it meant idle crews, rescheduled work, and mounting financial pressure.
Inside the Department of Buildings (DOB), teams were working hard to keep up with growing demand. But the systems they relied on were fragmented. Inspection scheduling required manual coordination. Certificate of Occupancy reviews were handled through disconnected workflows. Documentation was stored in static PDFs that were difficult to search, maintain, or access. Each process functioned in isolation, with limited transparency and no shared infrastructure.
This fragmentation didn’t just create delays, but it made it nearly impossible to scale.
By 2021, Washington D.C. was experiencing a construction boom, but its operational systems were struggling to support it.
Inspection scheduling alone could take up to four weeks, largely due to manual coordination, lack of a centralized database, and limited visibility into inspector availability. At the same time, Certificate of Occupancy applications were taking an average of 47 days to process, slowed down by paper-based workflows, fragmented communication, and a lack of real-time tracking across departments.
Documentation added another layer of complexity. Critical information was locked in PDFs that were not accessible, not searchable, and not compliant with accessibility standards. This made it difficult for both internal teams and external users to find the information they needed, while also creating maintenance challenges.
Individually, these issues were manageable. Together, they formed a system that could not keep pace with the city’s needs.
Rather than attempting a large-scale system replacement, DOB and platformOS adopted a more incremental strategy.
The goal was not to rebuild everything at once, but to identify the highest-impact bottlenecks and address them step by step, while building on a shared technological foundation.
As part of a four-year transformation journey (from 2021 to 2024), this approach allowed each new solution to build on the lessons, infrastructure, and capabilities of the previous one. What began as a single initiative evolved into a broader ecosystem of interconnected platforms, each addressing a specific workflow but contributing to a larger system.
Most importantly, this wasn’t a typical vendor-controlled model. Unlike SaaS or traditional ‘monolithic’ systems, the platformOS approach gave DOB (and their local system integrator) full, direct access to the application code and underlying data. This meant they weren’t dependent on a vendor’s roadmap or release cycles.
They could build, adapt, and extend the system at the speed of a new idea—whether introducing new workflows, refining existing ones, or layering in AI capabilities where they added real value.
In practice, this turned the platform into something fundamentally different: not just a system they use, but a system they can shape. A foundation for continuous innovation: without lock-in, and without limits imposed by an external software provider.
The first focus area was third-party inspections, one of the most visible and costly bottlenecks in the system. Contractors struggled to find available inspectors, coordination relied heavily on phone calls and emails, and there was no transparency into pricing, availability, or performance.
To address this, DOB partnered with platformOS to build Tertius, a digital marketplace for building inspections. The platform connected contractors with certified inspectors in a single, centralized system, allowing users to browse availability, book inspections instantly, and manage communication and payments in one place.
The impact was immediate. Inspection wait times dropped from four weeks to two days, representing a 93% improvement in scheduling speed. At the same time, the platform increased inspection volume by 67% and introduced full transparency into the process.
Beyond operational efficiency, Tertius demonstrated something bigger: a marketplace model – combined with a flexible platform architecture – can fundamentally reshape how government services are delivered.
With the success of Tertius, DOB expanded its focus to Certificate of Occupancy reviews: a more complex and multi-layered process involving multiple stakeholders and departments. The challenge here was not only coordination, but also the cognitive load. Reviewers had to process large volumes of information, manage communication manually, and navigate fragmented workflows.
Building on the same platform foundation, DOB introduced Certifi, a centralized system enhanced with AI-powered features. These features included automated summaries of applications, suggested next steps, and streamlined communication workflows.
The results were significant. Review times decreased from 47 days to just 7 days (which means an 85% improvement) while maintaining oversight and quality. AI did not replace human decision-making but enhanced it, reducing administrative burden and enabling faster, more consistent outcomes.
This marked a shift from simple digitization to intelligent process optimization.
The next step in the transformation was Wallcheck, a platform designed to manage foundation wall inspections. While similar in nature to earlier challenges, this process benefited from everything that had already been built.
Because Tertius and Certifi shared the same underlying architecture, Wallcheck could be developed and deployed faster: with built-in capabilities such as automated scheduling, real-time tracking, and predictive analytics. These features reduced scheduling delays by 53% and introduced greater accountability across stakeholders.
This phase demonstrated the compounding value of a platform-based approach: Each new solution required less effort to build and delivered faster results.
Over four years, what began as a series of targeted improvements evolved into a fully integrated digital ecosystem. Tertius, Certifi, and Wallcheck now operate as interconnected platforms, sharing data, infrastructure, and design principles.
Together, they support more than 70,000 transactions, generate millions in revenue, and improve efficiency across multiple workflows. More importantly, they create a consistent, transparent experience for both government teams and external stakeholders.
The transformation also extended beyond core workflows. By replacing PDF-based documentation with accessible, HTML-based systems, DOB improved usability, ensured WCAG compliance, and reduced content update times by 90%.
What once operated as disconnected processes is now a cohesive system, designed to evolve.
The Washington D.C. case highlights a fundamental shift in how digital transformation can be approached in the public sector. Rather than relying on large, disruptive overhauls, agencies can achieve meaningful progress through incremental, platform-based development.
By focusing on real user needs, measuring impact, and building on shared infrastructure, organizations can create systems that are not only more efficient but also more adaptable. This approach enables continuous improvement, allowing new capabilities (such as AI-driven features or enhanced analytics) to be introduced over time without requiring complete redesigns.
Just as importantly, this model changes how governments work with technology.
With a platform like platformOS, agencies are not locked into a vendor’s roadmap or dependent on external release cycles. They have full access to the application code and underlying data, and can work with their own local system integrators (or internal teams) to design, build, and evolve solutions at the speed of new ideas.
This stands in contrast to many traditional enterprise systems, where innovation is often constrained by vendor control and predefined product boundaries.
In this context, platformOS functions not just as a technology provider, but as an enabler of long-term transformation: supporting government teams in building scalable, interconnected services they can continuously shape, extend, and improve.
And importantly, this model is not unique to Washington D.C.: it offers a blueprint for other agencies facing similar challenges.
This transformation began with inspections, where the impact was immediate and measurable.
In the next article, we’ll explore that first breakthrough in more detail:
👉 How a marketplace model transformed building inspections—and unlocked speed, transparency, and economic impact
Ensure your project’s success with the power of platformOS.
