Hackathon ยท 2025
Powered by Sourceware
Build What Moves You Forward
๐Ÿ“… January 30-31, 2026
Duration
2 Days
Hours/Day
8 Hours
Teams
3 Teams
Participants
12 Devs
Format
In-House
โฐ Event Countdown
00
Days
00
Hours
00
Minutes
00
Seconds
Welcome to MOMENTUM
Where Ideas Meet Execution
About
What is MOMENTUM?
MOMENTUM is Sourceware's bi-annual innovation sprint. Over 2 intensive days, our engineering teams collaborate to build functional prototypes that solve real challenges in procurement and business automation.
Why
Accelerate Growth
Sharpen your technical skills, experiment with new technologies, collaborate across teams, and showcase innovation. Top solutions may be fast-tracked for production deployment.
Format
How It Works
Teams are randomly assigned. Choose your challenge track (first-come-first-serve). Build your solution over 16 hours across 2 days. Technical mentors available throughout. Demo and compete for glory!
Challenge Tracks
First come, first serve - Choose wisely!
Track 01
Mobile Approval Flow
Build a mobile-first approval system with smart multi-channel notifications (WhatsApp, Email, Push). Include swipe gestures, real-time budget validation, offline sync, and beautiful UX. Make approvals instant and intuitive.
React Native Real-time Notifications UX Design
Status
Available
Track 02
AI-Powered Procurement
Integrate AI into procurement workflows. Build smart quotation comparison engine, intelligent item discovery with duplicate detection, conversational procurement assistant, or ML-powered approval routing. Ship working AI.
AI/ML NLP Automation Claude API
Status
Available
Track 03
Open Innovation
Complete creative freedom. Identify a real problem in procurement, finance, operations, or developer workflows. Build your solution from scratch. Could be productivity tool, analytics dashboard, workflow automation - you decide!
Full-Stack Problem-Solving Innovation Impact
Status
Available

โšก First Come, First Serve

Once teams are assigned, team captains will select their challenge track. Once a track is chosen, it's locked for that team only. Download the detailed task specification for comprehensive requirements and guidelines.

Judging Criteria
How winners are decided
๐Ÿ’ป
Technical Implementation
30 pts
Quality of code, architecture, and technical execution
  • Code quality and organization
  • Technical complexity tackled
  • Use of best practices
  • Performance and scalability
  • Error handling and edge cases
๐ŸŽฏ
Innovation & Creativity
25 pts
Uniqueness of solution and creative problem-solving
  • Novel approach to problem
  • Creative use of technology
  • Original features
  • Thinking outside the box
๐Ÿ“Š
Functionality & Demo
20 pts
Working prototype and live demonstration quality
  • Core features working
  • Demo execution and flow
  • Real-world usability
  • Bug-free experience
๐ŸŽจ
Design & UX
15 pts
User interface and experience quality
  • Visual design aesthetics
  • User experience flow
  • Intuitive interactions
  • Responsive design
๐Ÿ“–
Documentation
5 pts
Code documentation and project explanation
  • README quality
  • Setup instructions
  • Code comments
  • Architecture docs
๐Ÿ‘ฅ
Team Collaboration
5 pts
Teamwork and contribution balance
  • All members contributing
  • Git commit distribution
  • Collaborative problem-solving
  • Communication effectiveness
Total Possible Score
100
๐ŸŒŸ Bonus Points Opportunities
+5 pts: Production Ready
Solution is deployment-ready with proper CI/CD, testing, and production configuration
+3 pts: AI Integration Excellence
Outstanding use of AI/ML that significantly enhances the solution
+3 pts: Mobile First
Exceptional mobile experience with native features and polish
+2 pts: Real User Impact
Solves an actual pain point identified by Sourceware users/clients
๐Ÿ“‹ Technical Requirements & Standards
Git Branch Naming
All development must be done in a feature branch following this convention:
feature/momentum-2025-[team-name]-[feature] Example: feature/momentum-2025-alpha-mobile-approvals feature/momentum-2025-beta-ai-quotations
Main branch protected. Create PR for final submission.
README Format
Your README.md must include:
# Project Title ## Team [Name] ## Challenge Track ### Problem Statement ### Solution Overview ### Tech Stack ### Installation ### Usage ### Architecture ### Team Members & Contributions ### Demo Link (if hosted)
Testing Requirements
Minimum testing standards:
  • Unit tests for core functions (min 60% coverage)
  • Integration tests for key workflows
  • Test command in package.json/requirements.txt
  • All tests must pass before submission
npm run test # or pytest # or cargo test
Code Quality
Required standards:
  • ESLint/Prettier for JS/TS
  • Black/Flake8 for Python
  • Rustfmt for Rust
  • No console.log/print in production code
  • Proper error handling
  • Meaningful variable names
Environment Setup
Provide complete setup:
  • .env.example with all required variables
  • Clear installation steps
  • Database migration scripts if needed
  • Seed data for demo
Commit Guidelines
Use conventional commits:
feat: add mobile notification system fix: resolve offline sync bug docs: update README with setup test: add integration tests refactor: optimize API calls
Minimum 10 commits per team with all members contributing.
Team Formation
Let the algorithm decide your destiny

๐ŸŽฒ All Participants

Your Teams
Time to build. Good luck! ๐Ÿš€
Final Standings
Congratulations to all participants!
๐Ÿฅ‡
Team Alpha
QuickApprove - Mobile Approval System
95
๐Ÿฅˆ
Team Beta
ProcureAI - Smart Quotation Engine
92
๐Ÿฅ‰
Team Gamma
FlowMaster - Workflow Automation
88