Platinum Lined Solutions / PT·950
PT·950 How we work

Plain answers to the questions that matter.

PT·950 Your data & AI

What happens to your data when we use AI.

This practice runs on AI, openly and by design. Here is exactly what that means for your information:

Your data lives on hardware we own, in infrastructure we control. It is not stored in a chatbot, not used to train anyone's model, and never sent anywhere unmasked.

Masking before transmission. When cloud AI assists with reasoning, a firewall on our own machines replaces names, organizations, identifiers, dates, and figures with anonymous tokens first. The cloud model works on [Person 1] at [Org 1], never on your employee's name at your company. Real values are restored only back on our hardware.

An audit trail, on request. Every transmission is logged: when, to which provider, and how many identifying details were masked. If you ever want to see what left, and what never did, ask.

Sensitive material stays local, period. Screenshots and files containing member-level detail are processed by models running on our own machines. For the most sensitive engagements, we can run in a mode where nothing reaches a cloud model at all.

The person is accountable, not the machine. AI accelerates the work; it does not sign it. Every deliverable is reviewed, tested, and stood behind by the consultant whose name is on it.

PT·950 Delivery discipline

Grounded, evidenced, documented.

  • Grounded answers only. Configuration and code are built against the vendor's published reference (actual table definitions, actual formula functions), not memory. When something is uncertain, we say so and verify it, rather than guessing confidently.
  • Evidence over assertion. Fixes ship with test cases and results. Changes to formulas run through where-used analysis before they ship, so a fix in one plan never surprises another.
  • Documented while it happens. As we build and test in your environment, a browser-side capture instrument records each step: screenshot, narration, and the ticket it belongs to, filed in the moment. Nothing depends on reconstructing the work from memory a week later.
  • Close-out means closed. A resolved ticket arrives as a package: the resolution in plain language, the documents, and the test evidence, filed to your folder in your branding.
  • Documentation is versioned and dated. Effective dating is how benefits works; it's how our documents work too. When your configuration changes, the documentation changes with it.
  • Your court is visible. Work waiting on us is measured against us; work waiting on you is marked as yours. The clock is honest in both directions.
PT·950 Engagement shapes
A Implementation Fixed scope, dated plan, staged delivery: requirements → configuration → conversion → parallel test → cutover → stabilization. You see the plan and the risks weekly.
B Managed support Contracted hours with burn-down visibility, ticketed intake with acknowledged SLAs, and a standing cadence. You always know what's open, what it's waiting on, and what it cost.
C Surge & season Open Enrollment season, rate renewals, an acquisition's benefits migration: bounded, calendar-driven engagements with a defined finish line.