Blog › Build Story · Market Gap
Every tool I found
solved a different problem.
Before I built BrandSwitch, I went looking for something that already did this job. Here's what I found instead, and why I think the gap exists for most vendors, not just by accident.
2
categories of document tool, one mostly ignored
550
templates rebranded in the flagship run
11 min
for that entire batch
1,000
pages processed in under 5 minutes
The tools I looked at first, and what they were all built for
Before writing a line of code, I did what most people do: assumed someone else had already solved this and went looking for their product. I found template management platforms, brand asset libraries, design system tools, and a handful of document generation services. Every one of them was polished, well-funded, and clearly built for the same job as each other - just not the job I had.
They were all built to help a team create new, on-brand documents going forward. Set up a template once, generate compliant new documents from it forever. Genuinely useful, for a different problem than the one sitting in front of me: a folder of hundreds of documents that already existed, in the wrong brand, that someone needed fixed this week.
The pattern: every existing tool assumes you're creating new documents, not fixing old ones
Outbound tools
Help you create new on-brand content from this point forward. That's the entire category.
The inbound problem
Documents you already have, in the wrong brand, that need fixing now - almost nobody builds for this directly.
Most document branding tools are outbound - they help you create new on-brand content. Almost none solve the inbound problem: documents you already have, in the wrong brand. Once I saw that pattern clearly, the market made a lot more sense. Nobody was ignoring the problem out of incompetence. They were solving an adjacent, more fundable problem instead.
Why that gap exists (it's a less glamorous problem than "brand management platform")
"Manage your brand going forward" is an easy pitch. It's ongoing, it's a platform, it renews every year, and it looks good in a product roadmap. "Fix the pile of old documents you're embarrassed about" is a one-off chore. It sounds like a feature, not a company, and most vendors build toward the pitch that scales as a platform rather than the pitch that scales as a job someone needs done once, thoroughly.
There's also a harder engineering reason. Outbound tools generate documents from a template they control. Inbound rebranding has to read the structure of a document someone else made, in whatever state it's actually in - inconsistent formatting, legacy styles, direct formatting layered over years of edits - and rewrite it correctly. That's a fundamentally different, fiddlier problem than generating clean output from a known template.
Almost none solve the inbound problem: documents you already have, in the wrong brand.
What building for the inbound problem actually required
It meant treating every document as an unknown quantity rather than a known template. The engine had to read a file's actual structure - where its headers, footers, tables and body text really live, not where a tidy template would put them - and apply a new brand consistently across all of it. It also meant handling batches, because the inbound problem is rarely one document. It's a library.
None of that is a platform feature you bolt onto an outbound tool later. It's a different starting assumption baked into the architecture from day one, which is probably the real reason this stays a gap rather than a checkbox on someone else's roadmap.
Why I think this stays a gap for most vendors, not just an oversight
I don't think the big platforms are missing this by accident. I think it's a genuinely awkward problem to build well, sell as ongoing, and market as exciting, all at the same time. That's exactly the kind of gap a small, focused product can occupy properly while a platform company reasonably chooses not to chase it.
Quick answers
What's the difference between an outbound and an inbound document tool?
Outbound tools help you create new on-brand content going forward - think template management platforms. Inbound tools fix documents you already have, in the wrong brand, right now. Most of the market builds for the first job and assumes the second doesn't exist.
Why hasn't a big vendor already solved the inbound problem?
It's a less glamorous problem to sell. 'Manage your brand going forward' pitches as a platform. 'Fix the folder of old documents you're embarrassed about' pitches as a one-off chore, so it rarely gets built as a standalone product.
Is this gap likely to close soon?
Possibly for a few vendors, but it stays a gap for most, because it requires a different kind of engineering - reading and rewriting existing document structure rather than generating new documents from templates.
Where does BrandSwitch fit in this gap?
BrandSwitch was built specifically for the inbound problem: uploading documents you already have and getting them back in your brand, without becoming a template management platform along the way.
The tool built for this specific gap
BrandSwitch exists because I couldn't find anything built for the inbound problem, so I built one. Upload the documents you already have, set your brand once, and get them back rebranded - without becoming a platform you have to manage forever.
See the tool built for the inbound problem
Documents you already have, rebranded, without a platform to manage.