ASM Systems

Service

Client portal

Your customers log in to the portal and check their own orders, statuses and documents, place new requests and see their history. Managers are asked “where is my order” less often and no longer send files by hand.

Who it is for

  • Customers call and message managers to find out what stage their order is at.
  • Invoices, statements and other documents have to be found and sent to each customer by hand.
  • Regular customers place similar orders and pass on the same details every time.
  • A customer should see only their own data, and your internal system must stay closed to them.

What is included

  • Login with a username and password, with each customer limited to their own data
  • A customer profile with contacts and company details
  • A list of orders or requests with statuses and a change history
  • Order documents: you upload them, the customer downloads them
  • A form for a new request or a repeat order, pre-filled from the profile
  • A section for your staff: customer orders, status changes, document uploads
  • Telegram notifications to managers about new requests
  • A layout for phones and computers, with no app to install

Billed separately

  • Pulling orders and statuses from your systems via an API
  • Online invoice payment in the portal
  • A second interface language
  • Moving your customer base from spreadsheets
  • Server rental in your name, paid by you

Price and timing

Estimated timing

6–10 weeks

What affects the price

  • How much the customer sees: orders, documents, invoices, history
  • Where the data is kept: in the portal itself or in your system
  • Whether several people at one customer need separate access
  • Design: based on a UI library or custom
ServicePrice
Client portalAuthentication, personal data, orders and documents, a link to your accounting system.from 4,500 BYN≈ $1,500

How we work

  1. Discussion: what customers ask about most and which data they may see

  2. A portal prototype: customer and staff screens for approval

  3. Development in stages, checked on test customer accounts

  4. Launch, inviting the first customers and training your staff

Terms of work: payment, revisions, warranty

Example

A demo on fictional data and a real project from my portfolio with a similar task.

  • Demo

    CRM and user portals

    I show how a small CRM is organised using a fictional appliance repair service: requests, statuses, technicians, timesheets, and client and employee portals.

    Open the demo
  • Flagship case

    Fleet management system: from a Telegram bot to an ERP

    Task
    A company with its own vehicle fleet needed shift check-ins, the daily plan, fuel accounting and vehicle maintenance in one system.
    Solution
    Started with a Telegram bot for START and FINISH check-ins and grew it into two services: the management system (bot and web admin) and a driver portal. Integrated with two GPS telematics systems and fuel cards.
    Result
    The system runs every day in a real company and keeps growing: about 620 commits since January 2026.
    • FastAPI
    • python-telegram-bot
    • PostgreSQL
    • SQLAlchemy 2
    • Alembic
    • Docker
    Read the case study

FAQ

How much does a client portal cost?

From 4,500 BYN for a portal with login, orders and statuses, documents and a section for your staff. The total depends on how much data there is and whether it has to be connected to your systems. I give an exact price once we have discussed the task.

How do customers get access?

There are two options: you create the customer's account yourself and send them the login, or the customer signs up and you approve the access. Either way, the customer sees only their own orders and documents.

Can the portal show orders from our own service or database?

Yes, if your service or database provides the data via an API. Orders and statuses then reach the portal automatically, and staff do not have to enter them twice. I estimate the connection once I have seen what data your API makes available.

How is customer data protected?

Every request is checked on the server: a customer receives only their own records, even if they put someone else's order number into the page address. Passwords are stored as hashes, and changes made by your staff go into an audit log.

Have you built anything similar?

The closest is the driver portal in my main project. It is a separate service where drivers enter trip reports and fuel readings from their phones, while the system checks permissions and keeps an audit log. A client portal is built on the same principles, only for your customers.

When will the portal be ready?

The estimate is 6–10 weeks. The portal can go live first with orders and statuses, and documents, repeat orders and the link to your systems can follow in later stages.

Contact

Tell me about your task — I'll reply with possible solutions. Or message me directly in the messenger you prefer.

Service: Client portal

All services in “Web apps, CRM and portals”