How PoC Studio works

After you submit an application or company profile you get a private link — your key to everything: check your review status, read and answer our messages, and update your submission. No account or password needed. Keep it to yourself: anyone with the link can see your page. If you lose it, contact us at hej@pocstudio.se and we'll re-issue it.

Only you (via your private link) and the PoC Studio team. Nothing is public before we approve it — and even then only public-safe fields: for builders, the profile fields marked public; for challenges, only the title and desired outcome, and only if you chose a public confidentiality level.

You pick a level when submitting: Public (fine on the Idea Board), Partially confidential (public card allowed, details stay private) or Private/NDA (never shown publicly; we sign an NDA before diving into details). Admin screens mark every non-public challenge with a PRIVATE/NDA badge.

The public board of ideas and approved challenges. Anyone can vote (one vote per idea, no account needed). The top-voted ideas get picked up for build sprints — 'Top 3 get built'.

We're actively reading your application. Who acts: PoC Studio What happens next: We approve, ask for more info, or (rarely) decline — you'll see it on your status page.

We need something from you — there's a message on your status page explaining exactly what. Who acts: You What happens next: Reply in the thread or update your profile; either automatically puts you back under review.

Welcome aboard! You're part of the builder pool and can be matched with PoC builds. If you opted in, your public profile appears on the builder pages. Who acts: PoC Studio What happens next: We contact you when a matching sprint comes up. Editing your profile keeps your approved status.

We couldn't take your application further this time — the message on your status page explains why when possible. Who acts: — What happens next: You're welcome to apply again later (e.g. when your availability changes).

The application was closed without a decision — usually inactivity or by request. Who acts: — What happens next: Contact us if you want to pick it back up.

We're checking the profile and your PoC interests. Who acts: PoC Studio What happens next: Approval, a question from us, or a decline — visible on your company page.

We asked you something — see the message thread on your company page. Who acts: You What happens next: Answer in the thread or update the profile; you go back under review automatically.

You're an approved partner: you can submit PoC challenges from your company page and they go straight into triage. Who acts: You What happens next: Submit your first challenge — and tell us if you want to be shown as a public partner.

We couldn't proceed with the profile — reasons in the message thread when possible. Who acts: — What happens next: You may submit again with updated information.

Profile closed without a decision. Who acts: — What happens next: Contact us to reopen.

First assessment: is it PoC-shaped? Do we understand the problem, data and success criteria? Who acts: PoC Studio What happens next: It moves to 'scoped' (we write a build brief), or we ask for more info.

Something is missing — check the message on your company page (tagged with the challenge title). Who acts: You What happens next: Reply with the missing details and triage continues.

We've written a concrete sprint brief: what will be built, in how many weeks, with which success criteria. Who acts: PoC Studio + you What happens next: We decide together whether it goes on the public Idea Board or stays private, then match builders.

The challenge is published as a card on the public Idea Board (title + desired outcome only — never confidential details). The community can vote on it. Who acts: PoC Studio What happens next: Builder matching. Popular cards get prioritized.

Approved for build but kept off the public board — used for NDA/confidential work. Who acts: PoC Studio What happens next: Builder matching happens privately (builders sign the NDA if required).

A builder team is assigned to your challenge. Who acts: PoC Studio + team What happens next: The sprint starts; you'll meet the team and agree on the demo cadence.

The team is building. Demo every Friday. Who acts: Build team What happens next: Sprint runs 2–4 weeks, then demo-ready.

The PoC is ready to show — a working deployment plus a short tech report. Who acts: Build team + you What happens next: You get the demo and the honest go/no-go recommendation.

Done: PoC delivered with the go/no-go call. The builders bank points and a verified reference. Who acts: — What happens next: If it's a 'go', we can talk about what a production version would take.

The challenge won't be built — reason in your message thread when possible. Who acts: — What happens next: You can rework and resubmit it.

Closed without a build — usually withdrawn or gone stale. Who acts: — What happens next: Contact us to revive it.