We built this because
we needed it.
Rootlayr comes from a working architecture and reality capture practice.
We have built tools for the AEC industry for years. On our own jobs, a site walk had to reach the office, the model and the client, and for a long time that ran on shared drives, file names and memory.
Everything we could buy was built for the largest firms, and came loaded with workflow layers nobody on site asked for. So we built what we wanted, and held it to two jobs: get the photo on the plan, and keep the list next to it. Other firms wanted the same thing.
Easy to build is not
the same as simple to use.
Software is quick to generate now, and the industry is filling up with platforms that do everything. Deciding what a tool will not do is the part that takes work, and it is the part that gets skipped.
Built on real projects
Rootlayr comes out of a working practice. Every feature is here because a job needed it, not because it looked good on a roadmap.
Made for smaller teams
This industry builds its software for the largest firms. A five person office has the same record to keep and cannot carry the same platform.
No bells and whistles
No augmented workflow, no intelligence layer. Software that guesses what you meant has to be checked, and checking it costs more than the guess saves. We would rather be predictable.
Every feature has a cost
Something to learn, something to maintain, something that can fail at the worst moment. We are more careful about what we leave out than about what we put in.
Tell us what
you need.
Questions about the products, a quote, or whether it fits how your team works. A person reads every message.
Where we are
McLean, Virginia
Dallas, Texas