3Dees Industries Manages Hundreds of Printing Jobs With CRM

3Dees Industries is a Czech manufacturer and reseller of industrial 3D printers, producing parts for automotive, aerospace, and defense customers. Together with its sister company Paarts Additive and branches in Slovakia, Ukraine, and Poland, the group generates over $10M USD in annual revenue with roughly 22–25 employees spread across six locations in Europe. How do you manage sales and custom manufacturing jobs at scale across four markets?

Running a business like this isn’t simple. People rarely see each other in person. Every location handles a different piece of the sales or production process, and information has to flow reliably without bottlenecks. That’s exactly what pushed the team to implement a CRM.

Two Different Sales Processes Under One Roof

3Dees operates in two fundamentally different modes, and eWay-CRM needs to handle both:
 
1. Selling Industrial 3D Printers

This is classic B2B enterprise sales with a long cycle. A single printer can run from tens of thousands to over a million dollars, so you’re moving a handful of units per year. Each opportunity needs its own deal history, communication log, and visibility into who’s making the call on the customer’s side. eWay-CRM handles this as a standard pipeline — reps track deal stages, schedule follow-ups, and share context across the team without flooding each other’s inboxes.

2. Custom Print Jobs (Job-Shop Manufacturing)

Here, the situation is completely different. The company runs hundreds of projects a year, each with its own customer, specs, deadline, and invoice. Orders come in continuously. Production runs in Ostrava. The back office sits in Prague. Without a system to automate the information flow, things will start getting missed, delayed, and lost.
 

 

The Core Feature: Automating the Job Workflow

The backbone of the eWay-CRM deployment at 3Dees is the integration between the CRM and the production system. The two platforms exchange data via JSON files processed by Make (formerly Integromat). Here’s how it works:
 
Automated Custom Print Job Workflow

• Customer places a print order — a new job is created in the external production system.
• Make pulls the relevant data into eWay-CRM and creates a matching record.
• Once production wraps up, the production system logs the status change.
• eWay-CRM picks up that change and automatically notifies the right person in back office.
• Back office gets a notification with instructions to issue the invoice — no manual chasing required.

 
The result is a closed loop where nobody has to actively track every job. The information comes to you — you don’t go hunting for it.

Why not connect the two systems directly, without a middleware layer? Intentional choice. A direct integration would create a hard dependency — if 3Dees ever decides to swap out the production system (something actively being considered at the time of this interview), they’d lose the entire integration investment. Using Make as a neutral middleware eliminates that lock-in.

eWay-CRM as a Flexible, Configurable Tool

One of the most common CRM implementation failures is buying a system and expecting it to run itself. At 3Dees, they take a different approach — actively tweaking the system, testing new configurations, and working directly with eWay-CRM developers to build out specific features.
 

 

One concrete example: access permissions. As the company grew and headcount increased across locations, it became clear that the original setup — where almost everyone could see almost everything — wasn’t sustainable, especially given their customer base. 3Dees serves defense industry clients where data security isn’t optional.

Rolling out granular permissions was organizationally heavy (changing one thing tends to cascade into others), but today the team knows exactly who has access to what — and when someone leaves, there’s no risk of sensitive data walking out the door.
 

CRM as a Management Tool and Cultural Accountability Layer

eWay-CRM plays one more role at 3Dees that’s easy to overlook: it’s a mirror of actual workload. Leadership can quickly check whether what someone says they’re working on lines up with what’s actually logged in the system.
 

 
That transparency helps managers, but it also helps the reps themselves. An account exec coming back from vacation or picking up a deal mid-stream doesn’t have to reconstruct anything from email chains — it’s all in the deal history. Handoffs stop depending on people’s memory and become part of the system.

Data Ecosystem and the Role of AI

Even though implementation is still recent, Faschingbauer’s expectations are specific and well structured. They fall into three main areas:
3Dees is gradually moving deeper into the Microsoft ecosystem — Teams, SharePoint, Copilot. The main driver is security: defense sector customers won’t allow their data to leave a controlled environment.

One of the next planned steps is integrating eWay-CRM with Microsoft Copilot Studio, which would let employees query CRM data in plain English. The goal is to put analysis and reporting within reach of people who aren’t data analysts.

Ladislav also uses AI tools in his day-to-day work with eWay-CRM — specifically calling out Claude by Anthropic as a go-to for dialing in filters and conditional views inside the system.
 
Key Takeaways From eWay-CRM at 3Dees Industries

• CRM needs to handle multiple processes at once — at 3Dees that means enterprise sales alongside custom job-shop manufacturing with hundreds of orders a year.
• Automation via Make (JSON + API) eliminates manual work and connects CRM to the production system without creating a hard dependency.
• Customization is a necessity, not a nice-to-have — the team actively collaborates with eWay-CRM developers to build out their specific workflows.
• Access permissions matter especially when your customers come from sensitive sectors like defense.
• CRM as a management tool — logged activity helps run a distributed team without constant check-in meetings.
• AI and the Microsoft ecosystem are the next step — the company is planning Copilot Studio integration for conversational access to CRM data.