{
    "componentChunkName": "component---src-templates-offer-js",
    "path": "/offers/dynamics-365-support/",
    "result": {"pageContext":{"num":"20","id":"d365-support","slug":"dynamics-365-support","name":"Dynamics 365 Support & Continuing Development","group":"E","displayGroup":"capacity","industry":"all","live":true,"servicePage":"/dynamics365/financeOperations","h1":"A named engineer on the Dynamics 365 you already run — maintained and extended, monthly","metaTitle":"Dynamics 365 Support & Continuing Development | Monthly | Visiomate","metaDescription":"Maintenance and continuing development for a live Dynamics 365 environment. A named engineer, 160 hours a month, incident response and update regression checks.","oneLiner":"Maintenance and continuing development for the Dynamics 365 you already run — a named engineer who knows your environment, 160 hours a month.","oneLiners":["Maintenance and continuing development for the Dynamics 365 you already run — a named engineer who knows your environment, 160 hours a month."],"whoFor":"Businesses already running Microsoft Dynamics 365 who need it maintained and extended, without hiring a permanent D365 engineer. Not an implementation and not a rescue — this is for a system that is live and in use.","timeline":"Monthly, 3-month minimum","timelineShort":"Monthly","price":"from $2,800/month for 160 hours","websiteDisplay":"from $2,800/mo","priceDisplay":"from $2,800/month","priceShort":"from $2,800/mo","priceDetail":"From $2,800/month for 160 hours of maintenance and continuing development, on a three-month minimum. A $2,800 environment assessment runs first.","symptoms":["Every change to Dynamics waits on a consultant who has to relearn your setup first","A Microsoft update lands and something in your customisations quietly stops working","Your finance team exports to Excel because the report they need was never built","The person who configured your environment has left and nothing was documented","Small improvements never happen because there is no one to do them","You are paying for modules nobody has opened in a year"],"included":["A named engineer who learns your environment and stays on it","160 hours a month of maintenance and continuing development","Incident response against agreed severity tiers","Configuration changes, new reports and dashboards","Integration maintenance as connected systems change","Regression checks against your customisations when Microsoft ships an update","A monthly review of what was done and what is queued"],"notIncluded":["Cover outside business hours — support runs eight hours a day on business days","New module implementations — scoped and quoted separately","Microsoft licence costs, paid directly to Microsoft","Raising and managing support tickets with Microsoft on your behalf","Version upgrade projects"],"process":[{"step":"Before cover starts","title":"Environment assessment","deliverable":"A written picture of your instance, customisations, integrations and outstanding issues"},{"step":"Getting started","title":"Onboarding your named engineer","deliverable":"Access provisioned, your environment learned, the first month's work prioritised"},{"step":"Every month","title":"The working cycle","deliverable":"Incidents answered, changes and reports built, integrations kept working"},{"step":"End of each month","title":"The review","deliverable":"What was done, what it cost in hours, and what is queued next"}],"processHeading":"Four phases, and the last one repeats every month","processLede":"Nothing is delivered once here — this is cover that starts and then continues, so the last phase comes round again rather than finishing.","commitments":["A named engineer who knows your environment, not whoever is free that week","160 hours a month, tracked and reported against what they were spent on","Every Microsoft update regression-checked against your customisations","A written review at the end of every month"],"weNeed":["Access to your Dynamics 365 environment and a sandbox to test in","A named contact who can prioritise what the month's hours go on","Feedback within 48 hours at each review point","Whatever documentation and customisation history exists, however thin"],"proof":{"summary":"CONFIRM — candidate: D365 Bulk Stock Distribution. Verify the client and metric before publishing.","client":null,"metrics":[],"caseStudyPath":null},"faqs":[{"q":"We already run Dynamics 365. Is this for us, or is it an implementation?","a":"This is for a system that is already live and in use. There is no configuration project and no go-live: the engineer picks up the environment as it stands and maintains and extends it from there. If your rollout never actually landed, the ERP Rescue Sprint is the honest starting point instead."},{"q":"What happens when Microsoft ships an update?","a":"Every release wave and routine patch is regression-checked against your customisations before it reaches production, in a sandbox rather than on your live environment. That check is part of the monthly hours, not a separate quote."},{"q":"Can you take over an environment somebody else built?","a":"Yes, and it is the normal case. The environment assessment exists for exactly that: it establishes what you actually have, what was customised and what is already broken, before anyone commits to maintaining it. There is no requirement that the original implementation came from here."},{"q":"What do the hours actually get spent on?","a":"Whatever you prioritise: incidents, configuration changes, reports and dashboards that were never built, integration maintenance as the systems around Dynamics change. The monthly review records where they went, so the split between keeping the lights on and improving things stays visible rather than assumed."},{"q":"How is this different from hiring a Dynamics contractor?","a":"Continuity. A contractor relearns your setup each engagement and leaves with what they learned; a named engineer on a rolling month accumulates that knowledge and it stays available to you. It is also why there is a three-month minimum, because the first month goes largely on learning the environment."}],"related":["platform-modernization-assessment","erp-rescue-sprint","development-month"],"note":"TWO ITEMS STILL OPEN. (1) Unused-hours rule: client is weighing no rollover, a two-month carry, or a quarterly reset. No rule is stated on the page until one is chosen. (2) Proof client unconfirmed; mD365BulkStockDistribution names no client and carries no metric, so no proof section renders. CONFIRMED: $2,800/month for 160 hours (client set this on 25 August 2026, down from the $3,800 originally proposed — see the margin note below), and coverage is business hours eight hours a day, NOT 24/7. That contradicts /dynamics365/financeOperations/, which claims critical response within one hour around the clock. That page is over-promising until corrected. MARGIN: offers-data.js recorded 160 hours at an internal cost of ~$1,500, needing $3,000 to clear the 2.0x floor and $3,750 for 60% margin. At $2,800 this offer sits BELOW that 2.0x floor, at roughly 1.87x. Flagged, not blocked — the client set the figure. Note also that the monthly fee and the environment assessment are now the same $2,800."}},
    "staticQueryHashes": ["1271460761","2880355952"]}