Accelerator & incubator portal

An accelerator and incubator portal is where startups apply to a cohort, the program team moves each application through review, and accepted founders tick off cohort milestones and browse a directory of the other startups.

Pattern: Requests

Describe it to Pory

“Startups apply to our twelve-week accelerator. The program team reviews applications, and founders who get in work through milestones and can see the other startups in their cohort.”

Viewing as

My applications

My applications

Powered by Pory

In plain English

What is an accelerator & incubator portal?

An accelerator and incubator portal is where startups apply to a cohort, the program team moves each application through review, and accepted founders tick off cohort milestones and browse a directory of the other startups. It follows the Requests pattern: someone submits, someone decides, it moves through statuses. Pory generates it from a plain-English description, with a login for each role (founder and program manager) that shows only what that role should see, and flat pricing with unlimited founders.

What it does

01

Founders apply with the pitch deck attached, not a share link

Applications used to come through a form tool, with decks sent as share links that had stopped working by the time the panel met. In Pory a founder names the startup, writes the one-line pitch, picks a sector and how much they've raised, and attaches the deck to the application itself. The program team stops chasing access requests the night before screening.

Forms to submit a recordDone by: Founder
02

Every applicant sits on one board, from screening to interview

Screening two hundred applications in a shared spreadsheet meant filters, frozen rows and the occasional accidental sort. The program manager sees each startup as a card under Applied, Screening, Interview or a decision, and drags it forward after each call. The whole team works from the same pipeline instead of five local copies.

Board by statusDone by: Program manager
03

Founders tick off cohort milestones as they hit them

Milestones used to live in a kickoff slide that nobody opened again until the week before Demo Day. Each founder signs in to their own milestone list, with customer interviews, a pricing page and a pitch draft each carrying a due date, and ticks them off as they land. The program manager sees who's on track without booking a check-in call.

ChecklistsDone by: Founder
04

A card for every startup, this cohort and the ones before

Founders kept asking who else was in the cohort, and the answer was a slide from orientation week. In Pory each startup has a card with its logo, what it does, its sector and its founders, across this cohort and earlier ones. Introductions start with a card, not an email to the program manager asking for one.

Gallery & image gridDone by: Founder

The parts every portal is built from

Pory generates a portal from these pieces and wires the permissions between them. The same parts run a grant round, a help desk, and a tenant portal — only the names on the pages change.

Collect

Forms

Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.

Public pages

An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.

Self sign-up

People create their own account and land in the role you chose for them.

File attachments

Upload and view files on the record they belong to — not in a folder named FINAL v2.

Decide

Approve / reject with a reason

Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.

Status tracker

“Where's my request?” answered as a progress bar on the submitter's own page.

Board by status

Cards in columns. Drag a record to move it along.

Checklists

Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.

Assign to a person

Name who a record is for and it lands on their list, and nobody else's.

Notes & scores

A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.

Reminders by date

Renewals, expiries and overdue work, in an in-app inbox and by email.

Share

Tables

Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.

People directory

Portraits, names, and roles from a table, shown only to the roles allowed to see them.

Calendar

Records on a month or week view, by date.

Gallery & image grid

Records as cards or photos.

Record pop-up & linked records

A shareable pop-up with a record's details and what's linked to it. Edit, change status, or add a linked record from there.

Notices & info pages

Check-in details, benefits, updates — a page for a role to read.

Counts, totals & averages

Live figures over the rows a viewer is allowed to read.

Control

Role & row access

Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.

No-Password Doors

A sign-in link by email, by default. Password sign-in if you'd rather.

Your brand

Your domain, your colours, your logo. Members see you.

On purpose

Four things Pory won’t do

A portal runs a program, a service, or a process. These jobs belong to tools built for them, and Pory keeps the records around them instead.

Take payments

Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.

Book time slots

Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.

Host the conversation

No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.

Plan routes

Pory keeps the service record, not the map.

Frequently asked questions

Your accelerator & incubator portal, live today.

Describe it in a sentence and send the invite. Unlimited founders, flat price.