Sofia · Bulgaria
EET · UTC+2
Independent solution architect and developer
Dynamics 365 CRM on Dataverse, ERP on Finance & Operations, and the Azure fabric that carries messages between them. I make the decisions that get expensive later — the data model, the integration pattern, the environment strategy — then write the code that has to live with them.
Dynamics 365 CE · Finance & Operations · Business Central · Azure
A reference flow, not a benchmark. The point is that every hop is named, timed and owned by one person.
What I build
Most Dynamics problems live in the seams between these. I work across all three rather than throwing a specification over the wall between them.
Dataverse · model-driven apps
Finance & Operations · Business Central
the fabric between everything
Architecture
Almost every Dynamics integration is one of five shapes. Picking the wrong one is the decision that gets expensive later, so this is where the design time goes.
business event → Service Bus → Function
Reach for it when
Volumes spike, the receiving system is slow or occasionally offline, and the business can live with a few seconds of lag.
Leave it alone when
Someone is at the form, waiting to see the answer before they save.
plug-in, pre-operation
Reach for it when
The record must not be saved unless the other system agrees to it first.
Leave it alone when
The remote call can outlive the two-minute sandbox limit, or its uptime is not yours to promise.
CE ⇄ F&O, platform-managed
Reach for it when
Both sides must share customers, products and addresses as one master, and the standard maps fit the model.
Leave it alone when
The mapping needs logic, or you only ever need to read the other side.
Dataverse over an external provider
Reach for it when
The data must be visible and searchable inside Dynamics but has to stay in its source system.
Leave it alone when
Users need to filter, sort or roll it up at Dataverse scale.
Data Factory · Synapse Link
Reach for it when
Millions of rows move on a schedule and nobody is watching them land.
Leave it alone when
The business needs the change reflected within the hour.
Practice
A Dynamics implementation is judged on its second year, not its go-live. These are the habits that decide which one you get.
DEV
unmanaged
BUILD
pack & sign
TEST
managed
UAT
managed
PROD
managed
Stack
What I work in day to day, grouped the way a solution is.
Working together
A fixed-scope read of what already exists — the data model, the integrations, the ALM and the licensing — and a written answer to what will break first and what it costs to fix.
From the model on the whiteboard through to the deployment pipeline. Both halves by the same person, which is the entire point of hiring one.
I take the technical stream of your Dynamics programme under your delivery lead, as a named engineer rather than a logo on a bench.
Something is slow, failing or unexplained, and it needs someone who will read the trace rather than the ticket.
Contact
A useful first message is short: what the system has to do, what already exists, and when it has to be live. If it is not work I should take on, I will say so and point you somewhere better.
26 in total
issued with Microsoft