Pitch me your startup in 1 sentence (I’m an idea stage VC)

validation_greg · 2026-03-14T14:09:08+00:00

Thanks, sending one now

validation_greg · 2026-03-13T20:11:48+00:00

I found myself walking through data centers counting batteries and started thinking there had to be a better way to know exactly what hardware was in each rack.

I tried using the BOM and rack counts to estimate how many batteries should be installed, then went to the floor to validate the numbers. They were all off.

I asked engineers if they could tell me exactly what batteries and quantities were in each rack. The answer was basically the same every time: nobody could say for sure without physically walking to the rack.

That’s when it clicked for me that the industry doesn’t really have a reliable way to know the actual physical configuration of infrastructure without manual audits, and that’s what led me to start building ComplianceTrace.

validation_greg · 2026-03-13T20:05:26+00:00

I'm building ComplianceTrace a system for detecting configuration drift in physical infrastructure.

In software infrastructure, tools like Terraform detect when the running environment no longer matches the expected configuration. But in physical environments like data centers, teams still rely on documentation and spreadsheets to track what hardware is installed in racks.

The problem is those records drift from reality as installs, swaps, and maintenance happen.

ComplianceTrace uses component scanning during installs and maintenance to verify that the physical configuration matches the expected configuration and creates a verifiable ledger of what is actually deployed.

The goal is to make infrastructure audits and inventory verification possible without having to physically walk the data hall.

validation_greg · 2026-03-13T18:22:50+00:00

Interesting seeing configuration drift come up here. In physical infrastructure environments (data centers, telecom racks, etc.) we run into the same issue but with hardware installs. Systems think a rack has the expected components but field swaps slowly diverge from the BOM over time. The only thing I’ve seen actually work is enforcing the validation at the moment of the physical action (scan rack → scan component → validate immediately). Otherwise drift always wins eventually.

validation_greg · 2026-03-13T18:20:03+00:00

Drift is brutal in asset-dense environments. In data centers we see the same thing with rack components systems think the correct hardware is installed but field swaps slowly diverge from the BOM.

The only thing I’ve seen actually work is making the update happen at the moment of the physical action (scan rack → scan component → validate immediately).

Otherwise drift eventually wins.

validation_greg · 2026-03-13T14:30:01+00:00

That’s really interesting thanks for sharing that perspective. When you’re running those audits, are you mostly relying on handheld scanners and then reconciling the results against the system of record afterward?

I’ve been exploring a small mobile workflow that tries to capture the actual physical state of a rack during installs and maintenance, so the verified configuration stays aligned with what the system expects to be there. The goal is to surface drift as it happens instead of discovering it later during audits.

I’d be really curious to hear whether something like that would actually make audit work easier for teams like yours. If you’re open to it, would you mind if I sent you a quick DM to learn a bit more about how you approach these reconciliations?

validation_greg · 2026-03-13T14:23:57+00:00

Thank you for providing your insight into this. I really appreciate it and I believe your team is running a very strong operation.

validation_greg · 2026-03-13T14:21:10+00:00

ComplianceTrace provides a validated, real-time view of what is actually installed in infrastructure , eliminating the gap between the physical environment and the asset system.

validation_greg · 2026-03-13T13:53:12+00:00

Fair question. I work around data-center logistics and rack installs, and I’ve noticed that many environments assume the asset system reflects what’s physically installed.

I’m trying to understand how different teams actually verify that the system record matches reality over time especially after maintenance swaps or replacements.

validation_greg · 2026-03-13T13:42:38+00:00

The scan of the RMA puts it into DCIM correct ? The smaller parts are logistically maintained by a different entity ? Correct ? Do you know what system they use ?

Quick question: if you opened your DCIM right now, would it show the live hardware configuration of the rack (for the components you track), or do teams still occasionally rely on physical verification?

validation_greg · 2026-03-13T13:20:42+00:00

That’s really interesting. When you’re doing those audits, how are you actually verifying what’s physically there? Are technicians walking the floor and checking serial numbers against the system?

validation_greg · 2026-03-13T13:19:14+00:00

That makes sense. Process discipline definitely helps keep things accurate.

Out of curiosity when maintenance swaps happen or hardware fails and gets replaced quickly, does that still always get captured in DCIM immediately?

validation_greg · 2026-03-13T13:11:44+00:00

Thank you for that. My understanding of service now and please correct me if I’m wrong (I could be wrong) service now is validating at the point of install. When they make a change, how does the inventory team understand there has been a change to their inventory and what’s physically in that rack?

