About

Built for SMBs, not enterprise overhead

Small and mid-sized businesses need Dynamics 365 and Power Platform solutions that are practical, cost-aware, and designed to be supported long after go-live.

I focus on right-sized architecture that delivers value without unnecessary complexity.

  • Designed specifically for small and mid-sized businesses
  • No enterprise frameworks, accelerators, or bloat
  • Focus on maintainable data models and automation patterns
  • Solutions internal teams can understand, support, and extend
  • Clear tradeoffs instead of over-engineering
  • Built to scale thoughtfully, not prematurely

A different approach

Enterprise implementations optimize for scale first.
SMB implementations need to optimize for clarity first. 

Connexus Solutions focuses on building systems your team can understand, maintain, and trust, without relying on constant outside support.

Services

What I Do

Connexus Solutions is my independent consulting practice, where I work directly with clients as a senior Dynamics 365 and Power Platform solution architect.

I work with small and mid-sized businesses, consulting partners, and internal teams to design, refine, and simplify Dynamics 365 and Power Platform implementations.

Dynamics 365 Solution Architecture
  • Data model and table design
  • Lead, contact, and process architecture
  • Environment strategy (Dev, UAT, Production)
  • Design decisions that prevent rework and technical debt
Power Automate & Process Design
  • Automation design and review
  • Simplifying complex or fragile flows
  • Configuration-driven logic instead of hard-coded rules
  • Long-term maintainability and supportability
System Reviews & Cleanup
  • Assessing existing implementations
  • Identifying over-engineering and risk areas
  • Clarifying what to keep, change, or remove
  • Creating a clear path forward
Embedded Architecture Support
  • Supporting internal teams during delivery
  • Acting as a senior design resource
  • Helping teams work through complex decisions
  • Translating business needs into build-ready designs
  • Training teams to understand, support, and extend the solution

Approach

How I work

I work alongside clients and delivery teams as a senior solution architect, focusing on clarity, structure, and long-term supportability rather than short-term delivery speed.

Clarify before designing

I start by understanding how your current Dynamics 365 or Power Platform setup actually works today. I look at what is delivering value, what is adding friction, and which assumptions are driving complexity. ​This makes tradeoffs visible early, before they become expensive to unwind.

Design for clarity, not scale theater

I design right-sized architecture that fits your business today and can evolve intentionally over time. That means prioritizing clear data models, configuration-driven solutions, and simple automation patterns, while avoiding enterprise frameworks that add overhead without real benefit.

Guide decisions during delivery

During active build phases, I work alongside internal teams and partners to validate design decisions as requirements shift. The goal is to reduce rework, prevent architectural drift, and ​keep the solution aligned with its original intent as real-world constraints emerge.

Leave teams confident after go-live

I focus on leaving behind systems your team can understand, maintain, and trust. That means clear structure, documented decisions, and reduced dependency on constant outside support, so ownership stays where it belongs after go-live.

The result is a system that works today, scales intentionally, and can be owned by the people who use it.

When I’m Usually Brought In

When clarity matters more than features

I’ve led and delivered Dynamics 365 and Power Platform implementations across new builds and existing environments. Some engagements begin from a blank slate. Others start with systems that function technically, but no longer align with how the business operates.

In both cases, the objective is the same: design a system that reflects current operations while establishing a structure that scales intentionally over time.

I’m usually brought in when:

  • —
    The implementation grew faster than the organization could absorb
  • —
    Customizations and automations have accumulated without clear ownership
  • —
    Small changes feel risky, expensive, or unpredictable
  • —
    The business needs clarity before committing to further build or investment
  • —
    Internal teams are capable, but need architectural direction and guardrails

In these moments, the work is less about adding features and more about restoring clarity, confidence, and control.

Need clarity before your next decision?

If you’re evaluating what to build next, reassessing an existing Dynamics 365 or Power Platform implementation, or untangling complexity that has grown over time, a short conversation can help clarify the path forward.