When a website needs to become a platform: signs you've outgrown a landing page
Personal accounts, roles, payments, reports: how to tell that a business needs a platform, and what that changes in development and price.
A landing page stops coping without you noticing. First a spreadsheet appears, where requests are "temporarily" stored. Then a chat thread where the order was "actually" agreed. Then an employee who spends half a day moving data from one system to another. The website still works — but the business no longer lives on the site, it lives around it.
Signs you've outgrown a landing page
- Orders, requests and statuses live in spreadsheets or in chats — and no one can say how many deals are currently "in progress".
- Clients ask for a personal account: "where can I see the status, invoices, history".
- The report for management is assembled by hand: export, reconciliation, formulas.
- There is more than one role in the process: client, manager, contractor, administrator — and each needs their own permissions and their own view of the data.
- There are operations repeated every day word for word: take a request, issue an invoice, remind about payment.
- The volume of requests grows, but the team does not: people physically can't keep processing everything by hand.
- Payments, documents and notifications happen outside the system: bank details in an email, an invoice in a chat, a signed act in a folder.
Three or four matching points are already enough to count as a platform rather than "a bigger website". One or two are usually cured by automation without rewriting everything.
What changes in development
- A database and migrations appear: data stops being "somewhere in files", and the schema can change without redoing everything.
- Roles and permissions are designed up front — adding them "later" costs more than doing it right away.
- Without automated tests and a release pipeline, a platform becomes scary to change: every update risks taking down someone else's data.
- Monitoring becomes necessary: the platform deals with money and requests, and you can't learn about a failure from a client.
- Requirements for personal data get stricter: access separation, an action log, channel encryption.
How we do it
A platform is not written in one go "from a big spec". We start with the smallest useful piece — for example, a personal account with requests and statuses — and expand it once we see it's actually being used. The data schema and roles, however, are designed up front, so growth doesn't hit the foundation.
How our case platform docase.ru is built
What it costs and where to start
A platform is quoted per estimate: the price depends on the number of roles, integrations and scenarios, not on the number of pages. The first step is a short process review: which operations repeat, who takes part, where time is currently lost. After it, you can see what to do first and what can wait.
If you're unsure whether you need a platform or automation is enough — describe the task in two sentences. We'll answer honestly, including if your case can be solved more cheaply.
Facing something similar?
Tell us what happens today: where time gets lost and which operations repeat. We will suggest what to automate first.