Is this just an X++ code generator?

No. It brings together Claude Code with metadata, shared engineering memory, protective rules and quality tools as an operating model.

Has it been used in real Dynamics development?

Yes. Some tools have been used on real Dynamics engineering work. Certain best-practice and regression checks have only been exercised in controlled or synthetic tests; results are not guaranteed across all customer environments.

Is client-specific code shared across customers?

Customer-specific code, documents and lessons must remain isolated per client and are not distributed to others.

Home / Products / DynamicsWithClaude

Give your Dynamics development team shared engineering memory.

DynamicsWithClaude brings Claude Code together with an X++ metadata catalogue, shared team lessons, guardrails and quality tools inside the development workflow. It is designed to amplify engineering teams, not replace them.

Discuss a technical pilot Explore the platform

Source code + metadataShared team memoryHuman-approved delivery

More than a model. An engineering operating model.

Built to help Claude inspect current source and relevant context, call quality tools and draw on the team's accumulated experience.

Context

Real X++ and metadata

Classes, tables, forms and relationships are inspected in the current development environment. Name validation and dependency context help reduce fictional object references and weak impact analysis.

Memory

Lessons shared between developers

Knowledge from one session can be made available to the team under appropriate scope controls. Customer-specific information should remain within that customer's boundary.

Quality

Build, best-practice and regression tools

Tools help review build output, selected X++ best-practice rules and report result comparisons. Coverage and applicability are verified within each pilot.

Control

Production and change boundaries

Guardrails, source-control rules and human approvals aim to limit sensitive actions. Go-live decisions remain with people.

Your project. Your pace.

Our engineers can deliver Dynamics development for you, or we can pilot an AI engineering setup for your own developers.

The toolkit is informed by real field work. Access, source control, knowledge isolation and testing boundaries are assessed separately for each client environment.

EnvironmentDynamics 365 F&O developmentKnowledgeShared team lessonsQualityBuild · BP · regression toolsDecisionsHuman-approved

How does a pilot work?

Discovery

Identify development environment, access and security boundaries.

Setup

Deploy approved tools with scoped knowledge.

Real task

Run a controlled development task.

Validation

Review build output, quality checks and human controls.

Decision

Expand only on the basis of observed results.

We do not promise unmeasured productivity multipliers or universal automated quality assurance.

Separate solutions for engineering and support.

DynamicsWithClaude

For developers and technical teams: X++ code, metadata, quality controls and shared engineering memory.

AI ERP Support

For end users and support teams: knowledge base, customer-specific code, authorised ERP data and human handoff.

Explore the support solution

Make your first pilot a real development task.

Let's review your Dynamics environment, goals and security boundaries together.

Book a technical discussion