Our journey into geotechnical software began early in our career in our previous role with another company, we were tasked with taking over and maintaining a Cone Penetration Test (CPT) spreadsheet that was prepared by a previous engineer.

The company wanted to keep using the tool but as it was built on Visual Basic for Applications (VBA) macro code, there was no one left who possessed the required programming knowledge required to maintain or troubleshoot it. Stepping into that gap was our first real exposure to how raw field data transforms into actionable soil profiles and empirical correlations. It also taught us a critical lesson about industry tools: spreadsheets are fragile, incredibly dependent on individual authors, and tethered entirely to desktop desks.

Even though mobile technology was not yet advanced enough to handle heavy engineering computations back then, a seed was planted. We realised that relying on fragile, macro-based spreadsheets was a massive risk for engineering firms.

We envisioned a robust and standalone application that could eliminate this hurdle and break the workflow free from office desktops, allowing engineers, whether standing in the field or sitting in an office, to process and analyse CPT data files the moment they were generated.

When we finally brought this app to life, our design philosophy revolved around creating a completely self-contained ecosystem. We wanted to eliminate the fragmented workflow of downloading files on one machine, running calculations on another, and formatting graphs on a third. To achieve this, we built a seamless pipeline that handles everything from handling raw data files to final reporting.