What you keep
You keep the working product.
An RJL engagement ends with AI workflows running in your cloud account, the code and specification behind them, and an operating model to run them.
Left behind with you
Six things you keep when the engagement ends.
Most AI engagements end with a recommendation deck or a software subscription. This one leaves the platform-neutral specification and an agreed operating model so your team can run and grow the workflows. Your CFO funds each step only after the last one has shown its return.
The method, published
26 whitepapers set out how data, AI and security fit together as one working system, from ownership and contracts to release evidence. You can read every one before we talk.
A specification for any platform
A product requirements document built from those papers: what each component must do, the contracts between them and the evidence each control produces. It names no single vendor, so it maps to the tools you already run.
A starter platform in your own account
A starter platform on AWS, deployed into your cloud account and hardened with your team: your sign-in, your encryption keys, your logging and your network rules. Your data stays in your account.
AI workflows built on your data
We choose the workflows worth redesigning, prove them on your data and controls, and take them into production with your team, starting where the return is clearest.
The code, yours to run
You own everything built for you: your workflows, configuration, changes and data. Your license to run and change the starter base delivered with it is permanent, with no fee. There is no RJL subscription; you pay your cloud provider for what you use.
An operating model and a path forward
Who owns each workflow, how it is funded, monitored and changed, and the signals that say when to expand. Agreed with your business and finance leaders before handover.
How it fits together
Read the method. Try it. Keep it.
Read it: free, no form.
The whitepapers and the book →
The method in full: architecture, data products, agents, governance evidence, AI economics and the operating model.
Try it: five-minute demos.
Ontology Studio and Workflow Studio →
The method as working tools: approve what words mean, then run a reviewed workflow on that meaning.
Keep it: in your environment.
An engagement →
The same method built on your data, in your cloud account, with your team, and left with you to run.
Why finance can lead it
Prove the return before you invest at scale.
Each phase ends in a decision your business and finance leaders make on evidence. Frame agrees the workflow, its owner and today’s baseline. Prove tests it on your data against acceptance criteria and stop conditions. Build releases it. Operate and transfer hands it to your team under the agreed operating model.
You fund the next phase only when the last one has shown it is worth it, and you can stop after any phase. The people whose work changes help design it, so adoption is part of the plan rather than an afterthought.
How the four phases run See a sample business case AI Token Economics
For private equity and venture investors
Value you can show, in a company that owns it.
A portfolio company gets AI workflows into production without a large up-front program or a new platform subscription. Spend follows evidence one phase at a time, so the case for scaling is made on the company’s own numbers.
What is left behind is an asset the company owns and can document: running workflows, the code, the specification and an operating model. That is easier to defend in a value-creation plan, and easier for a buyer’s diligence team to inspect, than a vendor dependency or a strategy deck.
Fractional leadership and investor due diligence See a sample first-workflow business case
How this differs
Senior judgment, left behind in working form.
Software companies sell a platform you rent. Large firms bring large teams and, increasingly, their own platforms. RJL brings a published method and a senior operator who has answered to regulators for the result, and leaves the product with you.
| Software vendors | Large consultancies and integrators | RJL Solutions | |
|---|---|---|---|
| What you are left with | A subscription to their product | Recommendations, or a build on the firm’s own platform | Running AI workflows, the code, the specification and the operating model |
| Who does the work | Their product, plus their engineers | A large team, mostly junior, led by a few senior people | A former Chief Data Officer with bank, insurer and Federal Reserve experience, involved all the way through, with specialists you approve by name |
| Lock-in | Their platform | Their platform or their people | None: it runs in your account and works with your tools |
| How spend is decided | Seats or usage | A large program agreed up front | One phase at a time, with the return shown before the next |
| The method | Private | Private | Published: 26 whitepapers you can read before you call |
Ownership
What is yours, and what RJL keeps.
You own everything built for you: your use cases, your configuration, your changes and your data. Nothing specific to your organization is reused for anyone else. RJL keeps the reusable starter and the method, which is why you do not pay to build them from scratch, and your license to run and change what is delivered is permanent, with no fee. The exact terms are set out in the written proposal before you commit.
Next step
Bring the workflow. Keep what we build.
Tell Richard where the work is stuck. The first conversation is free, with no obligation.