Regulatory Submission Services vs Software: Costs and Ownership

The deciding comparison is the cost and evidence required to produce the same accepted output. A software subscription does not include every person needed to operate it. An outsourced publishing quote does not necessarily include scientific writing, sponsor review, transmission or continuing archive access.

Calculate services, software and hybrid costs for the same workload

Download a working version of the twelve-package example below. Change volume, service rates and retained staff effort to compare first- and second-year costs. The starting figures are fictional USD assumptions, not vendor quotes. Scientific writing, strategy, taxes and financing are excluded; record extra scope and capacity constraints before selecting the cheapest model.

Download the editable calculator (XLSX)

Compare eligible publishing products after choosing the operating model

Plan a sponsor–CRO handback

This guide compares those operating models, then provides a worked cost example, a source handoff checklist, an in-house transition procedure and a provider exit checklist. The examples are fictional documentary exercises you can adapt; we have not run a vendor trial or produced a submission package for this article.

Disclosure: Assyro publishes this guide and is our first software evaluation recommendation for eligible FDA eCTD v4.0 workflows. That placement is an editorial preference, not an independent benchmark. Assyro does not currently support eCTD v3.2.2.

Services, software or hybrid: compare the operating responsibility

Start with the application, authority, format and submission history. FDA supports eCTD v4.0 for new CDER/CBER NDA, BLA, ANDA, IND and master file applications from September 16, 2024. Its current instructions still say forward compatibility is unavailable. An existing v3.2.2 lifecycle therefore cannot be treated as ready for conversion merely because a shortlisted tool supports v4.0. FDA eCTD instructions.

After confirming eligibility, use this operating-model comparison. These are procurement distinctions, not claims that every contract or software edition includes the same functions.

Separate six activities in every proposal: regulatory strategy, scientific writing, document formatting, submission assembly, technical validation/QC, and transmission with record retention. A provider might sell all six or only two. A platform might support several while your people remain responsible for decisions and operation.

For example, resolving an unsupported clinical interpretation is different from fixing a broken hyperlink. Give the scientific owner the first issue and the agreed document or publishing operator the second. Decide who identifies, corrects, reviews and releases each change. Without that allocation, both an internal team and a service provider can assume the other party owns the same unfinished task.

Concrete software and service scopes to evaluate

These examples illustrate purchasable scopes, rather than a market-wide ranking. Obtain an application-specific proposal and demonstration before treating any advertised capability as an accepted delivery commitment.

Assyro: evaluate first for eligible internally operated FDA v4.0 work

Assyro offers FDA eCTD authoring, validation, review and submission workflows, with eCTD v4.0 support. Evaluate it when your team wants to operate those activities and can supply the scientific reviewers and publishing owners. It is not a replacement for an existing eCTD v3.2.2 publishing workflow: that format is unsupported. Confirm the particular application and document scope before discussing a transition.

Use the demonstration to trace one approved source through review and the proposed submission workflow. Request the resulting package, validation evidence and review records that your process requires; confirm their availability, format and export terms. A screen demonstration alone does not establish that your operators can repeat the work or that every historical record can migrate.

This is a conditional software recommendation. It does not imply that Assyro supplies outsourced scientific writers, assumes your approval responsibilities or removes the need for specialist support. Keep any required service capacity separately scoped. A portfolio containing both a new eligible FDA v4.0 application and ongoing v3.2.2 work may reasonably retain different publishing arrangements.

Source: Assyro's product marketing demonstration screenshot, reviewed September 14, 2026; release unspecified. See Assyro authoring for product context. No document is selected and no execution result is shown. Use the image to discuss who operates the workspace, then request the package and records described above.

Celegence: scope writing and publishing as distinct services

Celegence describes Word formatting, PDF rendition, navigation aids, document QC and submission-level publishing. It also lists support for tracking and archiving acknowledgements and dossiers. Those are useful scope items to request explicitly in a publishing statement of work. Celegence publishing services.

