Subsea Cable Operations Software: Custom Build or Off the Shelf
Buy, or rather assemble. If you own capacity on systems other people manage, a shared drive and a disciplined administrator is the right answer and software here is overhead.
On this page
Buy, or rather assemble. If you own capacity on systems other people manage, a shared drive and a disciplined administrator is the right answer and software here is overhead. Build only when you operate or co-manage more than one system, when repair cost disputes routinely run past ninety days, and when the construction and maintenance agreement lives in one person's head.
What the off-the-shelf products actually do well
The invoice from your last repair is still being argued about and the ship demobilised in March. That is usually what sends someone looking for software. Before you commission any, be clear about what already exists, because parts of this problem are genuinely solved.
MakaiPlan and MakaiPlan Pro from Makai Ocean Engineering are the recognised tools for route engineering, slack management and building an as-laid route position list you can trust. If your geometry currently lives in a spreadsheet, buy that before you buy anything custom. Esri ArcGIS handles the geospatial layer properly, including plotting a fault position against charted hazards and against the awareness charts published through the Kingfisher Information Service. IBM Maximo, Infor EAM and SAP Plant Maintenance are competent asset and work order systems, and if your parent company already runs one for terrestrial plant, your depot spares and your planned maintenance can sit in it without argument. Microsoft Project and SharePoint do what they were designed to do.
None of them is a subsea cable operations platform, and that is not a criticism. There is no packaged product for consortium cable operations, which is the actual reason this phrase gets searched. If you hold an indefinite right of use on two systems, attend the management committee twice a year, and your involvement in a repair ends when you review the statement, the honest advice is to keep a good folder structure, write the clause summary down, and spend nothing. Most parties on a cable system are in exactly that position, and a build would be an expensive way to feel prepared.
Where they stop: apportioning a repair invoice under the maintenance agreement
Here is the workflow no generic tool models, and it is the one that costs you money after the fact.
The construction and maintenance agreement says who owns which fibre pairs, who authorises a repair and at what threshold, and how the cost is divided. In practice that clause is not a percentage column. Standby fees under your zone agreement, whether that is the Atlantic Cable Maintenance and Repair Agreement, the Mediterranean agreement, or a South East Asia and Indian Ocean arrangement, accrue continuously and usually split by ownership share. Repair day rates and jointing consumables split against the affected segment, which may be counted by fibre pair rather than by capacity. Recoveries from the fishing vessel that dragged the anchor offset in the same proportion, net of legal costs. That is bespoke arithmetic drafted by lawyers, and it changes for every system you operate.
Because no tool expresses it, finance rebuilds it in a spreadsheet after each event. Two owners then read the same clause differently, and neither side can produce the evidence that would settle it: the daily ship reports, the permit correspondence showing which authority granted what and when, the depot pick with repeater serial numbers, the record of who authorised the mobilisation under which clause.
An asset management system models a work order with a start date and a cost centre. It has no concept of a case that will be read by counsel eighteen months later, and it assumes you can send a technician. Your asset sits at 3,200 metres and is reachable only by a ship you share with the other owners under an agreement with its own priority rules. The scheduling model is wrong from the first screen.
The arithmetic: named-user licensing versus a build at your fault rate
Do the seat maths first, because in this category it settles quickly and not in the direction people expect.
Suppose an enterprise asset management suite quotes you 1,800 dollars per named user per year with a 40,000 dollar platform fee underneath. Your operations team is four people plus a landing party contact in each country and two in finance. Call it fourteen named users. That is about 65,000 dollars a year, and across five years roughly 325,000 before the implementation engagement. A build at 90,000 to 180,000 dollars plus 15 to 20 percent annually lands close to the same place. On seats alone there is no crossover worth the risk, because your team is small and it will stay small.
The crossover is not in seats. It is in mobilisations. Take two numbers you already have: the standby fee and the day rate written into your zone agreement. Then count the days lost on your last two repairs to a permit filed with the wrong ministry, a depot that shipped a repeater the system stopped using after the 2019 upgrade, or an authorisation that waited for a committee that had not been convened. At roughly three managed systems, or about eight mobilisations a year across your portfolio, or one apportionment argument a year that runs past ninety days, the coordination load exceeds what four people and a folder structure can hold, and the build pays for itself in ship days rather than in licence fees.
What a custom build actually costs
A first release covering the system model with a versioned route position list, the fault case from first alarm to post-repair acceptance, permit and ship coordination, and a cost apportionment engine for one agreement runs 90,000 to 180,000 dollars over 14 to 20 weeks. It should be used on the next real fault, not demonstrated in a meeting. A full platform adding multi-system support, depot and spare inventory with serial numbers, landing party coordination, capacity and ownership records including indefinite right of use holdings, and an owner portal runs 220,000 to 500,000 dollars phased across 9 to 15 months.
Two lines that never appear in a proposal. Data migration runs 10 to 25 percent of build cost and sits high here, because your as-laid geometry has to be reconciled against every repair that changed cable length since installation, and that is a person with the ship reports and the route position list open side by side. Year two and every year after runs 15 to 20 percent of build cost annually, which covers the next agreement you take on, the permit pack a new authority starts demanding, and a partner reachable at two in the morning when a shunt fault opens.
What pushes the number up here specifically: the count of distinct maintenance agreements, since each is a rule set rather than a setting. The number of permit jurisdictions, because each authority wants a different pack in a different language. Line monitoring integration, since interfaces on power feeding equipment and line monitoring equipment vary by vendor and generation and some are old enough to need serial handling.
The four situations where building wins
Regulatory fit. Your repairs cross territorial waters and exclusive economic zones where permits are required, your obligations under the cable protection provisions of the Law of the Sea Convention and your national implementing legislation are live, and each jurisdiction wants a different evidence pack on a different clock. A generic work order has no place to hold a permit with its own status, conditions and expiry.
Scale economics. You are past the mobilisation threshold above, and the days you lose to coordination now exceed the annual cost of the system that would remove them.
A workflow that is your competitive advantage. If you manage systems on behalf of other consortia, the quality of your apportionment statement is the product you are selling. An owner who receives a statement with the ship report attached to each allocated line renews. One who receives a spreadsheet argues.
Integration sprawl across three or more systems. Line monitoring and power feeding equipment on one side, depot stock somewhere else, ownership percentages in a finance workbook, permits in a mailbox, and the manager who joins them by hand. When your operations lead has become the integration layer, you already own a custom system. It is simply made of people.
How to decide in a week
Run one test. Take your last completed repair and ask one person to assemble, from scratch, the full apportionment statement for a single owner: every daily ship report, the permit correspondence for each jurisdiction, the depot picks with serial numbers, every authorisation with the clause it was given under, and the recovery position against the damaging vessel. Time it honestly and count the mailboxes and drives touched. Under a day and you have a filing problem, so fix the filing. Three days across five mailboxes, with one document that nobody can find at all, and the build case has made itself.
Then talk to two firms and hand each of them one real clause from your agreement. Watch what they draw. A firm that has done this will ask which segment the fault sits on, whether ownership is counted by fibre pair or by capacity, and how third party recoveries are treated. A firm that draws an invoice table with a percentage column has not read the clause. Ask the second question too: how is the case file treated as evidence rather than as a workflow. You want an append-only event log, the original documents preserved, and a complete export for one fault.
Finish with a paid discovery phase. At Digital Heroes nothing is coded until a product requirements document is signed covering the data model, the clause interpretations captured as written decisions, integration contracts and acceptance criteria, and that document is yours whether or not we build anything. We are the wrong choice if you want a vendor who hosts your operations data on their own accounts, or one who quotes before reading your agreement. We are an India LLP with a United States LLC and a United Kingdom LTD, so intellectual property assigns under your own law, and with more than fifty specialists and over 2,000 projects delivered you meet the named team before you sign. Our record is checkable on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
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.
- In PMI's 2014 Pulse of the Profession report on requirements management, inaccurate requirements management is cited as a leading cause of project failure, with 47% of unsuccessful projects failing to meet goals due to poor requirements management. Source: Project Management Institute (PMI) (2014) →
- 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) →
- Criteo's Global Commerce Review found retail apps convert at 18% versus 4% on mobile web (roughly 4.5x), and travel apps convert at 20% versus 6% on mobile web (about 3.3x). Source: Criteo (2017) →
- The NRF discontinued its long-running annual shrink report, stating that a broad study of retail shrink 'is no longer sufficient for capturing the key challenges and needs of the industry' - important context that qualifies how POS/shrink benchmarks should be cited going forward. Source: Retail Dive (2024) →
Frequently asked questions
How much does custom subsea cable operations software cost
A first release covering the system model, the fault case with permits and ship coordination, and cost apportionment for one maintenance agreement runs 90,000 to 180,000 dollars over 14 to 20 weeks in Digital Heroes delivery experience. A full platform with multi-system support, depot inventory, capacity records and an owner portal runs 220,000 to 500,000 dollars. Add 10 to 25 percent for migration and 15 to 20 percent annually after.
Who owns the code and the fault records if an agency builds our platform
You should own the repository, the cloud accounts and the unrestricted right to bring in another firm, agreed in writing before kickoff rather than at renewal. At Digital Heroes the client owns the code from the first commit. This matters more here than in most categories, because a fault case is evidence in a claim against a damaging vessel and has to remain producible for years.
What happens if a repair invoice is disputed and we cannot produce the evidence
You settle at whatever the other owners will accept, and the manager who ran the repair spends weeks reconstructing a record from memory and email. The practical defence is collecting evidence continuously rather than reactively: daily ship reports, permit correspondence, depot picks with serial numbers, and each authorisation with the clause it was given under, all attached to the case as it happens.
Can software really automate consortium cost apportionment
Yes, if the agreement is modelled as configurable rules rather than as hard-coded percentages. Standby, mobilisation, day rates, consumables and third party recoveries each allocate differently, and the split can depend on the affected segment and on whether ownership is counted by fibre pair or by capacity. The value is that every allocated line traces back to a source document, which is what stops a query becoming a dispute.
How long does it take to build a fault and repair management system
A usable first release ships in 14 to 20 weeks. Engineering is rarely the long pole. The long pole is turning the construction and maintenance agreement into explicit rules, which means sitting with whoever administers it and writing down decisions that have only ever been made by judgement. Operators who already keep a summarised clause table move noticeably faster through that stage.
Should the system connect to line monitoring and power feeding equipment
It should, and it is usually the highest value integration available. Pulling alarms and measurements directly means a case opens with its electrical distance and optical trace attached instead of typed in later from a screenshot. Scope and price it separately, because interfaces on this class of equipment vary by vendor and generation and older installations sometimes need serial or file-based handling.
What is the difference between an asset management system and a cable operations platform
An asset management suite such as Maximo models an asset, a work order and a cost centre, and assumes you can dispatch a technician. A cable operations platform models a case that holds evidence, a ship you share with other owners under a zone agreement with priority rules, permits per jurisdiction, and a cost split written by lawyers. The second cannot be configured out of the first.
Can one system handle several cable systems with different agreements
Yes, and that is the strongest reason to build rather than buy, because packaged tools have no concept of an agreement as a rule set. Each system carries its own ownership table, its own authorisation thresholds and its own apportionment logic, with a shared depot, spare and ship layer underneath. Expect each additional agreement to add real scope rather than a configuration toggle.
How should permit applications for cable repairs be handled
Each permit should be its own record attached to the fault case, carrying the jurisdiction, the authority, the submitted pack, the status and any conditions or expiry. The reason to keep them structured is reuse, because the pack submitted for the last repair in the same waters is the fastest starting point for the next. Operators who keep permits only in email rebuild every application and lose days.
We only hold capacity on systems others manage. Should we build anything
No. If you never chair a repair and your involvement ends at reviewing a statement, a shared drive and a competent administrator covers you, and the money is better spent on a lawyer reading your agreement carefully once. The picture changes if you take on operation or co-management of a system, or if you become the party assembling permits, ship schedules and the statement other owners will challenge.
How long does it take from first call to software my team can actually use?
Plan for four to six months: two to three weeks of discovery, two to four weeks of design, then a 10 to 16 week build with testing. In Digital Heroes delivery experience the schedule killer is not engineering speed but decision lag; a client who takes two weeks to approve wireframes adds two weeks to launch. Book a weekly 30-minute decision slot before kickoff and most of that risk disappears.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
How much should a small business expect to pay for custom software?
Across 2,000+ Digital Heroes projects, a small business system that replaces spreadsheets or one core workflow typically lands between $40,000 and $80,000, with more complex first versions running up to $150,000. The two levers that move the number most are integrations and user roles, not the team's hourly rate. Any quote under $15,000 for a full production system means the vendor has not understood your scope yet.
What is the biggest mistake first-time software buyers make?
Choosing the lowest quote without asking why it is the lowest. A bid 40% under the field usually gets there by skipping tests, documentation, and code review, which are invisible in a demo and brutal to pay for later; every stalled project Digital Heroes has been asked to rescue tells some version of that story. The second mistake is signing without a written scope, which reliably turns the winning cheap quote into 1.5x to 2x the price by launch.
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 run everything on Airtable and spreadsheets. When is it time to go custom?
The switch usually makes sense when you hit one of two walls: Airtable's record caps (125,000 records per base on the Business plan) or logic the tool cannot express, like multi-step approvals with conditional pricing. There is also a simple cost signal: 25 people on Business at roughly $45 per seat per month is about $13,500 a year, forever, for a tool you are already fighting. Custom is worth it when the workflow is core to how you make money; for peripheral processes, staying on Airtable is the right call.
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.
If we build for 20 users now, will the software cope with 500 later?
It should, without a rewrite, if it was built on a standard cloud stack; going from 20 to 500 users is mostly a hosting configuration change costing hundreds a month, not a second project. What actually breaks under growth is sloppier work: database queries never indexed for volume and features designed assuming one office's worth of data. Before signing, ask the vendor what happens to the system at ten times today's data, and listen for a specific answer.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
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.
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
Published · Last updated .
