Client
Sees only their own milestones.
- Pages
- Home, My briefs, My milestones, Files, Invoices, Working together
- Can start
- Send a brief, New brief, Upload a file
A freelancer client hub is where clients send a brief and follow each milestone of the work, and the freelancer keeps briefs, milestones and invoices in one place instead of three apps.
Pattern: Client hubsDescribe it to Pory
“I'm a freelance copywriter. Clients should send me a brief and see their own milestones, and I want to keep track of which invoices are still outstanding.”
My briefs
In plain English
Pory gives every client and freelancer a sign-in of their own. Each client sees only their own milestones. It covers brief intake → milestones → invoices. Milestones, briefs, invoices, things I need, shared files and who you'll work with live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
Briefs used to come as a LinkedIn message that said "quick one" and was never quick. In Pory the client says what they need, the deadline and the budget, and the brief lands as Received so you can quote or pass. You go into the first call already knowing the scope.
Clients checked in by email because they couldn't see where the work stood. Each milestone sits on the client's page with a due date and a status, from Not started to Done, and moves when you update it. You stop writing "just a quick update" emails between the actual work.
Knowing who still owed you meant scrolling through sent mail and squinting at a banking app. Each invoice is a row with its client, amount, due date and status, and your home page counts how many are issued and how many have gone overdue. Chasing becomes a short list, not a guess.
Keeping clients apart used to mean separate folders, separate emails and a careful eye on the CC line. Each client signs in to Pory and sees only their own briefs, milestones, files and invoices. You run one hub for every client, and nobody sees who else you're writing for.
Every person signs in to their own view. This is what each role in the demo gets.
Sees only their own milestones.
Sees every milestone in the portal.
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
“Where's my request?” answered as a progress bar on the submitter's own page.
Live figures over the records a viewer is allowed to see.
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
A sign-in link by email, by default. Password sign-in if you'd rather.
Your domain, your colors, your logo. Members see you.
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited clients.