Splitting DTP, PDF remediation, and file preparation across three specialist vendors feels like careful sourcing. It is usually the opposite: three onboarding conversations, three sets of file specifications, three invoices to reconcile, and three places a project can fall through a gap between vendors who each assume the other covered something. Foliage Solutions handles all three under one Clean Delivery standard, because the coordination cost of splitting them rarely shows up as its own line item, which is exactly why it goes unnoticed until it is counted.
This matters for LSPs currently running a fragmented vendor list for what is, functionally, one connected workflow.
Why this looks like careful sourcing, and usually is not
The instinct to specialize by service makes intuitive sense. A dedicated PDF remediation vendor should be better at remediation than a generalist. A dedicated OCR shop should be better at file conversion. In practice, this reasoning breaks down once you account for what happens at the seams between vendors, not within any single vendor’s own work.
A file that needs OCR conversion, then DTP layout, then PDF remediation, passes through three handoffs if three vendors are involved. Each handoff is a place where context gets lost, a specification gets restated imperfectly, or an assumption about what the previous vendor already checked turns out to be wrong. None of this shows up as a line item on any single vendor’s invoice. It shows up as delay, rework, and the specific kind of quality gap that falls between two vendors who each assumed the other’s scope covered it.
The pattern is familiar from anywhere handoffs happen without a single owner. The person or team closest to the actual work knows the details that matter. The moment that knowledge has to be communicated to a separate team rather than simply carried forward by the same one, something is lost in translation, sometimes literally.
What the numbers say about consolidation generally
This is not a pattern unique to translation-adjacent services. General procurement research on vendor consolidation puts typical savings at 10 to 20% once redundancy, administrative overhead, and stronger negotiating position are accounted for, and the trend is accelerating broadly: recent industry reporting found 68 percent of technology leaders planning active vendor consolidation in 2026. The reasoning behind that trend applies directly here. Fewer vendors means fewer invoices, fewer contract renewals, fewer separate points of contact to manage, and fewer places where the same question has to be asked and answered twice.
The specific mechanism for DTP, remediation, and file prep is coordination, not just administrative overhead. A single vendor handling all three does not need a handoff meeting to explain what the OCR step already caught, because the same team ran the OCR step and knows exactly what state the file was in when DTP work began.
This is the same Total Cost of Ownership argument that applies to DTP vendor selection generally: the invoice is not the cost. A fragmented vendor list can look cheaper on paper, three specialists each quoting competitively for their piece of the work, while the coordination overhead between them never appears on any quote at all. Once that overhead is counted, the cheaper-looking fragmented model frequently costs more than a single vendor’s blended rate across all three services.
Where the real cost hides in a fragmented vendor list
Three specific costs recur in a split-vendor model, and none of them are visible on any individual invoice.
Specification drift. Each vendor works from its own version of the brief, restated by whoever is coordinating between them. Small details, which languages need multilingual remediation versus single-pass, which CAT tool the DTP output needs to be compatible with, get lost or altered in the retelling. A single vendor working from one brief across all three services does not have this restatement step at all.
Accountability gaps. When a translated PDF fails an accessibility audit, was the failure in the OCR conversion, the DTP layout, or the remediation pass. With three vendors, each can reasonably point to the other two. With one vendor, there is exactly one place responsibility sits, which changes how seriously a problem gets treated before delivery, not just how it gets resolved after.
This is not a hypothetical concern. It is the exact scenario a Vendor Manager runs into when trying to determine root cause on a delivered file that failed review, and the answer determines who is actually accountable for the fix, not just who gets blamed in the moment.
Redundant onboarding. NDA execution, compliance documentation, capacity confirmation, and quality-standard alignment all have to happen three separate times in a fragmented model, and all three need to happen again if any one vendor changes their team or process. One vendor relationship means this overhead is paid once.
What this looks like on a real file
A scanned technical manual that needs to become a translated, accessibility-remediated PDF touches all three services in sequence: OCR conversion to make the source editable, DTP work to handle the multilingual layout and CAT-tool-safe file preparation, and remediation to rebuild the accessibility layer once translation is complete.
Run through three vendors, this project has three separate quality standards to reconcile, three separate timelines to coordinate, and three separate points where a problem in one step, undiscovered until the next vendor’s work reveals it, sends the file backward rather than forward. Run through one vendor working from a single Clean Delivery standard across all three steps, the same team that converted the file already knows its structure when they build the layout, and the same team that built the layout already knows what the remediation pass needs to preserve.
Consider what happens specifically when the OCR vendor misses a compound word split, common on technical content, and hands off a file with a subtly corrupted term to a separate DTP vendor. The DTP vendor has no reason to catch a linguistic error; that is not their scope. The remediation vendor, receiving the file even later, has even less visibility into where the error originated. In a single-vendor model, the same team that ran the OCR step is the team building the layout, and a compound-word error gets caught because the person doing the next step is looking at the same file with the same context, not receiving it cold from someone else’s handoff
When consolidation is not the right call
This argument has a real limit. If a single vendor’s capacity cannot absorb the actual volume, or if a client specifically requires named-vendor redundancy on their own Approved Vendor List for risk-management reasons, splitting the work deliberately across more than one vendor is the correct decision, not a failure of sourcing discipline. Consolidation is not about reducing to exactly one vendor as an end in itself. It is about not fragmenting a genuinely connected workflow across separate vendors by default, without a specific reason driving that split.
The question worth asking before defaulting to a split-vendor model: does this project actually need multiple specialists, or does it need one vendor whose scope happens to cover multiple services.
This distinction matters because the two failure modes run in opposite directions. Over-fragmenting a connected workflow creates the coordination costs described above. Under-diversifying a genuinely high-volume, high-risk workflow creates a single point of failure with no fallback, the same structural risk covered in our work on Approved Vendor List redundancy. Neither extreme is the right default. The right call depends on actual volume, actual risk tolerance, and whether the services in question are genuinely connected steps in one workflow or genuinely independent needs that happen to share a vendor category.
What to ask before consolidating your own vendor list
Does the prospective consolidated vendor actually have depth in all three services, not just a broad claim of general capability. Ask for evidence in each area specifically: named CAT-tool testing for DTP, a documented remediation report structure for accessibility work, and a specific process for translation-ready OCR, not just readable OCR. A vendor who cannot demonstrate real depth in one of the three is not a genuine consolidation option, just a single point of failure with a broader service list.
This same software-versus-managed-service question comes up specifically in PDF remediation, covered in more depth in our piece on remediation software versus a managed service, and the underlying logic applies just as directly here: depth has to be demonstrated, not claimed.
Ask how they handle capacity if volume spikes beyond what a single team can absorb, since this is the legitimate risk consolidation introduces. A vendor with a real answer describes a surge-capacity plan. A vendor without one is asking you to discover the gap during a live project.
How Foliage handles the full workflow
OCR, DTP, and PDF remediation run under the same Clean Delivery standard, the same team, and one point of accountability rather than three. A file’s history, what was caught during conversion, what the layout needed to account for, what the remediation pass has to preserve, travels with the project instead of being restated at each handoff.
Talk to Foliage Solutions about whether your current vendor list is genuinely specialized, or just fragmented. The difference is worth an honest look before the next project makes it obvious the hard way.