How Much Does Ship Repair Yard Software Cost in 2026?
$70,000 to $450,000 spans everything we quote for a repair yard, and the single decision that moves you across it is whether the system stops at variation capture or continues into posting labour, stores and subcontractor cost against the job number from your existing accounting ledger.
On this page
$70,000 to $450,000 spans everything we quote for a repair yard, and the single decision that moves you across it is whether the system stops at variation capture or continues into posting labour, stores and subcontractor cost against the job number from your existing accounting ledger. Stop at variation capture and you stay in the lower band and ship in a quarter. Push into job costing and invoicing and you take on an integration with a general ledger that was designed for something other than ship repair, which reliably adds two to four months and a six figure line.
The bands a ship repair yard build falls into
Two bands cover most of this work. A first release covering specification import and owner item mapping, quotation against a rate card, job numbering, dock and berth planning and mobile variation capture with photographs and captured signature runs $70,000 to $150,000 and ships in 12 to 18 weeks. That is a system your estimators and dock foremen use on the next vessel, not a pilot that sits beside the paperwork.
A full yard platform adding timesheet and stores posting to job numbers, subcontractor commitment control, permit to work and gate access, class survey attendance scheduling, progressive and final invoicing and an owner portal runs $180,000 to $450,000 phased over 6 to 14 months.
There is a third, narrower option worth knowing about. Variation capture on its own, meaning a tablet app that raises a priced variation on the dock bottom with photographs and a superintendent signature, feeding a simple exposure register, lands at $30,000 to $55,000. It does nothing about specification mapping or dock planning. It does address the part of the business where the money actually escapes, which is why yards under real dispute pressure sometimes buy exactly that and nothing else.
What drives a ship repair yard build up
Offline capability is first and it is not negotiable. A double bottom tank has no signal, and a variation raised there has to store locally with its photographs and sync when the foreman climbs out. That means local storage, a sync queue and conflict handling when two foremen raise overlapping items, and it adds real weeks that a developer quoting a simple web form will not have priced.
Dock count and dock variety is second. Two graving docks with the same tidal and pump constraints cost little more than one. A graving dock plus a floating dock plus a syncrolift is three genuinely different planning models, each with its own flooding, ballasting and lift limits.
Rate card complexity is third. Lump sum, per tonne with different rates for flat plate, shaped plate and overhead or confined positions, day rate per trade per man, subcontract at cost plus a handling percentage, dock occupancy per day, staging per square metre per week. Every pricing model you carry is logic to build and test.
Accounting integration is fourth and it is the one that decides whether you are in the lower band or the upper. Posting hours, stores issues and subcontractor invoices back into a ledger whose job costing structure was designed for a different industry is a project in its own right.
What keeps the number down
Write your rate card down before kickoff. In most yards the full commercial logic lives with one director and has never been documented, and discovery time spent extracting it is billed at the same rate as engineering. Yards that arrive with a written rate card and a consistent job numbering scheme routinely save three weeks.
Start with one dock and your top three repair types by revenue. Steel renewal, tailshaft and machinery work will usually cover the majority of your turnover, and the pricing logic for the remainder can be added once the model has proved itself on real vessels.
Keep your accounting package out of scope for the first release. Let the yard system produce a costed final account as a document, and let someone key the invoice into the ledger for now. That one deferral takes a large integration off the critical path and lets you go live a quarter earlier.
Resist building an owner portal in phase one. It is genuinely valuable, and it is also the component that changes most once owners start using it, so building it after you have six months of real variation data is cheaper than building it twice.
A worked example that adds up
One graving dock, roughly 40 vessels a year, mixed international owners, a single accounting package left out of scope.
- Discovery: rate card documentation, job numbering, specification mapping rules: $14,000
- Specification import with owner item to work order mapping carried through every downstream record: $19,000
- Quotation against the rate card supporting lump sum, per tonne and day rate on one job: $21,000
- Mobile variation capture with offline storage, photographs, automatic rate lookup and captured signature: $38,000
- Dock and berth planning with approved variations extending the undocking date automatically: $24,000
- Pilot across two vessels, then rollout to the full estimating and production team: $9,000
That totals $125,000, mid to upper band for a single dock yard. Take out dock planning and you are at $101,000, which is a defensible first release if slot utilisation is not your constraint. Add a floating dock with different flooding rules and multi-currency invoicing for international owners and you add roughly $18,000 and four weeks, landing at $143,000.
Variation capture is the largest line for the same reason it is the reason to build: it is the only component that has to work reliably in a tank, with no signal, in the hands of a foreman who has thirty seconds to spare.
How the spend phases
Phase one is 12 to 18 weeks. The sensible milestone schedule is specification import proven against three real owner specifications you supply, quotation reproducing a job you have already priced by hand to within a few percent, variation capture working offline in an actual tank, and dock planning running alongside your existing chart for two vessels before it replaces it.
Phase two splits into increments that ship independently. Timesheet and stores posting against job numbers is $30,000 to $55,000. Subcontractor commitment control, meaning the purchase order raised against the work order and the invoice matched back to it, is $18,000 to $30,000. Progressive and final invoicing with the accounting integration is $35,000 to $70,000 and is the single largest phase two item. An owner portal is $25,000 to $45,000. Class survey attendance scheduling is $15,000 to $25,000.
Sequence invoicing last, not first. Once variations, hours and stores are all posting to the job cleanly, the final account is close to a rendering problem. Attempt it before the cost data is trustworthy and you build a beautiful document full of numbers nobody believes.
The ongoing costs nobody quotes
Photograph and document storage grows faster in this category than almost any other we work in. A single vessel under a heavy steel renewal generates thousands of images, and you need to keep them for as long as your disputes and warranty exposure run. That is storage plus a retention policy plus a backup regime, and it is a real monthly line rather than a rounding error.
Mobile devices are a running cost too. Rugged tablets in a yard environment do not last, so budget replacement, a device management arrangement and the mobile data plans behind them.
Then the change budget. Rate cards get renegotiated, an owner introduces a new specification format, class requirements change, you add a berth. In our delivery experience, 15 to 20 percent of the build cost per year keeps a yard system aligned with the business. If you serve international owners, add translation upkeep for the owner-facing documents each time the rate card or terms change.
Hosting itself is modest. The data is measured in tens of thousands of records a year, not billions, so the infrastructure bill is a small fraction of the storage and change lines above it.
Comparing a build against your current renewal
Most yards have no yard system renewal to compare against, which makes this arithmetic unusual. What you have instead is an accounting package, a spreadsheet estimating workbook and a Gantt chart, and the real comparison is against the cost of the gaps between them.
Pull four of your own numbers. First, estimator reconciliation time: the days spent per vessel matching owner specification items to your work orders to your invoice lines, times your vessel count, times a loaded daily cost. Second, the value of variations written off or settled below quoted value in the last two years because the evidence was a photograph on a phone. Third, dock days lost to growth work that was agreed on the dock bottom but never reached the planner, priced at your dock day rate. Fourth, the working capital cost of final accounts that took four months to settle rather than four weeks.
In the yards we have worked with, the second and third numbers dwarf the first, and together they usually clear the entire first release cost inside a single year. If they do not, that is a genuine answer and you should not build.
When buying beats building
If you are an afloat repair outfit doing voyage repairs, small steel jobs and superintendent-assisted machinery work with no dock of your own, do not build. Your scarce resource is qualified people, not slots, and a disciplined spreadsheet with a strictly enforced signed variation form will hold at that scale. Spend the money on a crane or a second squad.
If your work is predominantly planned maintenance and component management for an owner fleet rather than commercial repair against a negotiated specification, buy SpecTec AMOS or SERTICA. Those systems are mature, they are built for exactly that shape of problem, and no bespoke build will match them on planned maintenance schedules, component hierarchies and certificate tracking. ShipNet is worth evaluating in the same conversation.
Build when two or more of these hold. You own a dock or a syncrolift and slot utilisation drives your profit and loss. Growth work is a material share of your typical final account. You have lost a dispute in the last two years for lack of evidence. You quote in more than one pricing model on the same job. Every owner sends specifications in a different format and your estimators retype all of it.
If you would rather someone argued with your brief than agreed with it, 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. 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.
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
- 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) →
- Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
- 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) →
Frequently asked questions
How much does custom ship repair yard software cost in total?
A first release covering specification import and mapping, quotation against a rate card, job numbering, dock planning and mobile variation capture runs $70,000 to $150,000 and ships in 12 to 18 weeks, based on Digital Heroes delivery experience. A full yard platform adding labour and stores posting, subcontractor control, invoicing and an owner portal runs $180,000 to $450,000 over 6 to 14 months.
A single graving dock yard turning around 40 vessels a year typically lands near $125,000 for the first release, with variation capture the largest single line at roughly $38,000 of it.
What does it cost to run each year after go live?
Three lines matter. Photograph and document storage, which grows quickly because a heavy steel renewal generates thousands of images per vessel and you keep them as long as your dispute and warranty exposure runs. Rugged tablets, which do not survive a yard environment for long and need a replacement cycle and data plans. And change work.
Plan 15 to 20 percent of the build cost annually for changes: renegotiated rate cards, a new owner specification format, an added berth. Hosting itself is a minor line, since the record volume is small.
How long before the yard is actually using it on a vessel?
12 to 18 weeks for the first release, and the sensible pattern is to run it alongside your existing paperwork for two vessels before it becomes the record. The engineering is rarely the constraint. Documenting the rate card is, because in most yards the complete commercial logic sits with one director and has never been written down.
Yards that arrive at kickoff with a written rate card and a consistent job numbering scheme routinely save three weeks against this timeline.
Is SpecTec AMOS cheaper than building our own yard system?
It is a different purchase rather than a cheaper one. SpecTec AMOS and SERTICA are built for the shipowner and technical manager: planned maintenance schedules, component hierarchies, procurement and certificate tracking across a fleet. If that describes your work, buy one of them and do not build, because you will not match a decade of maritime product development.
They were not designed to price growth work against a negotiated yard rate card, capture a superintendent signature on the dock bottom, or plan a graving dock against tidal and coating constraints. If those are your problems, the licence cost is not the comparison that matters.
Why is offline variation capture such a large part of the cost?
Because a variation raised inside a double bottom tank has no connectivity and the record has to survive anyway. That means local storage on the device, a sync queue, photograph handling that does not lose images on a flat battery, and conflict resolution when two foremen raise overlapping items on the same compartment.
A developer quoting this as a web form has not priced it. An unused variation feature is worse than paper, because it creates the belief that a record exists when it does not, so treat this line as the one you do not trim.
What does adding a second dock or berth add to the budget?
Almost nothing if it shares the same constraints as the first, since it is another row in the same planning model. A genuinely different dock is different money. A floating dock has ballasting and lift constraints a graving dock does not, and a syncrolift is a third model again.
In our worked example, adding a floating dock with different flooding rules alongside multi-currency invoicing added roughly $18,000 and four weeks to a $125,000 first release.
Should the first release integrate with our accounting package?
Usually not, and deferring it is the single largest saving available. Let the yard system produce a costed final account as a document and have someone key the invoice into the ledger by hand for the first few months. That removes the largest integration from the critical path and gets you live a quarter earlier.
Bring the ledger in during phase two, once hours, stores and subcontractor cost are all posting cleanly against job numbers. Integrating before the cost data is trustworthy just automates numbers nobody believes.
Can we buy only variation capture and nothing else?
Yes, and some yards should. A standalone tablet application that raises a priced variation on the dock bottom with photographs, automatic rate lookup and a captured superintendent signature, feeding a simple exposure register, lands at $30,000 to $55,000.
It will not map owner specification items, plan your dock or produce a final account. It does address the point in the process where margin actually escapes, which makes it a rational purchase for a yard that has recently lost a dispute and is not ready for a full programme.
Do we need this if we only dock 15 vessels a year?
Probably not yet. At that volume a disciplined paper or spreadsheet process with a strictly enforced signed variation form will hold, and the capital is better spent on dock equipment or a second squad. Software encodes a process, so the value only appears once the process is running at a volume a person can no longer hold in their head.
The trigger is not vessel count on its own. It is dock ownership plus growth work as a material share of the final account plus at least one dispute you lost for want of evidence.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
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.
How big a team does it take to build a project management platform?
A typical Digital Heroes pod is 4 to 5 people: a product designer, two or three engineers, and a shared project manager and QA. Smaller than that and timelines stretch because one person is context-switching across design, backend, and testing; bigger only helps after the MVP, when work splits into parallel streams. Headcount matters less than whether the same pod stays on your project from discovery to launch.
Can a solo freelancer build project management software, or do I need an agency?
A strong freelancer can deliver a single-team internal tracker in the $15,000 to $25,000 range. Once you need role-based permissions, real-time updates, several integrations, and someone on call after launch, you need a 4 to 5 person team, because those features cross design, backend, and QA at once. The bigger freelancer risk is continuity: one person on vacation becomes an outage in your delivery pipeline.
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.
Should I customize Jira with plugins or just build our own tool?
If two or three Marketplace apps close the gap, stay on Jira, since it starts around $8 per user per month and the apps ride on top. The trap is that cloud apps are licensed for every user on the instance, so in Digital Heroes audits a 200-seat Jira with three or four paid apps plus a ScriptRunner consultant often lands at $30,000 to $50,000 a year. At that run rate a custom tool scoped to your actual workflow pays for itself in two to three years and ends the plugin upgrade treadmill.
What does it cost to keep custom project management software running each year?
Budget 15 to 20 percent of the original build cost annually, so a $100,000 platform costs $15,000 to $20,000 a year to run. That covers hosting, security patches, dependency upgrades, and the item buyers forget: fixing integrations when Slack, Google, or QuickBooks change their APIs, which happens every year. Skipping the maintenance budget is how a two-year-old tool becomes impossible to upgrade.
What happens if the agency that built our project management tool shuts down?
Nothing fatal, if you set things up correctly from day one: code in your own GitHub organization, infrastructure in your own cloud account, and written deployment documentation as a contract deliverable. With those in place, any competent team can take over a standard-stack codebase in one to two weeks. Takeover disasters happen when the vendor hosted everything in accounts they owned, so verify account ownership before the first sprint, not after the relationship sours.
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
Published · Last updated .
