The AEC industry has a software problem, but it's not the one most people describe. The complaint is usually about adoption — contractors who won't change their workflows, field crews who revert to spreadsheets, PMs who manage million-dollar projects from a whiteboard. That's real. But the adoption problem is downstream of a trust problem, and the trust problem is downstream of something more fundamental: most AEC software wasn't designed by people who understand the work at operating depth.
Operating depth means something specific. It doesn't mean you've toured a job site or interviewed a dozen project managers. It means you've navigated a permit that got kicked back three times because the agency uses a custom form that isn't on their website. It means you've written a subcontractor contract at 11pm because the job starts Tuesday. It means you've had the conversation with a client about a change order and felt the specific social weight of that conversation — the relationship tension, the margin pressure, the instinct about whether to hold the line or absorb it. Software built without that experience tends to optimize the wrong things.
Hesiod's answer to this problem is structural. We don't just build software and hire advisors with construction backgrounds. We operate businesses at every level of the AEC stack simultaneously — and those businesses inform each other in ways that compound over time.
The permit desk, from the inside. EntitleHQ started because the permitting and entitlement process is one of the most consistent sources of project delay and cost overrun in civil and commercial construction — and it remains almost entirely unaddressed by software. The timelines are unpredictable. The agency contacts are informal knowledge that lives in practitioners' heads. The documentation requirements vary by jurisdiction and by reviewer. EntitleHQ is being built to address all of this: AI-powered document analysis, automated CPM schedule generation tied to permit milestones, agency contact intelligence, and a project view that gives civil engineers and developers visibility they've never had. None of these features were conceived in a vacuum. They came from working the process and cataloguing exactly where it breaks.
The contractor's back office, rebuilt. Chalk Line Studio builds digital infrastructure for contractors — the websites, CRM systems, and operations platforms that most contractors either don't have or have cobbled together from tools that don't communicate with each other. The insight behind Chalk Line is that the contractor market is underserved not because contractors don't value good tools, but because most available tools were designed for SaaS companies or professional services firms with fundamentally different operating rhythms. A flooring contractor doesn't need a Salesforce implementation. They need a system that tracks leads, manages job timelines, sends client updates, and integrates with how they already work — without requiring a full-time administrator to maintain. Chalk Line builds that. More importantly, Chalk Line's client relationships give us a continuous, unfiltered signal about what the contractor market actually needs from its technology stack.
Ground-level operations as a laboratory. Foothills Carpentry Co. is perhaps the most unusual part of the Hesiod structure, and the most strategically important. Foothills is a real carpentry contracting business operating in Treasure Valley, Idaho. Real projects. Real crews. Real permits, real schedules, real client relationships, real margins. Every tool Hesiod builds gets deployed at Foothills first — not in a controlled pilot, but in genuine operating conditions where failure has real consequences. This is not a vanity project or a marketing vehicle. It's a feedback mechanism. When EntitleHQ's permit tracking has a workflow assumption that doesn't match how agencies actually communicate, Foothills exposes it. When Chalk Line's CRM has an interface assumption that doesn't survive field conditions, Foothills surfaces it. The value of running an actual contracting business is that you can't fake the feedback.
A partner who validates the model externally. Associated Floor Co. — a flooring contractor serving San Antonio and Austin — was Chalk Line's first client, and their engagement has been formative in ways that extend beyond a single client relationship. AFCO runs on the systems Chalk Line built for them, and their day-to-day operation gives us visibility into what the model looks like from the outside. What does a contractor actually do with a CRM after the onboarding? Where does the operations platform create friction that wasn't anticipated? What does "working well" look like six months in, not six weeks in? AFCO answers these questions with real data from a real business, in a market (Texas) with its own permitting environment, contractor culture, and competitive dynamics.
The compounding advantage here is not immediately obvious, but it's real. Each company teaches the others things they couldn't learn in isolation. Foothills' permitting experience directly shapes EntitleHQ's product priorities — not as a feature request, but as ground truth about where the process actually breaks. Chalk Line's contractor relationships surface market problems that don't appear in any industry report but are immediately actionable in both EntitleHQ's roadmap and Foothills' operations. AFCO's external validation stress-tests assumptions that might otherwise go unchallenged.
Over time, this integration creates a structural advantage that's genuinely difficult to replicate. A company that builds AEC software from the outside can hire domain consultants and conduct user research. What they can't do is run a permit through a jurisdiction with a six-week review cycle and then immediately translate that experience into product decisions the next morning. They can't watch their own CRM get used by a four-person flooring crew and see exactly where the interface assumptions broke down. The feedback loops available to an integrated operator are qualitatively different from the feedback loops available to a pure software company — faster, less mediated, and grounded in consequence.
We're not claiming this approach is easy. Running multiple businesses simultaneously while building software is operationally demanding in ways that a pure software company doesn't have to contend with. But the difficulty is the point. The construction industry has consistently rejected software built by people who didn't understand the work. We're building a company structure designed to never have that problem — to be, by definition, inside the industry at every level we build for.
That's the bet. We think it's the right one.