Its separate writing offering covers areas including CMC, clinical and nonclinical regulatory documents. A team missing scientific writing capacity can therefore investigate a broader engagement; a team with approved content can ask for publishing alone. The existence of both offerings does not establish that both are included in a quoted fee. Celegence regulatory writing.

Ask which authority and format the delivery team will use, which document corrections are included, how urgent changes are charged, and what archive access survives termination. Request separate acceptance points for scientific approval and technical publishing so a completed formatting task cannot be mistaken for an approved scientific document.

EXTEDO: compare provider-operated publishing with a software proposal

EXTEDO describes a publishing service using its own tools, including document conversion, bookmarks and hyperlink checks. Secure client viewing and review access is optional. Specify that access if your reviewers need it; do not assume it accompanies every service engagement. EXTEDO publishing services.

Its current EXTEDOpulse Submission Publishing page describes assembly, viewing, validation, publishing and lifecycle functions, with eCTD v3/v4 support at the product-family level and eCTDmanager resources. A software proposal still needs the exact licensed product, deployment, authority profile and supported versions. EXTEDO Submission Publishing.

For a make-or-buy decision, request two scopes against your same workload: provider-operated delivery, and internally operated software with implementation, training and support. Sharing a vendor does not prove that service workspaces, licenses or history transfer automatically. Make those transfer conditions explicit before assuming the service can become an internal operation without rework.

Compare total cost using the same publishing workload

The following figures are illustrative assumptions in USD, not vendor prices, quotes or market averages. They model twelve comparable publishing work packages over one year. Each starts with approved scientific content; scientific writing and strategy are outside all three totals and must be added equally if retained, or separately priced if their scope changes.

Assume each work package has the same agreed document volume, regional scope, correction allowance, transmission responsibility and records deliverable. A large original application and a small lifecycle update should not count as interchangeable units. Software eligibility has already passed in this example; the internal-software column is not an Assyro quote or a claim of legacy-format support.

The hybrid's lower service unit price is an explicit assumption: internal preparation absorbs work that the full service would perform. Its higher internal hours reflect that allocation. If the provider does not offer that narrower scope at that price, replace the number. Do not count the same formatting activity as both outsourced and internal, or remove it from both columns.

The $100 hourly figure represents assumed loaded labor cost, not a consultant billing rate. The example excludes taxes and financing. Setup is assumed to occur once; subscriptions, backup and unit rates are assumed to remain unchanged. Those assumptions yield second-year totals of $84,000 for services, $90,000 for internal software and $84,000 for hybrid, at the same volume.

The $24,000 license looks cheaper than the $72,000 service line. Once internal operation and setup are included, software costs $14,000 more in year one in this scenario. That is the practical error a license-versus-service comparison can conceal.

Now change volume to twenty-four equivalent work packages, keeping the assumed unit rates and fixed costs unchanged. Double each model's variable service fees and staff hours. First-year totals become $174,000 for the service, $164,000 for internal software and $162,000 for hybrid. Internal software now appears less expensive than the service, but that conclusion depends on capacity and effort assumptions.

Increase internal publishing/QC effort by 25% at that higher volume: 960 hours becomes 1,200 hours. The additional $24,000 raises internal software to $188,000, reversing the apparent advantage. This is a sensitivity calculation, not a prediction that either effort estimate is typical.

Before deciding, replace the assumptions with your document counts, actual operator estimates and comparable written quotes. Ask about included revision rounds, rush fees, profile updates, support hours, storage/export charges and minimum commitments. Add temporary overlap during a transition. If a provider's fixed fee includes surge coverage, establish the reservation and response terms; if an internal plan relies on one employee, price credible backup.

Keep the financial and operational conclusions separate. The cheapest model may lack capacity for your filing window. An affordable internal license cannot compensate for an unsupported format, an untrained backup or unavailable submission history.

The eCTD software cost calculator separates recurring vendor cash from implementation and internal labor.

