Every role gets its own account
and its own permissions
A customer sees the catalog and their orders. A manager handles requests. A partner publishes listings and waits for moderation. A dealer sees their prices and stock. One platform with roles, not four websites and a messenger thread.
Three role-based platforms already in production
Different niches, one mechanic: every role has its own account and its own view.
Vsedomatut: buyer, manager, partner
A buyer browses listings and sends requests. A manager works them through Bitrix24, a CRM. A partner developer publishes listings, passes moderation, and sees analytics across four conversions.
Capless: an account with a balance and an operator
A customer sees the balance, rewards, and order history and talks to an AI assistant. An operator picks the chat up from Telegram and drives the order to completion. All money logic lives in the database.
Dealer portal: group prices and reorders from a price list
A dealer signs in, sees their prices and stock, and places a repeat order from the price list without calling a manager. Stock and prices come from your inventory system. Built for your catalog after a review.
What a platform with accounts is made of
The exact set for your model comes out of the review. Below is what almost always ends up in it.
From roles on paper to a platform in production
Role review
We list the roles, what each one sees and does, and where the data comes from. You get the scope, timeline, and price.
A build on your data
Accounts, moderation, and requests on your data. You test real scenarios, not mockups.
Launch and handover
We migrate data, connect integrations, and hand the code and documentation to your team.
The price is fixed before we start
Reference points below. The final figure depends on the number of roles, integrations, and data volume, and we name it after the review, not mid-project.
Customer and team. A catalog or registry, requests, a customer account, an admin panel, one integration. For a B2B portal, a dealer portal, or a platform for a single client.
- Customer account: orders, requests, documents, history.
- Admin panel for the team: users, content, statuses.
- One integration: your CRM, accounting, or ERP system.
- Handover of code, server, and documentation.
- No partner accounts or moderation of third-party content.
- Large data migrations are estimated after the review.
- Scope is fixed at the start so the timeline and budget hold.
Three or more roles, partner accounts, a moderation queue, partner analytics, several integrations. A marketplace, an aggregator, a platform with external suppliers.
- Accounts for customers, partners, and the team with role-based permissions.
- Moderation of partner content with decision history.
- Partner analytics and request routing.
- Integrations with CRM, inventory, payments, and delivery.
- The total depends on the number of roles, integrations, and non-standard scenarios.
- Payment and money flows go through a separate acceptance.
- The final price is named after the role review.
After handover: support from $200 a month (no development) or $900 a month (about 30 hours of development), with a reply within one business day.
Payment in stages, 12-month warranty. Terms in detail
Frequently asked questions
Short answers to what people ask before the start.
Describe the roles, and we will map the platform
Who will sign in and what they should see there. We will come back with the scope, timeline, and price within one business day.
Your platform review
Free. Roles, data, integrations, and the project scope.