About the Challenge
ConsulTech 2026 (180 Degrees Consulting × GDG UTM) is a week-long hackathon × case competition where students collaborate to solve real challenges from nonprofit partners. You will work with real constraints and real objectives to build solutions that are practical, clear, and implementable.
Teams deliver two things:
- A strategic case presentation
- A technical prototype that supports the strategy
2026 Case Partner: Circular Innovation Council (CIC)
This year’s case is based on CIC’s work advancing circular economy practices across Canada through programs, training, events, and shared resources.
Key Dates:
-
Feb 22, 2026 — Opening Ceremony
-
Feb 28, 2026 (11:59 PM EST) — Case Due
-
Mar 1, 2026 — Closing Ceremony
Requirements
What to Build
Teams must build a solution that addresses the nonprofit challenge provided at the Opening Ceremony. Your solution should combine strategy and technology and be designed for real-world implementation.
The technical component should be a lightweight, demo-able proof of concept (POC) that shows how CIC could deliver role specific value over time without a full platform rebuild: a simple way to capture or assign member segment and priorities, a basic membership experience that surfaces curated responses and clear next steps (i.e. by role and membership stage), a small set of maintainable engagement prompts (i.e. scheduled emails or in-portal reminders) to encourage repeat visits, and using minimal measurement that tracks whether members are actually re-engaging and using relevant content. Ideally, the admin setup should be simple enough for CIC staff to update pathways and content without ongoing developer support and the teams should clearly state assumptions, scope limits, and tools required so that CIC can judge feasibility against internal capacity.
By the end, teams should present a demo that shows the redesigned membership experience working end to end, with minimal ongoing effort required from CIC. Mock data is acceptable. Teams should clearly state their assumptions and explain, in practical terms, what CIC would need to do each month to operate and maintain the solution.
What to Submit
By the submission deadline, teams must submit the following :
- A slide deck (submitted by email) outlining:
- Problem understanding and key insights
- Strategic recommendations
- Implementation plan and expected impact
- A 3-5 minute video demo and description of your technical solution (submitted here on devpost), including:
- Link to a live prototype or repository
- Screenshots, mockups, and a recorded walkthrough
Hosting sponsored by .xyz
For teams that want to host their technical component, follow instructions in the link below:
https://drive.google.com/file/d/1ZCMrxWIq6VPO0NSDYMqzBR4hlw_B1g0F/view
Your code is DEG26. This code expires on Mar 31 2026 (America/Los_Angeles). Basically they gave this google drive pdf on the instructions on how to set up the domains
Prizes
ConsulTech 2026 Winner's Certificate
Certificates will be provided to the winning team at the in person closing event on March 1st.
Devpost Achievements
Submitting to this hackathon could earn you:
Judges
Irene Shao
Manulife
Nicholas Sutanto
AMD
Liam Brooks
Deloitte
Ayesha Kirimani
Microsoft
Sandra Leutri
Humber Polytechnic
Abrar Nasir
IBM
Laura Elshaer
IBM
Tanvi Patel
IBM
Ian Quan
Shopify
Fares Abdellatif
BCG
Deniz Demirel
IBM
Vineet Guliani
IBM
Katie Motta
CIC
Shirley Ouellette
CIC
Jo-Anne St. Godard
CIC
Judging Criteria
-
Technical POC Relevance
The POC must directly support the proposed membership model and show how experience changes by role, stage, or engagement. It should clearly demonstrate segmentation logic or adaptive features tied to the team’s strategic design -
Feasibility
The solution must be realistic for CIC’s small team to implement and maintain. Avoid heavy infrastructure or complex systems. Clearly state assumptions, scope limits, and trade-offs to show practical viability. -
Use of Existing CIC Benefits
Submissions should leverage CIC’s existing benefits and restructure how value is delivered over time. Focus on sequencing and surfacing current offerings rather than introducing entirely new services. -
Logical Implementation
The system should have clear user flow and structured progression. It must demonstrate how engagement evolves over time and guide members toward meaningful next actions within the experience. -
Clarity & Demonstration Quality
The demo should clearly explain functionality and logic. It must be well-structured, easy to follow, and effectively communicate how value is delivered through the technical solution.
Questions? Email the hackathon manager
Tell your friends
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


