Case study
Chemie en farma
One CRM for everything before the order confirmation
At an international distributor of specialty chemicals, everything after the order confirmation ran smoothly in Business Central. Everything before it lived in mailboxes and spreadsheets. In four months, we built a CRM on the Power Platform that connects directly to Business Central.

On this page
▾
Planning a project like this?
Tell us what you're running into today, and we'll explore what's possible together.
Book an intro callThe case at a glance
| Client | Transmare Chemie, headquartered in the Port of Antwerp |
| Industry | Specialty chemicals distribution: pharma, food, feed, personal care, coatings, plastics, oil and gas |
| Profile | More than 85 employees worldwide, twelve offices from Hamburg and Singapore to Guatemala and Ivory Coast |
| Starting point | Business Central as ERP, Power BI for reporting, no system for the pre-sales process |
| Solution | Model-driven CRM on the Microsoft Power Platform, integrated with Business Central |
| Modules | Relationship management, leads and opportunities, samples with inventory management, visit reports, tasks, mobile and offline |
| Timeline | Kickoff in September 2025, go-live in January 2026 |
| Next steps | Expansion phase in 2026, Power BI reporting in preparation |
Transmare Chemie distributes specialty chemicals from leading manufacturers worldwide. From its headquarters in the Port of Antwerp and offices in Hamburg, Singapore, South Africa, Morocco, Guatemala, and Uruguay, among others, the group serves customers in pharma, food, feed, personal care, coatings, plastics, and oil and gas, with strong expertise in emerging markets.
In specialty chemicals, it all comes down to knowledge: knowing which raw material fits which application, and which manufacturer can supply it. A customer looks for a product with specific properties, a trader matches supply and demand, requests a sample, keeps track of the test results, and negotiates. Only then does an order follow.
That process often takes months and spans multiple countries and business units. And none of it was recorded anywhere. An order in Business Central was the end of a story whose beginning nobody could trace.
During the analysis phase, three issues kept coming up.
Samples were impossible to find. Here, samples aren't a detail but the heart of the sales process: small quantities sent to a customer for testing. Request, shipment, tracking number, batch number, customer feedback, approval or rejection. All of that was tracked in an Excel file floating around on a shared drive. If you wanted to know six months later why a test had been rejected, you had to go ask a colleague.
Reporting to manufacturers was manual work. Manufacturers want regular updates on where samples of their products ended up and what their status is. That overview didn't exist. It had to be pieced together by hand every single time. As the analysis showed, this was one of the main reasons to start a CRM project in the first place.
The sample inventory was never quite right. The physical stock of samples at the office was updated by hand in a spreadsheet two days a week. Slow, expensive, and usually just out of date at the moment a trader wanted to know if something was still on the shelf.
On top of that, the classic picture: prospecting knowledge stuck in individual mailboxes, visit reports in Word, and no visibility into the pipeline per business unit or per market.
The question behind the question. Transmare didn't ask for a second system alongside Business Central. They asked for the missing piece: everything before the order confirmation, in the same Microsoft environment. That distinction makes all the difference. If you put a standalone CRM next to your ERP, you end up with two customer databases that drift apart, two product lists, and two versions of the truth. So the assignment wasn't “build a CRM.” It was: make sure a trader can work in one environment, where customers, suppliers, contacts, and products are simply what Business Central says they are.
Why not an off-the-shelf CRM package. Transmare had already looked at Dynamics 365 Sales. Functionally, it's a strong package, but the price was out of proportion to what they would actually use it for. They didn't need advanced sales automation or a marketing module. They needed structure.
So we proposed building the CRM as a model-driven app on the Power Platform. Technically, that's the same foundation as Dynamics 365 Sales: the same Dataverse database, the same accounts, contacts, and activities, the same look and feel, and the same Outlook integration. You just pay for the parts you use and not for the rest. You'll find more on that trade-off on our page about building a full-featured CRM with Power Apps.
The project itself followed a pragmatic, scrum-light approach. No months of analysis followed by a big bang, but a short analysis phase and then a fixed weekly check-in.
Analysis first, and thorough. In a series of working sessions, we documented the processes: relationship management, the path from lead to opportunity, the opportunity stages, sample management, visit reports, and the security model. Each part got a description with a data model underneath. That documentation evolved along with the project and is still the go-to reference today.
A demo every week. Weekly stand-ups where we showed what had been built that week and the client could respond right away. That sounds obvious, but it's exactly what keeps you from delivering something after three months that worked on paper but not in practice. Small decisions, from required fields to how lists are filtered, were checked within the week with the people who have to work with them every day. The system grew along with the way people actually work, instead of drifting away from it.
Testing with real users, then go-live. A broader group of colleagues from different departments tested the system, deliberately including people who had never worked with it before. We worked through their feedback point by point. Then came the migration to production over a single weekend, with a user guide in English and hypercare afterward.
Working with the existing partners. Transmare's Business Central environment is managed by Dynamate. An integration like this stands or falls with coordination between both sides, and that collaboration went smoothly: direct communication, quick answers, and a shared interest in a clean data flow. That's less of a given than it sounds, and it made this project move faster.
Relationship management with Business Central as the source. Customers, suppliers, contacts, and products come from Business Central. Fields that come from there are read-only in the CRM, so no second version of the truth can creep in. Whatever the CRM adds itself, such as extra contacts, additional addresses, and sales notes, stays editable, of course. Prospects who aren't customers yet are created in the CRM, with parent accounts for group structures and segmentation by industry, region, and business unit.
Leads and opportunities in fixed stages. Logging a lead deliberately takes only a few fields, so capturing knowledge never becomes a chore. Once things get concrete, the opportunity moves through fixed stages, from inquiry to offer and sample to negotiation, asking at each stage only for the information that's truly needed at that point. No more than that, because otherwise nobody fills it in.
Samples from request to feedback. Request, preparation, shipment with tracking and batch number, and then the customer's feedback with the reason for approval or rejection. Everything is linked to the manufacturer, so the report that used to be manual work is now just a filter. The physical inventory is tied in too: a shipped sample is deducted from stock automatically, and deliveries and corrections are logged with batch, expiration date, and the certificate of analysis attached. For samples requested directly from a manufacturer and forwarded the same day, there's a separate route that doesn't touch inventory.
Visit reports, email, and tasks. Customer visits are logged on the right account, with calendar sync to Outlook. Emails land on the right opportunity or account, including follow-up emails in the same thread. When someone is assigned a task, they get a message with a direct link to the record, plus a reminder if it's still open after a week.
Mobile and offline. Traders are often visiting customers in regions with poor connectivity. Accounts and contacts are available offline on their phones, along with opportunities and samples within their own business unit. As soon as they're back online, everything syncs back automatically.
Security that filters instead of blocks. The group consists of several legal entities. Everyone can see everything, because transparency is an advantage here, but editing happens within your own structure. For opportunities, that was later relaxed on purpose, because in practice colleagues work on the same deals together.
The Business Central integration. This is the piece that makes everything else work. Seven types of data flow automatically from Business Central to the CRM: customers, suppliers, contacts, products, industry codes, currencies, and salespeople. In one direction only, because the CRM shouldn't clutter the ERP with prospects and test samples that aren't official products yet.
The practical gains are in the details. A customer's currency comes along, so an opportunity for a customer outside the eurozone is in the right currency from the start and can still be reported on a consolidated basis. The industry code from the ERP flows through to the opportunity. And product variants with different packaging are merged into one product, because a trader wants to choose a raw material, not a package size.
The system went live in January 2026, as planned, and the sales team has worked in it every day since. The Excel files for samples and inventory are gone. Reporting to manufacturers happens from the system instead of by hand. Customer data comes from a single source. And for the first time, there's visibility into the pipeline, per business unit, per market, and per product.
Just as important: the system has kept evolving. A month after go-live, Transmare sat down internally with all the business unit managers and came back with a list of improvements, which were built in a next phase. That's exactly how it should go.
Profility took the time to really understand our organization and the way we work. That personal approach made for a smooth collaboration and an excellent CRM that exceeded our expectations.
From the very start, Profility invested in understanding our business and our work processes. That thorough preparation made a world of difference. Thanks to their expertise, they were able to deliver a CRM solution that perfectly matches our expectations.
The collaboration was always constructive and pleasant, with a team that acts as a real sounding board and adapts quickly.
We're extremely happy with both the process and the end result.
Matthias De Foer, Business Unit Manager, Transmare Chemie
What we took away from it
Terminology isn't a detail. Every organization gives words like lead, visit, or sample its own meaning. We carry that language into the system, right down to the menus and field names. A CRM that speaks its users' language is a CRM that gets used.
Required fields come at a cost. Every required field costs the user time, every single time they log something. We only make a field required at the point in the process where that information is already available, not where someone just wants to capture something quickly.
Not everything that sounds simple in plain language is simple on a standard platform. Being upfront about that during the analysis pays off more than having to explain it afterward. Sometimes the answer is smart configuration, sometimes a custom component, and sometimes a different way of working.
Frequently asked questions
Can a CRM be integrated with Business Central?
Yes. Customers, suppliers, contacts, products, currencies, and salespeople can be synced between the two systems, so they share the same master data. We usually choose one-way sync on purpose. Which direction depends on where that data is managed in your organization. Here, Business Central was the source.
Why a CRM on Power Apps instead of Dynamics 365 Sales?
Both run on the same Microsoft platform and the same database. Dynamics 365 Sales adds advanced sales functionality on top. If you don't need that, a model-driven app on the Power Platform gives you the same CRM foundation at a significantly lower license cost.
How long does an implementation like this take?
This project took about four months from kickoff to go-live, including analysis, build, a testing phase with key users, and data migration. The timeline mainly depends on how quickly decisions get made and how available the key users are.
Does the CRM work offline?
Yes. Accounts, contacts, and the records within your own structure are available offline in the mobile app and sync automatically as soon as you're back online. You decide which data comes along and how often it syncs.
Can a system like this keep growing after go-live?
That's the whole idea. Here, a month after go-live, the client ran an internal evaluation, after which an expansion phase was built. Because it runs on a standard platform, changes are a matter of configuration, not rebuilding.
Want a system like this for your organization?
Tell us about your situation, and we'll look at what's possible for your business together. No sales pitch.
Book an intro callMore case studies
How other organizations built a CRM, a custom app, or an integration with Profility.

Non profit en overheid
All customer contact for twenty municipalities in one system
Energiehuis SOLVA used to handle questions from residents of 20 municipalities in a commercial ticketing system that charged per agent. Today everything runs in Vesta, a custom-built CRM on the Microsoft Power Platform, where email, phone calls, and web forms come together in one case with its full history.
Read the case study

Energie en duurzaamheid
Working together toward a sustainable region
The Energiehuis at 3Wplus kept each client case in a different system or spreadsheet. Today, four core processes run in one CRM on the Power Platform, with a portal where partners and residents can follow their case.
Read the case study

Bouw en installatie
Faster case processing and fewer complaints with Power Apps
For years, a building materials certification body relied on an Access database that nobody could change anymore. Today, a Power App with an external portal supports the entire inspection process, from application to approval.
Read the case study
