PROOF · WHAT WE TAKE ON

We turn down work that isn't a fit. Here's what actually is.

Every services firm says they're selective. Most aren't. This page is the specific, checkable version: the project shapes we take, and the ones we'll point you elsewhere for.

WHAT WE TAKE ON

Four project shapes, and nothing outside them.

We don't run a general Dynamics 365 practice that does a bit of everything. We run these four situations well, repeatedly, and we say no to work that doesn't match.

New Business Central or GP implementations

Straightforward scope, a clear go-live date, and a business that hasn't been burned by a prior project.

Rescuing a stalled or troubled rollout

An implementation that's over budget, over deadline, or has lost the business's confidence, with another partner still attached or already gone.

Ongoing managed support for a live system

A system that's live and mostly working, where the gap is response time, configuration drift, or nobody owning it day to day.

Statutory expansion into a new entity or country

An existing Dynamics 365 footprint that needs to cover a new legal entity with real tax and compliance requirements.

WHAT WE TURN DOWN

Saying no here is what makes the yes list credible.

These aren't hypothetical edge cases. They're the requests we actually decline, and roughly where we'd point you instead.

  • Platforms outside Microsoft Dynamics 365We don't run NetSuite, SAP, or Oracle work. A Dynamics-only focus is why the four situations above go deeper than a generalist firm can.
  • Build-first custom development with no defined business processIf the ask is "build us a custom app on the Power Platform" with no ERP or CRM process behind it, that's a different kind of vendor than us.
  • Procurement processes that only want a rate cardWe scope against your actual situation. If the engagement has to be won on a blind RFP rate comparison before anyone will talk to us, it's usually not a good match either way.
  • Projects where the real ask is "rubber-stamp a decision already made"If the system, timeline, and budget are locked and the request is validation rather than judgment, we'll say so plainly rather than take the fee.
HOW WE DECIDE

The same four questions, every time.

1

Is it Dynamics 365?

Business Central, GP, or the CRM side. If not, we'll say so on the first call and point you elsewhere rather than waste your time.

2

Does it match one of the four situations?

New implementation, rescue, managed support, or expansion. Work that's genuinely a fifth shape gets an honest "that's not us."

3

Can we actually move the number that matters?

If the engagement can't plausibly change the metric you care about, we'd rather tell you that upfront than bill for activity.

4

Do we have the capacity to do it properly?

We'd rather turn down a good-fit project at the wrong time than take it on and deliver it thin.

FAQ

Questions about how we scope work.

Q.What happens if you turn us down?

We'll tell you why on the call, and where we think you'd get a better fit, even if that's another firm entirely.

Q.Does "selective" mean expensive?

Not directly. It means we scope against the four situations above rather than stretching to fit whatever comes in the door.

Q.Can a project change shape after it starts?

Sometimes. A rescue can surface a genuine expansion need, for example. We'll flag it and re-scope rather than quietly absorb it into the original engagement.

Not sure which of the four this is?

Get a straight read on your situation, not a pitch deck.

Tell us what's actually happening and we'll give you a straight answer, including if the answer is 'not us.'

Book a 30-minute call

With someone who can tell you honestly whether it's a fit.

Run the situation diagnostic

Four minutes, no email required to see the result.