National Logistics Operator — Logistics & Parcel Delivery · 2025 – 2026
Enterprise Logistics CRM Platform
End-to-end CRM architecture for a national logistics operator — from pre-sales estimation through detailed technical design with 10+ system integrations.
0+
External systems integrated (SAP, Comarch CPQ, Transparent Data, GUS and more)
0+
B2B sales reps the platform will serve
0+
Features specified for build
0
Delivery phases (pre-sales → LLD)
Challenge
A major logistics operator with nationwide parcel delivery infrastructure needed a greenfield D365 CE implementation to replace fragmented legacy tools. The platform required integration with 10+ external systems — including SAP ERP, Comarch CPQ, and multiple operational middleware services — while serving hundreds of B2B sales representatives.
Solution
As Tech Lead, I owned the technical direction of the project — from selecting which Power Platform technologies to use for each feature, to managing the developer team and making architectural decisions. I led the full lifecycle from pre-sales (estimation, RASCI, stakeholder alignment) through HLD (requirements, architecture blueprints) to LLD (feature specs, integration DTOs, middleware contracts). I also built the project wiki with best practices and coding standards, and enforced them throughout implementation via code reviews and solutioning sessions.
Tech Stack
The Problem
The company operated a nationwide parcel delivery network but managed B2B sales relationships through disconnected tools — spreadsheets, email threads, and a legacy system with no integration capabilities. Sales teams had no unified view of customer contracts, pricing was handled manually through a separate CPQ tool (Comarch), and there was zero synchronization with SAP ERP for financial data. The organization needed a modern CRM platform that could serve as the central hub connecting all operational and commercial systems.
Pre-Sales & Discovery
I joined the project during the pre-sales phase, contributing directly to solution estimation, competitive positioning, and the technical proposal. This included building the RASCI matrix for all workstreams, estimating effort for each integration point, and preparing architecture options for the client. The scope defined during pre-sales covered full D365 CE implementation with integrations to SAP (financial master data, invoicing), Comarch CPQ (product configuration, pricing rules), and 8 additional operational systems via middleware.
High-Level Design
During HLD, I led requirements gathering workshops with business stakeholders across sales, operations, and finance departments. We documented the target operating model, defined the integration landscape map, and established architecture principles. Key decisions included the middleware strategy (Azure Service Bus as the integration backbone), the data ownership model (SAP as master for financial entities, D365 CE as master for customer and opportunity data), and the CPQ integration pattern (bidirectional sync with Comarch for product configuration and pricing).
Technical Leadership
As Tech Lead, I was responsible for all technology decisions on the Power Platform side — evaluating when to use plugins vs Power Automate, choosing integration patterns, and defining the Dataverse data model. I managed the developer team through sprint planning, code reviews, and solutioning sessions. I built a comprehensive project wiki documenting coding standards, naming conventions, plugin patterns, and integration best practices — then enforced those standards throughout the implementation to ensure consistency across the team.
Low-Level Design
The LLD phase — completed in early 2026 — was the most intensive. I authored detailed feature specifications for 60+ features covering lead management, opportunity pipeline, contract lifecycle, and B2B customer portal requirements. For each integration point, I designed the DTO contracts, defined the middleware-to-CRM data mapping, documented error handling and retry strategies, and specified the authentication flows. The integration DTOs alone covered 40+ distinct data transfer objects across SAP, Comarch CPQ, and operational systems.
Status & Impact
This is an active, in-delivery engagement. Architecture and 60+ feature specifications were approved by the client and the build entered execution in 2026. Once live, the platform replaces the operator's fragmented spreadsheets, email threads, and a non-integrated legacy system with a single Dynamics 365 hub — connected to SAP, Comarch CPQ, and operational middleware over Azure Service Bus — giving hundreds of B2B sales representatives a unified view of contracts, pricing, and orders. As Tech Lead I continue to own the technical direction, integration design, and code-quality standards through implementation.