30-min call with RobBook a proof-of-concept call
Subsurface investigations and foundation reports

// AI for geotechnical engineering firms

AI for geotechnical engineering firms, tested on investigations you already scoped and reported.

For firms that drill, sample and test the ground under commercial buildings, public facilities and infrastructure, then write the foundation recommendations. Begin with investigation proposal scopes read from a client's request, or with boring log data tables reconciled from field logs and lab sheets. Either one becomes a free AI proof of concept on copies of 20 to 30 projects your office has closed, with no login to your project system or a client portal. Your reviewer, the engineer who knows that work best, decides whether it held up, and every technical call stays with a licensed engineer.

Book a proof-of-concept call30 minutes with Rob
Geotechnical firm proof of conceptAgreed up front
First job
Investigation proposal scopes, or boring log data tables
From you
20 to 30 closed projects, copied once the NDA is signed
Never touched
Your project system, a client portal, a live proposal or report
Engineer only
Scope, soil classification, foundation advice and every seal
Reviewer
Named by the owner, often a senior project engineer
Price
A range now, a fixed figure before signing

// Jobs we would test

Start before the rig moves, or after the lab reports back

Scopes or log tables first
Commercial and public work

// Why these two first

The engineer decides. The paper around each decision already has an answer key.

Codes name who sets the scope. New York City's Building Code, in its Chapter 18 as amended by Local Law 77 of 2023, says an engineer shall scope, supervise and approve the subsurface investigation and the classification of the soil and rock it finds. Section 1803.4.1 leaves the number, types and depths of borings, the drilling and sampling equipment, the in-situ tests and the lab program to the engineer responsible for the investigation. A draft can gather what a request asks for. What the site needs is decided by that engineer.

Much of a report is a record. The same chapter calls for a signed and sealed geotechnical report whose required contents start with a description of the planned structure, a plot of the boring locations, a complete record of sample descriptions, the soil and rock profile, groundwater and flood elevations, and in-situ and lab results, all listed ahead of any recommendation. Those record sections are assembled from field logs and lab sheets line by line, and each closed project shows how your firm assembled them.

Public clients put a clock on the scope. Loudoun County, Virginia's 2025 request for geotechnical engineering and soil scientist services gives the consultant 48 hours to respond once the county gives notice of work. A meeting follows, then a lump sum proposal priced from the contract's hourly rates, with hours by category of service, a narrative of the work, every non-labor cost and a schedule of subtasks in calendar days. Each task order proposal also names a quality control reviewer, a senior member of the firm who is neither the project manager nor the project engineer. That is a lot of careful reading to finish fast.

Each agency wants its own log. Caltrans requires any organization providing geotechnical reports or records of investigations to the Department to follow its Soil and Rock Logging, Classification, and Presentation Manual, whose 2022 edition took effect on July 1, 2023. Its Log of Test Borings is usually tied to a structure, sits in the project plans and travels with a separate Test Boring Layout sheet. A firm serving several agencies lays out the same kind of data many ways, and its finished reports show every layout it delivered.

A draft is not a sealed document. Texas engineering rules let a license holder seal only work they did or directly supervised. A preliminary document released from their control carries a statement instead of a seal: what it was released for, such as interim review, under whose authority and on what date, and that it is not for construction, bidding or permits. Nothing from this proof of concept is released, signed or sealed; it is a draft for your engineer to accept, correct or discard. These summaries of published rules are not legal or engineering advice.

One limit covers every job here. The proof of concept reads copies and drafts. It never touches your project system, a client portal, a live proposal or a live report, and it never classifies a soil, sets a scope, recommends a foundation or seals a document. Every technical call, and every seal, belongs to a licensed engineer.

// How the test runs

One job, three steps, nothing live

  1. Step 01

    Pick the job, name the reviewer

    The owner or a principal picks one job and names the reviewer, often a senior project engineer for scopes, or whoever checks final logs for the tables. Before a single file is copied, the success criteria are in writing, you hold a price range for the live job, and the NDA is signed.

  2. Step 02

    Run it on closed projects

    Send copies of 20 to 30 closed projects: requests with the proposals they became, or field logs and lab sheets with the report tables built from them. Massmarket's name for this step is the sandbox, and here it means reading finished geotechnical work only. Projects that can't leave the office become look-alikes, built with your reviewer.

  3. Step 03

    After a yes, about 30 days live

    New requests or newly drilled projects go through the same job for about 30 days. An engineer approves every draft before it reaches a client, a lab or a report. A second job, if you want one, is decided separately and carries its own price.

Priced per job. You get a range before the proof of concept and a fixed price before you sign.

Rob sets the range on the call from three counts: investigation requests your office scopes in a month, borings logged in a typical quarter, and the agencies whose log formats you deliver to.

// Questions

What geotechnical firm owners ask first

Does the test need our project system or logging software?
No. It runs on copies and exports only: requests, site plans, proposals, field logs, lab sheets and finished reports as PDFs or spreadsheets. We never log in to a system of yours or to a client's portal.
Will the AI classify soils or choose boring depths?
No. Classification, the number and depth of borings and every recommendation belong to your engineer. The drafts repeat what the documents say, show where they disagree, and leave each technical field for a licensed engineer.
Our clients range from DOTs and counties to private developers. Should the sample mix them?
Yes. Public agencies tend to bring their own scope forms and log layouts, while private requests are often shorter and looser. A sample with both shows your reviewer how the drafts handle each kind.
Which of the two jobs should we test first?
Whichever desk is more backed up. If requests wait days for a scope, start with proposals; if reports wait on someone keying logs and lab data into tables, start there. Both run the same way, on copies of closed work.
We also do construction materials testing. Is that covered?
Not in the first test. Daily testing reports could become a later job with its own sample and success criteria, once one of these two has been judged by your reviewer.
Rob Eason

Rob Eason, founder

// Book a proof of concept call

Start from the investigations you scoped last quarter.

Half an hour with Rob about your firm and your role, the job you'd test first, and roughly how many investigations you scope and report in a month. Requests, logs and lab sheets remain in your office until the NDA is signed.

  • Co-owned a 60-employee financial services firm and sold his share to his partner.
  • Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
  • 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
  • 4.3/5 from 6 Google reviews of Massmarket AI.
  • Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
  • Takes every proof-of-concept call himself.