Skip to main content
BJ Unlimited
Book a consultation
Jerold Billings, Principal Architect at BJ Unlimited LLC

The principal

I'm Jerold Billings, Principal Architect at BJ Unlimited.

I've spent 26+ years building on the Microsoft stack — 21+ of those years certified on Dynamics, and the last nine architecting on Power Platform professionally. When Microsoft started shipping Copilot, I was already building with it before general availability. That is the unusual combination this practice is built on: deep Dynamics architecture credibility paired with hands-on Copilot work from before it had a name the CIO recognized.

BJ Unlimited is intentionally principal-led. When you hire this practice, you get the architect who writes the design and the architect who writes the code. No bench, no offshored junior taking over in month two, no brochure-quality promise that quietly devolves into staff augmentation.

LinkedIn
  • 26+ yrs Microsoft business-application development
  • 21+ yrs Certified on Dynamics
  • 14 yrs On Microsoft Azure
  • 9 yrs On Power Platform and Power Automate
  • Pre-GA Hands-on Copilot work since early 2023

Credentials

Microsoft-certified Solution Architect.

Certifications listed with their issue dates. The Microsoft certifications are the primary credentials; the others are adjacent tooling you're welcome to ask about.

Microsoft certifications

  • Microsoft Dynamics 365 + Power Platform Solution Architect issued 12/2020
  • Microsoft Power Platform Functional Consultant issued 12/2020
  • MCSE: Business Applications issued 01/2019
  • MCSA: Dynamics 365 issued 01/2019
  • Microsoft Dynamics 365 for Customer Service issued 01/2019
  • Microsoft Dynamics 365 Customer Engagement Online Deployment issued 01/2019
  • Microsoft Dynamics 365 Customization and Configuration issued 01/2019

Additional certifications

  • Blue Prism Certified Developer issued 02/2019
  • North52 Business Process Activities Certified issued 02/2019

Client history

Real delivered Microsoft business-application work.

Every client named here represents delivered Dynamics 365 or Microsoft business-application work across federal, state, and enterprise engagements.

Federal

  • Social Security Administration
  • Library of Congress
  • Department of Veterans Affairs
  • Department of Health & Human Services
  • Peace Corps

State and Local Government

  • State of Indiana
  • State of Oklahoma
  • State of Illinois
  • Cook County Sheriff's Department
  • Municipal Employees' Retirement System of Michigan

Enterprise and Nonprofit

  • Kaiser Permanente
  • Bill & Melinda Gates Foundation

How I work

Five principles that describe how engagements actually run.

  1. Senior-led, from scoping to cutover

    I scope the engagement, I architect the solution, and I write the code that matters. You are not handed off to a junior after the statement of work is signed. Nothing against junior engineers; they are the future of this industry. But if you hired a principal architect, you should talk to one for the duration.

  2. Evidence over assertion

    Claims on this site are tied to specific years, named clients, or concrete deliverables. The same discipline holds inside engagements. If I tell you a customization will perform under load, it is because I have measured it — not because the vendor documentation suggested it would.

  3. No offshored juniors, no surprise bench

    I am the only architect on the engagement. If a project needs additional hands, I raise that explicitly in scoping, and any additional resources are disclosed by name, rate, and role. You never wake up to an unexpected name in the team channel.

  4. Scoped, written, and honored

    Scope is written. Changes are written. Out-of-scope requests get a direct answer — yes, no, or “here is what a change order would look like.” Consulting engagements fail quietly when scope drifts silently; this one doesn't.

  5. Honest about what Copilot can and can't do

    Copilot is a capable platform with real limits. I will tell you when a use case is ready for it, when it needs governance work first, and when the right answer is Power Automate with a small model rather than a Copilot Studio agent. A vendor who only knows how to sell Copilot will always recommend Copilot; that isn't the practice you need.

If the practice model fits what you need, let's talk.

Thirty minutes, no slides. Tell me what's in front of you and I'll tell you whether this is the right practice for it.

Start with a Copilot Readiness Assessment