Internal CRM Web App Development
Budget: €10 – €500 EUR
Got it — you’re **100% right**.
Long, over-structured job posts **signal complexity → higher price → worse candidates**.
What you want is **clarity without scaring people**.
Below is a **short, calm, textbook-style job description** that:
* Sounds reasonable (not “big system”)
* Explains context without noise
* Leaves room for discussion
* Attracts pragmatic builders, not CRM sellers
This is the version you should actually publish.
---
## Job Title
**Internal Web App for Machinery Sales & Service (Simple CRM)**
---
## Job Description
We are looking for a freelancer to build a **simple internal web application** for our machinery department.
The goal of this system is to bring together **pre-sales, sales, and post-sales service** for machinery in one place, in a way that is **easy to use and easy to expand later**. This is not meant to be a full CRM like HubSpot or Salesforce, but a **custom internal tool** designed around how a machinery business actually works.
The system will be used by salespeople, technicians, and management. Most users are not highly technical, so the focus must be on **clarity, speed, and simplicity**, not on many features.
---
## What the System Is About
Before selling a machine, our sales team spends time consulting customers, understanding their needs, and explaining whether a machine makes sense for them. After the sale, the relationship continues for many years through **consumables (ink), spare parts, training, and service visits**.
This application should support the **full lifecycle of a machine**, from first contact with a lead, through consulting and sale, and then through long-term service and consumable sales.
---
## Main Functional Ideas
The system should allow us to:
* Store **leads** and gradually turn them into clients, keeping the full history.
* Maintain a **client profile** that shows machines owned, past purchases, service history, and notes.
* Treat each sold machine as a long-term record with its own history (installation, warranty, service, parts, consumables).
* Import past sales data (machines, inks, spare parts) from our ERP system using Excel/CSV files. Data may be incomplete or messy, and the system must handle this without errors.
* Log basic sales and service activities (calls, visits, installations, maintenance).
* Generate **simple alerts**, for example when a client stops buying ink for a long time, a machine has not been serviced, or a warranty is about to end.
---
## Pre-Sales Value Calculator
As part of the pre-sales process, we want a **simple value calculation tool** inside the system.
This tool should help salespeople show customers, in numbers, what value a machine can bring.
The idea is that the salesperson selects a machine, enters a few customer estimates (such as approximate usage), and the system shows estimated benefits such as revenue, costs, savings, or payback time. This does not need to be perfectly accurate; it needs to be **clear and convincing** and saved as part of the lead or client history.
---
## Users and Access
Different users should see different things:
* Management/admin users can see everything, including costs and margins.
* Sales users can see prices, offers, and client history, but not costs or margins.
* Service users can see machines and service history, but not financial data.
This must be enforced in the system, not only visually.
---
## Technical Notes
The application should be web-based and secure, with login and basic role management.
The technology stack is flexible and can be proposed by the freelancer. Experience with Firebase/Firestore or similar setups is a plus, but not required.
The system should be built in a way that allows future improvements, such as better ERP integration or additional automation, without rebuilding everything.
---
## How We Will Work
We prefer a simple, staged approach:
1. Agree on structure and screen flow first
2. Build the core system
3. Add imports, alerts, and calculator
4. Test, deploy, and document
Short weekly demos are preferred to long meetings.
---
## What We Are Looking For
We are looking for someone who:
* Has experience building internal tools or CRMs
* Is comfortable working with imperfect data
* Understands business processes, not only code
* Can keep systems simple and usable
Long, over-structured job posts **signal complexity → higher price → worse candidates**.
What you want is **clarity without scaring people**.
Below is a **short, calm, textbook-style job description** that:
* Sounds reasonable (not “big system”)
* Explains context without noise
* Leaves room for discussion
* Attracts pragmatic builders, not CRM sellers
This is the version you should actually publish.
---
## Job Title
**Internal Web App for Machinery Sales & Service (Simple CRM)**
---
## Job Description
We are looking for a freelancer to build a **simple internal web application** for our machinery department.
The goal of this system is to bring together **pre-sales, sales, and post-sales service** for machinery in one place, in a way that is **easy to use and easy to expand later**. This is not meant to be a full CRM like HubSpot or Salesforce, but a **custom internal tool** designed around how a machinery business actually works.
The system will be used by salespeople, technicians, and management. Most users are not highly technical, so the focus must be on **clarity, speed, and simplicity**, not on many features.
---
## What the System Is About
Before selling a machine, our sales team spends time consulting customers, understanding their needs, and explaining whether a machine makes sense for them. After the sale, the relationship continues for many years through **consumables (ink), spare parts, training, and service visits**.
This application should support the **full lifecycle of a machine**, from first contact with a lead, through consulting and sale, and then through long-term service and consumable sales.
---
## Main Functional Ideas
The system should allow us to:
* Store **leads** and gradually turn them into clients, keeping the full history.
* Maintain a **client profile** that shows machines owned, past purchases, service history, and notes.
* Treat each sold machine as a long-term record with its own history (installation, warranty, service, parts, consumables).
* Import past sales data (machines, inks, spare parts) from our ERP system using Excel/CSV files. Data may be incomplete or messy, and the system must handle this without errors.
* Log basic sales and service activities (calls, visits, installations, maintenance).
* Generate **simple alerts**, for example when a client stops buying ink for a long time, a machine has not been serviced, or a warranty is about to end.
---
## Pre-Sales Value Calculator
As part of the pre-sales process, we want a **simple value calculation tool** inside the system.
This tool should help salespeople show customers, in numbers, what value a machine can bring.
The idea is that the salesperson selects a machine, enters a few customer estimates (such as approximate usage), and the system shows estimated benefits such as revenue, costs, savings, or payback time. This does not need to be perfectly accurate; it needs to be **clear and convincing** and saved as part of the lead or client history.
---
## Users and Access
Different users should see different things:
* Management/admin users can see everything, including costs and margins.
* Sales users can see prices, offers, and client history, but not costs or margins.
* Service users can see machines and service history, but not financial data.
This must be enforced in the system, not only visually.
---
## Technical Notes
The application should be web-based and secure, with login and basic role management.
The technology stack is flexible and can be proposed by the freelancer. Experience with Firebase/Firestore or similar setups is a plus, but not required.
The system should be built in a way that allows future improvements, such as better ERP integration or additional automation, without rebuilding everything.
---
## How We Will Work
We prefer a simple, staged approach:
1. Agree on structure and screen flow first
2. Build the core system
3. Add imports, alerts, and calculator
4. Test, deploy, and document
Short weekly demos are preferred to long meetings.
---
## What We Are Looking For
We are looking for someone who:
* Has experience building internal tools or CRMs
* Is comfortable working with imperfect data
* Understands business processes, not only code
* Can keep systems simple and usable
Related categories:
User Interface / IA
CRM
Backend Development
Frontend Development
Database Management
API Development