✓ Survived Rank 1 of 7 proposedIndie DevTools Oct 25, 2026

Office document fidelity test suite for migrations

Automated compatibility testing that catches where LibreOffice/Collabora breaks real-world Office docs before and during a migration.

Open the discussion ↗

A ready-to-paste brief for Claude Code, Cursor or any coding agent.

I want to build a small, bootstrappable product. Help me plan and start the MVP.

Product: Office document fidelity test suite for migrations
What it is: Automated compatibility testing that catches where LibreOffice/Collabora breaks real-world Office docs before and during a migration.
Who pays: IT directors and digitalization leads at European municipalities/ministries running open-source office pilots; $20k–$100k per migration project from the pilot/consulting budget
Closest alternatives: Microsoft Office compatibility checker (built-in, one-directional), OpenText/Accusoft document comparison tools, manual QA by migration consultants
The gap: No vendor-neutral, automated regression suite that runs an organization's real document corpus through open-source suites and reports exactly which workflows (mail merge, track changes, Excel models) break, with severity and remediation cost.
Why now: EU digital-sovereignty pressure is driving a wave of government pilots (Denmark, German states, France) that keep failing on document fidelity; each failed pilot is public evidence of an unmeasured problem.
Moat to build toward: Corpus of failure cases and per-workflow compatibility scores grows with each engagement; becomes the de facto benchmark procurement teams cite.
Biggest risk: Governments abandon migrations for political/price-negotiation reasons, so the testing tool gets bought once as negotiation leverage rather than as an ongoing product.

First three steps:
1. Build a harness that batch-converts a document corpus via LibreOffice/Collabora headless and diffs rendered output against Office rendering
2. Ship pre-built test packs for the top failure workflows: mail merge/labels, track changes, Excel financial functions
3. Package as a fixed-price assessment report sold to one Nordic municipality pilot

Start by asking me up to five questions about constraints (stack, budget, timeline), then propose the smallest version a paying customer would use, and scaffold it.

Overall6.2/10

Pain6

Willingness to pay6

Timing7

Gap7

Moat5

Feasibility6

For

Who pays

IT directors and digitalization leads at European municipalities/ministries running open-source office pilots; $20k–$100k per migration project from the pilot/consulting budget

What people said · 3

Danish pilot users hit typography and track-changes frustrations with Collabora and the project was shelved without evaluation. Read the comment ↗
Font issues in Word/PowerPoint and Excel financial models make interoperability with MS Office users hopeless. Read the comment ↗
Commenter re-tests LibreOffice/OnlyOffice yearly and mail merge to label sheets still comes out misaligned, ruining paper. Read the comment ↗

Paraphrased from the discussion. Follow the links for the original comments.

Competitors and gap

Microsoft Office compatibility checker (built-in, one-directional)OpenText/Accusoft document comparison toolsmanual QA by migration consultants

No vendor-neutral, automated regression suite that runs an organization's real document corpus through open-source suites and reports exactly which workflows (mail merge, track changes, Excel models) break, with severity and remediation cost.

Why now

EU digital-sovereignty pressure is driving a wave of government pilots (Denmark, German states, France) that keep failing on document fidelity; each failed pilot is public evidence of an unmeasured problem.

Moat · 5/10

Corpus of failure cases and per-workflow compatibility scores grows with each engagement; becomes the de facto benchmark procurement teams cite.

Against

Red team: A vendor-neutral regression suite that runs a real document corpus through open-source suites and prices the breakage per workflow has no direct incumbent, rides a funded EU sovereignty pilot wave, and render-diff automation makes it buildable by a small team.
What would kill it: Governments abandon migrations for political/price-negotiation reasons, so the testing tool gets bought once as negotiation leverage rather than as an ongoing product.

Start

First three steps: Build a harness that batch-converts a document corpus via LibreOffice/Collabora headless and diffs rendered output against Office rendering
Ship pre-built test packs for the top failure workflows: mail merge/labels, track changes, Excel financial functions
Package as a fixed-price assessment report sold to one Nordic municipality pilot
Source discussion: Danish Government silently drops plan to dump MS Office ↗ 223 points183 commentsFrom the commentsLinked article