A fair comparison starts with a common product definition. Buyers should ask each supplier to respond to the same activity, component list, sample needs, and review responsibilities, then identify differences in assumptions and scope.
Key takeaways
- Procurement compares goods and services against defined requirements; use common questions across proposals. [1]
- OEM scope does not automatically define design contribution, samples, or buyer responsibilities. [2]
- Manufacturing proposals should identify the specifications and product references they rely on. [3]
Buyers considering a custom excavation kit may receive proposals that differ in design work, component sourcing, packaging, and sample stages. A lower-level difference in scope can make two offers seem more comparable than they are. A structured comparison helps the buyer understand what each response actually includes.
This guide provides a practical way to normalize the brief and assess proposals. It does not recommend a particular supplier, estimate prices, or promise a production outcome. Confirm all terms directly and use qualified reviewers for technical, safety, and legal questions.
Normalize the product brief before requesting proposals
Prepare a dated brief describing the activity, intended user context, known components, package concept, destination markets, and open questions. State whether the buyer has a full specification, a sample, or an early concept. Give every supplier the same revision so each response addresses the same product.
Describe the excavation sequence. What does a user uncover? Which tool or medium is included? What happens after an object is found? A theme alone cannot determine the component list or instructions. Keep factual or educational claims separate from design assumptions.
List fixed requirements, preferences, and unresolved choices. A buyer may require a particular number of components but remain flexible about storage; or may require a defined learning task while asking the supplier to propose tools. Label those distinctions to avoid divergent assumptions.
Include a preliminary component schedule and identify what is missing. If material names, dimensions, or package format are not known, mark them as pending. Ask suppliers to specify what information they need before committing to a detailed proposal.
Compare scope and responsibility row by row
Create a matrix covering concept refinement, drawings, components, materials information, sample creation, instructions, package design, manufacturing, quality records, and change handling. For each row, state who performs the task, what output is expected, who reviews it, and whether it is included or optional.
OEM is commonly associated with manufacturing to another party’s requirements, [2] but the proposal should say whether the buyer provides a complete specification or expects design support. Ask who selects alternatives and who approves them. Do not infer that every desired service is part of a manufacturing offer.
Manufacturing uses materials and components to produce goods, [3] so ask which product documents and samples govern the proposed work. If the proposal relies on an assumption, record it and decide whether it is acceptable. A proposal that assumes a finished component list differs from one that includes component development.
Ask what the buyer must provide: brand assets, content, drawings, market information, or approvals. Identify any work the buyer must perform independently. An unanswered row should remain open with an owner rather than being silently assumed included.
Evaluate sample plans and evidence consistently
Ask each supplier what sample stages it proposes and what each stage is intended to demonstrate. A concept rendering, functional model, package proof, and representative pack-out are not interchangeable. Record provisional materials, content placeholders, and configuration differences.
Set review criteria before receiving a sample. The buyer may check whether components match the schedule, whether the activity flow is clear, and whether package copy reflects the actual kit. Technical and safety questions should be routed to qualified reviewers rather than answered by a general visual review.
Request evidence with scope. If a supplier offers reports, records, or process descriptions, ask which product revision they cover, when they were produced, and what limitations apply. A record for a different design should not be treated as proof for the proposed kit without confirmation.
Use the same feedback format for each candidate: sample version, observation, decision, requested change, owner, and open question. This lets a buyer compare how each supplier handles feedback and avoids confusing a polished presentation with a complete review process.
Review commercial assumptions and change paths
Ask each respondent to state assumptions and dependencies. These might include final components, package size, artwork status, destination, or buyer-supplied content. Clarify what additional information is needed before a firm proposal can be prepared. Do not compare estimates based on different assumptions as equivalent commitments.
Ask how a change request is handled. Does the buyer approve substitutions? How are affected drawings, instructions, and package files updated? Who determines whether another sample or review is needed? The answer should name responsibilities and records.
Identify rights and confidentiality terms for new design work, buyer assets, and existing supplier materials. Ask who owns or may use each item, whether the buyer can adapt it, and what happens when the project ends. Legal rights require project-specific agreement and may merit counsel review.
Keep product-safety and market questions separate from commercial scope. Ask who provides technical information and who determines applicable requirements. A mention of a standard or a general assurance does not establish a product-specific assessment or certification.
Select a proposal and write down the next gate
Use criteria that reflect the project: understanding of the activity, clarity of scope, sample process, evidence, communication, change management, and fit with buyer responsibilities. Keep verified facts separate from subjective impressions and list any claims that still require confirmation.
K&M’s custom excavation-kit buyer guide may serve as a starting point for questions about product scope, samples, and responsibilities. dig kit buyer's guide Confirm the specific proposal and terms directly; public information does not establish a particular product design, price, capacity, certification, customer, or result.
Before moving forward, document the selected brief version, included tasks, exclusions, buyer inputs, sample milestones, approval owners, rights, and open questions. Identify the next decision and what evidence is needed to make it.
A useful comparison does not eliminate uncertainty; it makes uncertainty visible. The buyer should be able to explain why a proposal fits the requirements, which assumptions it relies on, and what must be resolved before production or further development proceeds.
Sources
Frequently asked questions
How can I compare two custom excavation kit proposals?
Use the same brief and compare scope, assumptions, deliverables, sample stages, evidence, rights, and change responsibilities.
Does a sample plan prove a supplier can meet all requirements?
No. Ask what each sample demonstrates and identify technical or market questions that require separate review.
Should I choose the proposal with the most included services?
Not necessarily. Compare whether the included work matches the project’s needs, responsibilities, and evidence requirements.