How Much Does Geotechnical Investigation Data Software Cost in 2026?
$60,000 to $400,000 is the realistic span, and the single decision that moves it most is whether validation happens at the rig or back in the office.
On this page
$60,000 to $400,000 is the realistic span, and the single decision that moves it most is whether validation happens at the rig or back in the office. An office-side build, meaning schema first ingestion with AGS or DIGGS validation, sample chain of custody, laboratory scheduling and factual output, sits at $60,000 to $140,000 and ships in 12 to 18 weeks. Adding an offline field application so a driller's daily return is validated the same evening, while the rig is still on site, pushes you toward the $150,000 to $400,000 platform band, because genuine offline capture with photographs and geolocation is real engineering rather than a mobile view of a web form.
The bands a geotechnical data build falls into
Three price points, and they correspond to how far up the chain you push validation.
The first is an office-side data platform at $60,000 to $140,000, shipping in 12 to 18 weeks in our delivery experience. Every incoming file, whether an AGS transfer, a laboratory return or a spreadsheet from a subcontractor who has never used the standard, is parsed against a defined structure and rejected with errors that name the row, the field and the rule. Samples carry a chain of custody from rig to laboratory. Test suites are configurable per client. Factual output and log drafting are fed rather than replaced.
The second is a full platform at $150,000 to $400,000 over 6 to 12 months. That adds an offline field application for daily rig returns, contaminant screening against project assessment criteria, ground model export, and a firm wide spatial database you can query before pricing the next bid.
Below $60,000 you are buying an importer, not a system. A parser that turns three drillers' spreadsheets into one consistent file is genuinely useful and can be built for $25,000 to $40,000. It will not give you chain of custody, laboratory turnaround visibility or a queryable regional dataset, so be clear about which problem you are solving.
What drives a geotechnical build up
Five drivers explain nearly every quote at the top of a band rather than the bottom.
- The offline field application. Offline means a local store, a sync queue, an explicit conflict rule and a visible sync state, on a device that may be disconnected for days. It also means photographs and geolocation. This is the largest single swing in the category.
- Laboratory interfaces. Every laboratory returns results in its own layout, with its own internal sample numbering and its own treatment of values below detection limit. Each interface is real work. Two laboratories is not twice one laboratory, but four is close to four times one.
- gINT or OpenGround integration. Pushing validated data into Bentley's ecosystem so log drafting stays where it belongs is the right architecture and it is not trivial. Budget for it deliberately rather than assuming it comes free.
- Continuous instrument data. Cone penetration testing and similar produce volumes and processing needs that are nothing like discrete sampling. Treat it as a separate module.
- Historic migration. This is where budgets quietly disappear. Existing AGS files and gINT projects convert reasonably. Spreadsheets from 2011 and scanned paper logs require judgement per project.
What keeps the number down
The cheapest useful version of this system is narrow on purpose. Pick one client's schema, one investigation type and one laboratory, and put validation at ingest. That alone removes most of the three week reconciliation that happens after every rig has demobilised, and it does so without any of the expensive parts.
Give small drilling subcontractors a simple upload form or a template that produces valid data, rather than a licence they will not buy and an application they will not learn. Compliance you make easy costs almost nothing to build. Compliance you mandate costs you the rest of the project in resistance.
Leave the ground model export, the contaminant screening and the spatial database out of the first release. Do not migrate history in phase one either. Run the new system forward from a date, keep the archive where it is, and decide in six months how far back is commercially worth converting once you know what the data is actually being used for.
A worked example that adds up
A mid-sized consultancy, roughly 60 investigations a year, four regular drilling subcontractors, two laboratories, one major infrastructure client with an amended schema. Here is how a $112,000 first release breaks down.
- Discovery, base AGS schema and project profiles for the amended client requirements: $12,000
- Ingestion pipeline with row-level, field-level and rule-level rejection messages plus a quarantine queue: $26,000
- Subcontractor upload portal and validating templates for drillers with no geotechnical software: $14,000
- Sample chain of custody from rig to laboratory, with manifests and receipt confirmation: $18,000
- Two laboratory result interfaces, including detection limit handling and unit normalisation: $16,000
- Factual output and a push into gINT so log drafting stays where it is: $18,000
- Deployment, training and one live project run in parallel with the old process: $8,000
That totals $112,000. Drop to one laboratory, at $8,000 for the interface rather than $16,000, and skip the subcontractor portal, and you are at $90,000. Add an offline field application for rig returns and you add $45,000 to $70,000, which is exactly how a first release becomes a platform.
How the spend phases
In a 16 week first release the money goes out in three stages. Weeks one to three are schema and discovery, and this is the part clients try to shorten and should not, because an argument about what a sample reference means is far cheaper in week two than in week twelve.
Weeks four to twelve carry the ingestion pipeline, the chain of custody and the laboratory interfaces. The ingestion pipeline should be usable long before the rest is done. If your subcontractors can upload and get real rejection messages by week seven, the system has already started paying, because the errors it catches are errors that would otherwise have been discovered after demobilisation.
The last four weeks are outputs, gINT integration and a parallel run. Insist on the parallel run. One live project processed both ways is where you discover the undocumented rules your senior engineer has been applying by hand for years, and encoding those is the difference between a system your team uses and one they work around.
The ongoing costs nobody quotes
Running costs in this category are modest but not zero, and they are almost never in the proposal.
- Hosting and storage. Small until you add field photographs and continuous instrument data, at which point storage becomes a real line.
- Format drift. Laboratories change their export layouts. Clients revise their amended schemas between framework periods. AGS itself is revised. Assume two to four days of maintenance per interface per year.
- Project profile setup. Each new client with bespoke requirements needs a profile configured. If that is a development ticket rather than configuration, you will be paying for it forever, which is why the profile mechanism matters at build time.
- Support retainer. 12 to 18 percent of build cost annually is the sensible band, so roughly $13,000 to $20,000 on the worked example above.
- Long term retention. Ground data gets re-examined in disputes years later. Budget for keeping it accessible, not just backed up.
Comparing a build against your current renewal
This comparison is less clean than in most sectors, because you are probably not replacing your licences. Log drafting stays in gINT or OpenGround either way, so those seats remain on your renewal.
Do the arithmetic on the labour instead. Take a typical investigation with three subcontract drillers and two laboratories, and count the reconciliation hours honestly: a graduate engineer for two to three weeks per programme, plus the senior review, plus whatever a return visit costs when something genuinely missing is discovered after demobilisation. Multiply by the number of programmes a year that carry that pattern.
Suppose that is 12 programmes a year at 60 hours each. At $95 an hour blended that is $68,400 annually in reconciliation alone, before you count the return visits or the caveats you had to write into factual reports. Against a $112,000 build plus roughly $16,000 a year in retainer, the payback arithmetic is usually straightforward at that volume and clearly negative at three programmes a year. Count your own programmes before assuming which side you are on.
When buying beats building
If you are a small or mid sized consultancy producing logs on a modest number of projects a year, with conventional client requirements and one or two familiar laboratories, buy. gINT remains widely used, OpenGround is the current path, and Datgel adds genuinely useful tooling on top of that ecosystem. Log drafting in particular represents years of accumulated detail in hatching, abbreviation lists and layout rules, and nobody should be rebuilding it as part of a first release. Any developer who proposes to has not understood what they are quoting.
Buy also if your real complaint is the drafting workflow rather than the data flow. That is a configuration and training problem inside the tool you already own, and it is far cheaper to fix there.
Build when two or more of these are true: you run large programmes where data arrives from subcontract drillers and laboratories who do not share your software; clients impose bespoke schemas your team currently satisfies by hand, usually via one person who knows that client; you want validation at source with a field application, which changes the economics of the whole investigation rather than just the office; your work spans geotechnical and contaminated land on the same holes; or you work repeatedly in one geography and the accumulated ground dataset should be an asset you can query and price against rather than a folder tree organised by job number.
When the shortlist is down to two and you need a tiebreaker, 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.
- 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) →
- Analyst estimates place CRM implementation failure rates broadly between roughly 30% and 70% (Johnny Grow cites Forrester at 47%), with low user adoption repeatedly cited as a leading cause of failed CRM projects (this being Johnny Grow's own analysis, not a Forrester attribution). Source: Johnny Grow (industry analysis citing Gartner/Forrester) (2025) →
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
Frequently asked questions
How much does custom geotechnical data management software cost?
An office-side first release covering schema first ingestion with AGS or DIGGS validation, project profiles, sample chain of custody, laboratory scheduling and factual output runs $60,000 to $140,000 and ships in 12 to 18 weeks in our delivery experience. A full platform adding an offline field application, contaminant screening, ground model export and a firm wide spatial database runs $150,000 to $400,000 over 6 to 12 months.
A worked mid-sized example with two laboratories, four subcontract drillers and one amended client schema lands near $112,000.
What does it cost to run each year?
Budget 12 to 18 percent of build cost as an annual support retainer, so roughly $13,000 to $20,000 on a $112,000 build. Hosting is modest until field photographs and continuous instrument data arrive, at which point storage becomes a genuine line item.
The recurring cost people forget is format drift. Laboratories change export layouts, clients revise amended schemas between framework periods, and the standard itself is revised. Allow two to four days of maintenance per interface per year, and make sure new client project profiles are configuration rather than a development ticket, or that cost never stops.
How much does the offline field application add?
Expect $45,000 to $70,000 on top of an office-side build. That is the single largest cost decision in this category, and it is the reason a first release becomes a platform.
What you are paying for is a local store, a sync queue, an explicit conflict resolution rule and a visible sync state, on a device that may be disconnected for days rather than minutes, plus photographs and geolocation. It buys you validation while the rig is still on site, which converts a three week reconciliation into a same-evening correction. If a developer describes offline as caching, the price they quote is not for the thing you need.
Should we replace gINT or integrate with it, and what does that cost?
Integrate. Log drafting in gINT and OpenGround represents years of accumulated detail in fonts, hatching, abbreviation lists and layout rules, and rebuilding it inside a first release is the fastest way to lose a budget. Budget $15,000 to $25,000 for a proper push of validated data into that ecosystem as an output channel.
Your Bentley seats stay on the renewal either way, so this build is not a licence replacement. It is a change to how data reaches those seats, which is a labour saving rather than a subscription saving.
How long does it take to build?
A first release ships in 12 to 18 weeks, and a full platform phases over 6 to 12 months. Weeks one to three are schema and discovery, which clients try to shorten and should not, because an argument about what a sample reference means costs far less in week two than in week twelve.
Insist that the ingestion pipeline goes live early, ideally by week seven, so subcontractors are getting real rejection messages while the rest is still being built. Insist too on one live project processed in parallel with the old process before cutover.
What does migrating historic borehole data cost?
It is the line item that quietly consumes budgets, and it should be priced separately from the build rather than folded in. Existing AGS files and gINT projects convert reasonably predictably. Spreadsheets from a decade ago and scanned paper logs need judgement per project, so cost varies with how disciplined your archive was.
Our advice is to run the new system forward from a date, leave the archive alone in phase one, and decide in six months how far back is commercially worth converting. By then you will know which geographies you actually query, which is a much better basis for that decision than optimism at kickoff.
How much does each additional laboratory interface cost?
Typically $6,000 to $10,000 each, and the second is not half the first. Every laboratory has its own layout, its own internal sample numbering that must be reconciled to yours, its own unit conventions and its own way of representing a value below detection limit.
That last point deserves attention when you are comparing quotes. Handling non-detects wrongly corrupts every summary statistic downstream, so ask any developer to explain their approach before you accept the cheaper interface price.
Is a firm wide ground database worth the extra spend?
Once data is schema first and validated, spatial querying across historic investigations is one of the cheaper additions, usually $15,000 to $30,000, because the hard work was the schema discipline rather than the query layer.
Whether it pays depends on your geography. For a consultancy working repeatedly in the same city it changes commercial behaviour, because you can scope and price a new investigation against holes you already drilled two streets away instead of pricing the ground as unknown. For a firm whose work is scattered nationally it is a reporting convenience rather than an advantage.
Who owns the code and the data?
You should own the repository, the cloud infrastructure accounts and the unrestricted right to bring in another firm, settled in writing before kickoff. At Digital Heroes the client owns the code from the first commit and it is not a priced extra.
This matters more here than in most sectors. Ground data is evidence, and it may be re-examined in a dispute a decade after the investigation closed. Control of both the records and the system that validated them is a professional risk question rather than a commercial preference.
Is a solo freelancer enough for my project, or do I really need an agency?
A solo freelancer is a fine choice for a well-defined build under roughly $15,000 to $20,000 with a limited lifespan: an internal calculator, a scripted integration, a prototype. Above $50,000, or for any system your business will depend on for years, you are buying continuity as much as code: enforced code review, cover when someone is ill, and support that outlasts one person's career plans. Price the risk of a single point of failure, not just the hourly rate.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
What happens if I stop paying for maintenance after launch?
Nothing breaks on day one, which is what makes it dangerous. Within 6 to 18 months, unpatched dependencies accumulate known vulnerabilities, an integrated API like Stripe ships a breaking change, and the first fix requires a developer to relearn a stale codebase at full price. Budget 15 to 20% of the build cost per year for upkeep; it is the difference between a $500 patch and a $15,000 emergency.
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 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.
What is a discovery phase, and is it worth paying for separately?
Pay for it, and treat the output as yours. A discovery phase runs two to three weeks, typically 5 to 10% of the eventual build budget, and produces a written scope, wireframes, and a fixed quote you can take to any vendor, including a competitor of the agency that wrote it. Skipping it is how projects end up quoted from a two-paragraph email and delivered at twice the price.
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
More from Divyansh.
Client Success Manager · Lucknow · 1 post on the site
Published · Last updated .
