How to Hire a Subsidiary Rights and Permissions Software Development Company
Hand each firm one real reversion clause and watch what they draw. A developer who asks what your out of print definition says has worked in publishing. One who proposes a date field has not.
On this page
Hand each firm one real reversion clause and watch what they draw. A developer who asks what your out of print definition says has worked in publishing. One who proposes a date field has not. Expect $55,000 to $110,000 for a first release covering the rights grid, clause capture and permissions intake, rising to $300,000 with deals, splits and a portal.
Your backlist is an asset register nobody has audited. Thirty years of contracts across at least three template generations, a database inherited from a house acquired in 2011 that no one can query, and a colleague who retired holding a quarter of it in her head. Hiring a developer for this is closer to commissioning a title search than commissioning software, and the first question is not what the interface looks like. It is whether anyone can say which translation rights are actually free before the next book fair.
The category is hard to buy because vendors demo the rights grid, and the grid is the output. The input is your clause library. Your contracts changed in 2006, again in 2014, and again when audio became serious, so the same right behaves differently depending on which generation a title falls under. A system with a fixed rights taxonomy expresses that as a note in a field, which is how a fortnight of archaeology becomes a permanent operating cost.
What a rights and permissions development company actually does
The grid, the alerts and the fair list are what you see. The engineering sits under them.
Separating the right from the clause that governs it, so a title links to a contract, a contract belongs to a template generation, and each right record carries the clause reference defining its scope, its reversion trigger and its split. Making the taxonomy extensible, with unaddressed as a first class state alongside granted and reserved, because podcast adaptation and text and data mining were not contemplated by a contract signed in 2009 and you need to report on where the position is silent. Encoding reversion tests as evaluable rules run continuously against sales data, so a title approaching a threshold surfaces before the agent writes, which turns a defensive reply into a deliberate decision about whether to reissue, promote or let it go.
Then the commercial layer. Permissions intake with rules for extract size, fee schedule, third party illustration checks and automatic licence issuance for the routine cases, so a coursepack request stops costing more to handle than it earns. Deal records holding advance, royalty terms, split percentages, co agent, currency and withholding position, feeding your existing royalty system rather than replacing it. And the migration itself, which is a research task before it is a data task.
What it really costs in 2026
| Scope | Cost | Timeline |
|---|---|---|
| Rights grid with extensible taxonomy, contract and clause capture, options and expiries, reversion evaluation, permissions intake | $55,000 to $110,000 | 10 to 14 weeks |
| Adding subrights deal and income management with agent splits, currencies and withholding | $110,000 to $200,000 | 5 to 8 months |
| Full platform with rights guide generation, author and agent portal, royalty and title system integration | $200,000 to $300,000 | 6 to 10 months |
| Support and clause library maintenance | 15 to 20 percent of build per year | Retainer |
Two costs sit outside the quote and inside the project.
Contract archaeology. Somebody has to read the contracts. Modelling one template generation takes a rights person and a developer sitting together for days, and you have at least three generations plus whatever arrived with an acquisition. Firms price the software and assume the clause rules will be handed over as a document. They will not exist. Put your rights director's time into the plan and expect discovery to be mostly reading, with the payoff that the reading only happens once.
Withholding tax and currency. A translation advance from a foreign publisher arrives net of withholding, splits with the author at a contractual rate, may split again with a co agent, and has to land in the right royalty period against the right title. Quotes call this multi currency support. It is tax treatment, and getting it wrong is an author relations problem before it is an accounting one.
Signals of a strong partner
- They ask about your out of print definition first. That clause is the crux of reversion, and definitions written before print on demand behave very differently from ones written after.
- They propose a clause library keyed to template generations. Not a rights table with a notes column, which is where every legacy system ends up.
- They want to profile the inherited database before promising a migration. Mapping what is trustworthy and importing with confidence markers beats a clean migration promised unseen.
- They treat silence as a state. Being able to list titles where a right is unaddressed is a commercial advantage the moment a new licensing category appears.
- They plan to feed your royalty system rather than replace it. Deal truth in the rights platform, royalty accounting where it already works, is the proportionate design.
- They ask how many imprints and territories you run. Different imprints with different practices is real modelling work and should be priced as such.
- They will tell you a spreadsheet is fine. Under about fifty titles a year on a consistent template, a well kept grid plus your title management system is proportionate and they should say so.
Red flags
- Reversion modelled as a date field. Modern clauses define reversion by condition, and a date field puts you back to reading contracts within a year.
- A fixed rights taxonomy. If a new right category needs a developer, you will be late to every licensing conversation that matters.
- A clean migration promised before anyone has looked at the acquired database. Records that were never verified will get sold against.
- No concept of marking a right unsellable. Selling a right you no longer hold is the error in this field that costs money and reputation together.
- Splits treated as a single percentage. Co agents, territories and withholding make that number wrong more often than it is right.
Questions to ask on the first call
- Model a reversion clause on the whiteboard. What do you need to know about our out of print definition?
- Our contracts changed in 2006, in 2014 and again for audio. How does that live in your model?
- What is the state of a right our contract never mentions, and can we report on that category across the backlist?
- We inherited a database from an acquisition. What is your approach before you migrate any of it?
- How do we produce a list of free translation rights by language, and how long does that query take?
- A licensee lets a term lapse. What marks the right available again, and what prevents us selling one that reverted?
- A permissions request for two pages in a coursepack arrives. Which of those get priced and issued without a human?
- Where does a co agent split with foreign withholding live, and how does it reach the author's statement?
- Who owns the repository, the clause library and the rights data, and how do we export all of it?
A simple way to decide
Pay for a discovery phase before you commission a build. Two to three weeks, paid, ending in a written specification you own: the rights taxonomy including the categories your contracts never named, the clause behaviour for each template generation, the reversion tests expressed as rules, a profile of the inherited data with confidence levels, the permissions policy as pricing logic, and a first release limited to translation and audio rather than the whole grid. Send it to three firms and compare like for like.
Digital Heroes has delivered more than 2,000 projects, writes a product requirements document before any code, and hands the client the repository from the first commit, which matters here because a rights grid is an asset register accumulated over decades. We are the wrong firm if you publish under roughly fifty titles a year on a consistent contract template, because a rights module in your existing title system plus a disciplined grid will serve you and the money belongs in acquisitions. We are the right firm when nobody can produce the availability picture without archaeology.
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.
- 48% of private companies cite integration with legacy systems or technical debt as a top obstacle to realizing the full value of their digital and AI investments (behind data quality/availability at 72% and gaps in AI fluency or technology talent/leadership at 53%). Source: Deloitte (2026) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- The median annual wage for U.S. software developers was $133,080 in May 2024, and employment is projected to grow 15% from 2024 to 2034 - a core input to any in-house build-vs-buy TCO model. Source: U.S. Bureau of Labor Statistics (2024) →
- The global point-of-sale terminal market is projected to reach approximately $181.47 billion by 2030, growing at an 8.1% CAGR from 2025 to 2030, driven by digital payment adoption and demand across retail, restaurant, and hospitality sectors. Source: Grand View Research (2025) →
Frequently asked questions
How much does it cost to migrate a rights database inherited from an acquisition?
Budget $15,000 to $50,000 depending on how much of it can be trusted. The work is profiling before importing: establishing which records were verified against a contract, which were typed from a spreadsheet, and which contradict the paper. Import everything with an explicit confidence marker so nobody licenses a right on the strength of an unverified row. A migration quoted without a profiling phase is quoting an assumption.
Who owns the rights data and the clause library if an agency builds the system?
You should own all of it without qualification. Repository in your account from the first commit, hosting in your name, and full assignment of source, documentation and data on payment. The clause library is the valuable part, because it represents your rights director and a developer reading decades of contracts together. Losing access to that would cost more to rebuild than the original software did.
Can software tell us when a title is approaching reversion?
Yes, if the reversion test is encoded as an evaluable rule against sales data rather than stored as a date. The system then flags titles two royalty periods before they hit a threshold, which changes the conversation entirely: you decide deliberately whether to promote, reissue or let the right revert cleanly. Answering an agent's letter from a standing start is how houses lose titles they intended to keep.
What happens if we sell a right that has already reverted?
It is the most expensive routine error in the field, costing money and the author relationship at once. The system needs to mark reverted rights unsellable everywhere immediately, not just note the reversion on the contract record. Ask any firm you shortlist how a reversion propagates to the fair list, the rights guide and any agent facing view, and what physically prevents a sale being recorded against it.
Should we replace our royalty system as part of this?
Almost never. Royalty systems handle sales royalties competently and replacing one is a far larger project than the value it returns. The proportionate design keeps royalty accounting where it is and puts deal truth in the rights platform: advance, terms, splits, co agent, currency and withholding attached to the licence, feeding the royalty run instead of being transcribed from a spreadsheet at statement time.
Can permissions be handled without a person reading every request?
The routine ones, yes. Self service intake where the requester picks the title and describes the use, checked against the rights position, extract size policy and a fee schedule, issuing a licence with a reference for anything inside policy. Anything unusual, an embedded third party illustration, an oversized extract, an author approval requirement, routes to a human. That split is what turns permissions from a loss maker into a modest income line.
What is the difference between a rights management system and a title management system?
Title management holds product and metadata: the book, its formats, its identifiers, its distribution. Rights management holds what you are contractually permitted to sell, to whom, in which language and territory, and until when. Klopotek and Biblio are strong on the first and carry a rights layer along with it. The strain shows when your contracts across several generations do not fit the assumed shape.
How long until the rights team can use it to build a fair list?
Ten to fourteen weeks to a first release covering the grid, clause capture, options and reversion evaluation, which is enough to produce a fair list for translation and audio. The whole backlist takes longer, because loading it is a reading exercise rather than an import. Most houses model the last two contract generations properly, treat the older ones as exceptions, and grow coverage between fairs.
Do we need an author or agent portal in the first release?
Not usually. A portal looks simple and carries real access control and data protection work, since agents must see their own clients and nobody else's. Ship the internal grid and the permissions intake first, prove the data is trustworthy, then open a view outward. Opening a portal onto a grid you do not yet trust simply distributes the uncertainty to the people best placed to notice it.
How do we know where our backlist stands on rights that did not exist when contracts were signed?
Only if the system distinguishes explicitly granted, explicitly reserved and unaddressed, and can report on the third across the whole list. Whether silence favours the publisher or the author is a legal question for your counsel and it varies by jurisdiction and grant language. The software question is narrower: can you produce the list of titles where the position is clear and the list where it needs review, quickly.
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.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
Why do companies replace NetSuite with custom software?
The three reasons we hear most at Digital Heroes are per-user license growth, SuiteScript customizations that became fragile, and workflows the platform cannot model without workarounds. A company adding 50 users to NetSuite takes on roughly $59,000 per year in extra licenses at the commonly quoted $99 per user rate, which is often the moment the custom math starts winning. Replacements usually keep the accounting structure intact and migrate module by module.
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 does it cost to keep custom software running after launch?
Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
Can a custom ERP meet compliance requirements like SOC 2 or GDPR?
Yes, and often more cleanly than a shared SaaS platform because you control exactly where data lives and who touches it. The build includes role-based access control, full audit logs, encryption at rest and in transit, and data residency in whatever region your regulator requires. If you need SOC 2 attestation, tell the agency before development starts, since audit logging is far cheaper to design in than to bolt on.
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 .
