A site people log into and use, not read and leave.
Listings, bookings, member areas, internal dashboards, anything with accounts and roles behind it. The database is designed before the first screen is drawn, because a portal built screen-first has to be rebuilt the moment the data outgrows it.
Who it is for
When this makes sense
Organisations whose work does not fit a brochure site: property listings, booking systems, member areas, internal tools that staff use daily. Often replacing a spreadsheet that several people email to each other.
Typical timeline: Four to eight weeks, depending on scope
The spreadsheet became the system
It started as one file and now four people email versions of it to each other. Nobody is sure which is current, two of them disagree, and the answer to any question takes a phone call. That is a portal that was never built.
People cannot find what is there
The information exists but is spread across pages, attachments and documents nobody has opened in years. Without real search and filtering, having the data and not having it look the same from outside.
It was designed screen-first
A portal drawn as screens works until the first thing nobody anticipated arrives, and then it has to be rebuilt rather than extended. Getting the data structure right before the first screen is most of what the price actually pays for.
What the price covers
No hidden items. If something you need is not listed, you get the figure for it before the work happens, not on the invoice.
- User accounts with roles and permissions worked out before building
- Admin panel you can operate without calling anyone
- Search, filtering and sorting over real data, tested at real volumes
- Database design done before the first screen is drawn
- Everything in the website package: speed, accessibility, search setup
- Accessibility to WCAG 2.2 AA, which public bodies are required to meet
- Handover documentation for whoever operates it after us
How it goes
Your part fits in one sentence
Here is exactly what happens between the first call and the site going live, and what is asked of you at each step.
- 01
Scope
What the portal has to do, who uses it, and which roles see what. This is the conversation that decides the price, so it happens before any figure is quoted.
Your part: Explain how the work runs now.
- 02
Data design
The database is designed and reviewed with you in plain language before anything is drawn. Getting this wrong is the expensive mistake, so it comes first.
Your part: Confirm it matches reality.
- 03
Build
Accounts, roles, admin panel, search and filtering, tested against realistic volumes rather than three sample rows. Accessibility to WCAG 2.2 AA throughout, which public bodies are required to meet.
Your part: Answer questions as they come.
- 04
Handover
You get documentation for whoever operates it, and a walkthrough of the admin panel. Nothing in the portal requires us specifically to keep working.
Your part: Take it over, or leave it to us.
Questions
What people ask first
What separates a portal from a website?
People log in and do something. A website is read; a portal is used. Once there are accounts, roles and data that changes daily, the work is portal work regardless of how many pages it has.
Why does the database come before the design?
Because the data outlives every screen you put in front of it. A portal designed screen-first works until the first thing you did not anticipate arrives, and then it has to be rebuilt rather than extended. Getting this order right is most of what the price pays for.
Can it be extended later?
That is the assumption it is built on. New sections, roles and reports are added without rebuilding, and each is quoted before the work starts. Nothing in the structure depends on you never changing your mind.
Do you work with institutions?
Yes, and it is a significant part of the work in Serbia. Accessibility to WCAG 2.2 AA is treated as a requirement rather than an add-on, because public bodies are legally obliged to meet it and a supplier who ignores that cannot deliver for them.
Who operates it once it is live?
You can, through the admin panel, and the handover documentation covers it. If you would rather not, operation and updates are part of maintenance. Either way nothing about the portal requires us specifically to keep working.
Half an hour on a call.
Costs nothing and commits you to nothing.
Describe what the business does and what is going wrong. You get what we would do, how long it would take and what it would cost.
Book a call