How the founding program works

os.construction is being built with a small group of founding contractors. They get in first, they lock in founder pricing, and their workflows decide what we build first. This page explains how that works in practice.

Why a founding program

Construction software tends to fail in one of two ways. It is built by people who have never run a job, so it fights the way work actually happens. Or it is built for one company’s process and then stretched to fit everyone.

We want neither. The only way to get job cost, change orders, pay apps and WIP right is to build them against real jobs, real cost code structures and real month-end closes. Founding contractors give us that ground truth. In return, they get software shaped around how they work.

What founding contractors get

Early access first. Founding contractors get access before anyone else, in waves.
Founder pricing, locked. The first contractors on board get founder pricing. Details are shared directly with the founding cohort, not published.
A direct line to the team. Your workflows, your imports and your reports shape what we build first.

How it works

Get early access

Join from the early access form. Tell us your role (general contractor, specialty contractor, owner or developer) and, if you are willing, the tools you run today.
Tell us your stack

The most useful thing you can share is what you use now: your PM tool, your accounting system, and where your WIP schedule lives. It decides which import paths we build first.
Working sessions

We walk through how your team handles the workflows that hurt most: change orders, pay apps, AP coding, month-end WIP. We look at real (redacted, if you like) cost code structures and reports.
Access in waves

Founding contractors get access in waves as each part of the platform is ready. Early waves focus on the core record model and the workflows founding teams rank highest.
Shape what ships

You tell us what is wrong, what is missing and what to build next. We publish what changes in the changelog.

Who should join

The program fits best if at least one of these sounds familiar:

Your PM software and your accounting system disagree about a job’s budget, and someone reconciles them by hand.
Change orders are approved in one place and show up in billing late, or not at all.
Your pay app is assembled from a spreadsheet that gets rebuilt every month.
WIP, fade and cost-to-complete live in Excel and are only current at month-end.
AP spends hours coding invoices to jobs and cost codes and matching them to commitments.

General contractors and specialty contractors are the core audience. Owners and developers are welcome; we want to understand what you need from your contractors’ systems.

What we ask of founding contractors

Nothing is mandatory, but the program works best when founding teams:

Share how a real job flows from estimate to closeout, including the parts that are messy.
Give honest feedback on early versions, including “this would never work on our jobs”.
Name one or two people (often a PM and someone from accounting) we can talk to directly.

Your data during the program

Anything you share with us stays yours. Redact whatever you like, and ask us how something will be stored and used before you send it. See Data ownership and export for how ownership works in the product itself.

Questions

If something here is unclear, email hello@os.construction. Real people answer.