NoA Ignite

Consultant profiles — OnePagers — are a critical sales asset at an enterprise consulting firm. They need to be current, credible, and tailored to each bid or client conversation. At NoA Ignite, they were built in PowerPoint.

Every update required someone to open a file, find the right version, reformat content by hand, and export again. At scale, that process became a compounding liability: outdated information, inconsistent output, and hours of work that produced nothing transferable.

The brief was to replace that with something structured — a single place where consultant data lives, and a system that handles the rest.

Operational impact

Enterprise consulting teams typically spend 3–4 hours producing a single consultant profile for a bid. At NoA Ignite — a firm of 450+ consultants — that cost compounds with every tender cycle.

NoA Ignite operates with 450+ consultants across its network. These figures reflect the structural difference between document-based and data-based production — the time recovery scales directly with bid frequency and team size. At this scale, even a single tender cycle represents a significant operational cost without a system in place.

The solution treated Sanity CMS not as a content store, but as a generation engine. Consultant data — skills, experience records, education, credentials — was structured into a schema with explicit relationships between entities. Custom input components were built directly inside the Studio, designed for the workflows staff actually used.

The interface understood the data model: selecting a consultant pulled their experience records dynamically; selecting a layout variant adjusted which sections and emphasis levels surfaced in the output. Nothing required a formatting decision at export time.

Export logic was developed using React-PDF for document generation and PptxGenJS for PowerPoint output. Both drew from the same underlying data model. A change to a consultant’s profile propagated to all output formats without manual intervention.

Sanity’s native version history and timestamp controls meant the organization gained a full audit trail without any additional tooling — a critical requirement for tender processes where document integrity matters.

The system was deployed to the sales team, replacing the manual PowerPoint workflow. The structural efficiency gain was immediate — a process that took hours produced output in minutes.

The deeper outcome was structural: the organization moved from document management to data management. Consultant profiles became living records, not static files. Adding a new project, updating a skill, or correcting a credential updated every downstream output automatically. Version history was maintained by default. No file could become stale without someone actively choosing not to update the source.

The PowerPoint problem also went away — not by abandoning the format, but by removing the human formatting step entirely. The generated output was structurally consistent, brand-aligned, and produced in seconds. It looked better than the manually-built version because it was constrained by a system, not by individual effort.

This work demonstrated that Sanity’s architecture, used deliberately, can serve as the foundation for operational tooling — not just marketing websites. The same pattern — structured schema, relational content model, on-demand generation — applies anywhere a team produces repeated, high-stakes documents from shared data.