Using regulatory authoring software with outsourced publishing

Internal authoring and external publishing work together when the publisher receives a controlled, accepted source set. Buying an authoring tool does not establish that boundary. Agree which system holds the approved source, which rendition is authoritative, and who may change each file after handoff.

Create a handoff record with an application identifier, authority, format, intended submission, file inventory and freeze time. For every document, record its source revision, approval evidence, intended placement and correction owner. If the provider creates the submission PDF from an editable document, record that responsibility explicitly. If you supply the approved PDF, define which technical changes the provider may make and which require renewed sponsor review.

Use four outcomes: pass means the stated evidence has been inspected; fail means a known requirement is unmet; unknown means evidence is missing; N/A requires a documented reason. Unknown is not permission to proceed. The parties can agree to preparatory work on incomplete inputs, but should distinguish that work from acceptance of the final source set.

Here is a filled handoff record for fictional Harbour Therapeutics. It is a documentary example, not the result of a software test. Harbour retains scientific writing and approval; its publisher performs agreed PDF preparation, assembly and technical QC.

The publisher can inspect this inventory and identify work to schedule. It cannot infer approval from a filename containing “final.” Harbour resolves the two source issues, issues a new handoff revision and asks the publisher to acknowledge that specific revision. Do not silently replace a file in a shared folder while leaving the original inventory unchanged.

After publishing, reconcile the delivered document set against the accepted inventory. Record approved technical changes, outstanding findings and the release decision. A technically valid package could still contain the wrong approved revision if that comparison is skipped. Use the eCTD submission checklist for the wider readiness and delivery sequence.

Set the commercial consequence at this same boundary: when does the publishing clock start, which correction rounds are included, and how is a late scientific change priced? Both sides then know whether a delay arose from an unaccepted source set, a publishing defect or a new sponsor request. That evidence makes the hybrid model controllable without assuming either party owns all subsequent rework.

How to bring eCTD publishing in-house

Bring publishing in-house by accepting an operated process before ending the external one. A training certificate, installed license or successful document import is useful evidence, but none alone demonstrates that your team can produce and control the next submission.

1. Select a bounded workload. Choose an application and representative submission whose authority, format, history and deadline fit the proposed tool. Document what will remain outsourced. Harbour, for example, could evaluate internal publishing for a new eligible FDA v4.0 program while retaining its existing arrangement for a v3.2.2 program. Do not make legacy conversion a hidden prerequisite of the pilot; follow the applicable eCTD v4.0 migration constraints.

2. Agree the transfer inventory. Obtain the approved sources, submitted packages, relevant history, document identifiers, validation reports, correction records and procedural instructions needed for the selected workload. Separate viewable archives from data that the new software can actually use for continued publishing. Ask the outgoing provider to identify unavailable or licensed components before assigning a migration completion date.

3. Name operators and release owners. Assign a primary publisher, a trained backup, a scientific/content approver and the person who authorizes release. Record technical QC responsibilities and escalation coverage. Roles can be combined where your process permits, but overlapping labels must not disguise unavailable time. Reserve time for setup, corrections and a backup-operated rehearsal rather than assuming those activities fit around normal review duties.

4. Run a controlled parallel rehearsal. Use the same approved input inventory and agreed historical context for provider and internal preparation. Keep the rehearsal separate from authorized production transmission: two prepared outputs do not justify two live submissions. Record the tool version, authority profile, validation criteria version, operator, inputs and output locations. The article supplies this procedure; it does not claim Harbour or a vendor has executed it.

5. Compare the outputs against requirements. Inspect whether every required document and approved revision is present, navigation works, application and submission metadata are correct, and the required historical references are handled. Compare validation findings and their disposition, not just a green summary screen. Require accessible reports and release records. Do not demand byte-identical outputs when tools legitimately create different technical metadata; require explained differences and the same agreed content and applicable technical outcomes.