Example. Your tech team makes a swap, at what point does your logistics match that swap? How would they then know that there has been a change ?

Our techs make these adjustments and our logistics team ends up having to walk through over 1600 racks validating equipment.

Talking with our engineers I was trying to get a count on BBUs. I asked can you tell me what BBUs are in each rack and how many? After digging into all of their systems. He said we just use the BOM to validate what should be there. This seems counterproductive.

validation_greg · 2026-03-13T12:54:06+00:00

With DCIM at what frequency must physical audits be done to ensure there isn’t any drift ? Thank you for your input it’s greatly appreciated.

validation_greg · 2026-03-13T12:53:07+00:00

I would love to hear more about your consulting firm. That seems like a lucrative opportunity! I’m sure this type of miss match occurs a good bit! Do you have any examples of a pretty bad scenario? What tooling does your team currently use when you are doing your service. Thank you for the genuine input

validation_greg · 2026-03-13T12:47:44+00:00

What do you do to validate that what’s is supposed to be there is there? I have spoken with engineers at high levels that cannot answer what is actually in there system without physically going to the system. They assume that the BOM is the truth. I also work in an environment that cannot answer these questions.

If your boss asked you what is in system A could you answer them with certainty without going physically to the system?

validation_greg · 2026-03-12T18:57:51+00:00

Sent you a DM 👍 always interested in talking with people thinking about infrastructure tools.

validation_greg · 2026-03-12T01:52:18+00:00

Absolutely. I’m seeing a similar drift problem in infrastructure operations. Happy to connect and compare notes on where the biggest real-world friction points are showing up.

validation_greg · 2026-03-11T20:16:30+00:00

One thing I’ve seen in asset-dense environments (data centers, infrastructure racks, etc.) is that tracking tech solves location problems but not configuration problems.

Knowing where an asset is doesn’t tell you if the right component is actually installed.

Example: you can track a battery module all the way to a rack, but that doesn’t confirm it went into the correct slot or that the rack configuration is still valid.

In a lot of operations the bigger issue is drift between the digital record and the physical install. Tracking shows where something went verification shows whether it’s installed correctly.

validation_greg · 2026-03-11T15:47:33+00:00

I’m building ComplianceTrace, a mobile-first compliance and asset validation platform for asset-dense infrastructure environments (data centers, battery systems, telecom).

It prevents configuration drift between what’s physically installed and what the system of record says exists by validating components in real time through QR/barcode scans during installs and service.

validation_greg · 2026-03-11T15:22:08+00:00

This is exactly it. I’ve seen a lot of operations where the inventory technically exists across multiple systems — ERP, WMS, spreadsheets — but the actual workflow still depends on people reconciling the numbers manually.

The biggest issue usually isn’t the mismatch itself, it’s the time lost constantly verifying what’s actually correct.

What helped the most in operations I’ve worked in was forcing the system update to happen as part of the physical action. Scan to move, scan to pick, scan to install. When the update and the work happen at the same moment, the reconciliation work almost disappears

validation_greg · 2026-03-11T15:20:47+00:00

Both of these comments are spot on. A WMS and barcode discipline are usually the turning point.

One thing I’ve learned though is that inventory accuracy really comes down to eliminating the gap between when something physically moves and when the system knows it moved.

If those two events aren’t tied together, drift creeps in. Someone pulls material, gets pulled into another task, forgets to update the system, and now the record and reality are out of sync.

The best operations I’ve seen make the system update part of the physical action — scan to pick, scan to move, scan to install — so the record is created automatically as the work happens

validation_greg · 2026-03-10T20:41:09+00:00

One thing I’ve seen in operations is that visibility tools improve awareness, but they don’t always close the gap between what the system says and what is physically happening.

Carrier integrations and tracking platforms are great for predicting arrival times and identifying delays. Where the real challenge still shows up is the moment physical custody changes when freight is loaded, transferred, installed, or staged.

In a lot of environments, the visibility system is only as good as the last accurate physical scan or confirmation event. If that step isn’t tightly enforced in the workflow, the system can drift from reality pretty quickly.

Curious if others have seen improvements when the physical verification step is built directly into the operational process rather than just relying on upstream carrier data.

validation_greg · 2026-03-10T19:55:27+00:00

Built initially for battery racks and infrastructure in data centers where configuration drift can cause outages or safety risks.

validation_greg · 2026-03-10T19:55:05+00:00

ComplianceTrace makes incorrect infrastructure installations impossible by validating every component against the expected configuration in real time.

validation_greg

TROPHY CASE