Landon Reid

Hey PH I'm Landon. I live in Parowan, Utah (population 3,000). My son Carson and I are building proptech tools from our home office.

Quick background: I've been in real estate for 10+ years land deals, property development, the whole thing. Carson taught himself to code and turned out to be one of those rare people who can build a full product in a weekend.

We started TinyHomies.com in 2022 (tiny home marketplace, 15K sign-ups). That taught us the real pain point wasn't finding homes it was figuring out what you could actually build on a piece of land. Every city has different zoning, different rules, different processes.

So we built ReadyPermit.ai paste any US address, get a full buildability and zoning report in 60 seconds. We also just launched Landar.ai for land intelligence.

Here's the thing nobody tells you about building permit software: the problem isn't technical. It's that every city in America has different zoning rules, different codes, different processes. There's no API for "can I build an ADU on this lot in Dallas?"

So we built one.

My son and I spent a decade in real estate buying land, developing properties, running into the same wall every time: weeks of research just to figure out if a property was buildable. We'd pay consultants $2-5K or burn 40+ hours on municipal websites that look like they were built in 2003.

ReadyPermit.ai takes any US address and returns a full buildability report in 60 seconds. Zoning classification, setback requirements, flood zone risk, ADU eligibility, permit complexity scoring all sourced from real municipal data.

One thing we think is still underrated in compute platforms is observability.

A lot of infra feels simple until something breaks in production. A webhook fails, a cron job doesn t run, an AI agent gets stuck, or a function times out even though it worked fine in testing.

That is where just running code stops being enough.

In Inquir Compute, we think logs and observability are a core part of the product, because developers need more than raw output. They need context: what triggered the execution, which route or webhook was involved, how long it ran, whether it retried, and what happened right before the failure.