Captioning and Subtitling Workflow Software: Buy Minutes from a Vendor, or Build the Routing Engine
Ask one question: are you a content owner or a service operation? If you send work out and receive files back, buy from a vendor and build nothing, whatever your hours per year.
On this page
Ask one question: are you a content owner or a service operation? If you send work out and receive files back, buy from a vendor and build nothing, whatever your hours per year. If assignment decisions across your own linguists, freelancers and two or three vendors are made by a person reading a spreadsheet, and you deliver into three or more platforms with conflicting style rules, the routing engine is your operation and nobody sells it. Most brands and broadcasters reading this are content owners and should buy.
When is off the shelf genuinely the right call here?
3Play Media, VITAC and Verbit are service businesses. You send them media, they send back files, and they are good at that. Telestream sells tooling that does serious work on the encode and conform side. If your relationship with captioning is transactional, one of these is the correct answer and a build would be a distraction from whatever your business actually is.
Buy, and stop reading here, if this describes you:
- You are a content owner rather than a captioning or localisation vendor.
- Your delivery footprint is one platform, or two, in one or two languages.
- You send a few hundred hours a year outward and receive files back on a shared tracker.
- Your content profile is clean single speaker material, where machine transcription with human correction fits well.
- Nobody in your organisation currently spends their week deciding who gets which asset.
Verbit is a reasonable purchase where machine transcription with human correction suits your content, and it will be cheaper than anything you commission. Below roughly $45,000 of build spend you are not buying a workflow system anyway, you are buying a better tracker: a job board with states and assignees that replaces the colour coded spreadsheet. That genuinely helps a coordinator, and some operations should buy exactly that and stop, because it does not validate a file, measure quality or know what a platform will reject.
When does a custom build actually pay off?
The build case is about routing complexity, not hours. Two or more of these makes it real:
- You run your own linguist or vendor pool and assignment decisions are made by a person reading a spreadsheet with forty columns.
- You deliver into three or more platforms with conflicting style specifications, so the same asset needs different reading speeds and character counts per destination.
- You have an accessibility coverage obligation across titles, territories and languages that you currently prove by manual audit.
- You are a captioning or localisation vendor yourself, in which case the operations system is your margin rather than an overhead.
- Your rework rate on platform rejections is high enough to put a number on, which most operations can once they look.
The volume figure people ask for is around a thousand assets a month, and it is a symptom rather than a cause. What actually breaks is that one coordinator becomes the routing engine and cannot take leave during a delivery window. At 340 assets in flight that is stressful. At 3,400 it is not possible, and the alternative to building is hiring a second coordinator, which is the comparison worth running.
Take one month of platform rejections, count them, and multiply by the linguist and coordinator hours each consumed including the resubmission. Most operations can produce that number in an afternoon and most are surprised, because a rejection feels small and consumes a disproportionate amount of senior attention.
How do they compare on the things that matter in this industry?
Where validation happens. Format checkers catch structural problems. Rejections come from style rules: reading speed above the platform limit, a subtitle crossing a shot change, too many characters per line, an insufficient gap between events. Ask any tool whether it validates at submission, when a linguist can still fix it in four minutes, or at delivery, when the platform tells you four days later.
Specifications as data or as code. Platforms revise their style guides. If a rule change requires a release, you have bought a permanent maintenance bill disguised as a feature. Versioned rule sets with effective dates mean an update is configuration, and the system can tell you which in flight jobs are affected.
Format breadth. Broadcast formats such as SCC and MCC are a different world from streaming formats such as IMSC, and drop frame timecode at 29.97 frames per second is where careless implementations quietly break. Ask a vendor or a developer which of these they have written and parsed, and ask about frame rate conversion specifically.
Comparable quality measurement. Vendors report their own quality against their own methodology, which you cannot compare across suppliers. Automatic speech recognition word error rate is useful for transcription and close to meaningless for subtitling, where the skill is condensation, timing and reading speed. A typed, weighted error taxonomy scored at the quality control stage is the only thing that lets you rank an external vendor against your own bench on identical criteria.
Coverage evidence. Nobody sells a five dimensional coverage matrix across titles, territories, platforms, languages and service types, because nobody else knows your distribution footprint. Evidence assembled after a client asks for it is always the expensive kind.
What does total cost of ownership look like at your scale?
On the build side, from Digital Heroes delivery experience, the first real band is $70,000 to $140,000 over 12 to 16 weeks. That covers the job as a first class object with routing rules by language pair, service type and load, the freelancer pool with rates and availability, versioned specification rule sets validated at submission, quality control scoring against a typed error taxonomy, and packaging for the formats you deliver into. A representative vendor routing fourteen hundred assets a month across four platforms and six language pairs lands near $134,000.
The second band is $180,000 to $400,000 phased across 6 to 12 months. Audio description with script, voicing and mix stages runs around $58,000 as a phase two module. Multi stage translation chains with pivot languages are roughly $34,000, the compliance coverage matrix with an evidence trail around $48,000, client portals around $40,000, vendor cost reconciliation around $26,000, and secure watermarked review for pre release material around $30,000.
Two cost drivers dominate. Specification count compounds rather than adds, because each platform brings a format and each language brings its own reading speed and character rules within that platform. Against a proven, versioned model an additional platform runs $6,000 to $12,000, while twelve built at once while the validation approach is still unsettled costs several times that. Media handling is the second: proxy generation and shot detection, so shot change conformance can be checked at all, was $16,000 in that worked example. If your asset management system already generates proxies and holds shot lists, say so in the first conversation, because rebuilding that layer is one of the larger avoidable lines here.
Running costs are dominated by media storage and transfer, $700 to $2,500 a month at moderate volume, scaling with retention policy rather than job count. Maintenance runs $18,000 to $45,000 a year, driven mostly by platform specification changes. Automatic speech recognition is a per minute cost that continues indefinitely, usually cheap against the linguist hours it saves and still a real line. Then the internal one: roughly half a day a week of a senior linguist owning the rule sets and the error taxonomy weights, without which nobody believes the quality scores.
What does the hybrid look like, and when is it the honest answer?
For most operations at this size the answer is both, and saying so plainly matters because the two are not substitutes. Vendors sell minutes. They do not sell a system for routing work across your own staff, your freelancers and two or three suppliers at once with comparable quality measurement.
The pattern that works:
- Keep buying capacity. Use 3Play Media, VITAC or Verbit for overflow, for language pairs you do not staff, and for the volume spikes that would otherwise force a hire. That spend continues either way, so treat it as a constant rather than something the build replaces.
- Build the routing and specification layer, $70,000 to $140,000. Jobs, rules, the pool, versioned specifications validated at submission, and quality scoring. Your coordinator moves from doing the routing to supervising it.
- Score vendors on the same taxonomy as your own linguists. This is the quiet return. Once you can rank a supplier against your bench on identical criteria, procurement conversations change materially.
Cut the first release by destination rather than by capability. Validation that is right for your four highest volume platforms beats validation that is approximate for twelve, and the fifth platform against a proven model is a small line item later.
Which should you choose, by operator size and stage?
- Content owner, any volume, sending work out. Buy. Keep a shared tracker, put your engineering budget somewhere it earns, and do not read the rest of this list.
- In house team, one or two platforms, one language. Buy the tracker, not the platform. Under about $45,000 you get a job board with states and assignees, which is the right size when the pain is visibility rather than routing.
- Service operation, several hundred assets a month, two or three platforms. The decision point. Build the routing engine and specification validation for your top four destinations, then reassess after a quarter of live volume.
- Vendor or localisation operation past a thousand assets a month across a mixed pool. Build the first release properly, $70,000 to $140,000, and expect the parallel run to surface routing rules nobody wrote down.
- Operation serving broadcasters and streamers across several territories with a coverage obligation. Build toward the full platform, sequenced: routing first, then the coverage matrix at around $48,000, then audio description, then portals. Coverage tends to climb the list the first time a client asks for evidence and the answer takes a week.
Two conditions apply to every build row. Insist that specifications are modelled as versioned data rather than code, because that single decision is worth more than any feature in the first release. And budget the discovery properly, since its real output is the undocumented rules: which freelancer never gets sports, which client always wants a second check, which language pair goes through a pivot. Those live in a coordinator's head, and writing them down is the work rather than a preamble to it.
If you would rather scope this before committing budget, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. Nothing about that commits you to the build.
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 argues software developer productivity can be measured by combining system-level metrics (DORA and SPACE) with its own outcome-oriented approach, which it reports deploying across nearly 20 tech, finance, and pharmaceutical companies - a claim that sparked significant debate in the engineering community. Source: McKinsey & Company (2023) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
- In an October 2025 survey of 530 small-business employers (conducted by TechnoMetrica, October 3-9, 2025), 88% reported using AI tools and 73% said those tools had been important to their competitiveness and growth over the past year, with 60% citing efficiency and productivity as the primary motivation for adoption (42% cited improving customer service). Source: Small Business & Entrepreneurship Council (SBE Council) (2025) →
Frequently asked questions
Is building cheaper than buying minutes from 3Play Media or Verbit?
They are not substitutes, so the comparison misleads. Those vendors sell capacity and do it well, and if you use them for overflow that spend continues after any build. What they do not sell is a system for routing work across your own staff, your freelancers and two or three suppliers at once with comparable quality measurement.
If you are a content owner sending work out and receiving files back, buy from them and build nothing. Build when the routing, the rate management and the quality measurement are your operation rather than someone else's service.
What does it cost to move off a vendor or a spreadsheet tracker?
The data is rarely the problem. Rates, job history and the pool export readily enough. The migration surprise is the undocumented rules: which freelancer never gets sports, which client always wants a second check, which language pair needs a pivot. Getting those written down is a real part of discovery.
Budget two to three weeks of parallel running with coordinators comparing both systems. That is where the rules nobody mentioned surface, and skipping it is how a technically finished build gets worked around.
What if our vendor changes its per minute rates?
Work out now what your bill looks like at double your current volume, because per minute pricing scales exactly with success and there is nothing obvious to compare it against. Do that before renewal rather than during it.
The structural answer is to own the quality measurement. Once you score external suppliers on the same typed error taxonomy as your own linguists, a rate conversation becomes a comparison between measured options rather than a negotiation with your only source.
How long before coordinators are routing through a custom system?
Two to three weeks of discovery, then 12 to 16 weeks to a first release, then two to three weeks of parallel running. The milestone worth watching is the first week jobs route automatically against live volume rather than against a demo set.
Audio description and the compliance coverage matrix should wait a quarter. Operations regularly reprioritise once routing is live, and the coverage matrix tends to climb the list the moment a client asks for evidence.
Why do our caption files keep failing platform validation?
Almost always because the file passes format validation and violates a style rule: reading speed above the platform limit, a subtitle crossing a shot change, too many characters per line, or an insufficient gap between events. Format checkers catch structural problems and miss all of that.
The fix is to model each platform and language pair as a versioned rule set and validate at submission rather than at delivery, so the linguist sees the failure in minutes instead of the platform rejecting it days later.
Why does supporting more platforms cost so much?
Because each platform brings a format and each language brings its own reading speed, character count and gap rules within that platform, so rule sets multiply rather than add. Twelve platforms across twenty language pairs is not thirty two rule sets.
Against a proven, versioned specification model an additional platform runs $6,000 to $12,000. Built in parallel with eleven others while the validation approach is still unsettled, the same work costs several times more and delays every one of them.
Does audio description belong in the first release?
No. It is around $58,000 as a phase two module because it adds script writing, voicing and mix stages with their own resources, review criteria and deliverable formats. It is an expansion rather than a feature.
It slots into the same job model without redesign once routing is proven, which is why starting with captions and subtitles on your highest volume language pairs is the cheaper sequence and gets the engine tested against real load sooner.
We send about 300 hours a year outward. What should we spend?
Very little. Send the work to 3Play Media or VITAC, keep a shared tracker, and put your budget somewhere it earns. At that volume the routing complexity that justifies a build does not exist, and a build would be a hobby dressed as an operations project.
If visibility is the real pain, buy a job board with states and assignees rather than commissioning one. That is the sub $45,000 answer and it fixes the problem you actually have.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
How do I vet a software agency before hiring them to build a PM tool?
Ask to click through a workflow tool they shipped, live rather than in screenshots, and get a reference from a client whose system has been in production for over a year. Then ask two questions that expose weak vendors: how they migrate data out of your current tool, and what their maintenance retainer covered for that reference client last quarter. An agency that has genuinely shipped project management software answers both in specifics.
I run a 15-person business. Is there a cheaper option than a full custom project management build?
Yes: a custom layer on top of a tool you already pay for. Digital Heroes ships client dashboards, automated reporting, and workflow glue built on the Asana and ClickUp APIs for $8,000 to $20,000, which fixes the specific gap without replacing the whole tool. A full custom platform rarely makes sense below roughly 50 seats unless the software faces your own customers.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
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.
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.
We've outgrown ClickUp. Does that mean we need custom software?
Not automatically. First check whether ClickUp's Business tier at about $12 per user per month plus its API covers the gap, because most complaints about outgrowing ClickUp are really automation limits, not data model limits. The genuine signal for custom is structural: your work does not fit the task-in-a-list model, for example a job that must sit under two clients with separate billing at the same time. If you are paying someone monthly just to maintain workarounds, it is time to price a build.
What should the first version of a custom project management tool include, and what should wait?
Version one is the painful workflow plus the basics: tasks, projects, permissions, and one integration, shippable in 12 to 16 weeks. Everything that feels essential but is not should wait: Gantt views, custom report builders, native mobile apps, and public API access all belong in version two, once real usage shows what matters. Teams that run the MVP for a quarter before expanding consistently spend less and drop features that looked critical on paper.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
Can we move our existing Asana or Jira data into a custom tool?
Yes. Both expose full export APIs, and projects, tasks, comments, and assignees come across cleanly; Digital Heroes typically runs migration as a 2 to 4 week workstream in parallel with the build. The awkward parts are attachments, automation rules that must be rebuilt rather than imported, and deciding how much closed historical work to carry over. Migrate active projects fully and keep the rest as read-only archive exports.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
Who can build a custom project management software system?
Digital Heroes builds custom project management 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 project management 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 Arjun.
Chief Technology Officer · Delhi · 1 post on the site
Published · Last updated .
