Practical systems for contractors and small project businesses. Estimates, job tracking, and invoicing built around how your work actually gets done, installed in the tools you already use.
Run by an engineer with twenty years answering for budgets, schedules, and crews on capital projects. Every sample on this page is one we would use ourselves.
This is the pair of tools we would install first for most shops. Change a quantity in the estimate, turn it into a proposal, and the client, scope, total, and breakdown carry across. Nothing here is a screenshot.
Ridgeline Mechanical LLC is fictional and every number is made up. Your build runs on your real jobs.
Three places the week goes. Pick the one that costs you most and try the sample built for it.
Every one of these is the same problem. There is no system doing it, so it lands on you at night.
Each one ends with something concrete in your hands. Scope, timing, third-party costs, and support are confirmed in writing before any work starts.
Twenty minutes to find out whether this is worth your money.
Cost Free
Two weeks. A build order, plus the smallest real automation we find, already running.
Cost Fixed fee, quoted after the call
One scoped system, installed in your tools, with the written procedure that runs it.
Cost Fixed price per system
Keeps what we built working as tools, models, and your jobs change.
Cost Monthly, quoted with the build
Third-party subscriptions (the tools a system runs in, and the AI services it calls) are paid by you directly and named in the scope before you sign. Support after acceptance is part of Care, not part of a build.
Six stations. You sign off at the third one before anything touches a customer.
What it does, what it does not, which tools it lives in, what it costs, and what counts as done.
The system runs beside your current way of working for a few real jobs. Nothing goes to a customer yet.
You check it against the written scope and sign off, or list what is short. If we hear nothing inside the review window in the agreement, it counts as accepted. Then it goes live.
A written procedure your office can follow, and a record of every setting and connection.
A walkthrough with the people who will run it, on your data, until they can do it without us.
Care keeps it running. Its scope and response are agreed in writing, never assumed.
Anything a system would send to a customer, a sub, or a supplier goes through a human review step first. It drafts; a person on your side approves. That line is in the scope and it does not move.
A wright builds things that last. Millwright, shipwright, wheelwright. Runwright means systems that run right.
Runwright is run by an engineer who spent twenty years on your side of this problem: capital project execution, project management, multi-site operations, manufacturing. Budgets that had to hold, schedules that had to land, and paperwork that had to be right before anybody got paid.
That is why we build instead of advise. You already know what your problems are. You need somebody who can go build the thing that fixes them, in the tools you already pay for, and then show your office how to run it.
Ten sample systems, built the way we build for clients. The company is made up. The tools work. Open any one and try it.
The samples are independent of each other. The estimate hands off to the proposal through the link between them; the rest share no data, and none of them talk to a server. Client names and results will be listed here only as clients approve them. Nothing is invented in the meantime.
If one person is doing office work at night that a system could do, no. Most of what we build fits a shop of two to twenty people. If we think it is not worth your money, we say so on the fit call.
No. Where we can, we install the system in the tools you already pay for. If something genuinely needs a new tool, it is named in the scope with its cost before you sign.
It stays in your own accounts, except what a system has to send to the providers it runs on: the tools it lives in and the AI services it calls, each named in the scope. Which categories of data a system touches, which providers see it, who owns access, and how it is removed at the end are written into that scope for every engagement.
An audit is two weeks. A single-system build is usually measured in weeks, not months, and the timing is written into the scope. Pilot and acceptance happen on your real jobs before anything goes live.
The call is free. Audits and builds are fixed fees, quoted after the call as a follow-up, never hourly. Third-party subscriptions are yours and are named up front. We do not publish prices because every build is custom to how your jobs run.
Care covers monitoring, fixes, and small changes, with its scope and response agreed in writing. Anything larger is scoped as a new build. On final payment for a build, the configured system, its documentation, and its procedure are assigned to you, with a perpetual license to the shared components inside them. That is in the agreement, not only on this page.
Answer these and the brief writes itself below. It stays on your screen. Copy it, download it, or open it in your own email; nothing is sent or stored by this page.
This page has not sent anything to Runwright. To get it to us, send the email yourself or bring the brief to the call.
Bring how you run jobs today. We will tell you straight whether we can help, what we would build first, and roughly what it takes.