Run every job like the margin is real.
Strand is the job console for distributors who sell projects, not shelf stock. One job, one screen: the quote, what you need to buy, what shipped, what you’ve billed.
30-minute call. Your own job as the demo.
- New
- Contract Review
- Contract Reviewed
- Intake
- Estimating
- Verify CostsGate cleared: every BOM line quoted or waived
- Quote Generation
- Quote Submitted
- Awarded
- PO Review
- Order Entry
- ProcurementCurrent: 14 of 19 vendor POs received
- All Material InGate: every vendor PO received
- ShippingGate: every pick ticket shipped
- Delivered
- Invoiced
- Paid
- Closed
Product facts, not testimonials. Every gate is enforced by the console.
Estimating that holds up at award
The quote your customer signs is built the same way the buy is. A BOM carries alternates per line. One RFQ goes to several vendors at once, and their bids land side by side: base against alternate, unit against extended, each with a bid-validity date. Commodity lines index to COMEX copper and aluminum with the as-of date attached, so a spike is a dated fact and not a guess.
Margin floors stop the leak. A line below the floor stops before it reaches the customer quote, and the number that goes out is the number that was actually bid. No re-keying from a spreadsheet into an email, and no invoice surprise eighteen months later.
Request a walkthrough| Bid | Alt | Unit | Ext. |
|---|---|---|---|
| Vendor A, base | No | $2,410.00 | $96,400.00 |
| Vendor B, alternate | Yes | $2,180.00 | $87,200.00 |
| Vendor C, base | No | $2,315.00 | $92,600.00 |
| Selected: Vendor B alternate, bid valid through the stated date. Copper line indexed COMEX, 3-month hold. | |||
Sample rows shown for layout. Your jobs show your bids, your vendors and your validity dates.
What the console runs for you
These are the parts that live in someone’s head today.
Bring your sheet
Your BOM already exists. It’s a spreadsheet you keep, or a PDF that came by email. Bring it as-is: paste the rows, upload the file, confirm the column match. The estimate starts from your sheet instead of a retype.
See it on your job →Deadlines that cost money
Each job carries its submittal schedule, and due dates are computed rather than typed. Liquidated damages accrue against a capped exposure, and you hear about it before the slip: escalations when a submittal goes overdue or a delivery group moves, plus a daily digest so nothing sits unread in an inbox.
See it on your job →Your ERP stays in charge
Accounting, warehousing and expediting stay where they already live. Strand reads them through an adapter and shows exactly what the ERP reported. No ERP at all is a supported state: a manual adapter covers the same fields, and a fresh tenant still walks New through Closed.
See it on your job →Your name on it
Each tenant gets its own name, logo, accent color and vocabulary. If the word on your floor is Buy Order, the console says Buy Order. Labels are labels: the workflow and the data underneath stay the same regardless of what a noun is called.
See it on your job →Closeout that closes
Required documents, questionnaire answers and invoice checklist items attach per customer, so a job reaches Paid and archives instead of lingering in a shared drive forever. After closeout plus your warranty window, the job is deleted rather than hoarded.
See it on your job →FAQs
Do we need an ERP to start?
No. The manual adapter covers vendor POs, receipts, pick tickets, AR/AP and RMAs as first-class entry, and a fresh tenant walks New through Closed on it. If you have an ERP, an adapter reads from it and those panels turn read-only.
What moves into Strand on day one?
Nothing has to move in a weekend. Start with the job you are running this month and enter what you already have. Your ERP keeps the books either way.
Who hosts it?
We do. Infrastructure we operate ourselves, per-tenant backups off-box with a tested restore drill, tenant isolation held by an automated suite that runs on two database engines.
How much does it cost?
A pilot is scoped to the paperwork it gets built from: your formats, your flows. Pricing follows scope and we put the number in front of you on the call.
What happens to our data if we leave?
Offboarding is a documented hard delete. Jobs also go after closeout plus your warranty window — retention has a scheduled end.
Who builds Strand
It starts when a customer asks for a price. It ends when the customer pays. Strand is built by a small team that has lived the distributor job path: quote, buy, ship, bill, chase. We take a small number of design partners at a time and work from their actual paperwork. What they get wrong in the first month gets fixed that month — that is the point of the founding-partner stage rather than a feature vote.
How your data is held
- Self-hosted by us. Infrastructure we operate, not a console you have to staff.
- Backups off-box. Scheduled per tenant, encrypted, with a tested restore drill.
- Isolation is tested. Tenant separation is enforced at the app layer and held by an automated test suite.
- Releases are tested. Every push runs our full test suite, and the security and driver tests run again on a second database engine.
- Deletion is scheduled. Jobs go after closeout plus the warranty window. Offboarding is a documented hard delete.
Talk to us
Send an email and we’ll set up a 30-minute walkthrough with your own job as the demo. If it isn’t a fit, we’ll both know by minute ten.
or email us directly: [email protected]