How PBW compares to the alternatives.

The PBW Difference

Dual-platform means we can advise on platform selection without a product bias.

Most consultants came up on one platform. They advise from that history. When a client asks "which platform should we use," a consultant with deep experience on only one platform has a conflict — sometimes invisible, but structural. PBW has built production implementations on Bloomberg AIM and Charles River IMS. Platform recommendations follow your trading workflows, compliance structure, and growth trajectory. Not which demo went better.

Vendor-neutral means there is no conflict when vendor recommendations are needed.

PBW does not take referral arrangements, reseller agreements, or kickback structures from Bloomberg or Charles River. Engagements are priced to the work. The right answer for a given firm is the right answer — not the answer that generates the largest follow-on contract. When a client needs a recommendation for something outside PBW's scope, the recommendation is based on fit, not commission.

Founder-delivered means the person who wins the work does the work.

Large firms staff with junior resources. The senior consultant who scopes the engagement hands it off to a team that manages the delivery. That's a business model, not a flaw — but it's also not what the client signed up for. PBW is a boutique. The person who does the diagnostic is the person who builds the compliance rules, configures the integration, and gets you to go-live. That continuity is structural, not a promise.

Where We Fit — and Where We Don't

PBW is not the right fit for every OMS implementation. Saying so is not false modesty — it's calibration. An implementation where the fit is wrong is worse than no implementation at all.

Where PBW works well

• Firms evaluating Bloomberg AIM vs. Charles River and needing vendor-neutral analysis
• Buy-side asset managers implementing or migrating to AIM or CRD
• Firms where an implementation has stalled, drifted, or gone off-track
• Compliance rule configuration where the mandate logic needs to be built correctly, not defaulted
• Integration work where custodian, FIX, or reporting feeds need to work reliably under production conditions

Where PBW is not the right call

• Full PMO staffing — PBW does not provide bodies to fill a project management office. If the engagement requires a multi-person team managing a large workstream with governance overhead, a larger firm is the right structure.
• Ongoing trading desk support — PBW does not run trading desk operations. If the need is ongoing front-office support, trade monitoring, or desk coverage, this is not the right engagement model.
• Vendor training only — If the need is training on Bloomberg AIM or Charles River IMS, go direct to Bloomberg or Charles River. They have training teams. PBW is not a substitute for vendor training — it is a replacement for vendor implementation, which is different work.
• Organizations that need a vendor to recommend their own product — PBW is structurally neutral. If the engagement requires a vendor to endorse a specific product outcome, that conflict cannot be resolved through PBW's model.

The goal is an implementation that works. If PBW is not the right mechanism for that, the honest answer is better for both sides than a forced fit.

Due Diligence Before You Reach Out

PBW's engagement model and proof of practice are documented in two places. The content is there before the call. Review it and form your own view before reaching out.

• How We Engage — Step-by-step description of how a PBW engagement runs from diagnostic through go-live
• Proof Library — Implementation results, framework documentation, and practitioner insights from direct engagements
• Download Philip Williams — CV — Curriculum Vitae for direct review of background and credentials