How Much Does Geotechnical Data Management Software Cost in 2026?
A custom geotechnical data management build runs $60,000 to $420,000 in our delivery experience, and the decision that moves the number most is how you scope the historical archive.
On this page
A custom geotechnical data management build runs $60,000 to $420,000 in our delivery experience, and the decision that moves the number most is how you scope the historical archive. Extracting twenty years of borehole reports chronologically and chasing every value is where these projects overrun by six figures. Extracting location, depth, strata and headline results for the two or three corridors where you actually bid, and accepting that the engineer will open the source report anyway, delivers most of the commercial benefit for a fraction of the effort. Log presentation standards are the second lever: each distinct client format you must reproduce is genuine drafting work, not a template toggle.
The bands a geotechnical data management build falls into
Three bands, based on Digital Heroes delivery experience rather than published averages. The first runs $60,000 to $140,000 over 12 to 16 weeks. That covers the project, hole, sample and test data model, tablet field logging with genuine offline capture, laboratory ingestion profiles with exception reporting, and automated borehole log and section production in one or two of your standard presentations. It is the release that removes retyping, which is the cost most consultancies can already feel.
The second runs $160,000 to $280,000 over 6 to 9 months. It adds the spatial archive of historical investigations with extracted data, several client specific deliverable formats, laboratory scheduling with turnaround tracking, and export into your design software.
The third runs $280,000 to $420,000 over 9 to 12 months. That band is for firms with a large scanned archive, instrument level integration such as reading cone penetration test output directly rather than importing a file, multiple offices working to different national standards, and design parameter selection with recorded justification.
Below $60,000 you are buying a form that writes to a database. It will not survive contact with a laboratory that reports non detects in its own convention, and you will be back in Excel within a season.
What drives a geotechnical data build up
Presentation standards first. A borehole log is a drawing governed by hatching conventions, column order, how a water strike is shown, whether standard penetration test results appear as increments or a single value, and which laboratory results print alongside the description. Each distinct standard you must reproduce exactly is drafting work measured in weeks. Firms that maintain five presentations because five long standing clients each demand their own will feel that directly in the quote.
The historical archive second, and its condition matters more than its size. Digital text based reports extract reasonably. Scans of typewritten logs from the 1990s need a different approach and human verification, and a firm holding thousands of those should expect the archive workstream to rival the core build.
Laboratory count third. Every laboratory needs an ingestion profile that knows its column meanings, units, test method references and how it reports a non detect or a failed specimen. Seven laboratories is seven profiles plus seven maintenance relationships, because they change their output without telling you.
Then instrument integration. Reading a cone penetration test rig or an in situ instrument directly is a different class of work from importing a file somebody exported.
Then genuinely remote offline capture. Field logging that has to work for a full day with no signal, hold a day of records and sync safely with conflict handling, is more engineering than it sounds and it is not optional in ground investigation.
What keeps the number down
Use the AGS data exchange format wherever your market uses it, as a first class import and export rather than an afterthought. Inventing your own interchange format means explaining to every client and laboratory why you cannot send a standard file, and it adds work in both directions. Adopting the standard removes the structure argument entirely.
Start with your two highest volume laboratories rather than all seven. Those two usually carry most of the retyping, and the remaining profiles can be added one at a time as they justify themselves.
Keep the archive out of phase one. It is the highest value part of the project for an established consultancy and also the least predictable, so proving the live data model first means the archive work lands on a stable foundation. Order the extraction by value, meaning the corridors and cities where you bid most often, not chronologically.
Support one presentation standard properly before adding the rest. Your dominant client format is the one that pays for the release, and the others can follow once the rendering engine has been proven on real jobs.
And keep logs unrendered and unedited. Treating every log as a rendering of authoritative data rather than an editable artefact costs nothing to build and saves a category of rework, because the moment a log is edited outside the system you have two versions of the truth.
A worked example that adds up
A regional consultancy running roughly 60 ground investigations a year, receiving results from four laboratories, producing logs to three client presentation standards, and holding twenty years of digital reports across a region where two metropolitan areas account for most of its bidding. This is how the quote breaks down.
- Project, hole, sample and test data model, including composite sample identification: $22,000
- Tablet field logging with offline capture, sync and conflict handling: $30,000
- Ingestion profiles for four laboratories with exception reporting and plausibility checks: $24,000
- Log and section rendering across three client presentation standards: $33,000
- AGS import and export: $9,000
- Archive extraction and indexing for two metropolitan areas: $38,000
- Map based search returning prior investigations within a radius, linked to source reports: $14,000
- Access control, deployment, testing and engineer training: $18,000
That totals $188,000, comfortably inside the second band. Drop the archive and the map search and you are at $136,000, which is the first release band and a defensible place to stop for a year. Add two more presentation standards, three more laboratories and extraction of a scanned archive and you approach $300,000.
How the spend phases
Around 12 percent goes into discovery. That is modelling how a sample is identified in your firm, capturing your presentation standards precisely enough to build against, and agreeing what the archive scope actually is. Presentation standards are where discovery earns its money, because a column nobody mentioned is a change request later.
Around 50 percent goes into the first release: data model, field logging, laboratory ingestion and log production. This is the block that stops retyping and it should be in engineers' hands before the archive work starts.
Around 25 percent goes into the archive, if you are doing it, and it is the phase most amenable to being split across budget years. Two metropolitan areas this year, two more next year, with the search interface built once.
The final 13 percent is parameter selection, design software export, deployment and training. Run the new system in parallel on two or three live jobs before you commit a major project to it, and pick jobs with an awkward laboratory rather than an easy one.
The ongoing costs nobody quotes
Hosting is small. A consultancy of this size sits comfortably in the low hundreds of dollars a month, with the archive storage being the only line that grows.
Support and change should be budgeted at 15 to 20 percent of build cost a year, and in this category most of it is laboratory maintenance. Laboratories change their export format, change their instrument software, or start reporting a new test, and each of those breaks an ingestion profile until somebody fixes it. Firms that do not fund this discover it during a busy autumn.
Then the tablets. Field hardware in ground investigation has a genuinely short life, and replacement is an operational line rather than a software one, but it belongs in the same business case.
Archive extraction, if you continue it beyond phase one, is an ongoing cost with a clear stopping point. Budget it by geography and stop when the next region no longer pays for itself.
Finally an internal owner. A geotechnical data platform with nobody responsible for the taxonomy, the presentation standards and the laboratory profiles degrades within two years, exactly as an abandoned mapping module does.
Comparing a build against your current renewal
Get four numbers from your incumbent before you commit. Annual licence for your current seat count. The cost of adding four more engineers. The cost of a new log presentation standard, if they will quote one at all. And whether extracting your own data back out is included or chargeable.
That last question is the one worth asking hardest. Your borehole archive is your firm's accumulated knowledge of the ground under a region, and if the exit path is a chargeable export in a format nobody else reads, the licence price is not the whole price.
For a firm running fifteen investigations a year, the packaged licence will beat a build by a wide margin over three years and you should not pretend otherwise. For a firm running sixty, with four laboratories and three presentation standards, add up three years of licence, seat growth and presentation change requests, and compare it to a build plus three years of support. The build often looks worse in year one and better by year three, and the archive value sits entirely outside that arithmetic.
When buying beats building
If you run under about fifteen ground investigations a year, use one or two laboratories, and produce logs to a single common standard, buy. Bentley gINT or OpenGround will cover you properly, HoleBASE SI is strong in markets built on AGS, and Datgel builds serious extensions on top of these tools. The licence cost is modest against a build and there is a pool of engineers who already know them, which matters when you hire.
Buy also if your firm has no appetite to own a system. A data platform without an internal owner degrades within two years regardless of how well it was built, and a packaged product with a vendor maintaining it is the honest answer for a firm that will not fund that role.
Build when several of these are true at once: laboratory data entry is a recognisable cost line, you receive results from more than three laboratories in incompatible formats, you hold an archive in a region you keep working and cannot search it, a major client requires deliverables your current tool cannot produce without manual editing, or a professional liability review has made undocumented parameter selection uncomfortable. If the archive alone is the reason you are asking, consider a focused extraction and indexing project without replacing your logging tool at all. That is often the highest return spend in this category and it costs a fraction of a platform.
If you want a second opinion before signing anything, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- This analysis cites IDC research that companies lose 20-30% of revenue annually to inefficiencies caused by data silos, Gartner's estimate that poor data quality costs organizations at least $12.9 million per year on average, and a Salesforce benchmark that 80% of IT leaders say data silos hinder digital transformation - illustrating the business case for integrating systems. Source: Cherry Bekaert (citing IDC, Gartner, Salesforce, DATAVERSITY) (2024) →
- ITIF's 2025 report documents that SMEs operate at roughly 60% of large-firm productivity in advanced economies (citing McKinsey), that CRM platforms deliver a 25-40% improvement in customer retention and a 15-30% boost in sales, and that digital advertising returns about $8 in profit per dollar spent on Google Search and Ads. Source: Information Technology and Innovation Foundation (ITIF) (2025) →
- Sensor Tower's State of Mobile 2026 reports that global users spent 5.3 trillion hours in iOS and Google Play apps in 2025 (+3.8% YoY), roughly 3.6 hours per day per mobile user. (Note: the page does not itself contrast app time vs. mobile-browser time, so the 'overwhelming majority of time in apps vs browsers' framing is not directly supported by this source.). Source: Sensor Tower (2026) →
- In an RCT, the no-show rate was 23.5% for patients receiving a text-message reminder versus 38.1% for the control group - a 14.6 percentage-point reduction (p = 0.04). Source: Clinical Pediatrics / PubMed Central (Lin et al.) (2016) →
Frequently asked questions
What is the total cost of custom geotechnical data management software?
A first release covering the data model, tablet field logging with offline capture, laboratory ingestion profiles and automated log and section production runs $60,000 to $140,000 over 12 to 16 weeks in Digital Heroes delivery experience. Adding a spatial historical archive, several client deliverable formats and laboratory scheduling takes it to $160,000 to $280,000 over 6 to 9 months, and a large scanned archive with instrument level integration pushes it to $280,000 to $420,000.
A consultancy running about sixty investigations a year with four laboratories and three presentation standards typically lands near $188,000.
What does it cost to run this system each year?
Budget 15 to 20 percent of build cost annually for support and change. Hosting is a small line, usually low hundreds of dollars a month with archive storage the only part that grows. Most of the recurring spend is laboratory maintenance, because laboratories change their export format or start reporting a new test and each change breaks an ingestion profile until someone fixes it.
Field tablets are the other recurring line. They have a short working life in ground investigation and belong in the same business case even though they are not a software cost.
How long does it take to build and go live?
Twelve to sixteen weeks to a first release covering the data model, field logging, laboratory ingestion and log production. Run it in parallel on two or three live jobs before committing a major project, and choose jobs with your most awkward laboratory rather than your easiest one.
Firms that already export and import AGS in their market move noticeably faster, because the interchange question is settled and the build inherits a defined structure instead of inventing one.
Is gINT or OpenGround cheaper than building our own?
For a firm running under about fifteen investigations a year to a single presentation standard, yes, and by a wide margin over three years. Bentley gINT and OpenGround, along with HoleBASE SI and the Datgel extensions, cover that work properly and the licence cost is modest against any build.
The comparison shifts at higher volume. Add up three years of licence, the cost of four more engineer seats, what your vendor charges for a new log presentation standard, and whether extracting your own data back out is chargeable. The last question matters most, because your borehole archive is the firm asset and an expensive exit path is part of the real price.
How much does extracting a historical PDF archive cost?
It depends almost entirely on scope and condition rather than volume. Extracting location, depth, stratum descriptions and headline results from digital text based reports for two metropolitan areas is typically a $30,000 to $45,000 workstream. Scanned typewritten logs from earlier decades need a different approach with human verification and can cost several times that for the same number of holes.
The way to control it is to order the work by where you bid rather than chronologically, and to accept partial extraction. The engineer will open the source report anyway, so knowing that boreholes exist at a location and roughly what they found captures most of the value.
Why do log presentation standards add so much to the price?
Because a borehole log is a drawing rather than a report. Hatching conventions, column order, how a water strike is shown, whether standard penetration test results appear as increments or a single value, and which laboratory results print alongside the description all vary by country and by client. Reproducing a standard exactly enough that a client accepts it without markup is drafting work measured in weeks.
Build one standard properly first, usually your dominant client's, then add the others as they justify themselves. Firms maintaining five presentations because five long standing clients each demand their own will see that directly in the quote.
Can we spread this across two budget years?
Yes, and the archive is the natural split. Build the data model, field logging, laboratory ingestion and log production in year one, then take the archive region by region in year two with the search interface built once. Nothing is stranded if the second year budget moves, because the first release stands on its own.
Roughly 12 percent of total spend goes into discovery, 50 percent into the first release, 25 percent into the archive and the remainder into parameter selection, design software export and training.
What are the hidden costs in a geotechnical software project?
Three recur. Capturing your presentation standards precisely enough to build against, which usually reveals conventions nobody has written down. Laboratory profile maintenance after go live, which is permanent rather than one off. And parallel running on live jobs, which costs engineer time rather than developer time and is the step firms most often try to skip.
The one that surprises people is sample identification. Laboratories return results under their own numbering and clients renumber holes between phases, so the composite identification rules take longer to agree than to implement.
Who owns the borehole data and the code?
You should own the repository, the cloud infrastructure accounts and the unrestricted right to hire another firm to continue the work, agreed in writing before kickoff. At Digital Heroes the client owns the code from the first commit.
This matters more than usual in ground investigation because the archive is the firm's accumulated knowledge of the ground under a region. It is the asset that lets you propose a smaller, smarter investigation and de risk early advice, and it should not sit in a system somebody else controls the keys to.
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.
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.
Is it cheaper to customize Salesforce than to build a custom CRM from scratch?
If you use less than a third of what Salesforce does, a custom CRM is often cheaper by year three. Salesforce Enterprise lists at $165 per user per month, so 25 seats cost about $49,500 a year before admin and consultant fees, while a focused custom CRM runs $60,000 to $100,000 once plus 15 to 20% a year in maintenance. If you genuinely need Salesforce's ecosystem, reporting, and app marketplace, customizing it beats rebuilding it; the mistake is paying enterprise prices to use it as a glorified contact list.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
If an agency builds my software, who actually owns the code?
You should own everything, assigned in writing: the contract transfers full IP to you on final payment, the code lives in your GitHub organization, and hosting runs in cloud accounts you control. The red flag is a proposal that mentions the agency's proprietary platform or framework, which usually means you are renting, not buying. Digital Heroes structures every build this way precisely so a client can fire us and lose nothing but the relationship.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
What should I have ready before I contact a development agency?
Three things, none of them technical: a one-page description of the problem in your own words, a list of the tools and spreadsheets the new system must replace or connect to, and a must-have versus nice-to-have split of features. Add a budget range, even a wide one, because it changes the conversation from fantasy to engineering. You do not need a formal specification; producing that is what a discovery phase is for.
Does the tech stack matter, and which one should I ask for?
It matters less than agencies imply, provided it is boring. A mainstream stack, something like React or Next.js on the front end, Node.js or Python behind it, and PostgreSQL for data, means thousands of developers can maintain your system if you ever change vendors. Apply one test: ask how hard it would be to hire a replacement developer for the proposed stack, and walk away from anything built on an agency's in-house framework.
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 .
