The client portal of a digital agency.
Innoventon supports businesses with websites, software and ongoing care. Its client portal is built with Portenia — without custom development.
- Industry
- Digital agency: websites, software, ongoing care
- Built with
- Portenia — no custom development
- Team sign-in
- Microsoft company account (Entra ID)
Three questions, five seconds.
An agency client does not log in every day. They come when they need something — or when they want to see how far their project has got.
So the portal’s home page is built around three questions. Each should be answered in five seconds, without a click and without searching:
- 1
„Is anything waiting on me?“
- 2
„How far along is my project?“
- 3
„Where is that file from back then?“
Good morning, Ms Keller
Here is what matters right now.
Is anything waiting on me?
2 things for you
- Approve home page v3Waiting
- Accept quote A-0415Waiting
How far along is my project?
Website relaunch
- Concept
- Design
- 3Build
- 4Launch
Next up: build
Where is that old file?
- Logo_final.svg2024
- Styleguide.pdf2024
Redrawn — project and file names are examples.
What was built.
Everything in one place, under the agency’s brand — assembled in the portal editor.
View and request services
The client sees what Innoventon offers and requests a service right in the portal.
Projects with timeline and approvals
Milestones show where things stand; the client approves drafts in the portal.
Tickets for bugs and change requests
Whatever comes up after launch becomes a ticket — with a status, not an email thread.
Accept quotes, pay invoices
The client accepts quotes in the portal and pays invoices there.
Project chat and documents
Project conversations and their files live in one place — including the ones from back then.
Team sign-in with Microsoft
Staff sign in with their Microsoft company account (Entra ID, SSO).
Three paths, deliberately separate.
New business, ongoing work and bugs are different things — in the portal they have different places. The client knows where to ask, and the team knows what is in front of it.
- 1
Services
New business. A request becomes a quote that the client accepts in the portal.
- 2
Projects
Ongoing work. Timeline, approvals, chat and files belong to the project.
- 3
Tickets
Bugs and wishes. Reported briefly, tracked by status — separate from the project plan.
Website relaunch
Project · since March
- Conceptcompleted
- Designcompleted
- Buildin progress
- Launchplanned
Home page — draft v3
Today
ApproveChanges- Approved
Colours and fonts
Last week
- In progress
Contact form sends no confirmation
T-118Bug - Scheduled
New “Careers” page
T-117Wish - Done
Typo in the legal notice
T-112Bug
Search engine check
- Request
- 2Quote
- 3Accepted
Redrawn — project and file names are examples.
Data sources instead of custom code.
Projects, requirements and tickets are not specially programmed modules in this portal. They are data sources in the builder — tables with fields that Innoventon set up itself and shows as a timeline or a list.
That is the real point of this case: these are the same building blocks your portal is made from.
Clients with email, team with company account.
Clients sign in to the portal with their email address. The Innoventon team signs in with its Microsoft company account — the same sign-in as for mail and calendar, no second password for the portal.
Clients
Email address
keller@example.com
Staff
Sign in with Microsoft company accountWhat you can take from it
- Build the home page around the questions your clients arrive with — not around your menu.
- Separate new business, ongoing work and bugs. Each gets its own place.
- What you keep in spreadsheets today becomes a data source in the portal — without a development project.
Your portal looks different. It is built the same way.
We show you Innoventon’s portal and which parts of it fit your business.