CRM / ERP development
CRM and ERP for the process the company already has
A ready-made CRM is a good fit while your sales resemble someone else's template. Your own system is needed when you have your own stages, roles, documents, and exceptions. I build CRMs, records systems, and separate modules so an employee does the work in one window, not in three spreadsheets and a chat.
What it takes on
- 01
Stop losing requests
Every inquiry has an owner, a status, and a next step. Correspondence is no longer the only record.
- 02
Repeat the real process
Stages are named as they are in your work, including the exceptions, not only “new / won”.
- 03
Separate the permissions
A manager, a supervisor, and a neighboring department see different things. Other people's amounts and documents do not sit in a shared file.
- 04
Bring the records together
Sales, fulfillment, invoices, or stock stop living in unrelated spreadsheets.
Who it is for
Departments that have outgrown a spreadsheet
The file can no longer be given to a new person. It hides rules that are written down nowhere.
Companies with an unusual cycle
Their own approvals, objects, site visits, several legal entities, or a long fulfillment after payment.
A business that has outgrown the package
Every change to the package costs as much as a project, and the report is still assembled by hand.
If the sales department is typical and amoCRM or Bitrix24 suits you, there is no need to write a core from scratch. It is more honest to set up the packaged system, or to connect it to the site.
What can be built
Sales CRM
A pipeline, a card, tasks, reasons for refusal, and responsibility.
ERP system
Company operations: orders, resources, documents, fulfillment statuses.
Staff and shifts
Who does what, where the bottleneck is, and which data a supervisor needs.
Finance modules
Invoices, payments, and debts linked to the operation, with no promise to replace accounting.
Analytics
A summary of the statuses you actually use, not a set of random charts.
Integrations
The site, email, a messenger, payment, an accounting system.
How it looks in practice
- 01
Requests from the site dissolve in email
The form writes to a shared inbox. Some letters stay unanswered. A supervisor hears about it from the client. The CRM records the source, the owner, and the deadline of the next action.
- 02
The deal is longer than the package's pipeline
After “won”, production, purchasing, or a site visit begins. You need linked statuses, not a second file called “in progress”.
- 03
Several departments look at different spreadsheets
Sales, fulfillment, and finance argue about which figure is right. A shared system leaves one source for the operation.
How development goes
- 01
The process as it is
Roles, stages, exceptions, and the places where data is lost.
- 02
The first release
What goes into the launch, and what stays outside on purpose.
- 03
Data and permissions
Entities, statuses, and who may change what.
- 04
Workplaces
Screens for roles, not one table for everyone.
- 05
Build and a walkthrough
Scenarios on your examples, including a refusal and a return.
- 06
Launch
Access, an import if it is needed, and short guides by role.
Technologies
- TypeScript
- React
- Next.js
- PostgreSQL
- REST API
- Roles and an action log
You receive a working system with statuses and permissions, the source code, a description of the roles, and a short map of how to run a deal or an operation.
Demonstrations on this topic
Request console
A workplace where a request is not lost between email and a spreadsheet.
Request board
A request lives on the board, not in the correspondence between the measurer and the manager.
Cash desk and payments
Payment, the cash desk, and debt look at one request, not at three different spreadsheets.
Field measure
On site, a person closes the job on the phone. The office sees the same status.
Shift calendar
The shift is visible as a day: who is going out, who is calling back, and what is already closed.
How to commission it
A project with a clear scope
We agree what goes into the next batch, and we hand over that scope, not an endless list of ideas.
MVP
We build one scenario you can already work in, or use to test demand. The rest is not thrown away. It goes into the next batch.
Support
After launch, there is someone to give a bug, a question, or a new branch of the process.
Questions
When is a custom CRM the wrong choice?
When the process lives calmly in a ready-made system and its limits do not break your work. Custom development pays for unique rules, not for a wish to “have our own”.
Will you move the old deals?
Yes, as a separate stage. First we agree which fields are required, and what to do with broken rows. A dirty import “as is” carries the chaos into the new system.
Can the site and a messenger be connected?
Yes. A request from the site, or a conversation, can create a card. The integration is designed as part of the process: who answers, and what counts as a duplicate.
Will this replace 1C or the accounting department?
Not necessarily, and often it should not. An operations system can exchange documents and statuses with the accounting system. The boundary is better drawn before development, not after.
Will staff actually keep the system up to date?
Only if it is shorter than the current correspondence. That is why the first release holds the daily scenario, not every report that is opened once a quarter.
Related reading
Neighbouring directions
- Automation
The process moves between systems on its own. A person steps in for the exceptions.
- Services
A working scenario in the browser: an account, data, roles, and a next step.
- Support
A clear queue of changes in a live product.