Open source / Published releases
Prism MCP Rust SDK
An independently usable Rust implementation of the Model Context Protocol. Review the source, documentation, package, and release history before you talk to us.
Inspect the repositoryEvidence & scenarios
Proof before promises.
Inspect what can be verified today, work through three illustrative engagements in the open, and see the measurement standard we apply before calling any outcome a result.
Evidence status
How a claim earns its label.
- 01Illustrative modelA worked example. The scenarios on this page.
- 02Assessed baselineMeasured on your current work
- 03Accepted implementationAccepted by your owners on evidence
- 04Measured operating outcomeCompared with the baseline in operation
How to read this page
The scenarios on this hub are illustrative worked examples, clearly labelled on every page. They show how PrismWorks designs, evaluates, and measures an engagement. They are not anonymized client stories and their figures are not delivered customer outcomes. Permissioned case studies will be published here only with a named or customer-approved profile, an agreed baseline, and measured results.
Verifiable today
Start with what
you can inspect.
Enterprise experience
Leadership you can check
Founder Rishi Randhawa leads strategy, architecture, and delivery, with enterprise technology experience including TD, Accenture, and IBM.
Meet our founderPractical guidance / Ungated
Guides & worksheets
Seven practical guides and three editable worksheets on choosing, evaluating, and owning enterprise AI workflows. Use them with or without us.
Read the guidesIllustrative engagement scenarios
Worked examples.
Honest arithmetic.
Illustrative scenario / Client operations
Client onboarding, prepared for a decision
Organize agreements, records, and service requirements into a source-linked review package, with approval kept with the responsible team.
Work through the scenarioIllustrative scenario / Finance operations
Invoice exceptions, prepared for finance review
Gather permitted invoice, purchase, receipt, and policy records, explain the discrepancy, and prepare each exception for the accountable owner.
Work through the scenarioIllustrative scenario / Knowledge & decisions
A knowledge assistant people can verify
Connect owned, current sources to the questions staff actually ask, show the evidence behind each answer, and escalate what cannot be supported.
Work through the scenarioEach scenario states its illustrative profile, the baseline to collect, controls and evaluation cases, worked arithmetic with sensitivity, acceptance gates, and the conditions under which we would recommend stopping.
Our measurement standard
How a scenario
becomes a result.
01
Baseline
Observe real work first: volume, total effort, elapsed time, quality, rework, and cost.
02
Evaluation
Test representative, difficult, restricted, and failure cases against agreed criteria.
03
Acceptance
Named business and technical owners accept the scoped result from evidence, not a demo.
04
Operating review
Compare accepted outcomes with the baseline and decide to improve, expand, or retire.
- A published result names its evidence status: illustrative model, assessed baseline, accepted implementation, or measured operating outcome.
- Figures always show volume, total effort including review and rework, recurring costs, and the measurement period.
- Customer stories appear only with permission and the customer owner’s acceptance of the result.
- Failures, escalations, and unresolved cases stay visible. A pass rate without its case mix is not evidence.
Your first evidence
Replace our examples
with your baseline.
A focused workflow assessment turns an illustrative scenario into a decision grounded in your work.
Bring one workflow, an accountable owner, representative cases, and the systems involved. The assessment establishes the baseline, feasibility, constraints, and a build, buy, improve, or stop recommendation with an investment estimate. Scope and fixed fee are confirmed in writing before work begins.
Your next step
Bring one workflow.
Leave with a decision.
Tell us the work, the systems involved, and what success looks like. A fixed-scope assessment gives you a measured baseline, a build, buy, improve, or stop recommendation, and an investment estimate—before you commit to implementation.