About the challenge

We're building the tools that make us better — faster, smarter, and leaner. This hackathon is all about creating internal tools that directly impact the bottom line: software that saves time, cuts costs, unlocks revenue, or streamlines the way we work.

Got an idea for automating a painful manual process? A dashboard that gives leadership better visibility? A workflow that eliminates hours of back-and-forth? This is your moment to build it.

What we're looking for

Projects will be judged on real-world impact and feasibility. The best submissions won't just be clever — they'll be tools people actually want to use on Monday morning.

Cost reduction — tools that eliminate waste, automate repetitive tasks, reduce vendor spend, or cut down hours lost to manual work.

Revenue enablement — tools that help teams close deals faster, surface better insights, improve customer experience, or unlock new opportunities.

Operational efficiency — dashboards, automations, integrations, or workflows that remove friction and help teams move faster with fewer errors.

Get started

Form your team, pick a problem worth solving, and start building. Stuck on ideas? Think about the last time you said "why do we do this manually?" — that's your project.

• Register your team and submit your project idea before the deadline
• Build anything: a web app, script, integration, dashboard, or automation
• Demo your tool live to a panel of judges at the final showcase
• Winners get bragging rights — and their tool considered for production

• Business Impact
  How meaningfully does this tool save the company money, generate revenue, or improve operational efficiency? Judges will look for a clear, quantifiable benefit — even if estimated. The stronger the real-world impact, the higher the score.
• Technical Execution
  Is the tool well-built, functional, and reliable? Judges will assess the quality of the implementation, how well it works in the demo, and whether it could realistically be maintained and scaled beyond the hackathon.
• Feasibility and Adoptability
  Could this tool actually be deployed and used by the company after the hackathon? Judges will consider how practical the solution is, how easy it would be for employees to adopt, and whether it integrates well with existing systems and workflows.
• Presentation and Clarity
  Does the team clearly communicate the problem they're solving and why it matters? Judges will evaluate how well the demo and pitch convey the tool's purpose, value, and functionality to someone seeing it for the first time.