eCTD Submission Publishing Software: Licence Lorenz docuBridge, or Build Your Own Publisher?
Sequence volume decides this and the number is roughly 300 a year.
On this page
Sequence volume decides this and the number is roughly 300 a year. Below it, licence Lorenz docuBridge, Extedo eCTDmanager, GlobalSubmit or Vault Submissions Publishing, or use a publishing service provider, and stop: a build will never pay back at that volume and the specification maintenance burden alone outweighs any saving. Above it, or if you are a service provider publishing for multiple clients where per seat licensing scales against you with every new client, a build starts earning. Most sponsors publish well under 300 sequences a year and should licence.
When is off the shelf genuinely the right call here?
If you publish a handful of sequences a year, licence a packaged publisher or hand the work to a publishing service provider. Lorenz docuBridge and Extedo eCTDmanager are mature, GlobalSubmit and Vault Submissions Publishing are credible alternatives, and all of them are maintained against specification and validation criteria changes you would otherwise have to track yourself. That maintenance is the quiet value in the licence fee and it is easy to underprice when comparing.
The same applies to most mid sized sponsors publishing in the major regions. These tools work. Building an equivalent publisher is a poor use of budget when the vendor already carries the burden of following each authority's release schedule, and the electronic Common Technical Document specification is not a stable target you implement once.
Buy and stop, too, if your pain is upstream of publishing. Most technical rejections trace back to a document that was never normalised properly rather than to a backbone the tool generated. If your authors produce documents with broken bookmarks, missing searchable text and inconsistent page setup, that is a document preparation problem and a new publisher will not fix it.
The test that settles it: count your sequences for the last two years and price your per sequence fees or licence renewals honestly, adding portable document format toolkit licensing to both sides of the comparison because it recurs either way. If the total is comfortably below a build plus 18 to 25 per cent annual maintenance, licence and move on.
When does a custom build actually pay off?
Two or more of these need to hold before the case is real, and all of them are volume arguments rather than feature arguments.
You publish more than roughly 300 sequences a year, at which point the per sequence economics change shape. You are a service provider publishing for multiple clients and need tenant separation, per client document code mappings, per client audit boundaries and throughput reporting that no sponsor oriented tool provides. You file in many markets and thirty of them are handled by a manual process outside your tool, because your vendor covers the major regions and the long tail is where your regulatory affairs team is quietly spending its evenings. Your remediation burden before every filing is measured in weeks of staff time. Or your publishing volume has grown to the point where per user licensing constrains how many people can help during a filing crunch, which is a genuinely absurd place to be and one we hear about often.
The structural reason is that packaged publishers are priced and designed for a sponsor filing a moderate number of sequences into the major regions. That is the correct design for their market. A service provider's economics run the opposite way: their margin is throughput across clients, and per seat licensing scales against them with every new client won.
The remediation trigger deserves separate attention, because it is the one that justifies partial building. If your team spends weeks fixing documents before each filing, the answer is an intake checking layer, not a new publisher.
How do they compare on the things that matter in this industry?
- Document intake checking. Publishers publish. Returning compliance findings to the author within minutes, covering security settings, fonts, bookmarks, hyperlinks, page setup, file naming and searchable text, is where your team's hours actually go and it is thinly served.
- Long tail regions. Vendors cover the major markets thoroughly. Each additional regional module 1 is roughly $55,000 of work whoever does it, so the markets your tool ignores are the markets you handle by hand indefinitely.
- Lifecycle correctness. New, replace, append and delete operations tracked so the cumulative current view stays correct three years and forty sequences later is the hard part of this category, and it is the thing to test hardest in any evaluation.
- Validation criteria versioning. Different regions and different active submissions sit on different criteria versions simultaneously. Treating rules as data with versions and effective dates, rather than as code, is what makes that manageable.
- Multi client separation. Tenant isolation, per client document code mappings and per client audit boundaries are a different architecture from a single sponsor tool, and no sponsor product is built for it.
- Per user economics. Licensing that limits who can help during a filing crunch is a real operational constraint rather than a line item, and it worsens as volume grows.
What does total cost of ownership look like at your scale?
In Digital Heroes delivery experience the publisher runs $120,000 to $260,000 and ships in 16 to 22 weeks. A representative first release breaks down as discovery, granularity and document code mapping at $16,000, document intake and normalisation at $40,000, leaf and lifecycle operation management at $46,000, backbone generation for one region at $34,000, the validation engine at $38,000 and sequence assembly and packaging at $24,000. That totals $198,000, which is typical for a sponsor publishing in one region.
The full platform runs $300,000 to $800,000 phased over 12 to 20 months. Each additional regional module 1 is roughly $55,000. Gateway submission with acknowledgement processing is about $80,000, including the negative acknowledgement path that tells a publisher what to fix rather than that something failed. A cumulative review viewer is about $70,000, document management integration roughly $55,000, and computer system validation of the platform itself typically adds 20 to 30 per cent on top of engineering.
Two costs sit outside every quote and belong in the comparison. Portable document format toolkit licensing recurs whether you build or buy, so get it quoted during scoping. And publisher training plus a parallel run, because your publishers know the current tool intimately and will be slower on a new one for a full submission cycle.
Ongoing cost is 18 to 25 per cent of build value a year, driven less by your change appetite than by authorities publishing new validation criteria on their own schedule. Add archive integrity at $8,000 to $30,000 a year, because every sequence you ever sent must remain retrievable and identical to what was transmitted.
What does the hybrid look like, and when is it the honest answer?
In this category the hybrid is not a compromise, it is the recommendation for most sponsors who arrive with a genuine problem.
Build the intake checking layer and keep your publisher. Authors submit documents, the layer checks them against your granularity rules and technical requirements within minutes and returns findings to the author, and only compliant documents reach your existing publishing tool. That removes the remediation weeks before every filing, which is where the staff time actually goes, without touching the part of the process that already works and is already validated.
The sequencing argument is strong. Building intake first gets you most of the benefit before the largest spend, it does not disturb an active filing calendar, and it is testable against the documents you already have. If it turns out your remediation burden was smaller than it felt, you have learned that for a fraction of a platform budget.
The second hybrid is skipping the gateway. Producing a validated package that a service provider transmits is entirely legitimate and defers $80,000 until sequence volume justifies owning the connection, along with the certificate and credential renewals that come with it.
The third is one region first. Publish to your home authority only, prove lifecycle handling across ten real sequences, then add regions at roughly $55,000 each. That is the single largest saving available in this category and it also derisks the hardest part of the build.
Which should you choose, by operator size and stage?
Small sponsor, a handful of sequences a year: licence docuBridge or eCTDmanager, or outsource publishing entirely. Nothing else here applies and a build would never repay.
Mid sized sponsor, major regions only, remediation is painless: licence and configure. Your publisher is doing its job and the specification maintenance you are renting is worth more than it costs.
Mid sized sponsor spending weeks on document remediation before every filing: build the intake checking layer, keep the publisher. That is the highest value partial build in this category and it does not put your filing calendar at risk.
Sponsor filing into many markets with thirty handled manually: build the module 1 handling for the long tail while keeping your vendor for the majors. Budget region by region rather than assuming the second is cheaper because the first exists.
Above roughly 300 sequences a year: build the publisher. Start with one region, prove lifecycle across ten real sequences, skip the gateway initially and defer the viewer, which is useful but not on the critical path for a compliant submission.
Publishing service providers: build, and design tenant separation from the first architecture conversation rather than retrofitting it. Per seat licensing scales against you with every client won, and your margin is throughput, which is precisely what a sponsor tool is not built to optimise. Per client document code mappings and audit boundaries belong in the same first design pass, because both are painful to introduce once real client history exists.
If you want a second opinion before signing anything, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The Standish Group 1995 CHAOS Report found only 16.2% of software projects fully succeeded; success varied sharply by size, with large-company projects succeeding about 9% of the time versus far higher rates for small projects - best treated as an industry survey, not an audited dataset. Source: Standish Group (1995) →
- McKinsey's Developer Velocity research finds best-in-class tools are the top contributor to software business success, yet only about 5% of executives ranked tools among their top-three software enablers, signaling underinvestment in developer tools (this finding originates in McKinsey's Developer Velocity study rather than the linked generative-AI article). Source: McKinsey & Company (2023) →
- Brandon Hall Group research on onboarding reports that done well, structured onboarding drives measurable gains in new-hire productivity, employee engagement, and retention; the page notes 41% of organizations experience greater than 5% turnover among new hires. Source: Brandon Hall Group (2024) →
- IBM frames first-time fix rate as a core field service KPI, noting the industry average sits around 80% (roughly one in five jobs needs a return visit). Correction: IBM cites best-in-class providers at 89-98%, not '85%+'. Source: IBM (2024) →
Frequently asked questions
What does it cost to move off docuBridge once we have years of sequences in it?
The difficulty is legacy lifecycle history rather than the software. Importing existing sequences correctly, so the cumulative current view stays valid across products with long publishing histories, is genuinely hard work and should be scoped as its own piece.
Do not attempt it during an active filing window. Move product families at natural boundaries, validate the current view against the old tool before you rely on it, and keep the old system readable for as long as your retention obligation runs.
What if our publishing vendor changes per user licensing?
Per user licensing is the constraint that pushes most operations towards a build, because a filing crunch is exactly when you want more hands and the licence says otherwise. Model it against peak concurrent publishers rather than your average headcount.
Owning the publisher removes that ceiling. For a service provider it removes it permanently, since every new client would otherwise add seats before it adds margin.
How long does a first release take before it publishes a real sequence?
Sixteen to twenty two weeks for the publisher covering intake, leaf and lifecycle management, backbone generation and validation for one region, in our delivery experience.
Then budget a full submission cycle of reduced throughput while publishers learn the new tool. That reduction is real and predictable, and discovering it during a filing window is the worst possible time. Plan it deliberately rather than hoping your team absorbs it.
Is Extedo eCTDmanager enough if we file in three regions?
For three major regions with moderate volume, almost certainly. It handles the regional module 1 structures and follows validation criteria updates, which is exactly the burden you would otherwise carry yourself at roughly $55,000 per region to implement and a standing allowance per region to maintain.
The case changes when your long tail markets are handled outside the tool by hand, or when volume passes roughly 300 sequences a year. Both are counted rather than argued.
Can we build only the document checking layer and keep our publisher?
Yes, and for most sponsors with a real problem this is the right answer. Automated compliance checking returned to authors within minutes covers where the staff hours actually go, and most technical rejections trace back to documents rather than backbones.
It also carries the least risk. It sits before your validated publishing process rather than replacing it, so an active filing calendar is undisturbed and you can stop at any point without stranding anything.
Do we need the gateway connection in phase one?
No. Producing a validated package that a service provider transmits is entirely legitimate and defers roughly $80,000 until sequence volume justifies owning the connection.
Owning it also brings certificate and credential renewals into your operation. Small money, real disruption if one lapses on the day a sequence is due, so put those renewal dates in the same calendar as your filing dates from the beginning.
Is a review viewer worth building when the authority has one?
The authority's viewer is sufficient for the authority. It does not answer the question your own regulatory team asks weekly, which is what the current approved version of a given document is across forty sequences and three regions.
Today that is answered by somebody opening folders. A cumulative viewer at roughly $70,000 removes that, and it is the second band feature internal reviewers request most. It is useful rather than critical, so defer it if budget is tight.
Who owns the validation rule set and the archive if an agency builds this?
You should own the repository, the validation rule set, the infrastructure accounts and the right to hire anyone else to continue, agreed before kickoff. At Digital Heroes the code is yours from the first commit.
Ask specifically about the archive. Every submitted sequence must remain readable and reconstructable long after any tool that produced it has been retired, so it belongs in storage you control with a retention policy you set.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
Our developer disappeared mid-project. Can another team pick up the code?
Yes, this is a routine engagement, provided the code exists somewhere you can access, so your first move is securing the repository, hosting, and domain credentials today. A takeover starts with a one to two week paid code audit that ends in one of three verdicts: continue the build, keep the design but rebuild the weak parts, or start over. Digital Heroes has inherited enough projects to say plainly that sometimes the rebuild is cheaper than the rescue, and an honest agency will tell you which one you have before taking your money.
How do I work out whether custom software will pay for itself?
Do the arithmetic on hours before anything else: if the system saves three staff eight hours a week at a $35 loaded hourly cost, that is about $43,700 a year against, say, a $70,000 build plus 15 to 20% annual maintenance, a payback around two years. Add revenue effects only if you can name them specifically, like faster quotes or fewer abandoned orders, not as vague growth. In our delivery experience the businesses that see payback inside 24 months are the ones automating a process they already measure.
Couldn't I just build my app in Bubble or another no-code tool instead of hiring an agency?
For validating an idea with real users, yes, and we tell clients that honestly. The walls come later: Bubble apps cannot be exported as code to run anywhere else, performance drops on complex data operations, and usage-based pricing climbs as you grow. A meaningful share of Digital Heroes custom builds are rebuilds of no-code MVPs that proved the business worked, which is the system operating as intended: validate cheap, then build the version that scales.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
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.
If an agency builds my software, who actually owns the code?
You should own everything, assigned in writing: the contract transfers full IP to you on final payment, the code lives in your GitHub organization, and hosting runs in cloud accounts you control. The red flag is a proposal that mentions the agency's proprietary platform or framework, which usually means you are renting, not buying. Digital Heroes structures every build this way precisely so a client can fire us and lose nothing but the relationship.
Who can build a custom software system?
Digital Heroes builds custom 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 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
More from Oliver.
Senior Account Director · UK · London · 3 posts on the site
Published · Last updated .
