How Much Does Subsidiary Rights Software Cost in 2026?
Custom subsidiary rights and permissions software costs $55,000 to $300,000, with a first release covering the rights grid, contract and clause capture, option and expiry tracking and permissions intake at $55,000 to $110,000 in 10 to 14 weeks, and a full platform at $130,000 to $300,000 over 6 to 10 months, based on Digital Heroes delivery experience.
On this page
Custom subsidiary rights and permissions software costs $55,000 to $300,000, with a first release covering the rights grid, contract and clause capture, option and expiry tracking and permissions intake at $55,000 to $110,000 in 10 to 14 weeks, and a full platform at $130,000 to $300,000 over 6 to 10 months, based on Digital Heroes delivery experience. The decision that moves the number most is how many distinct contract generations you model properly. Your contracts changed several times over the decades and each generation makes the same right behave differently, so modelling the last two properly and treating the older ones as exceptions is the difference between the bottom and the top of the first release band.
The bands a rights platform falls into
A first release covering the rights grid with an extensible taxonomy, contract and clause capture, option and expiry tracking with alerts, reversion rule evaluation and permissions intake runs $55,000 to $110,000 and ships in 10 to 14 weeks. A full platform adding subrights deal and income management with agent splits and currencies, rights guide generation, an author or agent portal and integration into royalty and title management systems runs $130,000 to $300,000 phased across 6 to 10 months.
Title count matters less than contract variety. A house with 8,000 backlist titles all issued on two templates costs less to serve than a house with 2,500 titles across five contract generations plus an inherited database from an acquisition that nobody can query. What you are paying for is the number of ways your contracts define the same right.
Be careful with quotes under $55,000. In this category that usually means the rights taxonomy has been modelled as a fixed list of checkboxes. A fixed taxonomy cannot represent a right that is neither granted nor reserved but simply unaddressed, and that third state is exactly what you need when a new licensing category appears.
What drives a rights build up
The number of contract generations. Each needs its clause behaviour modelled and then verified against real contracts, which requires the rights director's time as much as a developer's. This is the dominant driver and it is the one publishers underestimate.
Imprint and territory structure. Several imprints with different practices, or a house holding English language rights in specified territories while another publisher holds the rest of the world, multiplies the grid rather than extending it.
Legacy data from an acquisition. An inherited rights database has to be profiled and interpreted before it can be migrated. Some fields will be trustworthy, some were populated inconsistently by a team that no longer exists, and some are simply wrong.
Multi currency and withholding. A translation advance arrives in a foreign currency, subject to withholding in that country, splitting with the author and possibly a co agent. Getting that arithmetic right is a real piece of work.
Author and agent portals. They look simple and carry genuine access control and data protection requirements, because an author must see their own titles and nothing else.
Reversion rules against older out of print definitions. Contracts written before print on demand define out of print in terms that no longer map cleanly, and each such definition is its own rule.
What keeps the number down
Model the last two contract generations properly. Handle the older ones as exceptions flagged for human reading. Most of your active licensing activity sits in the recent generations, and the older ones can be modelled later once the clause library has proved itself.
Start with translation and audio. They are where the money and the enquiries are. The full grid, including serial, book club, large print and anthology, can follow.
Leave royalty accounting where it is. The rights platform should own deal truth and feed allocated income into your existing royalty run. Replacing royalty accounting is a much larger project than the return justifies.
Import with confidence markers rather than cleaning first. Bring the inherited data across with explicit trust levels, then verify the titles that actually earn. A migration plan written before anyone has looked at the data is a plan to import errors faster.
Defer the portal. Authors and agents are currently emailing your rights team and will continue to do so for another two quarters without harm.
A worked example that adds up
An independent publisher with roughly 4,000 backlist titles across three imprints, five distinct contract generations, an inherited rights database from a house acquired some years ago, active translation and audio licensing, and steady academic permissions traffic. Here is the first release we would quote.
- Discovery and clause library capture for the two most recent contract generations: $14,000
- Title, contract and clause data model with an extensible rights taxonomy that treats unaddressed as a first class state alongside granted and reserved: $22,000
- Rights grid derived from clause records, queryable by right type, language, territory and term: $20,000
- Option and expiry tracking with alerts before a lapse rather than after: $12,000
- Reversion rule evaluation running continuously against sales data: $18,000
- Permissions self service intake with policy rules, pricing schedule and automatic licence issuance for routine cases: $16,000
That totals $102,000, near the top of the first release band because of the imprint structure and the reversion work.
Phase two: subrights deal and income management with agent splits, currencies and withholding at $42,000, rights guide and fair list generation at $18,000, author and agent portal at $32,000, integration into royalty and title management systems at $24,000, migration of the acquired house's database with confidence markers and verification workflow at $30,000, and modelling the three older contract generations at $20,000. That is $166,000, taking the platform to $268,000 across roughly nine months.
How the spend phases
Discovery in this category is document work and it is bounded by your rights director's availability, not by developer capacity. Expect several weeks of reading contracts and writing down what each clause generation actually does. Publishers who already have their template history documented move noticeably faster than those reconstructing it from PDFs, and that difference is worth real money.
The clause library and the rights grid are built together, because the grid is derived from the clauses rather than maintained separately. That is the architectural decision the whole project rests on, and it is what makes a book fair list a query rather than an archaeology project.
Time the launch against your fair calendar. Going live six weeks before a major fair is asking your rights team to learn a system during their busiest period. Going live immediately after gives them a full cycle to populate and verify. Invoice against shipped modules across three or four milestones for the $102,000, then phase two module by module, taking deal and income management before the portal.
The ongoing costs nobody quotes
- Maintenance and iteration at roughly 15 to 20 percent of build cost per year. On a $268,000 platform that is $40,000 to $54,000.
- New contract generations. Every time your standard contract changes, somebody has to add the generation and its clause behaviour. This is a small, recurring, unavoidable task and it should be budgeted rather than treated as a change request.
- Currency data. Exchange rate feeds for multi currency deal reporting, plus the accounting judgement about which rate applies when.
- Document storage. Contract scans going back decades, plus licences issued, plus correspondence attached to deals. Not expensive, but it accumulates and it must be retained.
- Portal support. External users mean password resets, access questions and the occasional data protection request. Somebody in the rights team absorbs that.
- Verification of migrated records. The inherited database imported with confidence markers needs working through over the first year, title by title, prioritising what earns.
Comparing a build against your current renewal
Use your own contract. Pull the Klopotek, Virtusales Biblio or Ingenta renewal and separate the core licence, the rights module if it is charged separately, per user seats and support. Multiply across twelve months. That is the visible figure, and for a mid sized house it is often modest against a build.
Then price what the renewal does not show, which in publishing rights is mostly time and foregone income. Count the days your rights director spends assembling a fair list from a spreadsheet, a folder of contract scans and a colleague's memory. Count the reversion enquiries that take days to answer and produce inconsistent results across a list. Count options that expired without anyone noticing, which means a title sat blocked for two years after it stopped being blocked, and put your own average translation advance next to that.
Permissions is the clearest arithmetic because it is nearly pure contribution. Take the number of requests you receive in a year, your average fee, and the handling time each one currently consumes. Houses that have quietly stopped answering permissions requests because the handling cost exceeded the fee are foregoing income at a margin no other line in publishing matches.
Compare licence plus that time plus that foregone income against build cost plus annual maintenance. University presses usually reach the answer through permissions volume. Trade houses usually reach it through the fair list.
When buying beats building
If you are a small or mid sized house publishing under roughly fifty titles a year on a consistent contract template, buy. A rights module inside Virtusales Biblio, or Klopotek if your needs are broader, is proportionate, and the money is better spent on acquisitions and marketing. A well maintained spreadsheet is also a defensible answer at that size, and there is no shame in it.
Buy also if your primary need is title and product data rather than rights. Klopotek and Biblio are strong there and the rights layer comes along with it, so building a separate rights system to solve a metadata problem is the wrong purchase.
Build when two or more of these are true. Your backlist runs to thousands of titles across multiple contract generations and nobody can produce the availability picture without archaeology. You have acquired another house and inherited a rights database you cannot query. Your reversion answers take days and are inconsistent. Or you are being asked new licensing questions, whether podcast adaptation or machine learning use, and cannot report on where your backlist stands.
That last one deserves emphasis. Whether contractual silence favours the publisher or the author is a legal question for your counsel. Knowing which titles are silent is a data question, and publishers who could answer it quickly when those conversations began had a real commercial advantage over those who could not.
When you are ready to turn this into a specification, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. You keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- McKinsey found that tech debt can amount to 20-40% of the value of a company's entire technology estate before depreciation, and CIOs report that 10-20% of the budget for new products is diverted to resolving tech-debt issues. Source: McKinsey & Company (2020) →
- Deloitte reports that modern ERP implementations aim to deliver reduced manual effort, greater transparency, a single source of truth, and increased productivity, but many organizations do not capture the full expected benefits (a significantly lower ROI) without disciplined strategy, change management, and data readiness. Source: Deloitte (2024) →
- Flexera's 2025 State of the Cloud Report (survey of 750+ technical and executive leaders) found that 84% of respondents believe managing cloud spend is the top cloud challenge for organizations today, with cloud budgets already exceeding limits by 17%. Source: Flexera (2025) →
- One in four US employees report lacking career advancement opportunities; 48% of employees who participated in mentorship programs report high job satisfaction versus 29% of non-participants, and access to advancement opportunities ranges from 33% at organizations under 10 employees to 74% at those with 1,000+. Source: Gallup (2025) →
Frequently asked questions
How much does custom subsidiary rights and permissions software cost in total?
A first release covering the rights grid, contract and clause capture, option and expiry tracking, reversion rules and permissions intake runs $55,000 to $110,000 and ships in 10 to 14 weeks, based on Digital Heroes delivery experience. A fuller platform adding subrights income with agent splits and currencies, rights guide generation and an author portal runs $130,000 to $300,000 across 6 to 10 months.
A representative independent publisher with 4,000 backlist titles and three imprints lands at about $102,000 for the first release and roughly $268,000 for the full platform.
What does it cost to run each year?
Budget roughly 15 to 20 percent of build cost annually for maintenance and iteration, so $40,000 to $54,000 on a $268,000 platform. The recurring item unique to this category is adding a new contract generation and its clause behaviour every time your standard contract changes.
Add exchange rate data for multi currency reporting, document storage for contract scans and issued licences, portal support for external users, and the first year of verifying records migrated with confidence markers.
How long until the rights team can use it for a book fair list?
Ten to fourteen weeks to a first release. The practical test is whether the fair list becomes a query rather than an archaeology project, and that depends on capturing clause behaviour for your main contract generations, which needs the rights director's time in discovery.
Time the launch after a major fair rather than six weeks before one. That gives the team a full cycle to populate and verify before it matters.
Is Klopotek or Virtusales Biblio cheaper than building?
Considerably, and for a house publishing under roughly fifty titles a year on a consistent template they are the right choice. Split your renewal into core licence, the rights module if charged separately, seats and support, then multiply by twelve months.
The comparison turns when the same right behaves differently depending on which contract generation a title falls under, because a fixed rights taxonomy records that variation as a note and a note cannot be queried before a fair.
Why do contract generations drive the price so much?
Because each one changes how a right behaves. Reversion triggers, territory definitions and what counts as out of print all shift between templates, so a single rights table cannot hold them. Modelling the two most recent generations is $14,000 of discovery plus the clause model in the worked example.
Modelling three older generations is a further $20,000 in phase two. Handle the older ones as exceptions flagged for human reading in year one and you keep the first release near the bottom of its band.
Can software tell us when a title is approaching reversion?
Yes, and it is $18,000 in the worked example. Encode the contract's reversion test as an evaluable rule and run it continuously against sales data so titles approaching a threshold surface before the author's agent writes.
That turns reversion from a reactive scramble into a deliberate decision about whether to promote, reissue or let the right go. Contracts with older out of print definitions need particular care, since print on demand availability changes the answer.
Will permissions actually pay for itself?
Often, because permissions income is nearly pure contribution and the current cost is handling time. Self service intake with policy rules, a pricing schedule and automatic licence issuance for routine cases is $16,000 in the worked example.
Do the arithmetic with your own numbers: annual request volume multiplied by average fee, against the handling time each request currently consumes. University presses usually find this line alone carries a meaningful part of the case.
What happens to rights data we inherited from an acquired publisher?
Profile it before promising anything, then import with explicit confidence markers so nobody licenses a right on the strength of an unverified record. That is $30,000 in the worked example, including the verification workflow.
Prioritise verifying the titles that actually earn rather than working alphabetically. A migration plan written before anyone has looked at the data is a plan to import errors faster.
Who owns the code and the rights data if an agency builds it?
You should own the repository, the database and the cloud accounts, with the unrestricted right to hire another firm, agreed before kickoff. At Digital Heroes the publisher owns everything from the first commit.
This matters more here than in most categories. A rights grid is a register of assets accumulated over decades of publishing, and it should never sit in infrastructure a supplier controls.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
Should I pick Microsoft Dynamics 365 Business Central or build a custom ERP?
Pick Business Central if you already live in the Microsoft stack, your processes are close to standard, and around $80 per user per month for Business Central Essentials stays affordable at your headcount. Build custom when your revenue-driving workflow, such as custom manufacturing steps or unusual pricing logic, would need heavy extension work anyway. In our experience, once Dynamics customization quotes pass about $100,000 the custom option deserves a serious side-by-side.
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.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
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.
What should I prepare before contacting an ERP development agency?
Bring a list of your current tools and spreadsheets, a rough map of how an order or job moves through the company today, your user count by role, and the three problems costing you the most hours. You do not need a formal specification; a good agency writes that with you during discovery. Companies that arrive with those four things typically cut two to three weeks off scoping in our experience.
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.
Can a custom ERP integrate with the tools we already use, like QuickBooks or Shopify?
Yes, and keeping tools that already work well is usually the right call. The integrations we build most often are QuickBooks or Xero for accounting, Shopify or WooCommerce for orders, ShipStation for fulfillment, and Salesforce or HubSpot for CRM. A typical integration adds $5,000 to $15,000 to the build depending on how much two-way syncing the workflow needs.
What does it cost to maintain a custom ERP each year?
Budget 15 to 20 percent of the original build cost per year, so a $150,000 ERP needs roughly $22,000 to $30,000 annually for hosting, security patches, integration upkeep, and small improvements. Across Digital Heroes maintenance contracts, third-party APIs changing is the biggest recurring work item. That total still usually sits well under the license bill for a comparable NetSuite or Dynamics seat count.
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 .
