Customer-specific pricing
A separate price list is attached per customer and the right one loads automatically when a quote is generated.
Regions
Bitrix24 in Bursa
Most of our Bursa clients are manufacturers. In those businesses after-sales processes have to live inside the CRM as much as sales does; quality and sales need to see the same record.
At a glance
- Customer-specific pricing
- Sample and validation tracking
- Complaints and corrective action
- Order forecasting
- Visit and contact tracking
Typical problems for tier suppliers
With few customers a CRM looks unnecessary, but that is exactly where the risk sits: losing one customer leaves a large hole in revenue.
- Customer-specific price lists carried in people's heads
- Sample dispatch and approval tracked over email
- Complaints staying with the quality team and never reaching sales
- Order forecasts not kept systematically
- Customer visit notes staying in a notebook
- Noticing too late that a customer has stopped ordering
Scope of Bursa implementations
Where the effort sits for manufacturers in a supplier position:
Sample and validation tracking
Sample dispatch, customer approval and series production release are tracked as separate stages.
Complaints and corrective action
A complaint opens as a record, the quality team receives a task, and sales sees the closure.
Order forecasting
Expected order volumes per customer are recorded and made visible for production planning.
Visit and contact tracking
Customer visits are logged from the mobile app, making it visible who was visited and when.
Dormant customer alerts
Customers with no orders or contact for a defined period are flagged automatically.
Quality and sales looking at the same record
In manufacturing, particularly in a supplier position, how a complaint is handled directly affects the next order. Even so, in most firms the complaint lives in the quality team's own file and the sales rep visits the customer unaware there is an open issue. Opening the complaint in the CRM as a task attached to the customer record removes that gap: the rep sees open complaints before a visit, and the quality team knows where the commercial relationship stands.
- Complaints open against the customer record
- Tasks and deadlines assigned to the quality team
- Root cause and corrective action kept on the same record
- Complaint history reportable per customer
Few customers, high risk
In a company that earns half its revenue from three customers, the CRM's job is not finding new customers but not losing the ones you have. That is why Bursa implementations lean on early warning: customers whose order frequency is falling, whose contact gap is widening, or whose complaints stay open too long are flagged automatically and escalated to management. The problem becomes visible before it grows.
- Automatic detection of falling order frequency
- Alerts for customers not visited within a defined period
- Escalation when an open complaint passes a time threshold
- Revenue share and dependency reporting per customer
Pipeline stages in supplier sales
What differs from a standard pipeline is that sample and validation become stages in their own right.
| Stage | What happens | Typical duration |
|---|---|---|
| First contact | Enquiry received, drawing or specification shared | 1–2 weeks |
| Feasibility | Manufacturability and cost assessment | 2–4 weeks |
| Quotation | Price and lead time issued, revisions run | 2–6 weeks |
| Sample | Sample produced and shipped | 3–8 weeks |
| Validation | Customer approval and series production release | 4–12 weeks |
| Series production | Order flow begins and becomes recurring | Ongoing |
How would this work in your process?
In a free 30-minute call we listen to your workflow and map out how this would run in your company.
How we work in Bursa
We start by hearing sales, quality and production planning together.
- 01
Mapping the current flow
The path from enquiry to series production is mapped, including sample and validation steps.
- 02
Pipeline and pricing structure
Stages and customer-specific price lists are built, preserving your existing quote format.
- 03
Quality connection
The complaint and corrective action flow is connected to the CRM and the quality team is brought into the system.
- 04
Early warning setup
Alert rules are defined on order frequency, contact gaps and open complaint duration.
What you end up with
- A sales pipeline including sample and validation stages
- Customer-specific price lists and quote templates
- A complaint and corrective action tracking flow
- Order forecasting visible to production planning
- Early warning rules for dormant customers
- Revenue share and dependency reporting per customer
- Separate training sessions for field and quality teams
Features
Related features
The modules we most often roll out alongside this one; they reinforce each other in the same setup.
Sales Pipeline
When the pipeline is unclear, nobody knows which deals are moving and which are stuck. We design your stages around your real sales process and make the next step visible on every card.
Service Requests
Whichever channel a service request arrives through, it should land in the same queue with an owner and a deadline. That is exactly how we configure the Bitrix24 Contact Center.
Workflows
When approvals run over email and chat, nobody knows where a request is sitting. We turn your internal processes into flows with defined steps, owners and deadlines.
Team Performance
A performance conversation should start from data both sides accept. We configure Bitrix24's task reports, workload charts and efficiency scores around the way your company actually works.
Other cities
Istanbul
Most of our Istanbul clients are in health tourism. What sets the city apart is volume: hundreds of leads a day, shift-based consultant teams and the most expensive advertising competition in Turkey.
Antalya
Most of our work in Antalya is health tourism and hospitality. Both share the same pattern: inbound demand from abroad, in several languages, mostly over WhatsApp.
Izmir
Health tourism dominates our work in Izmir too. What differs from Istanbul is scale: fewer leads, but a longer and deeper evaluation process per patient.
Frequently Asked Questions
We only have 15 customers. Do we need a CRM?
With few customers the CRM's job is not keeping a list but protecting the relationship. If most of your revenue comes from a handful of accounts, one of them quietly drifting away is a serious risk. That is why our Bursa builds concentrate on early warning reports and complaint tracking.
Our quality team uses separate software. Will they clash?
No. Your quality management system can stay in place; we keep the customer-facing complaint record and its closure in the CRM so sales can see it too. An API connection between the two systems can be built if you want one.
Can customer-specific prices stay confidential?
Yes. Price lists are visible by permission, so you define which user sees which customer's pricing. Field staff see their own accounts and not others.
Can we track sample processes in the system?
Yes, and we build it as a distinct stage of the pipeline. Sample request, production, dispatch and customer approval open as tasks, and the time each step spends waiting is measured. That makes it visible where validation is getting stuck.
Let's configure this around your business
Book a free intro call and we'll walk through your process and show which settings fit you.