A Dynamics 365 system your team builds and owns

Some teams want to own their Dynamics system, not hand it to a vendor and depend on them for every change after. The risk in doing it yourselves is the early configuration. Get the foundation wrong and you spend the next year undoing it.

CoBuild45™ pairs your team with a solution architect who trains them as they build. Your people do the design and configuration and learn the system as they go, with the architect teaching best practices for decisions that are costly to reverse. In 45 days, you have a working system your team built and can extend on its own.

Start the Conversation

What is CoBuild45™?

CoBuild45™ is structured training paired with hands-on configuration. Across the program, your team learns the system end-to-end and applies each piece to your real environment, so by the end, the system is configured, and the people who configured it know why every decision was made.

Most guided programs are group training. Several companies share the same scheduled workshops, and the model works by assigning one consultant to multiple teams. That keeps the price down and the attention thin, and the architecture decisions are still yours to get wrong.

CoBuild45™ is one solution architect working with one team. In training, they teach your people how to configure the system and the best practices for decisions that are expensive to reverse, such as the data model and security design. During office hours, they review what your team has built and flag problems before those decisions are locked in. Your team does all the building and makes every decision. The architect's job is to make sure you make those decisions right.

How does CoBuild45™ work?

What needs the architect's eye varies by product, but it is always the same kind of decision: the foundational setup that is cheap to get right now and painful to redo once everything else sits on top of it.

The chart of accounts and the dimensions are nearly impossible to change once a year of transactions has posted against them. Build them to a generic template instead of how you report, and month-end becomes manual reconciliation that never goes away. The training covers how to structure both, as well as the best practices that keep your reporting clean. Your team builds it, and in office hours, the architect reviews the structure and flags anything that will break reporting before the first transactions post.

Reps abandon a CRM the moment its pipeline stages no longer match how they actually sell, and they go back to running the real numbers in a spreadsheet. That spreadsheet is the thing you bought Sales to eliminate. Your team designs and builds the stages, with training showing them how and the best practices for tying the pipeline to how you really close deals. In office hours, the architect reviews what they built and flags stages that your reps will route around before forecasting gets layered on top.

Case routing is the difference between a system that clears work and one that just moves it around. Route on the wrong rules and cases land in the wrong queues, so agents spend the day reassigning instead of resolving. Your team designs the routing and configures the case model. The training covers how, and in office hours, the architect reviews the rules and flags the ones that will misfire once real case volume hits them.

Most Power Platform messes start with a data model nobody designed and environments nobody separated. Left alone, it becomes a sprawl of apps and flows that run fine until the person who built them leaves. Your makers build the schema and set up the environments, with training on how to do both and best practices to keep it maintainable. In office hours, the architect reviews what they built and flags the shortcuts that turn into the next rebuild.

What's included:

Training

Two to three hours a week for seven weeks, inside a 45-day window, taught live by the solution architect to your team alone. Your team learns how to configure the system and the best practices behind each decision.

Office hours

One to two hours a week, running alongside the training. The architect reviews what your team has built and flags problems before they get locked in.

Ongoing support

40 hours of additional ad hoc support are included after the program ends, as your team applies what it learned to live work.

Who is CoBuild45™ for?

CoBuild45™ fits a company that wants to own the system build rather than outsource it, and has the people to do the work but not the expertise to do it safely.

For the CIO or IT Director, the result is a team that owns and runs the system, with no dependency on an outside firm for routine changes. For the COO, the people who run operations understand the system those operations depend on. For the CFO, the cost of ownership drops over time, because day-to-day changes stay in house instead of going back to a vendor.

You own the system. Your team owns the know-how.

Most of a system's life occurs after go-live, as the business evolves and the system must keep up. What decides whether it does is how well the people running it understand it.

That is what CoBuild45™ leaves inside the business. Your team configures the system and learns why each decision was made, so the knowledge to run and change it stays with the people who use it. When something needs to change, they can make the change on your schedule, because they built the thing they are changing.

The program delivers a working system, and the return that outlasts it is a team that can keep that system aligned with the business as it changes. For a company that wants its own team to own the system, that capability is the value.

Let's discuss whether
CoBuild45™ fits your team.

A 30-minute conversation comes first to understand your needs.