PI Apparel events are among the most operationally focused gatherings in fashion technology: the audience is practitioners, the agenda runs to live demos and working sessions, and the conversations that matter happen in the margins of the schedule. Whether you attend as a brand-side product or technology lead, or as a solution provider exhibiting or presenting, the return you get is almost entirely a function of how well you prepare before you arrive.
Key takeaways
- Agenda selection should be driven by a written internal brief, not by what looks interesting on the day.
- Vendor briefing protocols set before the event prevent demo sessions from becoming sales pitches with no actionable output.
- A structured post-event evaluation framework is what converts conference notes into procurement or partnership decisions.
- Brand-side and vendor-side preparation share a common logic: define the outcome you need, then work backwards to the sessions and conversations that serve it.
- The evaluation criteria you apply to a PLM or 3D tooling vendor at the event should mirror the criteria in your internal RFP scoring sheet.
What you need before you start
Before working through the steps below, confirm you have the following in place:
- A confirmed registration for the relevant PI Apparel event and access to the published agenda (the event programme for PI Apparel West Coast 2025, for example, is available at the event page).
- An internal brief of one to two pages covering your organisation's current technology priorities, open vendor evaluations, and any regulatory or compliance pressures shaping your roadmap (Digital Product Passport readiness, AI governance, data localisation).
- A shortlist of vendors you intend to meet, drawn from the exhibitor list, with at least one named contact per vendor confirmed in advance.
- A shared note-taking template your team will use consistently across all sessions and vendor meetings.
- Budget and authority clarity: know before you arrive whether you are in discovery mode, active evaluation, or final-stage selection — this changes every conversation you will have.
Step 1: Translate your internal brief into a session map
Open the published agenda and read every session title and abstract against your internal brief. For each session, make a binary call: does this session address a problem your organisation is actively trying to solve, or does it address something adjacent that you are not yet resourced to act on?
Mark the first group as mandatory and the second as optional. Where two mandatory sessions overlap, assign one team member to each rather than defaulting to seniority. The goal is a personal schedule for every attendee that is traceable back to a specific organisational priority.
Expected result: Each attendee arrives with a printed or digital schedule that maps every session to a named internal objective. No session appears on the schedule without a corresponding objective.
Note: PI Apparel programmes frequently include sessions drawing on technology from adjacent industries — gaming engines, cinematic rendering pipelines, and similar. These are worth attending if your team is evaluating 3D product creation workflows, but should not displace sessions on core operational topics such as PLM integration or data governance if those are your primary concerns.
Step 2: Write a vendor briefing document for every meeting you book
For each vendor meeting you schedule, prepare a one-page briefing document before the event. The document should contain four sections:
- What we do today — your current tooling stack and the specific workflow the vendor's product would touch.
- The problem we are trying to solve — stated as a measurable outcome, not a feature wish list.
- What we need to see in the demo — three to five specific scenarios, not a general product walk-through.
- Our decision timeline — when you expect to move to RFP, pilot, or contract, so the vendor can calibrate the conversation accordingly.
Send this document to the vendor contact at least five working days before the event. Ask them to confirm receipt and to structure their demo around your scenarios rather than their standard deck.
Expected result: Demo sessions run to your agenda, not the vendor's. You leave each meeting with answers to your specific questions rather than a general impression of the product.
Warning: Vendors who decline to adapt their demo to your briefing document are giving you useful information about how they will behave post-sale. Note this in your evaluation.
Step 3: Prepare your demo evaluation scorecard
Before the event, build a scorecard that every attendee uses to evaluate every vendor demo. The scorecard should score each of the following dimensions on a consistent scale (for example, one to five):
- Fit to stated use case — does the product address the specific scenarios in your briefing document?
- Integration evidence — can the vendor demonstrate live or documented integration with your existing PLM, ERP, or 3D tooling environment?
- Data governance posture — how does the vendor handle your data? Where is it stored, who can access it, and what contractual protections exist?
- AI capability maturity — if the product includes AI features, are they embedded in the core workflow or added as optional modules with limited connectivity to the underlying data?
- Reference customer profile — does the vendor have documented deployments at organisations of comparable scale and complexity to yours?
- Regulatory readiness — is the vendor able to speak to Digital Product Passport compliance, EU AI Act obligations, or other regulatory requirements relevant to your market?
For PLM evaluations specifically, confirm whether the vendor's platform supports end-to-end lifecycle data — from design and sampling through to supplier collaboration and compliance documentation. Centric PLM, for instance, now operates as part of Dassault Systèmes and ships an AI-powered platform that spans PLM, planning, pricing, and product experience management across fashion and adjacent consumer goods sectors; understanding the full scope of a vendor's current offering prevents you from evaluating a product against a description that is months or years out of date.
For 3D tooling evaluations, confirm whether the platform supports physics-based simulation, AI-assisted fit validation, and connectivity to your PLM and ERP systems. Browzwear offers a 3D digital product creation platform — VStitcher, Lotta, and SmartDesign — that covers design, fit validation, supplier collaboration, and asset generation for e-commerce, and is expanding toward AI-generated on-model imagery and tighter PLM/ERP connectivity.
Expected result: Every demo produces a completed scorecard. Scores are recorded immediately after the session, before the next meeting begins.
Step 4: Run structured debrief sessions each evening
Do not allow evaluation to accumulate until the end of the event. Schedule a thirty-minute debrief with your full team at the end of each conference day. Work through the scorecards completed that day, surface any gaps or contradictions between individual scores, and agree on follow-up questions to put to vendors the following day.
This discipline serves two purposes. First, it prevents recency bias from distorting your final evaluation — the vendor you met last will not automatically feel more relevant than the one you met first. Second, it allows you to adjust your remaining schedule if a session or vendor meeting has revealed a priority you had not anticipated.
Expected result: By the final morning of the event, you have a consolidated team view of every vendor and session, not a stack of individual notes that will take weeks to reconcile.
Note: Assign one person to maintain the master evaluation document throughout the event. Distributed note-taking without a single owner produces irreconcilable records.
Step 5: Execute the post-event evaluation framework
Within five working days of returning, complete the following sequence:
- Consolidate scorecards into a single ranked vendor matrix. Include every vendor you met, even those you have already ruled out — a documented rationale for exclusion protects you in a formal procurement process.
- Request follow-up materials from vendors who scored above your threshold. Specify exactly what you need: a written response to your briefing document scenarios, reference customer contacts, and a data processing agreement for review.
- Schedule internal alignment with procurement, legal, and any other function that will need to approve a contract. Brief them on the top two or three vendors before they receive vendor materials directly.
- Set a decision gate — a specific date by which you will either move a vendor to pilot or formally close the evaluation. Communicate this date to vendors.
- Archive the full evaluation record — scorecards, briefing documents, vendor responses, and the final decision rationale — in a location accessible to the team that will manage the vendor relationship going forward.
Expected result: A procurement decision that is traceable, defensible, and made within a defined timeframe rather than allowed to drift.
For solution providers: preparing to exhibit or present
The preparation logic above applies in reverse if you are a vendor at the event. The brands you will meet have prepared briefing documents and scorecards. Your job is to make it easy for them to score you accurately.
Before the event:
- Audit your demo environment. Every scenario a brand is likely to bring should be runnable in your demo instance without live data from their systems. Prepare three to five pre-built scenarios that reflect common use cases for your target customer profile.
- Prepare integration evidence. If your product connects to PLM, ERP, or 3D tooling systems that your target customers use, document those integrations with architecture diagrams and, where possible, a live demonstration path.
- Brief your team on regulatory questions. Brands attending PI Apparel are increasingly asking about Digital Product Passport readiness and AI governance. If your product touches product data, your team should be able to speak to data residency, access controls, and your roadmap for regulatory compliance without escalating to a specialist.
- Define your reference customer policy. Know in advance which customers you can name, which you can connect prospects to directly, and which you can reference only in aggregate. Inconsistency on this point in a demo meeting is a significant trust signal.
- Set a realistic follow-up protocol. Agree internally on the maximum time between a meeting and a follow-up communication. Five working days is a reasonable standard; longer than that and the conversation momentum is lost.
Warning: Presenting a roadmap feature as a current capability is the single fastest way to lose a technically sophisticated audience. PI Apparel attendees include product managers and engineers who will ask specific implementation questions. Distinguish clearly between what ships today and what is planned.
Troubleshooting common preparation failures
The agenda was not mapped to internal priorities before arrival. Result: attendees default to sessions with the most prominent speakers or the most familiar topics, and the organisation leaves without answers to its actual questions. Fix: complete Step 1 before travel, not on the morning of day one.
Vendor meetings were booked without a briefing document. Result: demos run to the vendor's standard script, and the team leaves with general impressions rather than comparative data. Fix: if you have already booked meetings without sending a briefing document, send a condensed version — even three bullet points covering your use case, your current stack, and your decision timeline — before the event.
Scorecards were not completed in real time. Result: end-of-event recall is dominated by the most recent or most visually impressive demo rather than the most relevant one. Fix: complete scorecards immediately after each session, before the next one begins.
Post-event follow-up was not assigned to a named owner. Result: vendors chase your team for weeks without a response, and the evaluation stalls. Fix: assign a named owner for each vendor relationship before the event ends, and communicate that name to the vendor at the close of your final meeting with them.
The internal brief was not shared with all attendees. Result: different team members evaluate vendors against different implicit criteria, and the consolidated scorecard reflects personal preferences rather than organisational priorities. Fix: circulate the internal brief to every attendee at least one week before the event.
What success looks like
A well-prepared PI Apparel attendance produces three concrete outputs within thirty days of the event:
- A ranked vendor matrix with documented rationale for every inclusion and exclusion.
- At least one vendor in active follow-up with a defined next step — reference call, pilot scoping, or RFP submission.
- An updated internal brief that reflects what you learned, including any priorities that shifted as a result of what you saw.
If you leave the event with notes but no framework for acting on them, the preparation work described above was not completed. The conference is not the output; the decisions you make in the thirty days after it are.
FAQ
How far in advance should I book vendor meetings at PI Apparel? Aim for three to four weeks before the event. The most in-demand vendors fill their meeting slots early, and booking late often means accepting whatever time remains rather than the slot that fits your schedule.
What should I do if a vendor's demo does not match their briefing document response? Note the discrepancy on your scorecard and ask directly in the meeting. A vendor who cannot demonstrate what they described in writing is a material risk in procurement. Escalate the discrepancy in your internal debrief that evening.
How many vendor meetings is it realistic to hold in a two-day event? Four to six substantive meetings per day is the practical ceiling for a single attendee who is also attending sessions. Beyond that, evaluation quality degrades because there is insufficient time to complete scorecards and process what you have seen.
Should brand-side and vendor-side attendees share their preparation materials with each other? Brand-side briefing documents are internal and should not be shared with vendors in full before a meeting. A summary of your use case and decision timeline is appropriate to share; your scoring criteria and internal budget parameters are not.
How do I handle a vendor who asks for an NDA before discussing their product roadmap? This is standard practice for enterprise software vendors discussing pre-release features. Have your legal team prepare a standard mutual NDA template before the event so you can execute it quickly if needed, rather than losing the conversation to administrative delay.
Further reading
- PI Apparel West Coast 2025 — event programme
- Reimagining Customer Connections Through Digital Product Passports