From the first quote
to the last invoice
We customize, extend and connect Microsoft Dynamics 365 apps, from sales and service to Business Central, and try every change before it reaches your teams, so what sales quotes, finance can invoice.
Thanks, we’ll be in touch soon.
{{ heroStatus }}
You’re in good company
A few of the companies we’ve worked with.
When changes are made straight in production
Many companies have run Microsoft Dynamics 365, or Microsoft Dynamics CRM before it, for years. In many of them, much of it was changed by hand in production, the live environment your teams work in, one request at a time. An environment is one copy of the apps, with its own data and settings.
Where there’s no development copy and no record of what changed, a change is hard to repeat, test or undo, and changes from different vendors can sit on top of one another.
Meanwhile the sales side and the finance side often keep their own customers, typed twice. So each update, and each new request, carries more risk than it should.
What we build
Work on Microsoft Dynamics 365 apps that fits how your teams sell, serve and invoice, linked to the other systems you run, with each change built in a development environment and tried in a sandbox, a copy kept apart for testing, before it reaches production.
Sales and service apps shaped to how you work
Tables, forms, views and business process flows in Microsoft Dynamics 365 Sales, Customer Service and Field Service, changed through configuration first, so each team sees the fields and steps it uses.
Code where configuration stops
Plug-ins in C#, code that runs on the server when a record changes, written for the .NET version Microsoft Dataverse requires, with client scripts and custom controls for the screens, each tested before it reaches production.
Business Central extensions
Extensions in Business Central’s own language that add to Microsoft’s base application without changing it, the only kind of development Business Central now supports, with tests that run before each update.
Sales and finance kept in step
Business Central’s own integration with the sales app, through Dataverse, or connections built for another ERP, deciding first which system is in charge of each record, so a customer or an order is entered once.
Changes moved as solutions
Each change built in a development environment and packaged as a solution, a set of changes that moves together, then moved to test and production as a managed solution, with pipelines where they fit. Nothing is made by hand in production.
Automation moved to Power Automate
Classic background workflows reviewed and, where they fit, rebuilt as cloud flows in Microsoft Power Automate, which Microsoft recommends for new automation. A step that must run the moment a record saves may need a plug-in instead. Each is tried in a sandbox before the old one is turned off.
Integrations with your product and other systems
Connections through Dataverse’s and Business Central’s own APIs, each signing in as its own app rather than as a person, with only the access it needs.
Moves to the cloud
Microsoft Dynamics 365 Customer Engagement (on-premises) moved online, and older Microsoft ERP on your own servers moved to Business Central online, in planned steps, as Microsoft’s migration guidance sets out.
AI agents where they help
Copilot features and agents in Dynamics 365 apps, used where they help, with controlled access and a person approving what matters. For the AI assistants your team already uses, Microsoft’s MCP servers for Dataverse and Business Central, both generally available, act within each person’s own access.
- Connecting any of your systems:Systems & API Integration
- Automation across your tools:Workflow Automation
- Care once it’s live:Support & Maintenance
- Developers in your own team:Hire developers for Dynamics 365 apps
Every app on the same tables
Microsoft Dynamics 365 Sales, Customer Service and Field Service keep their data in Microsoft Dataverse, in tables such as accounts, contacts and cases. A table holds one kind of record, with a column for each detail.
Apps and flows your business builds itself can use the same tables, under the same security roles, the sets of permissions each person is given. So a warehouse app sees the same customer the sales team does, with no copy to keep in step.
Business Central keeps its own data, and Microsoft’s integration can keep chosen records, such as customers and their contacts, in step with Dataverse. So we design the tables first, and build every app and flow on them.
Apps and flows
Tables
Kept in step
Each table is kept once, and every app and flow works from it.
{{ tbStatus }}
Updates you can plan for
Microsoft updates Dynamics 365 apps online itself, so there’s no upgrade project to run, but everything built on them has to keep working through each update.
Business Central has two major updates a year, in April and October, each with a preview a month before, and an admin can schedule each one within a five-month update period. Microsoft’s documentation describes two major releases a year for the sales and service apps too, in April and October, with a schedule for each app.
Since September 2026, Microsoft publishes what’s coming to Dynamics 365 on its AI at Work roadmap as each capability is committed, rather than in twice-yearly release plans, and Message Center still carries the changes for your own tenant. Microsoft says how its products are built and released stays the same.
On your own servers, Microsoft’s lifecycle pages set the dates. For Dynamics 365 Customer Engagement (on-premises) version 9.1, mainstream support runs until January 12, 2029, and extended support until January 9, 2031.
So we try each update in a sandbox first, and move each older version in planned steps, before its date.
Start with a review of your setup
The review covers your environments, and how changes reach production: which were made by hand there, and which arrive as solutions; your solutions, which are yours, which came from other vendors, and what sits on top of what; your tables and columns, which are used and which repeat; your plug-ins, scripts, workflows and flows, and what runs on each table; your Business Central extensions and their tests, if you have them; each integration, what it reads and writes, how it signs in and what access it has; your security roles, business units and teams, and who can export data; and how each update is tried, with Microsoft’s dates for any versions on your own servers.
Moving to the cloud, or adding an integration? The first step is the tables and one connection, built and tried in a sandbox with real records, then released early, so your team works with it before the rest is built.
Either way, you get a written review and a proposal for the first step.
Questions worth asking
Microsoft says it’s retiring release waves. What changes for us?
Mostly where you read about what’s coming. From September 2026, Microsoft publishes new Dynamics 365 and Dataverse capabilities on its AI at Work roadmap as each one is committed, in place of its twice-yearly release plans, and its Release Planner is set to retire by November 15, 2026. Message Center still carries the changes for your own tenant. Microsoft says the change is to how it communicates, not to how its products are built, released or deployed.
How do you make sure an update doesn’t break our customizations?
We try each one in a sandbox first. For Business Central, each major update has a preview a month before it, and an admin can schedule the update within its five-month update period, so your extensions are tested on the preview and the update is set for a date that suits you. For the sales and service apps, we keep tests for your solutions, plug-ins and flows, and run them for each update, starting in a sandbox, on the schedule Microsoft sets for each app.
We run Customer Engagement on our own servers. What are our options?
There’s time to plan. Microsoft Lifecycle gives Dynamics 365 Customer Engagement (on-premises) version 9.1 mainstream support until January 12, 2029, and extended support until January 9, 2031, and support for version 9.0 has ended. So the first step may be a supported version, then a move online in planned steps, with your data and customizations checked at each one. The review lists the versions you run, with Microsoft’s dates for each.
Should we change it with configuration or with code?
Configuration where it fits, and code where the logic needs it. Tables, forms, views and business process flows cover a lot without code; plug-ins, client scripts and Business Central extensions handle what they can’t, such as logic that must run the moment a record saves. We choose for each change, and keep both in solutions or extensions, so either is tested and moved the same way.
Can you clean up changes made straight in production?
Yes, after the review. We bring what was changed by hand into solutions built in a development environment, check each against production, then move them to test and production as managed solutions, so every later change has a record and can be repeated and tested.
Can our AI assistants or agents use our Dynamics 365 data?
Yes, within each person’s access. Dynamics 365 apps include Copilot features and agents, which we use where they help, with a person approving what matters. For the AI assistants your team already uses, Microsoft’s MCP servers for Dataverse and for Business Central are both generally available, and Microsoft says the Dataverse one respects security roles, so each person reaches only what their role permits. An admin turns each on and allows each assistant, and some uses can be charged, depending on your licenses.
Do we need more Microsoft licenses for this?
Sometimes. Some features depend on the licenses you hold, as Microsoft’s licensing guide sets out. We check what yours already cover, and tell you what any part of the plan would need before anything is bought.
Can you move us onto Dynamics 365 from another CRM, or from an older Microsoft ERP?
Yes. From another CRM, we map your records to Dataverse tables, match duplicates first and move them in planned steps, with your team checking each one. For some older Microsoft ERP products on your own servers, Microsoft provides a cloud migration path to Business Central online, and we plan the move around your data, extensions and integrations.
Can you take over our existing setup?
Yes. We start with the review, so we know what was built, how it reaches production and what each integration does, then take it over from your team or your last provider, with every account and key moved to people you name.
Can it connect to our product and other systems?
Yes. Through Dataverse’s and Business Central’s own APIs, each connection is built and tried in a sandbox with real records, then released early, so you see it working before the rest is built. Each signs in as its own app rather than as a person, with only the access it needs.
Systems & API IntegrationHow do you keep our data secure?
Each person gets security roles set for their job, and each integration signs in as its own app rather than as a person, with only the access it needs. People sign in through Microsoft Entra ID, your organization’s own sign-in, and changes reach production only as tested solutions, so who changed what is on record.
Application SecurityWhat does it cost?
The price follows the work: how much your setup holds and runs, and whether it’s being built, cleaned up or extended. You get a written proposal before any work starts: the scope, the price or rate, and how you pay.
PricingCan we hire Dynamics 365 developers for our own team?
Yes. Tell us what your setup needs, and we’ll introduce developers who build on Dynamics 365 apps, on the CRM or the ERP side, matched to it, within 48 hours, working in your time zone. You meet them and decide who joins.
Hire developers for Dynamics 365 apps
Microsoft, Dataverse, Dynamics, Dynamics 365, Microsoft Entra and Power Automate are trademarks of the Microsoft group of companies, and the other Microsoft product names on this page, such as Business Central and Copilot, may be too. Webair is independent of Microsoft, and isn’t sponsored by, endorsed by or affiliated with it.
Let’s build it better
Tell us what runs in your Dynamics 365 apps today and what you’d like them to do next. A short call is enough to see where to start.
Thanks, we’ll be in touch soon.
{{ ctaStatus }}