Post a problem

What needs solving?

Fill in the essentials. The form grows with your problem. We'll reach out within 1 business day to confirm details and get it live.

Your name required Stays private. Solvers never see it.

Email required Used only to contact you about the winner. Never shared.

Organization or project name Optional. Leave blank to post as an individual or stay anonymous on the board.

Problem headline required This is what solvers see first. Specific enough that the wrong solver self-selects out.

Problem brief required Cover the situation, the output you need, and how you'll verify it's solved.

Brief assist Answer three questions and we'll draft your brief. You edit — you don't write from scratch.

01 — What's broken, missing, or unknown right now? The situation as it stands. What have you tried? What's the cost of leaving it unsolved? 0 / 40 min

02 — What would a winning solution look like? How would you know it worked? Describe the output, the metric, the deliverable. 0 / 40 min

03 — What constraints matter? Budget, format, tools, audience, timeline, data access, things to avoid. 0 / 40 min

Takes about 5 seconds. You'll edit the result before it goes into your submission.

Generated brief — edit freely

This draft belongs to you. Edit it until it's accurate, then click "Use this →" to move it into the main field above.

Prize type required What does the winner get? Problems get solved here for less than you think.

Cash Money. Held in escrow, released when you approve a winner. Full refund if no solution qualifies.

Recognition Public acknowledgement. The win goes on the solver's public profile — a real career asset. Costs you nothing.

Charity Recognition + a named cause. You name the organization. The solver wins the credit; the cause gets the recognition.

Prize amount required

Any amount. Prize is held in escrow — released when you approve a winner, or refunded in full if no solution qualifies.

Named cause or organization The cause gets credited publicly alongside the winner's profile. No financial donation required — the recognition is the prize.

How long should this run? required Shorter deadlines attract solvers who thrive under pressure. Longer ones attract thorough, research-heavy approaches.

Helps solvers find the right problem

Work type What kind of solution does this require? Honest categorization helps the right solvers find it.

Analyze Find the insight in data, a market, a situation, or a corpus. e.g. "Tell us why customers churn."

Build Create the artifact — code, model, tool, prototype, system. e.g. "Build a working onboarding flow."

Write Persuade, explain, translate, draft, or reframe. e.g. "Rewrite our pricing page."

Decide Synthesize options, evaluate tradeoffs, recommend a path. e.g. "Tell us which vendor to pick."

Additional context for solvers

Domain Helps solvers self-identify. Leave blank if your problem spans multiple areas.

Materials or context you'll share with solvers Optional — but the more specific you are, the more serious solvers you attract.

Problem access & visibility

Visibility Can the problem brief be posted publicly on the board?

Public The full brief is visible to any solver. Maximum reach.

Restricted You want to limit who sees the brief. We'll discuss access controls when we reach out.

Anything else?

⇒

We'll review and reach out within 1 business day. No problem goes live without your confirmation.

Received — we'll be in touch

Your problem
is in.

We've got everything we need. Expect an email within 1 business day to confirm your details and get your problem live on the board.

What happens next

01 We review your brief — usually same day. If anything needs clarification, we'll email you.

03 Your problem goes live on the board. Solvers can start entering immediately.

04 After the deadline, we send you all qualifying submissions. You select a winner — or declare no winner.

See the open board →

One quick question — how did you find us?

Got something youcan't solve alone?

Your problemis in.

Got something you
can't solve alone?

Your problem
is in.