top of page

Orix McLaren Hackathon
2026


Remote Event
3rd - 4th Jan 2026

Top 3 teams invited to Goa
to present to the Judges
7th Jan 2026


 

Join the Innovation

2 day Remote Online Hackathon 

Weekend remote hackathon bringing participants over Zoom for an immersive build experience.

At the end of the event, submit your entry as a GitHub link with source and presentation to hackathon@mclarensv.com

At the end of the event, submit your entry as a GitHub link with source and presentation to hackathon@mclarensv.com

The top 3 teams will be invited to the McLaren Goa office for an in-person presentation on 7th Jan 2026.

Exciting Prizes

By joining the hackathon, you'll have the chance to win exciting prizes, gain recognition for your work, and even land opportunities to take your projects to the next level.

Winners  - Rs. 25,000/-
Runnerup - Rs. 15,000/-
2nd Runnerup  -Rs. 10,000/-

Credit Memo Auto-Generator 

Problem Statement 01

Reads documents → produces a clear first draft 

What it is: A tool that reads long documents and writes a clear first-draft summary for humans. 

In simple terms: AI reads PDFs, pulls key numbers and risks, and produces a structured, editable draft. 

Think of it like: ChatGPT that reads PDFs and writes drafts. 

Example builds: 

  • Upload a PDF and generate a one-page executive summary 

  • Highlight key numbers and show the source page 

  • Export the draft to Markdown or Word for editing 

  

Example Ideas 

  • Upload a PDF with multiple financial statements → tool outputs: 

  • 5-bullet executive summary 

  • Key metrics table 

  • “Top 3 risks” section 

  • Highlight a sentence in the output → tool shows which page of the PDF it came from 

  • Confidence tags like: 

  • ✅ Strong data 

  • ⚠️ Incomplete data 

  • “Rewrite this section in simpler language” button 

Example User Flow 

Upload PDF → Click “Generate Memo” → Review → Edit → Download 

Asset Manager AI Copilot

Ask questions → get answers from data 

What it is: A chat assistant that answers questions using company data. 

In simple terms: Users ask questions instead of digging through dashboards; the system finds data and answers clearly. 

Think of it like: A search engine for internal data. 

Example builds: 

• Ask which assets declined the most this quarter 

• Return a ranked table with trend indicators 

• Show the data sources used to answer 

Example Ideas 

  • Ask: “Which assets declined the most this quarter?” 
    → Copilot returns a ranked list with % change 

  • Ask: “Show trends for Asset X over the last 6 months” 
    → Table + simple line chart 

  • Click a result → see data sources used 

  • Copilot asks clarifying questions: 

  • “Do you want revenue or profit?” 

Example User Flow 

Type question → Get answer + table → Ask follow-up → Export result 

Problem Statement      02

Covenant Breach Detection Agent

Problem Statement  03

Checks rules → raises alerts 

What it is: An automated rule-checker that warns you before something breaks. 

In simple terms: The system checks numbers against rules and raises alerts when values look risky. 

Think of it like: A smoke alarm for rule violations. 

Example builds: 

• Define rules in a simple config file 

• Run checks on demand or on a schedule 

• Flag near-breach versus breach with explanation 

Example Ideas 

  • Rule: “Debt ratio must stay above 1.2” 

  • Agent detects: 

  • Current value: 1.25 → ⚠️ “Near breach” 

  • Current value: 1.10 → 🚨 “Breach” 

  • Alert includes: 

  • Rule violated 

  • Current value vs limit 

  • Trend (getting worse / improving) 

  • Daily scheduled run + manual “Run Now” button 

Example User Flow 

Agent runs → Alert generated → Click alert → See explanation 

Month-End Close Exception Finder

Scans data → finds unusual values 

What it is: A system that finds strange or unexpected numbers in large datasets. 

In simple terms: The system scans data, flags unusual entries, and explains why they stand out. 

Think of it like: Spam detection, but for numbers. 

Example builds: 

• Upload a CSV and scan for anomalies 

• Rank exceptions by severity 

• Explain why each value was flagged 

  

Example Ideas 

  • Flag transactions that: 

  • Are 10× larger than last month 

  • Appear in a new category 

  • Break historical patterns 

  • Rank exceptions: 

  1. High impact 

  1. Medium impact 

  1. Low impact 

  • Show explanation: 

  • “This value is 3 standard deviations above normal” 

  • Compare: 

  • This month vs last month vs average 

Example User Flow 

Upload data → Click “Scan” → Review ranked exceptions 

Problem Statement       04

Rules

Event Overview 

  • Event: Public 24-hour Hackathon 

  • Team size: Exactly 4 members.

  • Format: Build a working prototype and present a demo at the end. 

​

​Coding Rules 

  • You may come with ideas, sketches, and boilerplate templates. 

  • Code must be primarily written during the hackathon. 

  • If you reuse code, you must disclose it in your README under “Prior Work / Reused Components”. ​

​

Allowed 

  • Any programming language/framework 

  • Open-source libraries and public APIs (must be credited) 

  • AI tools (Copilot/ChatGPT/etc.) are allowed 

​​

Not allowed 

  • Using real personal/customer data (PII). Use synthetic/public datasets only. 

  • Attacking or scanning real systems/networks 

  • Submitting a previously built full project (see below) 

​​

Submission

Submit before the deadline: 

  1. GitHub/GitLab repo link 

  2. README with: 

    • Problem statement + target user 

    • Solution overview 

    • How to run (local or hosted) 

    • Architecture diagram (simple is fine) 

    • Tech stack + credits for any reused code/APIs 

  3. Pitch deck link (max 6 slides) 

  4. Demo plan (what you’ll show in 3–5 minutes) 

​

Demo format 

  • 5 minutes demo + 2 minutes Q&A per team 

  • Demo should show: problem → solution → live prototype → impact/next steps 

​

Teams can be disqualified for: 

  • Code of Conduct violations 

  • Plagiarism / undisclosed prior work 

  • Using prohibited data or unsafe/illegal activity 

IP & Media Policy

Intellectual Property 

  • Teams retain ownership of their projects and IP. 

  • By participating, teams grant organizers a non-exclusive, royalty-free right to share project names, screenshots, and demo clips for event promotion and reporting. 

  • If sponsors/companies want to explore a project further, any collaboration happens only with team consent after the event. 

​

Media Consent 

  • The event may be photographed/recorded. 

  • By attending, you consent to use of photos/videos for event communication (website/social/reports). 

  • If you do not wish to appear on camera, inform the registration desk at check-in. 

key features

We’re committed to a welcoming, respectful experience for everyone. 

Expected behavior 

  • Be respectful and inclusive 

  • Collaborate constructively 

  • Ask for consent before taking close-up photos/videos of individuals 

  • Report issues early 

​

Unacceptable behavior 

  • Harassment, discrimination, intimidation 

  • Abusive language or unwanted attention 

  • Deliberate disruption of the event 

​

Reporting 

If you feel unsafe or witness a violation, contact: 

  • [Name, Phone] (Primary) 

  • [Name, Phone] (Secondary) 

​

Organizers may take any action needed, including warnings or removal from the event. 

Code of Conduct

bottom of page