Founding-partner stage
Strand is a job console for distributors who sell projects instead of shelf stock. Estimating and BOM, vendor RFQs and POs, submittals, shipping, invoicing, the change orders in between: one workspace per customer job, so nobody stitches the job back together out of spreadsheets and email threads.
We host it in your browser. Your ERP stays the system of record.
Eighteen named phases, one job at a time. Three of them are gates, and a gate checks the work itself instead of asking someone to remember it.
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.
| 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.
These are the parts that live in someone's head today.
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.
Pre-slip alerts. Escalations fire when exposure crosses 50, 90 or 100 percent of the cap.
Accounting, warehousing and expediting stay where they already live. Strand reads them through an adapter and shows what the ERP reported, nothing invented. No ERP at all is a supported state: a manual adapter covers the same fields, and a fresh tenant still walks New through Closed.
No ERP required. Manual entry is a first-class path, not a degraded demo mode.
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.
Per tenant. Branding and terminology are configured at runtime, per company.
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.
Retention has an end. Jobs are deleted after closeout plus the warranty window.
Distributors running project-based work: jobs with BOMs, long-lead purchases, submittals and milestones, currently held together by a shared drive and whoever remembered what. If your team quotes, buys, ships and bills the same job in four different tools, that is the gap.
We take a small number of design partners at a time and work from your actual paperwork. Tell us what we get wrong in the first month and we fix it that month; that is the point of the founding-partner stage rather than a feature vote.
$15k pilot floor. It covers the work built from your documents: your formats, your flows. That configuration is yours for your subscription term.
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.
There is no signup link. Strand is currently founding-partner work with a small number of distributors, and the first conversation is a call.
or email us directly: [email protected]