6. Accept operation, including failure handling. Give the backup operator a defined correction and ask them to repeat the affected preparation and review steps. Establish how support is reached and how an unresolved publishing issue returns to the current delivery route. Preserve the provider arrangement until the agreed acceptance evidence and retained records are complete; include the overlap in the cost model.

Harbour's hypothetical decision record illustrates the stop condition: the internal operator can assemble the selected input set, but the backup has not completed the correction exercise and the historical-record export is unverified. The decision is not accepted for transition, with named owners for both gaps. It is not a failed scientific submission or proof that the software is unsuitable. Once the missing evidence exists, assess the same criteria again instead of relaxing them because the service termination date is approaching.

Use the implementation planning workbook to assign the work that moves from the service provider to your team.

Regulatory publishing vendor transition checklist

Changing publishing providers is a separate decision from bringing publishing in-house. The incoming provider may supply the operators and tools, but you still need to establish what leaves the outgoing service, who can access it and how the next submission will proceed.

Begin the exit inventory before issuing a termination date. Request an application-by-application list of records, formats, delivery locations and any dependencies on the old provider's licenses. Assign a receiving owner for each category. A statement that “all data belongs to the client” does not, by itself, identify which usable exports and ongoing access are included in the contract.

Archive services are a real purchasable scope, not necessarily a benefit that disappears when publishing is outsourced. Freyr, for example, describes managed archiving for final packages, gateway receipts and authority correspondence. That description does not establish your entitlement to free exports or post-termination access; those terms still belong in the agreement. Freyr regulatory publishing archive services.

Treat submission accounts separately from dossier files. FDA instructs CROs, agents and consultants to register under their own company and obtain client authorization. Plan the incoming operator's authorized access; do not put the outgoing provider's shared password on the transfer checklist. FDA account instructions for CROs, agents and consultants.

Retain the applicable acknowledgement chain rather than a single screenshot reading “sent.” FDA distinguishes gateway upload and center transmission/response stages, with applicability depending on the submission route. Those records document delivery processing; they do not resolve an incorrect scientific source or establish scientific approval. FDA submission acknowledgements.

Complete the checklist using the same pass, fail, unknown and justified N/A states as the source handoff. In Harbour's fictional provider change, submitted packages and reports are received and reconciled: pass. The archive link is documented to expire on termination while the agreed export is missing: fail. The incoming provider's authorization record has not been supplied: unknown. A workspace transfer is N/A only if the signed scope excludes it and the required usable records are otherwise accepted.

Harbour's regulatory operations lead therefore withholds handover sign-off. The outgoing provider must deliver the agreed archive output, the receiving owner must demonstrate retrieval from that output, and the account administrator must establish the incoming route. Schedule a retrieval check under the intended post-exit access conditions; merely opening the old provider's link while its contract remains active does not prove continuing access.

Keep termination and acceptance as separate recorded events. Assign unresolved corrections and support obligations through the transition, then have the receiving owners sign the completed inventory. If access or continuity remains unknown, resolve the gap or explicitly maintain the current arrangement before ending the service.

The vendor-switching acceptance pack adds the inventory, rehearsal and fallback records needed before cutover.

Make the decision on a representative delivery

Ask each shortlisted option to price and demonstrate the same approved source set, publishing responsibilities, correction allowance and records deliverable. Use the pharma vendor selection framework to document the evidence and decision owners, and the regulatory publishing software guide for the narrower tool comparison.

Evaluate Assyro first where an internally operated FDA v4.0 workflow fits; bring the completed scope to an Assyro evaluation, and retain a compatible route for unsupported v3.2.2 work. Choose services when their contracted capacity and expertise solve your actual staffing gap. Choose a hybrid when source control stays internal and the accepted publishing handoff is clear. In every model, require usable outputs and continuity evidence before changing the operating arrangement.

Request Assyro pricing for the retained work and supported workflow so the software proposal can be compared with the same service scope.