Enterprise Solutions
Publishing software, built at the speed of AI.
Publishing runs on software that was old a decade ago. We build and modernize it with AI-assisted development, so the work that used to take four quarters takes a few weeks.
What we build
All of it inside publishing, which is the part that matters. We are not a general software shop learning your business on your budget.
Integrations
Getting your catalog, rights, royalties, and retail systems to speak to each other instead of meeting in a spreadsheet.
Catalog and metadata tools
ONIX in and out, bulk correction, and the tedious reconciliation work that currently consumes a person.
Direct storefronts
Selling to your own readers, with delivery and ownership handled rather than bolted on afterwards.
Reader experiences
Custom reading and listening surfaces when an off-the-shelf reader does not fit what you are trying to do.
Workflow automation
The manual hand-offs between systems that quietly set the pace of everything else you do.
Modernization
Moving a system that works but cannot be changed onto ground where it can be, without stopping the business to do it.
Built this way already
The argument for working like this is what it has produced, not a description of the method.
Galley Forecast
Predictive reader intelligence that simulates how a manuscript will land before the first advance copy goes out.
Rights Management
Immutable ownership and licensing records across music, film, publishing, and art, verifiable across several chains.
book.io
A storefront, reader, and ownership platform serving readers, authors, and publishers in six languages.
How an engagement runs
Three stages, in this order, because each one decides whether the next is worth starting.
A week to find the real constraint
We look at what you actually run and where the time goes. Often the expensive problem is not the one that prompted the call.
Something working, quickly
A narrow slice in front of the people who will use it, early enough that changing direction is still cheap.
Built out and handed over
Widened to the full scope, documented, and either operated by us or handed to your team. You are not held hostage by the choice.
Common questions
What kind of publishing software do you build?
Integrations between catalog, rights, royalties and retail systems, metadata and ONIX tooling, direct storefronts, custom reading experiences, and workflow automation.
How long does a project take?
Weeks rather than quarters for a first working slice. The first week goes on finding the real constraint, which is often not the one that prompted the call.
Do we own what you build?
Yes. It is documented and handed over, and you choose whether we keep operating it or your own team takes it on.
What is slowing you down
Describe the system, the workflow, or the integration that keeps costing you time. We will tell you honestly whether it is worth building and roughly what it takes.