From quote to signed field report. One system.
blueGrape CRM connects the three lives of machine builders: the deal that brings in the order, the job that builds it, and the service that follows it for the next ten years. No moving data between three tools that do not talk to each other.
Nessuna carta di credito · Dedicated environment · Your data import included
- Dashboard
- Agenda
- Companies
- Deals
- Ticket
- Field work
- Jobs
- Items
- Assistente AI
The data exists. It is just in five different places.
Almost no technical company starts from scratch: most start with a sales CRM, an ERP, an Excel Gantt chart, a folder of scanned reports and the memory of two senior technicians. The cost is not buying one more tool: it is constantly translating between those worlds.
| Moment | How it works today | How it works with blueGrape |
|---|---|---|
| A request comes in | Email in the inbox of whoever answers first, or a phone call written down on a notepad. | It becomes a ticket with customer, machine and due date — from email, portal, phone or API. |
| A quote is prepared | A Word file copied from the last similar quote; revisions are identified by filename. | Quote generated from the deal, numbered revisions on the same document, PDF and customer price list applied. |
| The machine is built | An Excel Gantt chart updated for the first two weeks, then everyone works from memory. | One job per unit, phases from templates, dates planned backwards on working days and cascading progress. |
| The technician visits the customer | A signed paper field report that gets back to the office whenever it gets back. | Field report on the tablet with hours, spare parts and signature; if the contact is not there, remote signature by OTP code. |
| Invoicing | At month end someone reconstructs what was done, and something gets lost along the way. | "To invoice" filter with hours, travel and spare parts already detailed per service visit. |
| The same fault comes back | The team starts from scratch because nobody can find the ticket from two years ago. | Search by meaning across closed tickets, with an AI assistant that cites already solved cases. |
Everything you need, already connected
Non sono add-on da acquistare e integrare: sono parti dello stesso sistema. Il ticket conosce la macchina, la macchina conosce l'ordine, l'ordine conosce la trattativa.
Sales
Leads, deals, quotes, orders and invoices in one document chain.
Learn moreCalendar and tasks
Tasks, tickets and appointments in the same calendar, with reminders that start automatically.
Learn moreService and tickets
Guided creation, multiple assignment, customer chat, scheduling and feedback.
Learn moreField work and signature
Hours, spare parts, expenses and customer signature directly from the tablet — or remotely with an OTP code.
Learn moreProduction and jobs
One job per unit, Gantt phases from templates, binding dependencies and backward scheduling on working days.
Learn moreProduct catalog and installed base
Product catalog, installed items by customer, machine licenses and backups that arrive automatically.
Learn moreArtificial intelligence
Assistant on company data, semantic search, knowledge base, summaries and document reading.
Learn moreCommunications
Multichannel sending with retries, multilingual templates, emails that become tickets, push, Telegram and SMS.
Learn moreCustomer portal
Reserved area with the customer's machines, tickets, documentation and AI assistant.
Learn moreAdministration and security
Roles, groups, customizable master data, documents, logs, languages and scheduled maintenance.
Learn moreOne path, from first contact to year-ten maintenance
Every step inherits the previous one. No field is entered twice. See the full path with a real case →
Three things sales CRMs do not do
They know customers, not machines
Here every delivered unit is a real serial number: configuration, accessories, events, versioned backups, signed licenses and every ticket in its life. When the customer calls, you know what they have on site.
They stop at the customer's door
The service visit is closed on site: travel and work hours separated, spare parts installed, receipts read automatically and customer signature on the tablet — or remotely by OTP code if the contact is not there.
They do not understand production jobs
An order for three machines generates three jobs, each with product phases, dependencies and dates calculated backwards from delivery. Progress rolls up automatically to the order line.
AI that learns from your tickets, not from the web
The value is not having a chat inside the system: it is having a chat that knows your machines and the faults your company has already solved. When a senior technician retires, their experience stays in closed tickets — if someone can find it.
-
Search by meaning
"The machine stops after ten minutes" finds the ticket that mentioned spindle overheating.
-
Answers that cite records
Every assistant answer links back to the ticket or document it came from: verifiable, not magic.
-
Actions only after confirmation
The assistant can open a ticket for you, within your permissions and never without your approval.
-
Fully optional
If company policy does not allow sending text to external services, the CRM works fully with AI turned off.
In the installed base of Meccanica Vallese there are two units of the affected model. I found three similar closed cases:
- #4821 — same alarm after 8-12 minutes: spindle NTC sensor out of calibration. Solved by replacement.
- #5109 — clogged intake filter, gradual temperature rise.
- #5644 — auxiliary fan not driven because parameter P.412 was wrong after the update.
The knowledge base manual contains the calibration procedure in chapter 7.3. Recommended check order: filter, P.412 parameter, sensor.
Confirm request. I am about to create a ticket for Meccanica Vallese, serial number 20418, type "Blocking fault", high priority.
Three ways to use it, one product
Machine builders
From deal to installed serial number, without switching systems three times.
Industry scenarioService and technical support
Ticket queue, scheduling, field technicians and hours that actually reach the invoice.
Industry scenarioPlant contractors and installers
Installation jobs, installed base by site and scheduled maintenance.
Industry scenarioThe three questions everyone asks
"How long does it take to get started?"
For tickets and field service, a few days are enough: import companies and installed base from CSV and start. For the full production cycle, four to six weeks are typical because your product process needs to be modeled — work that then becomes company know-how.
"What about the data we already have?"
Companies, contacts, products and serial numbers are imported from Excel or CSV with column mapping, so your files do not need a special format. At termination, we deliver a full backup: the data is yours.
"Do I need to call you for every change?"
No, and we insist on that. Statuses, types, categories, groups and email templates are master data you edit from the interface, including translations. No supplier ticket, no cost, no release wait.
Try it on your data, not on a fake demo
We activate a dedicated environment, import your companies and installed base from CSV, and show you the system with your own customers inside. If after thirty days it is not convincing, we close it there.
No credit card. No automatic renewal. We reply within one business day — info@bluegrape.it