10 / Services
CRM and internal systems
A pipeline, tasks, a warehouse system, or your own workspace, instead of a set of scattered spreadsheets.
For departments where a standard box does not follow their steps, and their own system is not built yet.
CRM
Pipeline
01
New
02
In progress
03
Closed
Status
In progress
Who
Department
History
Feed
What it consists of
What goes into the system
- 01
The path of a request
We draw how a deal or a request moves through departments: who creates it, who carries it, who closes it.
- Statuses that people can tell apart
- Required fields on the transition
- Where a request must not land
- 02
Record
A record holds only what people open while working. We do not add dozens of empty fields “just in case.”
- Client, amount or site, timing
- A history of contacts
- The file beside the status
- 03
Roles
Sales, the warehouse, and the lead see different things. Someone else’s queue is not used as a shared chat.
- Own requests, and shared ones
- Who changes a price or a status
- What is hidden from the role
- 04
Syncs
Email, telephony, the warehouse, or the storefront are connected when the record would otherwise still be filled in by hand.
- Where a new request comes from
- What goes into the records
- A log, if the sync did not go through
- 05
Old records
We move what people work with now. A five-year-old archive does not come along in the first week.
- Which fields are required for the move
- What we match after the load
- The first week alongside the people who run the day
What we do
- 01How a deal or a request moves through the departments
- 02Setting up a boxed product, or building your own system
- 03Syncs with email, telephony, and the warehouse
- 04Moving the old records
- 05Training for the people who will run the day
How we proceed
- 01The path of a request
- 02Setup
- 03Syncs
- 04Move
- 05The first week alongside
Stack
- CRM
- API
- PostgreSQL
- Exports
A guide for the timing
A basic sales system takes about a month. Custom entities and roles take longer.
Outcome
A request has one status, one owner, and a history that does not have to be searched for in the correspondence.
What usually comes later
Custom entities “for every department,” complex permissions, and a mobile warehouse round come after the main request path already runs in one record.