// expertise & offering
Our expertise
Architecture, industrialisation and operational continuity.
Our expertise was built in large-scale document transformation contexts. This requirement for rigour remains our foundation, we now apply it to entire enterprise software ecosystems.
FIG.E0 · SCROLL FAST: THE TITLE LEANS WITH YOUR VELOCITY
// 01 · domains
Our areas of expertise
D1
Architecture of complex systems
- Urbanisation and structuring of application ecosystems
- Definition of target architectures and transformation trajectories
- Multi-system integration and interoperability
- Scalability, resilience and observability
- Audit and rationalisation of existing platforms
D2
Document environments
- Migration and modernisation of CCM platforms
- Orchestration of high-volume document flows
- Conversion and normalisation of electronic formats
- Multichannel distribution and accessibility
- Regulatory compliance and traceability
D3
Business applications
- Digitalisation of complex processes
- Advanced role and workflow management
- API integration and flow orchestration
- Document generation from business data
- Progressive, scalable deployment
D4
Operations and continuity
- Controlled deployment
- Monitoring and observability
- Corrective and evolutionary maintenance
- Security and continuous updates
- Support for internal teams
// 02 · our approach
Whatever the scope, a structured approach
STEP 01
Analyse
Mapping the existing system: inventory of systems and flows, survey of technical constraints and dependencies.
STEP 02
Understand
Business perspective: challenges, priorities and breaking points that shape the target trajectory.
STEP 03
Design
Target architecture, structuring choices, transformation trajectory.
STEP 04
Industrialise
Integration, automation, environment hardening.
STEP 05
Operate
Go-live, monitoring, evolution over time.
// 03 · cross-functional capabilities
Cross-functional industrial capabilities
Some environments require additional layers to guarantee their robustness, compliance and long-term steering. Purplsoft designs and integrates these cross-functional capabilities, consistent with the chosen vendor solutions.
T1Document migration and transformation
Industrialisation of complex CCM migrations: analysis of legacy sources, normalisation to a canonical model, automated generation to target engines.
T2Traceability and regulatory persistence
Implementation of aggregation, normalisation and long-term retention of critical metadata. Ability to reconstruct a process years after its execution, independently of source systems.
T3Operational security of data flows
Integration of quality control, business validation and cross-functional monitoring mechanisms in sensitive document environments.
T4Steering of transformation programmes
Structuring of workloads, multi-year planning, governance and capacity control in multi-stakeholder contexts.
These capabilities can be integrated into existing platforms or activated as part of new structuring programmes.
// 04 · support
Strategic and operational support
Purplsoft ensures the full continuity of the lifecycle:
Scoping
Audit, urbanisation, structuring choices
Design
Target architecture, interoperability
Industrialisation
Integration, automation, securing
Go-live
Controlled deployment and monitoring
Evolution
Continuous adaptation to business challenges
// 05 · accessibility
Document accessibility, at every scale
Digital accessibility is not a separate skill: it is a property of the document, won or lost at every stage of its making. Whether a document is written by hand, produced in series or has been published for ten years, the gesture is not the same, and the most common mistake is to apply one situation's answer to another.
A1The single document, at source
A letter, a memo, a presentation, a spreadsheet. What is written by hand is fixed by hand, or better, built right from the first keystroke. Google Docs, Sheets and Slides, Word and PowerPoint all offer some assistance with tagging, reading order and text alternatives, but it often falls short: add-ons exist to cover what is missing. The right choice depends on usage and scale, and Purplsoft advises on both, for a single workstation and for an enterprise estate. The right moment remains the one at which you write: whatever is deferred until after export costs several times more.
A2Expertise, when tooling falls short
A heterogeneous archive, a PDF produced by a scanner, a two-way table, a site whose structure nobody remembers: some cases cannot be handled with a click. They call for an audit, a diagnosis, then remediation carried out by someone who knows what a screen reader actually announces. That holds for websites, for a single document and for an entire archive alike.
A3Volume
Everything changes beyond a few hundred documents. Making accessible every file published on a site or an intranet, or an entire variable-data production run (statements, notices, invoices, payslips) is a matter of industrialisation: batch processing, in SaaS or on premise, integrated into the existing chain rather than bolted onto it. This is where our document-factory experience transposes directly.
A4Governance, in a large organisation
Past a certain size, the question stops being technical. Who deployed what? Are the licences handed out actually being used? How do you recharge autonomous entities, and how do you demonstrate progress from one year to the next? Without that visibility, a rollout stops at the first budget review, and this is precisely what market tooling handles least well.
Conformant, or genuinely accessible?
PDF/UA (ISO 14289-1) describes how a document must be built: a complete tag tree, semantic structure, declared reading order, stated language, decoration marked as such, an alternative present on every image. It is a standard of form, and its virtue is being machine-verifiable. A validator can state that a document is conformant, and prove it.
WCAG asks a different question: does the person understand? Sufficient contrast, an alternative that actually describes the image, a link label that keeps its meaning out of context, a heading hierarchy that follows the document's logic, a table whose headers genuinely describe the data. None of that can be measured automatically.
The gap between the two is exactly where quality is decided. A document can be 100% PDF/UA conformant and remain unusable: an alt text reading "image1.png" satisfies the standard, since it exists, while telling nobody anything. A contrast ratio of 2:1 breaches no PDF/UA checkpoint, since the standard does not address colour, and fails WCAG.
The European framework says the same: EN 301 549, the technical reference for the accessibility directive, incorporates WCAG 2.1 level AA and extends it to non-web documents.
Our position fits in one sentence: PDF/UA is the floor, and a machine can prove it; WCAG is the target, and only a human can reach it. Tooling is not an alternative to expertise: it is its precondition, absorbing the volume so that judgement can concentrate where it cannot be replaced.
These four situations in detail, the regulatory framework and the questions we are asked most often: document accessibility.