Content engineering across three markets — technical publishing, content technology, and intelligent content — for federal agencies, Fortune 500 manufacturers, life sciences companies, financial institutions, and defense contractors.
Five phases. Same shape on every engagement. The tone here is definitional — what each phase is in our practice, not what activities happen during it.
We don't move past Discovery until the constraints that would otherwise sink a content model have surfaced. That includes interviewing the people who will produce, edit, and consume the content, auditing what exists today, and mapping the use cases the system has to support. The goal isn't to gather requirements; it's to find the constraints the architecture has to obey.
The architecture is the leverage point. Schema design, taxonomy, metadata strategy, and reuse decisions made here determine what's possible in every downstream phase. We design against the use cases Discovery surfaced, not against generic structured-content principles. The architecture has to work for this client's content, not for a textbook example of DITA.
Migration is recovery, not transcription. The conversion engine identifies reusable assets in legacy content and lifts them into the target schema; what isn't recoverable gets retired or rewritten with intent. We design the QA harness before the first batch runs — failing migrations fail because the validation strategy was an afterthought.
Implementation makes the architecture operational across the toolchain — CCMS configuration, publishing pipelines, integration points. The discipline at this phase is to resist scope expansion: every feature added during implementation is a feature the team has to maintain afterward. We deliver the smallest implementation that runs.
Enablement runs through every phase, not at the end. Discovery teaches the practitioner how the program works. Architecture documentation becomes the team's runbook. Migration training transitions authors. CCMS rollout becomes the operating manual. The handover isn't a phase — it's a discipline applied throughout.
Principles in practice
The work ships in two-week increments, not six-month black boxes. Each sprint produces output the team can review — schema fragments, converted samples, plugin builds. Progress is visible from Sprint 1; scope adjustments happen mid-engagement, not at the end.
A fifty-page conversion pilot before the fifty-thousand-page batch. A PDF spread before the branded plugin. The discipline is to invalidate the architecture before scaling production against it — proof before investment.
Training isn't a Phase 5 deliverable; it begins in Phase 1 and runs alongside every sprint. Discovery interviews are themselves teaching moments. Architecture documentation becomes the team's runbook. The handover is a continuous discipline, not a single event.
Extense is a small firm of practitioners who have shipped structured-content systems for federal agencies, Fortune 500 manufacturers, life sciences companies, financial institutions, and defense contractors. We don't feature individual team members on this site — the work is the work, and clients evaluate firms by what those firms have shipped, not by team-page photography. The composition we describe below is what's behind every engagement.
From a two-person consulting practice in Maryland to a full-stack content engineering firm. The arc of the practice, year by year.
Incorporated in 2012 as an XML and publishing consulting firm in Maryland, focused on structured content for technical documentation.
Awarded the firm's first government contract — DITA engineering and publishing-automation services to a major federal agency. The engagement established the model for downstream federal work.
Expanded the technical team and service offerings to support Fortune 500 enterprise clients in regulated industries, alongside continued federal civilian agency engagements.
Added full CCMS implementation, integration, and ongoing support to the service line. The expansion was driven by client demand for production-grade content operations on platforms like IXIASOFT and Heretto.
Grew the commercial practice to serve Fortune 500 clients in automotive, financial services, and life sciences — industries where documentation operates as a regulatory artifact, not a marketing one.
Launched the AI-ready content practice — metadata enrichment, section-aware chunking, controlled vocabulary, and JSONL export for RAG pipelines — alongside containerized DITA-OT publishing with Docker and CI/CD.
Today, Extense delivers end-to-end content operations — strategy and IA through DITA engineering, CCMS, AI-ready output, and automated multi-channel publishing — across government, commercial, and non-profit sectors.
Procurement-ready vendor details. Useful for contracting officers, vendor onboarding teams, and BD prospects researching the firm.
Company details
NAICS codes
Submit a 20-page sample. We'll return conversion feasibility, content recovery rate, and engineering effort within two business days. The analysis is the basis for any further engagement, with no obligation to proceed.
Submit a sample →