Good morning. We are PixelDrive — four students from Ahmedabad competing in STEM Racing India Regionals 2026. Our team name says everything about who we are: pixels — the building blocks of digital precision — and drive — the relentless pursuit of performance. High technology meets high ambition.

Our brand was applied consistently across every key deliverable — the car livery, team uniforms, all three portfolios, the pit display, and every digital post. Each piece was reviewed against Brand Guidelines before sign-off. This discipline ensured PixelDrive presented as a unified, professional team — not four individuals working separately.

Our biggest marketing moment was the car reveal — rolled out in three phases: a teaser, the full reveal across all platforms simultaneously, and then a sponsor tags reveal. We also delivered a school presentation to students and teachers, expanding our community reach and mentoring younger teams along the way.

Our sponsorship strategy moved beyond conventional tier structures. We crafted bespoke ROI packages tailored to each partner's unique business objectives — from logo placement and social media posts to co-branded content, product integration, and verbal presentation acknowledgements. Our revenue BAC was ₹96,075, funded entirely through partnerships.

Every successful project starts before any work begins. Our kick-off meeting was held online within the first week — its purpose was to align the team on our goals, structure our workflow, and establish clear responsibilities for the 60-day campaign ahead. We conducted a SWOT analysis to identify strengths, weaknesses, opportunities, and threats from the start.

From the charter, we built a full scope definition — starting with a Work Breakdown Structure that broke the project into work packages, deliverables, and individual activities. Time was our primary constraint: just 60 days to learn the format, build the car, and produce all deliverables. So we built our preliminary BAC of ₹1,00,000 early, using parametric estimation scaled to our team size and competition location.

We applied the Critical Path Method to sequence all activities and calculate float — identifying exactly which tasks could not be delayed without pushing back our overall completion date. This fed directly into our Gantt chart, which mapped every task, duration, and dependency across the full project. You can see both the baseline and actual schedules reflected in our submitted Gantt.

We deliberately front-loaded our major expenses to preserve flexibility later in the campaign — because the cost of making changes rises as a deadline approaches. Every expenditure went through a formal approval procedure before it was committed, with the Team Lead signing off all financial decisions.

We adopted a projectized team structure — organised directly around our work packages. Four roles were defined: Team Lead, Marketing Lead, Manufacturing Lead, and Aerodynamics Lead. I'm Khushit, Team Lead — overseeing all operations and keeping the team aligned with goals and deadlines.

Risk identification was ongoing — every one to two weeks, using our SWOT framework to surface new threats. Each risk was assessed for probability, impact, and mitigation strategy, then captured in our Risk Register. High-threat risks received immediate attention; medium threats were monitored and contingency-planned; low threats were logged and reviewed periodically.