Early Era (Pre-Cloud) · Custom CRM · Foundational Search Intelligence
At the time of engagement, this professional services firm operated in a high-value, relationship-driven business environment — one where information, timing, and communication directly impacted revenue. This is the story of how a fragmented technology stack became a unified, intelligent operating system long before anyone called it “AI.”
At the time of engagement, the firm operated in a high-value, relationship-driven business environment — where information, timing, and communication directly impacted revenue. Every client relationship, every piece of research, every internal handoff carried real financial weight.
However, the underlying technology infrastructure had not evolved with the business. Key systems — including CRM, communications, and research tools — were:
Disconnected across departments, with no shared source of truth between teams.
Dependent on manual processes to move information from one system to the next.
Limited in their ability to surface relevant information quickly, when it mattered most.
As the organization scaled, these limitations became more pronounced. Teams were spending increasing amounts of time searching for information, reconstructing past interactions, and manually coordinating across systems that were never designed to talk to one another.
Rather than incrementally improving existing tools, the approach focused on rethinking the system as a whole. A fully integrated platform was designed and implemented to unify:
Customer relationship management, unified across the entire client lifecycle.
Internal and external communications, connected rather than siloed.
Research, data access, and operational workflows across every business unit.
At the core of this system was a custom-built CRM platform, developed using ColdFusion on a Java-based architecture, designed specifically around how the firm operated — not around a generic vendor template.
But the critical innovation was the introduction of intelligent search and classification. Using early implementations of technologies such as Apache Lucene — combined with emerging machine learning concepts — the system enabled:
This transformed how information was accessed and used across the organization.
Once implemented, the system fundamentally changed how the firm operated. Instead of relying on individual memory, manual tracking, and disconnected data sources, teams could now:
The organization moved from searching for information to working with it in context.
While the impact was not measured in a single KPI, the transformation delivered clear operational advantages:
Significant improvements in information retrieval speed across every department.
Reduced dependency on manual coordination and individual memory.
Increased efficiency in business development and client engagement.
Greater alignment across teams through shared system visibility.
The system became a central operational asset — supporting both execution and strategy, not just record-keeping.
Although developed well before modern AI frameworks, this system represented an early form of what is now recognized as intelligent automation. It introduced key elements of what I now define as Iterative Intelligence — systems that improve their usefulness through interaction and data over time.
The platform continuously indexed new data, improved the relevance of search results, and refined how information was connected and surfaced. This created a feedback loop:
More usage → Better indexing → More relevant results → Increased reliance on the system
At the time, these capabilities were not described as “AI.” But functionally, the system was already classifying information, identifying patterns, and improving retrieval based on usage.
In today’s terms, this would be recognized as:
Contextual retrieval built from usage patterns, not static keyword matching.
Workflows shaped by how the business actually moved, not by rigid process maps.
Classification and relevance scoring that anticipated what modern ML platforms formalized.
What required custom architecture and emerging technologies at the time can now be implemented more efficiently using modern tools. However, the principle remains the same: intelligence doesn’t come from the tools — it comes from how systems are designed.
This work directly informs my current approach — where systems are designed not just to store data, but to:
Before AI was a category, the system was already learning — surfacing insight from data most teams didn’t even know how to use.
This case study is one thread in a larger pattern: organizations that treat information as a static archive fall behind organizations that treat it as a living, improving asset. That pattern is the foundation of Iterative Intelligence (IteraOS) — the operating system approach for building intelligent business platforms from the ground up.
For firms carrying legacy CRM, communications, and research tools that no longer match the pace of the business, the path forward isn’t another point solution. It’s a technology strategy engagement that maps the current system, identifies where intelligence is missing, and architects the unified platform to replace it.
“Intelligence doesn’t come from the tools — it comes from how systems are designed.”
That single principle carried this firm from a fragmented, manual-heavy infrastructure to a unified platform where information worked for the business instead of against it. It is the same principle applied to every architecture PSM Design designs today.
Specific company details have been generalized to maintain confidentiality. This case study reflects real-world system design and operational outcomes, drawn from a genuine engagement with a professional services firm operating in a relationship-driven, high-stakes business environment.
The architecture, technologies, and outcomes described are accurate representations of the work performed — the firm’s name and identifying specifics have simply been withheld out of respect for the client relationship.
This engagement is one example within a broader body of work applying human-guided AI and automation strategy to organizations building intelligent business operating systems. Explore more of that work:
Real engagements, generalized for confidentiality, showing the pattern in practice.
Browse Case StudiesLong-form thinking on architecture, automation, and Iterative Intelligence.
Read the ArticlesWritten by Shaun McNicholas, principal architect and strategist at PSM Design.
ConnectLegacy infrastructure buries information. Iterative Intelligence surfaces it — continuously, contextually, and at the exact moment your team needs it.