CRM / ERP systems
You have Symfonia: you do not use half its features, and half the features you need are missing. I build custom CRM and ERP systems for precisely these customers.
Transparent Investment Ranges // Engineering Standard
A fixed price agreed before work begins, based on the audit. No hidden costs or endless hourly billing.
The first tangible production result in your business. I focus on one critical process, eliminating risk and delivering working software in a fraction of the usual time.
- Database and API architecture with FastAPI
- Modern React / TypeScript management dashboard
- Invoicing and order workflow module
- 30-day stability warranty and post-launch support
A comprehensive platform for the entire organization. Advanced decision loops, deep two-way database integrations, complete audit logging, and dedicated engineering support under an SLA.
- Database and API architecture with FastAPI
- Modern React / TypeScript management dashboard
- Invoicing and order workflow module
- Employee roles and precise ACL permissions
- Two-way integration with Subiekt GT/Nexo
- Priority SLA, 24/7 monitoring, and architect support
Custom CRM / ERP System in practice
Engineering approach and system architecture
I solve business problems by starting with the process. No rigid ready-made templates: I build software around your procedures.01 // MODULE
For teams managing orders outside their system
For teams using spreadsheets, email, and manual re-entry because the fields in an off-the-shelf CRM or ERP do not match their actual orders, customers, and inventory. Scope: process analysis, orders, customer records, inventory and documents, roles, an operations dashboard, API integrations, monitoring, and development after launch.
Results
02 // MODULE
What the team uses after the first release
The first version should remove Excel workarounds, rather than add another set of empty fields. The team should work with a real order, customer, or stock level.
Your own orders instead of manual workarounds
Customers and history in one place
Inventory management tailored to your logic
A dashboard the team uses every day
Process
03 // MODULE
From mapping an order to a dashboard in daily use
01
One object to start with
I choose an order, a customer, or an inventory record and narrow the first version to that single object using real data.
02
A dashboard you can actually use
I build the screen, roles, and backend so the team can open a real order that day, rather than a slide.
03
Support after day one
After launch, you retain monitoring, fixes, development and clear responsibility for production.
A system built for the process, not the box
04 // MODULE
An operations dashboard from scratch, not another off-the-shelf tool
I build the system from scratch. If Comarch or Symfonia is already in place and you need AI on top of it, that is an integration, rather than a new CRM.
01
Orders, customers and stock do not fit the fields
Companies rarely build a CRM or ERP just for fun.
First they buy an off-the-shelf product, then add spreadsheets, emails and manual exports because orders, customers or stock do not fit its predefined fields. A custom system makes sense when these areas are specific and repeatable: your own order statuses, customer rules, stock states or documents. Then I build a dashboard around that process instead of adding more spreadsheets.
02
Evidence: CoreTSL TMS and the B2B platform
I do not build Enova, Optima or Comarch. I build operational systems. CoreTSL TMS includes jobs, fleet management, invoices and CRM, plus customer and carrier portals. The B2B platform has its own catalog and wholesale orders; Comarch is an integration target, not an MKM product. A broader explanation of TMS logic is also in the blog post about the TMS system. It is the same kind of work: your company's process becomes a dedicated dashboard, rather than replacing one boxed product with another.
03
Already using Comarch or Symfonia?
This is a different service. A new system is built around your orders, customers, and inventory. I do not implement off-the-shelf Comarch or Symfonia software as an MKM product. If you already have Comarch, Symfonia, or another ERP and want AI, automated entries, or reports on your existing system, the right service is AI integration with ERP and CRM. If you need a store with shipping and payments and your ERP is already in place, go to the online store service.
05 // MODULE
When to build a system and when to integrate
I build a custom CRM and ERP when off-the-shelf software does not cover orders, customers, or inventory, and workarounds start costing more than development. I do not add AI to Comarch or Symfonia here.
If the system already exists and needs AI, that is a separate implementation described on the integrations page. A store with shipping and payments is outside this scope.
That is a separate online store service. The decision: first, I map who enters orders today, who manages customers, and where inventory data lives.
Coding begins once I know which step the system should take over. The first scope must be usable with real data.
A large specification for a "complete ERP" can wait until this scope has been used in daily work. If our conversation shows that AI added to the current ERP or a store alone is enough, I do not push for a new system.
I direct you to the right service. Implementation in practice
06 // MODULE
From a real order to the first integration
I start with one real order. Then I narrow the initial scope to one object, deliver a dashboard you can try and only then connect the rest.
01
I start with a real order
I map one order as it actually moves through the company:
who enters data, who approves it, and where statuses get lost. Off-the-shelf fields are not a specification.
02
I limit the start to one object
The first version covers an order, customer record, or inventory level.
I do not build a 'complete ERP' on day one.
03
I deliver a dashboard the team uses
The team should open a real record and work through their day.
A slide with a mockup is not a delivery.
04
Integrations only when the object is in use
I add APIs, roles and logs once that one object works.
If your existing Comarch or Symfonia is to remain the core, I return to AI integrations. CRM and ERP system
07 // MODULE
Tell me about your orders, customers, and inventory
Tell me where the off-the-shelf tool falls short. I will return with a first-version scope, or direct you to integration or a store if that is a better starting point.
Book a free conversation
What You Receive with the Implementation:
- Database and API architecture with FastAPI
- Modern React / TypeScript management dashboard
- Invoicing and order workflow module
- Employee roles and precise ACL permissions
- Two-way integration with Subiekt GT/Nexo
Technologies and production standards:
I choose technologies for stability, speed, and reliability. No technical debt.
Custom CRM / ERP System
FAQ
Frequently asked questions about custom CRM/ERP systems: architecture, implementation, data security, costs, and technologies:
01 When is an off-the-shelf CRM or ERP not enough? +
When orders, customers, or inventory do not fit into off-the-shelf fields and the team manages the process in spreadsheets. I then build a custom dashboard for that process instead of adding more workarounds.
02 You already have Comarch or Symfonia. Do I build a new system? +
No. If you already use Comarch, Symfonia or another ERP and want AI, automatic entries or reports in that system, the right service is AI integration with ERP and CRM. Here I build from scratch rather than add AI to an off-the-shelf product.
03 Will you build us Enova, Optima, or Comarch? +
No. I do not implement Enova, Optima or Comarch as an MKM product. Comarch is an integration target when a B2B client already uses it. Here, I design your dashboard around your process.
04 What evidence do you have of a custom operational system? +
CoreTSL TMS: orders, fleet, invoices, CRM, customer and carrier portals. A separate B2B platform with its own orders. Details: the CoreTSL project and TMS article.
05 Does this also include an online store? +
No. A store with shipping, payments, and a possible ERP connection is a separate service: online stores. Here, I am discussing a system for managing orders, customers, and inventory inside the company.
06 How does this differ from custom software development? +
If you know you need your own CRM and ERP instead of an off-the-shelf system, this is the scope. If you are not yet sure which system you need, I start with broader custom software development.
Start building.
First conversation free.
A free 30-minute technical consultation. After the call, I will provide an architecture proposal, timeline and transparent quote within 24 hours.