The story begins in 1977, before insurance software had become an obvious category and before the market had settled on the systems that would define the decades ahead.

CDL’s founding moment should be told with intimacy: the people first, then the problem. The company emerges as a practical response to a changing industry, built around the belief that technology could make complex insurance work more precise, repeatable, and scalable.

The manuscript should supply the exact founding detail and attribution. In the book rhythm, this spread should stay quiet: one portrait-led image, a few lines of context, and enough margin to let the year land.

By 1982, the founding energy of the company can be shown as a more disciplined operating pattern. The book should treat this as a craft moment: people learning how to deliver specialist systems reliably, repeatedly, and close to the working detail of insurance.

This spread is a place for small evidence rather than grand claims. Archive documents, installation notes, annotated forms, or team photographs can show the practical habits that made later platform work possible.

The page rhythm should stay quiet: one strong archive image, a narrow prose column, and a few exact labels.

The 1989 spread brings character into the technical timeline. Telebroking gives the period its strategic weight; Fozzy gives it a memorable handle.

This is a useful page for balancing the book’s quiet editorial tone with the specificity of company language. The spread should explain what the system made possible, but it should also preserve the texture of the name, the screens, and the era.

The layout can split between a dense archive column and a large technical placeholder, with the timeline rule continuing through the gutter.

By 1998, the book can begin to show the pull of the web era. The important story is not simply that the internet arrived; it is that customer expectations, distribution models, and access to information were changing.

For CDL, this period should read as preparation. The platform years that follow make more sense when the reader has seen the late-1990s pressure building.

By 2009, the book can make platform resilience visible. The story should not become technical for its own sake; it should show why continuity matters in insurance operations and why the system behind the screen is part of the customer promise.

This is a quiet spread about strength: infrastructure, routines, and the ability to keep changing without losing control.

The story of 2011 can be told through data discipline. Insurance systems depend on the right information being available, structured, governed, and passed through the right workflows.

This spread should make invisible work visible: models, notes, rules, and operational clarity.

The 2015 spread can show automation before it becomes a headline. The important ingredients are already familiar: rules, workflow, data quality, and the ability to control complex operational processes.

This is a useful page for joining older product discipline to newer automation language.

In 2017, the company’s fiftieth year is still a decade away, but the story begins to take on a different shape. The book can use this moment to pivot from archive to continuity.

The spread should ask what the past is preparing the company to do next.

The 2026 spread is the final approach. It can show the act of preparing the anniversary itself: choosing what to remember, deciding what to explain, and bringing people, systems, and places into one narrative.

This is a reflective page, but it should still carry forward motion.