Hackathons for your people. A fair say on builds of your app.
Two things we do for companies: run a private build day for your own staff, and give you a published right of reply when somebody builds a feature your app is missing.
Paid · for your own people
Private hackathons
- Your teams build against a brief you choose, with a deadline.
- Entries stay private to your organisation; you judge on criteria you set.
- Afterwards, a written read on what is actually shippable and where the risks are.
- Nothing from a private round is published without written approval.
Free · when someone builds for your app
A right of reply
- We tell you when the first build lands — not when a challenge is posted.
- Your reply is published unedited, above the builds. “No comment” is recorded as a decision.
- No logos, no lookalike names, synthetic data, nothing touching your systems.
- Ask and a build comes down, no reason needed, within two working days.
Why a reply is worth it
What happened at DNB
Someone rebuilt DNB’s banking app in under two hours and published it. The CTO, Nicolai Rygh, answered by building his own version of the Ruter app the same evening — then wrote about what a two-hour prototype cannot do. His own staff were the ones sharing it, and the reply travelled further than the build.
“The hard part isn’t the screens. It’s everything you can’t see.”
The details
How replying works, step by step
We email a named person, once
When the first build lands — not when someone posts an idea. One message with a link. No follow-ups, no chasing, no automated reminders.
The link needs no account
You click it, you type, you publish. No signup, no password. It takes about ten minutes.
It goes up unedited, at the top of the page
In full, above the builds, with your name and role on it. We do not trim it, comment underneath it, or put it behind a tab.
You can decline on the record
“We would rather not comment” is recorded as a decision, which is more accurate than leaving the page silent.
Saying nothing costs you nothing
Most companies will not reply, and the page says so plainly, without counting the days. Silence is not treated as an admission of anything.
If you would rather this did not happen at all
Tell us, and we will not publish builds aimed at your products. We would rather have that conversation now than argue after the fact. Email support@bineric.com and it is handled.
Who runs it
Umair Imam. Previously Director of AI & Quantum Computing at Ruter, where I built a public-sector AI unit that took more than a hundred use cases into production. Research Council of Norway Innovation Award, Nordic 100 in Data & AI, assistant professor at OsloMet. I was the one who rebuilt the DNB app, so I have been on both ends of this.
Every commitment to companies, and what builders are forbidden from doing, is written once on the rules page.
Talk to us first
Twenty minutes, no commitment — about a hackathon, or a challenge of your own.