My projects
A design and creative agency portal is where clients submit briefs and approve or send back each deliverable, and the studio keeps every project, file and change note in one place.
Pattern: RequestsDescribe it to Pory
“We're a 12-person design studio. Clients should submit briefs, see only their own projects, and approve each deliverable or send it back with change notes.”
My projects
In plain English
A design and creative agency portal is where clients submit briefs and approve or send back each deliverable, and the studio keeps every project, file and change note in one place. 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 (client and studio) that shows only what that role should see, and flat pricing with unlimited clients.
What it does
Briefs used to turn up as a voice memo, a mood board and a forwarded email from someone's boss. In Pory the client fills in one brief: what they need, the due date, the budget and the details, and it lands as a new project the studio can scope. Nobody reassembles the request from four inboxes.
Approvals used to hide in replies such as "looks good, maybe bigger?" that nobody could act on. The client opens the deliverable, looks through the attached files, and marks it Approved or Changes requested. The studio sees the decision on the card instead of three replies down an email chain.
Feedback arrived in fragments: a call, a text, a PDF with circles scribbled on it. Now the client files a change note against the deliverable, saying what to change and why, and it appears whenever anyone opens that deliverable. Designers stop hunting for which message had the final word.
Sharing work meant a folder link per client and hoping nobody forwarded the wrong one. In Pory each client signs in and sees only the projects that name them, with their briefs and deliverables. One portal holds the whole client list, and no client ever sees another brand's unreleased packaging.
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
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.
People create their own account and land in the role you chose for them.
Upload and view files on the record they belong to — not in a folder named FINAL v2.
Decide
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
“Where's my request?” answered as a progress bar on the submitter's own page.
Cards in columns. Drag a record to move it along.
Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.
Name who a record is for and it lands on their list, and nobody else's.
A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.
Renewals, expiries and overdue work, in an in-app inbox and by email.
Share
Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.
Portraits, names, and roles from a table, shown only to the roles allowed to see them.
Records on a month or week view, by date.
Records as cards or photos.
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.
Check-in details, benefits, updates — a page for a role to read.
Live figures over the rows a viewer is allowed to read.
Control
Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colours, your logo. Members see you.
On purpose
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.
Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.
Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.
No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.
Pory keeps the service record, not the map.
Describe it in a sentence and send the invite. Unlimited clients, flat price.