Customer portal
development
The initial conversation is free. We will review customer tasks and suggest the scope of the first release.
What customers can do themselves
The scope follows your processes. You can start with one use case and expand as customers use the service.
Place and repeat orders
Purchase history, repeat ordering and a cart with individual prices. For wholesale purchasing, ordering by product code or uploading a spreadsheet.
Get invoices and documents
Order and shipment documents in one place. We establish which files come from 1C or another system and which need to be generated by the website.
Follow progress
Order, shipment and support request statuses. Customers can see what is happening and ask a question in the context of the relevant order.
Work as a company
Multiple employees, roles and permissions. We agree on who can place orders, view documents and change company details.
How we build a portal
A usable screen is only part of the work. The source of data and what follows each action matter just as much.
Define the initial release
We review common customer requests and account manager tasks. Together we choose the use cases, data sources and scope of the first version.
Design the interface
We show the path from signing in to ordering or receiving a document. We review desktop and mobile flows before the main development begins.
Connect 1C and CRM
We agree on exchanging orders, prices, stock, statuses and documents. Each data set gets a defined source and update rules.
Check permissions and launch
We check roles, isolation between customer accounts, exchange errors and core actions. After launch we collect feedback and plan further improvements.
Questions before you start
You do not have to rebuild the entire website or move every process into the portal at once.
Can a portal be added to an existing website?
Yes. First we review the website, authentication and data exchange. Then we recommend an embedded portal or a separate application connected to the site.
How does a customer portal differ from a B2B platform?
A customer portal handles a specific customer account after sign-in. A B2B platform may also include a catalog, company registration, negotiation of terms and other processes. The customer portal is often one part of it.
Will we need a separate mobile app?
For orders, documents and statuses, a responsive portal in a mobile browser is often enough. We discuss a separate application if your use cases require one.
How do we start the conversation?
Send us your website URL and examples of tasks that customers currently handle through an account manager. Tell us where prices, orders and documents are stored and which systems you use.
From signing in to completing a task
The customer signs in
Sees their company data, available sections and business terms.
Completes a task
Places an order, downloads a document or submits a support request.
Systems exchange data
The order reaches the accounting system and its status returns to the portal through the agreed data flow.
Pricing
We estimate the first release based on customer workflows and the integrations you need.
Development
From RUB 2,000
/ hour
The rate depends on the specialist and the complexity of the task.
Hourly development (Time & Material) starts at 20 hours per month.
Cost depends on portal features and integrations. We help define the first release and estimate it by phase.
Get an estimateThe initial discussion and preliminary estimate are free.
How we calculate the cost
Prices are in Russian rubles, excluding VAT. We agree the final price and scope before work begins.
What do your customers repeatedly ask an account manager for?
Describe a few recurring tasks. We will discuss which ones belong in a customer portal and how to start the first version.
Discuss your customer portal