Meeting Log¶

Purpose and reliability¶

This log records the coordination and mentor meetings used to manage the PackyTrace MVP / pre-event phase for Startup Day. Validation interviews and external feedback sessions are kept in the separate Validation Sessions document.

The Sunday team meetings were reconstructed from team memory, working notes and the project timeline. Mounir Samite and Giorgio Musarella were present at every Sunday meeting. Attendance for the other members is reported at the level needed for project management traceability, not as a legal attendance register. If a precise audit is ever needed, this page should be cross-checked against ClickUp, Notion AI notes, WhatsApp history and calendar entries.

Participants referenced¶

Person	Main role in the phase
Mounir Samite	Project management for the software platform, architecture, implementation coordination, documentation and AI-agent coordination
Giorgio Musarella	Market analysis, business model, startup positioning and pitch support
Vishaka Singh	Product research, feature framing, user feedback synthesis and design-thinking cycles
Chao Yuan	Website, public image, startup communication and pitch material support
Amir Fooladi	Sustainability-related contacts and external-relation input
Giada Raffaelli	Interviews, consumer feedback and public-presentation support
Davide	CBI / Tetra Pak mentor and domain advisor
Matteo Vignoli	Startup mentor and innovation-program advisor

Recurring Sunday team meetings¶

Date	Participants	Agenda	Summary and decisions
2026-04-26	Mounir, Giorgio, Vishaka, Chao, Amir, Giada	Restart after CBI, define whether PackyTrace remains a DPP idea or becomes a startup project, identify first workstreams.	The team agreed to continue PackyTrace as a startup-oriented project starting from the Digital Product Passport opportunity. The first scope was still broad: traceability, sustainability, consumer information, brand value and possible reward mechanisms were all considered. Mounir and Giorgio took ownership of turning the idea into a manageable plan; product research and market work were split across the team.
2026-05-03	Mounir, Giorgio, Vishaka, Chao, Giada	Compare possible value propositions, define early user segments, plan the first validation activities.	The meeting showed that the original brand-first framing was too broad. The team decided to interview consumers and domain contacts before adding more features. The initial MVP candidates were product scan, personalized product explanation, expiry tracking and a simple brand dashboard.
2026-05-10	Mounir, Giorgio, Vishaka, Giada	Review early feedback, prepare interview questions, align on target users and public narrative.	The team narrowed the likely target toward young adults who care about diet, fitness, health or sustainability but do not want long product pages. Giada supported interview planning and feedback collection. The team also agreed that Startup Day could be used as an external milestone rather than a final product launch.
2026-05-17	Mounir, Giorgio, Chao	Translate product direction into backlog areas, separate startup work from software-platform work, prepare questions for mentors.	The team separated the work into two connected flows: startup validation and platform delivery. Mounir started turning the software side into domain analysis, architecture, contracts and a thin end-to-end slice. Giorgio focused on business-model assumptions and stakeholder positioning.
2026-05-24	Mounir, Giorgio, Vishaka, Amir	Review scope risk, decide what must stay out of the MVP, prepare the first mentor check with Davide.	The team recognized the risk of scope creep. Reward systems, a full AI assistant, community features and a polished B2B dashboard were moved outside the immediate MVP. Amir gave input on sustainability messaging, but the group decided not to make sustainability the only reason to scan.
2026-05-31	Mounir, Giorgio, Vishaka, Chao	Consolidate the MVP backlog, define the weekly execution rhythm, assign platform and pitch tasks.	The team adopted Sunday meetings as the main weekly control point. The backlog was organized around scan, profile, personalized verdict, Fridge, trust/privacy and brand dashboard. ClickUp remained the shared work tracker; WhatsApp was used for fast coordination.
2026-06-07	Mounir, Giorgio, Vishaka	Review mentor feedback, apply the consumer-first pivot, update priorities for software and pitch.	After mentor and interview feedback, the team made the consumer-first direction explicit: PackyTrace should first help the person holding the product, then use engagement to justify brand analytics. Gamification was not deleted forever, but it was removed from the MVP.
2026-06-14	Mounir, Giorgio, Chao	Check progress toward Startup Day, stabilize the demo strategy, review documentation and pitch material.	The team agreed to keep a safe demo path while continuing the real platform work. Mounir focused on CI, documentation, deployment and the demonstrable software flow. Giorgio and Chao focused on communication and presentation material.
2026-06-21	Mounir, Giorgio, Chao	Final pre-event review, confirm deliverables, define feedback-capture plan.	The team treated Startup Day as a phase acceptance milestone. The decision was to show the platform as a concrete MVP, collect feedback systematically and avoid claiming full validation before real user and brand evidence existed. Next-cycle priorities were defined as user tests, more interviews, brand validation, LOI/pilot attempts and funding.
2026-06-22	Mounir, Giorgio, Vishaka, Chao	Complete the Startup Day presentation, align logistics for the event, assign final preparation tasks.	The team reviewed the pitch structure, refined the wording around PackyTrace's consumer-first value proposition and checked that the public narrative stayed consistent with the MVP scope. The meeting also covered practical organization for the event: who would handle the pitch, who would support demo and networking, what material had to be ready, and how feedback would be captured for the next project cycle.

