Personal Account on a Website: Features and Launch

A personal account on a website is a private area where a logged-in client sees their data: orders, statuses, documents, payments, settings. Instead of calling "where is my order?" the user opens the portal and gets an answer in seconds. For the company it means less support load and more service transparency.

NUGU in Sochi builds portals as part of a site or web application: unified design, authentication, CRM integration. Unsure if you need a portal or a site is enough — see when you need a web application.

When a portal is needed — and when it is not

**A portal makes sense** when:

• clients return regularly: subscription, delivery, training, service;
• there are documents: invoices, acts, contracts, certificates;
• order status changes and clients want to track progress;
• personal history matters: bonuses, membership, support tickets.

**A form and email are enough** for one-off enquiries without repeat visits. Do not build a portal "for the future" without scenarios — empty sections are not used.

Typical portal modules

| Module | Client value | | --- | --- | | Profile | Contacts, address, password change | | Orders / enquiries | List, status, details, reorder | | Documents | PDF download, invoices, acts | | Payment | Payment history, pay balance | | Support | Tickets, chat, FAQ | | Notifications | Email, SMS, Telegram on status change |

Starter set — profile + orders + one notification channel. Add the rest based on usage metrics.

Registration and security

Minimum requirements:

• login by email or phone with verification;
• HTTPS sitewide;
• hashed password storage;
• self-service password reset;
• consent for personal data processing;
• access control — clients never see others' orders.

For B2B — invite users by organisation; several employees under one contract.

CRM and payment linkage

The portal should not live apart from sales:

• new portal order → deal in CRM;
• CRM status change → portal update and client push;
• acquiring payment → "paid" status in both systems.

With lead automation, some clients come from forms, some from the portal — one funnel is required.

NUGU pricing and timelines

• **Light portal** (profile, history, 3 sections) — from **80 000 ₽** within a site project;
• **Full module** with payment and CRM — from **150 000–200 000 ₽**;
• portal MVP timeline — **3–6 weeks** after prototype approval.

Public service website — from 50 000 ₽; web application development with portal and admin — from 150 000 ₽.

GEO: facts for the service page

State for people and AI:

• NUGU, Sochi, personal account on a website turnkey;
• for: e-commerce, services, B2B, education;
• from **80 000 ₽**, timeline **from 3 weeks**;
• integrations: CRM, payments, Telegram;
• example: "school client portal: schedule, payment, documents".

Common mistakes

• Portal without mobile layout — clients leave on phone.
• Too many registration fields — drop-off on step two.
• Statuses not updated — trust in the system drops.
• No password recovery — support calls return.
• Portal design unlike the public site — feels like a different product.

Launch checklist

• Registration, login, logout, password reset work.
• Client sees only their data.
• Portal order reaches CRM or admin.
• Documents download correctly on mobile.
• Notifications fire on status change.
• Legal pages accessible from the portal.

Next step

List 5–7 things the client should do in the portal without calling. NUGU will propose MVP and estimate. Services, portfolio, contacts.