The Quiet Perth Company That Turns a Word Document Into a Document Factory

Somewhere right now, a bank is emailing you a statement. An insurer is issuing a policy. A logistics firm is printing a consignment note. A law firm is producing a contract nobody will read until something goes wrong. These documents look nothing alike, yet underneath a surprising number of them sits the same unglamorous task: take structured data, drop it into a designed layout, and hand back a clean PDF. That task is the entire business of Docmosis, a software company you have probably never heard of, run out of Perth, Western Australia, by two people who decided long ago that they would rather stay small and own the whole thing.

Docmosis makes document generation software. The pitch, printed plainly on its homepage, is not trying to sell you a revolution: a smart template-based approach to generating custom PDF and Word documents. The important word is template. You design the layout - a letter, an invoice, a proposal, a report - in Microsoft Word or LibreOffice Writer, the same tools your colleagues already use. You mark the spots where data should go. Then a developer wires it up once, sends data plus template to Docmosis through a REST API, and gets back a finished document in PDF, DOCX, ODT or TXT. Change the wording of the contract next quarter? Open the Word file, edit it, save. No code, no deploy, no ticket to engineering.

The problem hiding in every enterprise app

Ask any developer who has built line-of-business software and they will tell you the same war story. The application works beautifully until someone says: now generate the PDF. Suddenly you are gluing together libraries, hand-positioning text, fighting page breaks, and rebuilding the layout in code every time legal changes a comma. Co-founder Paul Jowett lived exactly this, across finance, health, education and defense projects in Australia, Britain and America. Starting around 2005 he spent roughly three years in research and development on a better way before the first version shipped into healthcare, defense and education systems.

The insight was organizational as much as technical. The person who cares most about how a document looks - the compliance officer, the marketer, the operations lead - is almost never the person who can change code. By making the template an ordinary Word file, Docmosis moved control of the document to the people who actually own it, and left developers to handle only the plumbing.

The templates are not dumb, either. Inside that familiar Word file you can nest conditional content that appears only when the data warrants it, loop over rows to build tables and repeated sections, run calculations, and drop in images and barcodes. A single template can therefore stand in for what would otherwise be dozens of near-identical layouts - one invoice design that quietly adapts to a customer in Berlin, a customer in Boston, and a customer with fourteen line items and a discount.

Who actually uses it

The customer list reads like a tour of the industries that live or die by paperwork: finance, insurance, healthcare, legal, education, government, HR, logistics and manufacturing. Sizes run from solo developers to large enterprises, spread across more than 30 countries. What unites them is not their sector but their shape - they all need to produce many variations of the same document, correctly, repeatedly, without a human retyping anything.

Three products, one engine

Docmosis ships the same core technology three ways, which is a quietly clever way to meet very different buyers where they stand. Some want speed and zero infrastructure; some cannot let data leave the building; some want to bury the engine deep inside their own code.

CloudThe hosted SaaS, running on AWS with multi-region distribution. You call a REST endpoint and documents come back. Pricing starts at $49 a month, and there are no overage charges waiting to ambush you at the end of a busy quarter.

TornadoA self-hosted, standalone engine for Linux, Windows or Docker. This is the answer for the security team that will not let customer data touch a third party. Same templates, same output, inside your own walls.

Docmosis-JavaThe original: a high-performance Java library you embed directly in your application. It is where the whole thing started, and it remains the option for teams that want the engine woven into their own code.

How it is different

Document generation is a crowded shelf. PandaDoc, Conga Composer, Windward, Nintex, ActiveDocs and a long tail of newer tools all promise to turn data into documents, and plenty of teams just hand-roll it with Word, LibreOffice or Adobe. Docmosis does not out-feature all of them - it is candid, for instance, that it focuses on PDF, Word, ODT and TXT rather than spreadsheets or slide decks, and that connecting to platforms like Salesforce often means custom work rather than a click.

What it optimizes for instead is a specific kind of buyer: the developer who wants document generation to be a solved problem, not a project. The template-in-Word model, the three deployment options, the pricing without traps, and the fact that a support reply comes from someone who wrote the code - these are the edges. It is a tool built by people who clearly got tired of building the same thing badly and decided to build it once, well.

Docmosis is also unusually honest about its own limits, which is rarer than it should be. Its published values describe template-based generation as an approach rather than the approach, and the company would rather tell a prospect it is a poor fit than win a deal that unravels in six months. In a category full of demos engineered to dazzle, offering impartial advice is its own kind of differentiation.

The business model, and the discipline behind it

Docmosis is 100% founder-funded and founder-owned. No venture round, no board demanding a hockey stick, no exit clock. The company earns through recurring Cloud subscriptions plus licensing for Tornado and the Java library, and it has grown the old-fashioned way - by finding a real problem people will pay to make disappear, then not overreaching.

The restraint shows up in the timeline. Paul Jowett handled the technical side; Graham Hughes, a former IT professional and certified pilot who once worked as a flying instructor, formally incorporated Docmosis Pty Ltd in 2013 and runs the business. Tornado arrived in 2014. And yet the company did not hire its first two employees until 2017, moving into a dedicated office in 2018 and picking up a Rising Stars award that same year. That is a company that added people only when the work genuinely demanded them.

Where it fits

In the map of enterprise software, Docmosis sits in the plumbing - the layer that is invisible when it works and catastrophic when it does not. That is a hard place to build a brand and a good place to build a business, because once a document pipeline is generating your invoices and statements reliably, you do not go looking to replace it. The low-code and no-code integrations added around 2022, connecting to platforms such as Mendix, Appian and Zapier, extend that reach to teams who never write Java at all.

It helps that the switching costs run in Docmosis's favor without any lock-in tricks. Because the templates are just Word and LibreOffice files, a customer's document designs stay theirs; the value is in the engine that renders them reliably at volume, not in a proprietary format holding anyone hostage. That is a comfortable moat to sit behind - one built from trust and reliability rather than friction.

There is something almost contrarian about the whole operation. While much of the software world chases scale, funding and speed, Docmosis has spent two decades doing one boring thing carefully, from a city closer to Jakarta than to Sydney, and let the reliability do the marketing. It is a reminder that a lot of critical software is not built by the companies making headlines - it is built by small teams solving a problem so well that everyone quietly forgets it was ever hard.