Customer ↔ Supplier Requirements
Requirements shouldn't get lost between companies.
ShareReqs gives customers and suppliers one shared workspace to review requirements, clarify deviations, agree baselines and control every subsequent change.
Built for engineering teams working across company boundaries.
Falcon Power Unit · Baseline 1.2
The enclosure shall meet IP65 ingress protection.
Comply
Operating temperature range: -20°C to +65°C.
Clarification required
Interface connector shall be M12, 8-pin, A-coded.
Partially comply
The unit shall operate from 18 VDC to 32 VDC.
Comply
| ID | Requirement | Response | Status |
|---|---|---|---|
| REQ-012 | The enclosure shall meet IP65 ingress protection. | Comply | Accepted |
| REQ-018 | Operating temperature range: -20°C to +65°C. | Clarification required | Clarification required |
| REQ-024 | Interface connector shall be M12, 8-pin, A-coded. | Partially comply | Deviation proposed |
| REQ-037 | The unit shall operate from 18 VDC to 32 VDC. | Comply | Accepted |
| REQ-045 | Mean time between failures ≥ 50,000 hours. | Cannot comply | Deviation proposed |
| REQ-052 | Unit shall be traceable to a unique serial number. | Comply | Accepted |
REQ-037 · Northstar
Please confirm range including transient dips.
REQ-037 · Apex
Confirmed 18–32 VDC continuous, per EN 61000-4-11.
REQ-037 · Northstar
Accepted.
Requirements cross company boundaries. Your tools often don't.
Specifications are sent as spreadsheets, documents and PDFs. Responses arrive by email. Clarifications happen in meetings. New revisions are exchanged as attachments. Months later, determining exactly what the customer requested and what the supplier accepted can become unnecessarily difficult.
Scattered communication
Requirements, responses and clarifications live in different places.
Version uncertainty
Teams lose time establishing which revision is current.
Unclear agreement
"Discussed" is not the same as "agreed."
Uncontrolled change
A requirement can change after work has already started.
ShareReqs creates a shared, traceable interface between customer and supplier.
From specification to agreed baseline
Share
Import or create requirements
Bring the requirements into a shared project and invite the other organization.
Respond
Review requirement by requirement
Comply, partially comply, cannot comply, or request clarification — response by response.
Clarify
Resolve questions and deviations in context
Keep discussion attached to the requirement it affects.
Agree
Create an accepted baseline
Establish the version both sides are working against.
Change
Control what happens next
Proposed changes create a new traceable revision without rewriting history.
Replace document ping-pong with a shared process
Before ShareReqs
- Customer_Requirements_v7_FINAL.xlsx
- Email clarifications
- Meeting notes
- Supplier response spreadsheet
- Revised PDF
- "Which version did we quote against?"
- Manual change tracking
With ShareReqs
- One shared requirements workspace
- Requirement-level responses
- Contextual clarification
- Explicit status
- Accepted baselines
- Version history
- Controlled change
- Audit trail
Excel isn't the problem — uncontrolled exchange across organizations is.
Built for the customer–supplier interface
Customer → Supplier
Issue technical requirements, collect responses and manage deviations before and during development.
Supplier → Customer
Record compliance, assumptions and exceptions against the requirements you received.
Supplier → Sub-supplier
Flow requirements down the supply chain while maintaining visibility of what has been agreed.
Requirements management without the handover gap
Falcon Power Unit
Customer Northstar Systems
Supplier Apex Electronics
- Projects
- Baselines
- Changes
| ID | Requirement | Status |
|---|---|---|
| REQ-039 | Enclosure shall be sealed to IP65. | Accepted |
| REQ-042 | The unit shall operate from 18 VDC to 32 VDC. | Accepted |
| REQ-044 | Firmware shall be updatable over CAN bus. | Pending |
| REQ-047 | MTBF shall be ≥ 50,000 hours. | Deviation proposed |
REQ-042
The unit shall operate from 18 VDC to 32 VDC.
Supplier Comply
Status Accepted
History
- Customer created v1
- Supplier requested clarification
- Customer revised to v2
- Supplier accepted
- Included in Baseline 1.2
Project, company and requirement names are illustrative.
Help shape ShareReqs
ShareReqs isn't built yet. Before it is, we want to understand how engineering teams like yours actually exchange and agree requirements with customers or suppliers today — and whether a shared workspace would genuinely help. If this sounds like your problem, telling us here is exactly how we'll decide whether to build it.
We've temporarily paused new submissions while we sort out some things on our end. Check back soon.
Frequently asked questions
Is ShareReqs a requirements-management tool?
ShareReqs focuses specifically on requirements exchanged between customers and suppliers: review, clarification, agreement, baselines and change control.
Does ShareReqs replace our existing requirements tool?
It doesn't have to. ShareReqs is designed as the shared layer between organizations. Future integrations and exchange formats can connect it to existing engineering workflows.
Can suppliers participate without buying their own subscription?
Our goal is to make external collaboration frictionless. Invited customer and supplier participants should be able to collaborate without every external user needing to purchase a separate seat.
Can we import Excel requirements?
Excel import is planned as part of the intended workflow, since many customer–supplier exchanges begin with spreadsheets.
Is our data ours, or ShareReqs'?
Yours. While we build ShareReqs, we're evaluating the export formats that make the most sense — CSV, Excel and ReqIF among them — so your requirements, agreements and history stay portable and you're never locked into the tool.
When will ShareReqs be available?
ShareReqs is currently being validated with engineering teams. Request early access if you'd like to participate in the pilot.