HOTPASS
← Back to Hot Pass
Last updated 4 August 2026
Two conversations come up often enough to be worth a page. One is a contractor whose divisions each keep their own records and whose procurement department wants one contract. The other is a firm that wants to put this in front of its own customers. Neither is a normal signup, and neither of them is a sales process.
If you landed here on the way to a security review rather than a purchase, the security and architecture page is the one you want. It lists the subprocessors, says where the data sits, and starts with what is not built — no SOC 2, no SSO, no penetration test — so nobody spends a questionnaire round trip finding out.
Worth saying before anything else, because it is the opposite of how this usually works. Every feature is on every plan already. A one-person shop gets the same weld log, the same audit view, the same job book compiler as a company with forty welders, and there is no tab that unlocks at a higher tier.
So an enterprise agreement here is not about capability. It is about commercial terms and paperwork — how you are billed, what you are billed, and what we commit to in writing about your records.
These stand today and are not up for negotiation in the sense that they need negotiating — they are what the Enterprise tier means.
A master service agreement exists in draft and is available on request. If your legal team would rather work from their own paper, that is fine too.
The same document control system has been built out for three trades. They share an architecture and a founder. They share nothing else, and the distinction matters if you are planning to offer more than one of them.
| Product | Trade | Status |
|---|---|---|
| Hot Pass QC hotpassqc.com |
Pipeline, structural and industrial welding. Welds, WPSs, MTRs, NDE, hydrotests, job books. | Live |
| Sparky QC sparkyqc.com |
Electrical. Cable schedules, terminations and torque, megger and loop checks, energization. | Live |
| CodeShop QC codeshopqc.com |
ASME code shop fabrication, built around the item rather than the job — a vessel stays traceable to its materials, welds and NDE for its whole service life, not just until the job closes. | Live |
One thing to be straight about on CodeShop, because it looks like a gap until you know why it is not. It does not print your U-1, U-1A or R-1. Those forms are ASME's and the National Board's, they are copyrighted, and reproducing them in software is not ours to do. The shop obtains those forms itself and uploads its completed copies; CodeShop records which form the item was certified on, holds every record that has to stand behind it — materials, welds, NDE, hold points, the Authorized Inspector's sign-offs — and packages the lot into the data book that ships with the item.
Same posture as the other two: it organizes the records, and the code, the AI and your own quality program decide whether the work conforms.
The three are separate products with separate databases, separate billing and separate logins. A customer using two of them has two accounts and two invoices. There is no single sign-on across them and no combined bill. That is a deliberate architectural decision rather than an oversight — an electrical contractor's records have no business sharing a database with a pipeline contractor's — but it is a real constraint on how a bundle can be sold, and you should hear it from me rather than discover it in month two.
This is the newer conversation and I am not going to pretend it is a finished program with a tier sheet. It has come up a handful of times and the shape has been different every time. Three that have been raised:
Which of those is right depends on things I do not know yet: whether you want your name on it, whether you want to handle first-line support, and whether your customers are buying software from you today or would be for the first time. The first few of these will be negotiated one at a time, and the terms will be better for being early rather than worse.
Of those three, one contract across several divisions is the one that now exists rather than being a thing I would have to build for you. A division can be recorded as belonging to a parent company, one agreement on the parent covers every division under it, and the parent gets a rollup of seat counts and live project counts per division for reconciling the invoice.
What a parent does not get is any access to a division's records. Not the projects, not the weld logs, not the roster, not the audit trail. The hierarchy is a commercial fact about who is on whose contract, and it is deliberately not a way in — every access rule in the system was left untouched when it was built, precisely so that attaching a division could not quietly widen anything. If you want a parent's QA department to see a division's records, that is an auditor seat on that division, which is free, and which the division grants.
Resale and referral are still unwritten, and the rest of this page still applies to them.
Every one of these is buildable and none of it is built. If a partner arrangement depends on one, it becomes part of the agreement and gets a date — it does not get described in the present tense.
The form below asks more than an email address on purpose. The terms are being shaped out of these answers, so the detail is the point.
You get a reply from Jacob Horton, who built all three of these and spent the years before that auditing contractor documentation in the Delaware Basin. Not a sales desk, not a discovery call with a qualification script.
If what you need turns out to be something Hot Pass should not be doing, you will be told that too. An arrangement that only works if nobody looks at it closely is not worth signing.
Hot Pass QA/QC — Texas, USA. support@hotpassqc.com. Company registration in progress; full business details will be published once filed. See also the Terms of Use and the Refund and Cancellation Policy.
Enterprise and partner terms — hotpassqc.com/enterprise