Extra mentor meetings¶

Date	Participants	Agenda	Summary and decisions
2026-04-29	Mounir, Giorgio, Davide	Clarify Tetra Pak's role, understand DPP / GS1 Digital Link constraints, test whether the startup should focus on QR infrastructure or user-facing value.	Davide clarified that Tetra Pak should be considered a mentor/domain reference, not a customer, investor or buyer. The meeting helped separate industrial QR serialization from PackyTrace's actual scope: the project should focus on the digital experience and on combining product data with consumer context. The team learned that producer systems, batch identifiers, serial numbers and industrial data pipelines are mostly outside the MVP.
2026-04-30	Mounir, Giorgio, Matteo Vignoli	Discuss continuation after CBI, startup positioning, Startup Day opportunity and business-model preparation.	Matteo encouraged the team to use Startup Day as an external feedback point and to make the business assumptions more explicit. The team discussed how to present PackyTrace as a startup project rather than as only a course prototype. This meeting reinforced the need for a simple, understandable pitch and for a credible validation path after the MVP.
2026-06-05	Mounir, Giorgio, Chao, Davide	Review updated product direction, pitch narrative, regulatory context and differentiation from existing apps.	Davide pushed the team to avoid copying existing products such as Yuka and to define a narrower target. He recommended focusing on personal usefulness, clear language, RAMI analysis and a stronger connection between product scan, personal goals, expiry and waste reduction. Chao appears as "Joanna" in part of the raw transcript, but this is a transcription error. The team also received guidance on how to mention Tetra Pak / CBI in public materials and agreed to share the relevant slide before Startup Day.

Decisions traceability¶

Decision	Source meetings
Treat Tetra Pak as mentor/domain context, not customer or investor.	Davide mentor meeting, 2026-04-29
Focus PackyTrace on the user-facing digital experience, not on QR printing or industrial serialization.	Davide mentor meeting, 2026-04-29
Use Startup Day as the MVP phase acceptance milestone.	Sunday team meetings from 2026-05-10 onward; Matteo mentor meeting, 2026-04-30
Move from brand-first DPP communication to consumer-first personal usefulness.	Sunday meetings, Davide mentor meetings and consumer interviews
Remove gamification, rewards, community and full AI assistant from the MVP.	Sunday meetings on 2026-05-24 and 2026-06-07; Davide mentor feedback
Use weekly Sunday meetings, ClickUp, WhatsApp and living documentation as the operating rhythm.	Sunday meeting, 2026-05-31
Keep a demo fallback while progressing the real cloud platform.	Sunday meeting, 2026-06-14
Close only the MVP / pre-event phase, not the startup project.	Sunday meeting, 2026-06-21
Finalize the presentation and organize team responsibilities for We Make Future.	Pre-event team meeting, 2026-06-22