Subrights and Permissions Management Software: Build vs Buy
Buy, or keep the spreadsheet. If you publish under fifty titles a year on one contract template, a well kept grid alongside your title management system is proportionate and a build would be indulgent.
On this page
Buy, or keep the spreadsheet. If you publish under fifty titles a year on one contract template, a well kept grid alongside your title management system is proportionate and a build would be indulgent. Cross the line when contract wording has changed across generations, nobody can say which translation rights are free, and subrights income is reconciled by hand at royalty time.
Custom versus off the shelf: what Klopotek, Biblio and Rightsline do well
The rights director preparing for a book fair with four sources of truth open is not necessarily looking at a software problem. Sometimes it is a records problem, and buying will fix it faster than building. Start there.
Klopotek and Virtusales Biblio both model rights properly, and for houses whose contracts fit the assumed shape they do it well. They hold titles, contracts, licences, royalty terms and the grid, and they connect to the rest of your publishing operation rather than sitting beside it. Ingenta handles content distribution and the commercial side competently. Rightsline comes at licensing from the media side and suits houses with substantial audio and adaptation activity. On the permissions side, clearance services such as PLSclear and the Copyright Clearance Center remove a large share of incoming requests before they ever reach your inbox.
What buying earns:
- A rights record that survives the departure of the person who held it in their head.
- Territorial rights expressed in a form your metadata already uses, since ONIX for Books from EDItEUR carries them into the trade.
- Licence and royalty terms in the same system as your sales data.
- Option and expiry dates that generate reminders without anyone maintaining a calendar.
- A vendor who upgrades the product as contract practice shifts.
Buy or stay on the spreadsheet if you publish under about fifty titles a year, your contract template has been stable, and one person can still answer a rights question in an afternoon. That is a large share of independent houses and there is no build that pays back at that size.
Where they stop: your contracts changed and the rights taxonomy did not
The workflow that generic rights systems model badly is the one that decides whether you can sell anything, and it comes down to clause generations.
Your contracts changed in one year, again in another, and again when audio became serious. The same right behaves differently depending on which generation a title falls under. A translation right may revert automatically in one generation and only on written request in another. Out of print is defined in terms that predate print on demand entirely in your older contracts, which is exactly why the definition matters and why the answer differs by title.
Systems built around a fixed rights taxonomy express that variation as a note in a field. Then the grid becomes something a person maintains rather than something the system derives, and maintenance decays. Options expire without anyone noticing, so a title sits blocked for two years after it stopped being blocked.
What a build does differently is separate the right from the clause that governs it. Each title links to a contract, each contract belongs to a template generation, and each right record carries the clause reference defining its scope, its reversion trigger and its split. The question of which titles have free German translation rights becomes a query rather than an archaeology project.
The second break is reversion. Modern contracts define it by conditions rather than dates: out of print under a specified definition, sales below a threshold across consecutive royalty periods, or failure to exploit a right within a window. Title management systems hold sales data and hold contracts, and connect the two only through a person. So when an agent writes, the process is find the contract, read the clause, pull the sales history, compute, reply. It takes days and produces inconsistent answers across a list. Encoding the reversion test as an evaluable rule run continuously against sales lets you see a title approaching a trigger before the author does, which changes the conversation entirely.
The third is income. Subrights money arrives in several currencies, through co agents with their own splits, subject to withholding that a treaty form such as a W-8BEN may reduce. Most houses reconcile that by hand at royalty time, which is the least forgiving moment in the publishing year.
The arithmetic: per user licensing versus the cost to build
Rights systems are priced per named user, sometimes with a module fee for the rights and royalties components. Convert everything to cost per year and hold it beside your title output.
Then add what the licence does not cover: the days spent assembling a rights availability list before each fair, the weeks of delay on reversion enquiries, the permissions administration that costs more to process than the fee recovers, and the royalty period spent reconciling subrights income across currencies and agents.
Cost the build the same way. Midpoint of the bands below, plus year two support, over five years, divided by active titles.
In our delivery experience the crossover lands near 4,000 active backlist titles, or three or more contract template generations still in force, or the point at which subrights and permissions income has become a line your finance director asks about by name. The middle trigger matters most and is independent of size. A house with 1,200 titles on one template is well served by a product. A house with 1,200 titles across four generations and two acquisitions is not, because the variation is the work.
Ask whether the fee follows users, titles or modules, and price it at your acquisition plan rather than at today's catalogue.
What a custom build actually costs
From Digital Heroes delivery experience, a first release covering the rights grid, contract clause capture, option and expiry tracking and permissions intake runs $55,000 to $110,000 and ships in 10 to 14 weeks. A full platform adding subrights income accounting, agent splits, rights guide generation and an author facing portal lands at $130,000 to $300,000 across 6 to 10 months.
Data migration is 10 to 25 percent of build cost and this category sits at the top of the range for a reason nobody enjoys. The contracts are scanned files, some of them thirty years old, and the value is in the clauses rather than the documents. Extracting the grant of rights, the territories, the reversion trigger and the splits from each contract, then having a second person verify the extraction, is the project. Machine extraction with confidence scoring helps, and a human still confirms anything that will ever be relied on in a negotiation.
Year two runs 15 to 20 percent of build cost annually. It buys clause library additions as your template evolves, new rights categories as the market invents them, and the reporting your royalty system needs each period.
The four situations where building wins
- Contractual fit. Several contract generations in force at once, inherited lists from acquisitions with their own wording, and reversion definitions that predate current formats.
- Scale economics. A backlist large enough that per user licensing has passed the amortised cost of owning the system, or a group where several imprints each pay separately.
- A rights list that is your commercial advantage. Producing an accurate availability list in an afternoon rather than a fortnight is the difference between selling at a fair and apologising at one.
- Integration sprawl across three or more systems. Title management, the royalty system, sales data feeding reversion tests, the metadata feed carrying territorial rights to the trade, and the permissions inbox.
One of those true means keep the product and build the clause layer beside it. That single piece removes most of the guesswork.
How to decide in a week, ending with a specification you own
Run the fair list test.
Pick a language you sell into regularly. Ask for a list of every title where translation rights in that language are currently free, with the contract reference supporting each entry. Give it a working day. Then have a second person spot check twenty entries against the contracts. Count the errors in both directions: titles listed that are not actually free, and titles omitted that are. Both cost money, and the second kind costs more because you never learn about it.
Then run the reversion test. Take five titles from different contract generations and ask how close each is to a reversion trigger today. If the answer requires reading five contracts, note how long that took and multiply by the number of enquiries you receive in a year.
Finish by pricing your permissions line honestly. Count the requests handled last quarter, the fees collected and the staff hours spent. If the second number is smaller than the third, that is a decision about whether to build, outsource or stop.
If the case holds, buy a discovery phase before a build. At Digital Heroes it ends in a signed product requirements document covering the rights data model, the clause library and acceptance criteria, and you own it whether or not you continue with us. We hold India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law, run more than fifty specialists across over 2,000 projects, and you meet the named team before signing. We are checkable on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
We are the wrong firm for a house publishing thirty titles a year on one template. Tidy the spreadsheet, agree a naming convention, and put the budget into acquisitions.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The right combination of digital transformation actions can unlock as much as US$1.25 trillion in additional market capitalization across Fortune 500 companies, while the wrong combinations put more than US$1.5 trillion at risk; companies with all three core factors (strategy, aligned technology, and change capability) saw a 5% market-value lift relative to peers. Source: Deloitte (2023) →
- In a survey of 113 supply chain leaders (conducted late March to mid-April 2022), 67% had implemented digital dashboards for end-to-end visibility, and those companies were about twice as likely as others to avoid supply chain problems during the disruptions of early 2022; 71% expected to revise inventory policies going forward. Source: McKinsey & Company (2022) →
- The average developer spends more than 17 hours a week dealing with maintenance issues such as debugging and refactoring, and about four of those hours on 'bad code' - waste that equates to nearly $85 billion annually worldwide in opportunity cost. Source: Stripe (2018) →
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
Frequently asked questions
How long does a rights and permissions system take to build?
Ten to fourteen weeks for a first release covering the rights grid, clause capture, option tracking and permissions intake. A full platform with income accounting, agent splits and an author portal takes six to ten months. Plan the launch away from a fair season and away from royalty close, since those are the two periods when the rights team has no capacity to learn anything new.
Who owns the rights records and the code if the developer relationship ends?
You should own the repository, the cloud accounts and every record. Agree it before development starts. At Digital Heroes the client owns the code from the first commit. This matters unusually here because the rights register is an asset register: it is the evidence of what you control, and it must remain queryable for as long as the contracts run, which for backlist can mean decades.
Can we build only the clause library and keep our current system?
Yes, and it is the highest value first slice. A clause service holds contract generations, the grant of rights, reversion triggers and splits, keyed to titles in your existing system. Your rights team keeps the interface they know and gains the ability to query availability. Confirm your incumbent exposes title records programmatically before scoping it, since some older installations do not.
What happens if we sell a right we no longer hold?
You refund, you apologise, and in a small market the reputational cost outlasts the financial one. This is why reverted rights must be marked unsellable everywhere the moment reversion takes effect, rather than noted in a file someone may check. Any system you evaluate should be judged on how it propagates a reversion, not on how it records one.
Should a house publishing forty titles a year build anything?
No. At that size a disciplined spreadsheet with one owner, consistent title identifiers and a scanned contract folder named to match will answer every question you have. The failure at small houses is naming and ownership rather than software. Revisit the build question when a second contract generation comes into force or you acquire another list, since variation is what breaks manual records.
What is the difference between subrights and permissions?
Subrights are grants of substantial exploitation, such as translation, audio, dramatic, serial or book club rights, usually negotiated with an advance and a royalty. Permissions are small licences to reuse an extract, an image or a few lines, typically for a modest one off fee. They share a dependency, which is knowing what you actually control, but their workflows and economics have almost nothing in common.
Can we tell whether permissions is worth running in house?
Count the requests handled last quarter, the fees collected and the fully loaded staff hours spent. If the hours cost more than the fees, the choice is to automate intake so simple requests self serve, route them to a clearance service, or decline the category. Many houses discover the line is worth keeping only after intake and licence generation stop being manual.
How do we handle rights categories that our older contracts never mentioned?
Treat silence as unresolved rather than as a grant. Where a contract predates a format, the right should sit in an explicitly unknown state that requires a decision, usually a conversation with the author or agent, before anything is offered. Systems that default unmentioned rights to controlled are how houses end up licensing something they were never granted.
What happens to subrights income across currencies and agents?
It should be computed rather than transcribed. If the licence record holds the advance, the royalty terms, the split percentages, the co agent, the currency and the withholding position, then allocation to the author and to any agent falls out automatically at royalty time. Hand reconciliation is where errors enter, and they enter in the one period of the year when nobody has time to find them.
Is it worth building if we have grown by acquisition?
Usually yes, and acquisitions are the single strongest indicator in this category. Each acquired list brings its own contract wording, its own identifiers and often a database nobody can query. The value of a build is not the rights grid itself but the mapping layer that lets several legacy conventions resolve to one title identity, which is what makes a group wide availability list possible at all.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
Is SAP overkill for a mid-sized company?
For most companies under about 500 employees, yes. SAP S/4HANA is built for multi-entity, multi-country enterprises with implementations measured in years and seven figures, while SAP Business One, the mid-market product, still forces your processes into its mold. If your competitive edge lives in how you operate, a custom ERP scoped to your actual workflows ships faster and costs a fraction of an SAP program.
Is a custom ERP cheaper than NetSuite over five years?
Often yes once you pass roughly 20 to 30 users. NetSuite is commonly quoted at $999 per month for the base platform plus about $99 per user per month, so a 30-user company spends over $200,000 on licenses across five years before paying for implementation. A custom build in the $120,000 to $250,000 range is a one-time cost, and in Digital Heroes projects annual upkeep runs 15 to 20 percent of build cost with no per-seat fees as you hire.
Can I start with one ERP module instead of the full system?
Yes, and it is how most successful custom ERP projects at Digital Heroes begin. We build the single module causing the worst pain first, typically inventory or order management, get it live in 10 to 14 weeks, and let it prove ROI before the next phase gets funded. Starting with one module also derisks data migration because you move one dataset at a time.
Is customizing Odoo cheaper than building an ERP from scratch?
Usually yes in year one, and often no by year three if your workflows sit far from Odoo's assumptions. Odoo's published pricing starts around $25 per user per month and the Community edition is free, but heavy customization means every version upgrade can break your modules and needs paid rework. If you expect to rewrite more than about a third of the core flows, a scratch build with clean ownership tends to cost less over the life of the system.
How many developers does it take to build an ERP?
A typical Digital Heroes ERP pod is five to seven people: two or three backend engineers, one frontend engineer, a QA engineer, a project manager, and a part-time architect and designer. Bigger teams rarely go faster on ERP because the bottleneck is decisions about your business rules, not typing speed. What you need on your side is one empowered internal owner who can answer process questions within a day.
What tech stack should a custom ERP be built on?
A boring, hireable one: Digital Heroes most often ships ERPs on PostgreSQL with a Node.js or Python backend and a React frontend, hosted on AWS or Azure. The stack matters far less than the database design, because your ERP schema will outlive every framework choice. Be skeptical of any agency proposing a niche or proprietary framework, since your ability to hire maintainers later is part of the total cost.
How much does a custom ERP cost for a small business?
A small-business ERP covering two or three core modules typically runs $40,000 to $120,000, with inventory, ordering, and accounting sync being the usual starting set. Across 2,000+ Digital Heroes projects, integration count and user roles drive cost far more than screen count. A full mid-market ERP with six or more modules usually lands between $150,000 and $400,000.
Who can build a custom ERP software system?
Digital Heroes builds custom ERP software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other ERP software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .
