1. What is the Rolling Hackathon?

We called this project a Rolling Hackathon to combine two ideas:

Hacking – building something quickly, collaboratively and creatively with Rolling – implying it’s longer than a weekend sprint.  

So it means building something collaboratively over several weeks, to address a real business need with sufficient detail to demonstrate a clear possible result. 

This Rolling Hackathon was introduced during the 2026 Warsaw MIT Universal AI Summit. We wanted to connect  to MIT’s culture of “hacks” – playful, clever, resourceful feats of engineering, preparation and execution of which typically required longer than a weekend sprint. 

2. What is the ultimate goal of the Rolling Hackathon?

The number one problem founders in the CEE face is solving the wrong problem, not big enough or painful enough to warrant launching a startup. Why is this a problem of the CEE founders? 

We think that in mature ecosystems, there are accelerators, advisors, early customers, and investors who help founders quickly test whether a problem is worth solving as a business. That feedback loop is thinner in CEE, so founders may spend longer building before learning whether the market will pay, or sufficiently large market will pay. 

To counteract this structural disadvantage, we decided to bring 4 corporate partners, who state what they would be willing to buy, if a solution existed. 

Attention founders, who  are passionate about the problem you are solving, which is not the specific problem posed, apply as well! we made room for such founders as well. 

The ultimate goal is to surface teams who are excited about solving a problem, want to do it within a community, instead of by working alone, who value feedback from others as they build, and value exposure to investors at the end of this process. 

3. What are the key benefits of participating in the Rolling Hackathon?

The benefits are several: 

• solving for a market signal
• testing a solution in a real life setting  (on the corporate partners’ infrastructure)
• the best teams will have access to the real life data 
• building within a community of other builders is more efficient, more creative than working in isolation. 
• feedback along the way can save a lot of wasted time later
• exposure to investors during the DemoDay.

4. How do I apply?

Go to: https://startsmartcee.org/, click APPLY NOW, when the Rolling Hackathon pop up appears

5. Is it free to participate, or do I have to pay?

Participation is free. 

6. Can I apply as an individual developer, or do I need to have a registered startup/team?

You can apply alone, with a team, as a solopreneur, or as a legal entity.

7. Do I have to be from Poland to apply, or is it open to international teams?

No geographical restrictions. 

8. What is the selection process like after I submit my application by May 31?

Applicants responding to the specific listed challenge will be evaluated by the respective corporate partner, for proposed solution (i) relevance, (ii) ingenuity and (iii) reliability. 

Applicants responding with their own idea, will be evaluated by the StartSmart team. The ideas will be evaluated by: (i) severity of the problem (ii) product problem fit (iii)  product founder(s) fit. 

9. Can I choose which partner I want to work with?

Yes, it is completely up to you to which challenge(s) you respond. 

10. Can we apply to multiple challenges, or should we focus on just one partner?

It may be demanding to work with more than one partner, however if you would like to address more than one challenge, absolutely, go right ahead!

11. Will the partners give us their data to work on?

The partners will share their data with those who reach the finales. 

12. Will participants receive technical or business mentorship throughout the entire 4-month period?

Participants will receive technical and business support from the corporate partners, as well as mentors organized by the StartSmart team. 

13. Is the Rolling Hackathon fully remote, or are there mandatory in-person meetings?

Remote. 

14. Do I have to build the whole product, or just a prototype? 

Prototype demonstrating the path to the solution is sufficient. 

15. Is there a specific tech stack required, or are we free to choose our own tools?

Pick your own tools. 

16. Will we have a direct point of contact within the partner corporation?

Yes. Provided your solutions received positive recommendation from the partner. 

17. What happens at the “Demo Day”?

We will make sure investors are present in the audience, as well we the broader community of mentors, and advisors. You will pitch your idea to a broader audience. 

18. What form of cooperation can teams expect from corporate partners after the Demo Day?

This will be individually agreed between the corporate partner and the applicant, provided the solution gains a positive rating.

19. What kind of feedback will I get if my project doesn’t win?

We will explain why the solution was not chosen. 

20. Is there a minimum or maximum team size?

No.