BuilderPot

Hi Fazier. I built BuilderPot because hackathon prizes and startup credits are scattered across Devpost, sponsor pages and random tweets, and deadlines are easy to miss. It is a deadline-sorted list with links to official sources, checked weekly, plus a free newsletter called The Pot. Feedback on what to add next is very welcome.

Sorting hackathon prizes and startup credits by deadline, with every entry linked to the official source, makes this far more trustworthy than the usual scattered lists. Do you plan to add filters for eligibility, such as region, remote vs. in-person, or whether a credit program requires prior funding? That's usually what rules an opportunity out for me before the deadline matters.

useful. as solo founder I always find out about credits after the deadline. do you track crypto/web3 grants too or only cloud credits and hackathons? also Korean version is interesting choice, is it because of your audience or you are from there?

useful. as solo founder I always find out about credits after the deadline. do you track crypto/web3 grants too or only cloud credits and hackathons? also Korean version is interesting choice, is it because of your audience or you are from there?

Sorting by deadline is the right default. Most hackathon lists sort by prize size, and you find the good ones a day too late. How do you handle programs with rolling deadlines, like cloud credits with no end date? Do they sit at the bottom or get their own section?

hi fazier . the builder pot is prizer for real

hi fazier . the builder pot is prizer for real

Sorting by deadline is the right default; credit programs are spread across so many sponsor pages that it's easy to find one a week late. Many hackathons and credit programs come back every year, so a "notify me when it reopens" option on expired entries would help. Do you plan to tag credits by cloud provider (AWS, Azure, Google Cloud)? That's often how builders decide where to deploy.

Do deadline entries include the closing time and time zone? An add-to-calendar link with a reminder would help builders avoid missing an opportunity on the final day.

Bringing hackathon deadlines and always-open credits together makes this a useful starting point for indie builders. The direct links to official sources and clear eligibility summaries are especially helpful.

A weekly digest sorted by deadline is the format I'd actually read. Small idea: a calendar feed (.ics) with the deadlines would let people drop them straight into Google Calendar and not miss one.

Verifying each entry against Devpost and the program pages is what makes a list like this trustworthy. Do you flag programs that require a prior funding round or a registered company, since that trips up solo builders?

Sorting by deadline, with a link to the official page and a check against Devpost, is the part that stays useful after the week a program closes. Most credit roundups go stale. I'd want each row to say whether the award is cash, cloud credit, or a grant, and whether it can be stacked, because founders usually apply to several at once. A weekly note only helps if it drops deadlines that already passed.

A deadline-sorted list linked to official sources solves a real pain for indie builders who miss credit programs. A weekly calendar (ICS) feed of upcoming deadlines would pair nicely with the newsletter for people who live in their calendar.

We keep a catalogue of startup credit programs too, and what breaks most often isn't dead links. It's terms that change quietly: the credit amount, who qualifies, whether it stacks with others. Do your weekly checks compare those fields to last week, or only confirm the page still loads? A "terms changed" flag on an entry would be really useful.