Geotechnical Investigation Data Software: Feed OpenGround, or Build Validation at Source?
The deciding question is not volume, it is who creates your data. If your own staff log the holes and one familiar laboratory returns the results, buy: gINT or OpenGround with Datgel tooling covers that properly and a build will not repay you.
On this page
The deciding question is not volume, it is who creates your data. If your own staff log the holes and one familiar laboratory returns the results, buy: gINT or OpenGround with Datgel tooling covers that properly and a build will not repay you. If data arrives from three or more subcontract drillers and two or more laboratories who do not share your software, and reconciliation takes a graduate engineer two to three weeks after every programme, build the ingestion and validation layer. Note the shape: you feed the drafting package, you do not replace it.
When is off the shelf genuinely the right call here?
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 in that ecosystem, and Datgel adds genuinely useful tooling on top. Log drafting represents years of accumulated detail in fonts, 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. If the pain is that section production is slow, that templates do not match how your team works, or that nobody has configured the abbreviation lists properly, that is a configuration and training problem inside the tool you already own. Fixing it there costs a fraction of a build and fixes it this quarter.
And buy if your investigations are staffed by your own people. Validation at source is the single highest value idea in this category, and it is only worth paying for when the source is somebody else. When your own engineer logs the hole and enters the data, the feedback loop already exists in the form of a conversation.
The honest test is how long the gap is between a driller's daily return and anybody checking it. If that gap is a day, you have the discipline the software would buy you. If it is three weeks and the rigs have demobilised, you do not.
When does a custom build actually pay off?
The signals appear on the same Wednesday after every large programme finishes.
One driller reported penetration test results with blow counts in separate columns per increment and another reported only the final value. Sample references from rig two do not match the laboratory schedule, because the driller renumbered after redrilling a hole. Water strike depths are recorded in a comments field as free text. One laboratory returned moisture content as a percentage and the other as a decimal fraction. None of that is exotic, every geotechnical team has a version of that week, and it takes two to three weeks to reconcile after every rig has left site.
That timing is the whole problem. Anything genuinely missing is now either a return visit or a gap in the factual report with a caveat attached. Unforeseen ground conditions are a classic source of dispute on civil projects, and the borehole record is the evidence base those arguments are settled from. A dataset cleaned up under time pressure by whoever was available, with the judgement calls buried in a spreadsheet, is a weak position to argue from years later.
The other trigger is client schemas. Large infrastructure clients amend the AGS standard, specifying additional groups and fields, mandating particular abbreviation lists or requiring their own naming for locations. Most consultancies satisfy that by hand, and usually through one person who knows that client. A build turns it into a project profile extending a base schema, which makes it configuration rather than tribal knowledge with a leaving date.
How do they compare on the things that matter in this industry?
- Where validation happens. Packaged tools validate what you type into them, which is the office. Validating a subcontractor's daily return the same evening, with errors that name the row, the field and the rule, is a different architecture. A same evening rejection is a fix while the rig is on site. A three week rejection is a caveat.
- Supply chain reach. Products assume everyone in the chain owns the same licence. Small drilling subcontractors will not buy geotechnical software and will not learn an application for one client, so compliance has to be made easy through a simple upload form or a validating template. That reach is the thing a build has and a licence does not.
- AGS as schema versus AGS as export. Most firms treat the standard as a deliverable produced at the end by exporting whatever they accumulated. Used as the internal schema from the first daily return, the deliverable becomes a byproduct and every project's data is comparable with every other project's.
- Sample chain of custody. Logged at the rig, transferred with a manifest, received by the laboratory with a confirmation, scheduled against a test suite, returned against your reference rather than a laboratory internal number. Turnaround tracking falls out of that for free, and laboratory delay is one of the most common causes of a late factual report.
- Non detects and units. Every laboratory has its own way of representing a value below detection limit. Handling it wrongly corrupts every summary statistic downstream, so ask any developer or vendor to explain their approach before comparing prices.
- Contaminated land on the same holes. On brownfield sites the same holes produce geotechnical and environmental samples, and geotechnical tools do not attempt screening against project assessment criteria. Most firms run two systems and maintain the location register twice.
What does total cost of ownership look like at your scale?
From Digital Heroes delivery experience, an office side first release covering schema first ingestion with AGS or DIGGS validation, project profiles for client specific requirements, sample chain of custody, laboratory scheduling and factual output runs $60,000 to $140,000 and ships in 12 to 18 weeks. A full platform adding an offline field application for rig returns, contaminant screening, ground model export and a firm wide spatial database runs $150,000 to $400,000 over 6 to 12 months.
A worked shape: a mid sized consultancy with about 60 investigations a year, four regular drilling subcontractors, two laboratories and one major infrastructure client with an amended schema lands near $112,000. Drop to one laboratory and skip the subcontractor upload portal and it is $90,000. Add the offline field application and you add $45,000 to $70,000, which is exactly how a first release becomes a platform and why that is the single largest cost decision in the category.
Component prices are worth knowing before you compare quotes. Each additional laboratory interface is $6,000 to $10,000, and the second is not half the first. Pushing validated data into gINT or OpenGround properly is $15,000 to $25,000 and should be budgeted deliberately rather than assumed free. A firm wide spatial database is $15,000 to $30,000 once the schema discipline exists, because the hard work was the schema rather than the query layer.
Annual support runs 12 to 18 percent of build cost, so roughly $13,000 to $20,000 on the worked example. Most of that 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 per interface per year. Your Bentley seats stay on the renewal either way, so this is a labour saving rather than a subscription saving, and the comparison should be run against reconciliation hours.
What does the hybrid look like, and when is it the honest answer?
The hybrid here is not optional, it is the only sensible architecture. Keep gINT or OpenGround for drafting and feed it validated data. A single data store with multiple outputs, where logs, sections, laboratory summary tables, exceedance tables and model input files all render from the same records with a version stamp, is what stops the log and the ground model diverging after a review meeting.
Within that, the cheapest useful version is deliberately narrow. One client's schema, one investigation type, one laboratory, and validation at ingest. That alone removes most of the three week reconciliation, and it does so without any of the expensive parts. Give small drilling subcontractors a simple upload form or a validating template rather than a licence they will not buy. Compliance you make easy costs almost nothing to build; compliance you mandate costs you the rest of the project in resistance.
Stage the expensive items honestly. The offline field application is the largest swing and it is worth having, but it is a local store, a sync queue, an explicit conflict rule and a visible sync state on a device that may be disconnected for days, plus photographs and geolocation. If a developer describes offline as caching, the price they quote is not for the thing you need. Leave contaminant screening, ground model export and the spatial database out of the first release.
Do not migrate history in phase one. Run the new system forward from a date, leave the archive where it is, 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 far better basis for that decision than optimism at kickoff. Existing AGS files and gINT projects convert predictably; spreadsheets from a decade ago and scanned paper logs are where budgets quietly disappear.
Which should you choose, by operator size and stage?
Own staff logging, one or two familiar laboratories, conventional client requirements: buy. Configure the tool you already have and spend the difference on training. Nothing else here applies to you.
Three or fewer large programmes a year, even with subcontract drillers: buy. The reconciliation arithmetic does not work at that volume and we would tell you so with the numbers in front of us.
Ten or more programmes a year with subcontract drillers and two or more laboratories: build the office side release. Start with the ingestion pipeline and the subcontractor upload path, because those are what convert a post demobilisation reconciliation into a same evening correction.
Firms with a major client running an amended schema: build, and put the project profile mechanism in the first release. If a new client requirement is a development ticket rather than configuration, you will be behind within a year and your team will go back to spreadsheets for the awkward jobs.
Consultancies doing geotechnical and contaminated land work on the same holes: build, and keep the location and sample registers common from day one. Rescreening against changed assessment criteria, which happens whenever a scheme's proposed end use changes, then becomes a recalculation instead of a fortnight of spreadsheet work.
Firms working repeatedly in one geography: build, and add the spatial database once the schema discipline is proven. Being able to scope a new investigation against holes you already drilled two streets away changes how you price work. For a firm whose work is scattered nationally, it is a reporting convenience.
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.
- Almost half of all the activities people are paid almost $16 trillion in wages to do in the global economy have the potential to be automated by adapting currently demonstrated technologies. Source: McKinsey Global Institute (2017) →
- Per the Standish Group CHAOS 2020 report (reviewed at this URL), across tens of thousands of software projects roughly 31% end successfully, about 50% are 'challenged', and roughly 19% fail outright; small projects succeed far more often than large ones, and Agile approaches succeed at markedly higher rates than Waterfall. Source: The Standish Group (2020) →
- Salesforce's field-service research (State of Service / field service trends, survey of 5,500+ service professionals) found that 74% of mobile workers report increasing workloads and 47% say appointments don't go as planned due to customer miscommunication, unaccounted-for parts, or insufficient appointment lengths and travel times. (The separate claim that admin tasks consume ~30% of a technician's hours is NOT supported by the report - the seventh-edition data instead states technicians spend about 18% of working hours, ~7 hours/week, on admin, and only ~32% of time interacting with customers.). Source: Salesforce (2024) →
- One in four US employees report lacking career advancement opportunities; 48% of employees who participated in mentorship programs report high job satisfaction versus 29% of non-participants, and access to advancement opportunities ranges from 33% at organizations under 10 employees to 74% at those with 1,000+. Source: Gallup (2025) →
Frequently asked questions
What does it cost to switch drafting packages later if we build the data layer?
Much less than switching cold, because the authoritative records already sit in your own store in a standard schema rather than inside the drafting tool. Moving from one drafting package to another becomes a matter of rebuilding output templates rather than migrating data.
That is one of the quieter arguments for the layered architecture. Templates are weeks of drafting work and painful either way, but they are a known quantity. Recovering data that only ever existed inside a vendor's project file is the part that turns a switch into a project.
What happens if AGS is revised or a client changes its amended schema?
Both happen on their own schedule and neither should be a rebuild. A base schema with project profiles extending it means a client revision is configuration, and a standard revision is a version of the base schema that new projects adopt while old ones stay pinned.
Budget for it rather than hoping. Two to four days of maintenance per interface per year is the realistic figure, covering laboratory layout changes and client framework revisions together. Firms that do not fund this discover it during a busy autumn.
How long does the build take, and when does it start paying?
Twelve to eighteen weeks for the office side release, six to twelve months for a full platform. 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 the ingestion pipeline goes live early, ideally by week seven. If subcontractors are getting real rejection messages while the rest is still being built, the system is already catching errors that would otherwise be found after demobilisation.
Should we replace gINT, and what does integrating with it cost?
Integrate, and treat anyone proposing to replace it as a warning about their judgement generally. Log drafting carries years of accumulated detail in hatching, abbreviation lists and layout rules that is invisible until you try to reproduce it.
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 changes how data reaches those seats, which is a labour saving rather than a subscription saving.
How do we get small drilling subcontractors to submit valid data?
Make compliance easy rather than mandatory. A simple upload form or a validating spreadsheet template that produces conforming data costs little to build and asks nothing of a subcontractor beyond what they already do.
Demanding they buy geotechnical software or learn your application for one client is a conversation that ends politely and changes nothing. This is the specific point where a build reaches further than a licence, because products assume everyone in the supply chain holds the same seat.
How much does the offline field application add, and is it worth it?
Between $45,000 and $70,000 on top of an office side build, and it is the decision that turns a first release into 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 disconnected for days rather than minutes, plus photographs and geolocation.
It is worth it when validation at the rig converts a three week reconciliation into a same evening correction across many programmes a year. At three programmes a year it is not, and we would say so.
What does migrating our historic borehole data cost?
It should be priced as its own decision rather than folded into the build, because it is the line item that quietly consumes budgets. Existing AGS files and gINT projects convert reasonably predictably. Spreadsheets from a decade ago and scanned paper logs need judgement per project and vary enormously with how disciplined the archive was.
Run the new system forward from a date, leave the archive alone in phase one, and revisit in six months. By then you will know which geographies you actually query, which is a much better basis for the decision.
Who owns the code and the ground data if an agency builds this?
You should own the repository, the cloud infrastructure accounts and an 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 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.
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.
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.
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.
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.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
How many people should be working on my software project?
A typical $40,000 to $150,000 build runs on three to five people: a technical lead, one or two developers, a designer, and someone owning QA and project communication, often as overlapping part-time roles. More bodies do not make software arrive faster; past a point they slow it down with coordination overhead. The question that matters more than headcount is whether one named senior engineer is accountable for the outcome.
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 much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
Will custom software work with the tools we already use, like QuickBooks and Stripe?
Yes, and this is one of custom software's genuine advantages: QuickBooks, Stripe, Shopify, and most mainstream business tools publish documented APIs built for exactly this. Expect each standard integration to add one to two weeks of build time, and be suspicious of any quote that lists five integrations without asking what data flows in which direction. The hard cases are legacy systems with no API, which is a question to raise in discovery, not in week nine.
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.
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.
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 Ahaan.
Senior Android Engineer · Delhi · 1 post on the site
Published · Last updated .
