Roles and accountability
Each action has an owner, permissions and transition rules.
BIG FISH / Portal development
Web portal development
We build portals and accounts for customers, partners and staff. Requests, documents, approvals and statuses become part of one system with clearly defined access.
from RUB 1 000 000 · scoped around your project
DEMO / REQUEST 024
Equipment delivery
Created
123
▤ Specification.pdfDemonstration document
Customer → Manager → Approver
DESIGN × DEVELOPMENT × BUSINESS
Beautiful in the details.
Considered as a whole.
Connected data
We define the owner of each value and the exchange rules for CRM or ERP.
Manageable growth
We define an initial working scope and extend it in separate stages.
EXPLORE THE JOURNEY
See how it works.
Switch options to see how the solution changes. This demonstrates the approach using fictional data.
01 / Portal development
Created
A customer submits a request with a specification.
How the work is estimated ↘DEMO / REQUEST 024
Equipment delivery
Created
123
▤ Specification.pdfDemonstration document
Customer → Manager → Approver
DEMO / REQUEST 024
Equipment delivery
In review
123
▤ Specification.pdfDemonstration document
Customer → Manager → Approver
03 / Portal development
Approved
The decision is visible in the account and the document is available to authorised participants.
How the work is estimated ↘DEMO / REQUEST 024
Equipment delivery
Approved
123
▤ Specification.pdfDemonstration document
Customer → Manager → Approver
A CLEAR PROCESS
See the result.
At every stage.
- 01
Discover
Discuss the business, audience, content and constraints. Define the first release goal.
- 02
Design
Agree architecture, key journeys and visual direction before full implementation.
- 03
Build
Implement the agreed scope, connect data and review progress in stages.
- 04
Launch
Check working journeys, hand over access and agree ongoing support.
WEBSITE PRICING
Clear scope.
A reasoned quote.
The starting price is a discussion guide. The final quote depends on unique page types, workflows, source materials and integrations. Work scope and additional expenses are recorded in the proposal before the project starts.
Portal developmentfrom RUB 1 000 000
A precise quote follows a discussion of your project.
Page types
Unique templates and content volume
Features
Selection, forms, roles and states
Connections
CRM, payments, back office and migration
IN DETAIL / 01
Start with the business process
We identify who creates a request, checks the information and makes a decision. Exceptions include rework, cancellation, missing documents and overdue responses.
This model determines screens, notifications and permissions. Without it, a portal can become a collection of forms with manual email work behind them.
IN DETAIL / 02
Permissions are enforced on the server
Roles and data ownership are checked for protected actions. Hiding an interface button is not a substitute for server-side authorisation.
We agree which events are logged, how access is recovered and how a company manages staff in its account.
IN DETAIL / 03
Integrations and data ownership
We decide where customers, orders, prices and documents are maintained. Exchange rules cover retries, errors and duplicate prevention.
If an external service is unavailable, users need a clear status and the responsible team needs information to investigate.
IN DETAIL / 04
The first release and beyond
The first release should complete a meaningful workflow, such as creating and approving a request. We define acceptance criteria and test them with representative roles.
Further modules follow business priorities. Portal cost depends primarily on processes, permissions, data and integrations, not screen count.
FAQ
Before we start.
Can you connect our back-office system?
We first review its API, documentation and test environment, then define the exchange scope and limitations.
Who manages users?
That depends on the roles: your administrator, a customer administrator or another nominated employee. Permissions are defined during planning.
Does the first release need every feature?
No. It should complete a useful workflow without leaving critical operations outside the system.
BIG FISH / DEVELOPMENT
Find the right solution
for your project.
Product catalogue website development
Website redesign for business
Tilda website development
Custom ecommerce website development
Joomla website development
Landing page design and development
Website prototyping and UX design
Responsive website development
Website and interface frontend development
End-to-end website development
↗NEXT STEP
Let’s discuss your project.
Start with an idea, your current website or a list of things you want to change. We will help define the next step and project scope.