Learn: We teach your teams
Technical and non-technical labs, taught on your own work and in your environment.
Labs
Teach your teams. Then build on Rayify.
Hands-on labs for business and engineering teams, taught on your own work. Then start from the solutions our practitioners built, or build your own on the platform.
Learn it. Use it. Build on it.
What Labs gives you. Labs is where we teach your teams. From there, your business teams run the solutions our practitioners built, and your engineers build their own on the same platform.
Use: Start from solutions
Workflows our practitioners have built for regulatory change, credit, claims and diligence. Adapt one instead of starting from a blank page.
Build: Engineers build on the platform
Your engineers build their own workflows on Rayify, with modules, connectors, replay and sign-off built in.
Map it. Build it. Run it.
How a Lab runs. Three steps, a few hours of your team’s time, and one workflow that works by the end.
Map the workflow worth doing first
Two short calls with your team. We look at your tools and past attempts, and pick one workflow you can ship.
Build it together in half a day
A hands-on session with our engineers, on your infrastructure. Live where access allows, deployment-ready where it does not.
Run it, with an engineer on call
Follow-on support from your dedicated engineer, a runbook for IT and security, and a plan for the next workflow.
A track for each team
Two tracks. Business and engineering teams learn on their own work, then build the same workflow together.
Business teams: Automate the work your team repeats
Investment, risk, compliance and operations teams. Prompting, playbooks and workflows in the tools you already use.
Engineering teams: Ship governed systems to production
Engineering, data and platform teams. Orchestration, retrieval, guardrails and observability, on your stack.
All labs
AI agents in financial services - Executive briefing
What boards and executive committees need to know about AI that executes actions - capabilities, risk, regulatory exposure and where value is emerging across financial services.
Code: EXEC-001 | Track: non-technical | Duration: 1-1.5 hr
Custom workflow automation workshop
Map your priority operational challenges, then build custom automated workflows on your existing infrastructure - deployed live where access allows.
Code: CORP-CWAW | Track: non-technical | Duration: 0.5-day workshop + 2-4 hrs of calls
Improving productivity with AI (non-tech)
An introductory session covering AI foundations, Claude's core features and practical task automation for non-technical corporate professionals.
Code: CORP-001 | Track: non-technical | Duration: 2 hr
Claude Connectors deep dive
A deep dive into integrating Claude with enterprise tools like M365/Google Workspace, Slack and Zoom/Webex to automate daily document and messaging workflows. Claude-first delivery; the principles transfer to your existing Microsoft/Google estate.
Code: CORP-002 | Track: non-technical | Duration: 2 hr
Agentic governance, guardrails, data and risk management
Governance for AI that takes actions, not just answers - practical guardrails, human oversight and audit trails that keep automation safe without stifling it.
Code: CORP-003 | Track: non-technical | Duration: 3 hr
Multi-team automation hackathon (non-tech)
Bring multiple teams together in person for a focused build day - shared tooling briefing, one priority automation per team, and closing presentations that spread what works.
Code: CORP-HACK | Track: non-technical | Duration: 0.5-1 day in-person
Custom workflow automation workshop (tech)
Map your priority operational challenges, then build custom automated workflows on your existing infrastructure - deployed live where access allows.
Code: CWAW-ENG | Track: technical | Duration: 0.5-day workshop + 2-4 hrs of calls
Improving productivity with AI (tech)
Turn Claude Code from a generic tool into your team's tool with scoped sub-agents, skills and shared memory.
Code: ENG-001 | Track: technical | Duration: 2 hr
Sub-agent orchestration and observability with Claude
Advanced engineering workshop on building custom sub-agents, orchestration patterns and implementing observability with telemetry. Choose this workshop if your teams orchestrate interactively in Claude Code; building programmatic pipelines in code, see ENG-003.
Code: ENG-002 | Track: technical | Duration: 0.5 day
Code-driven agent orchestration
Designing reliable, stateless, multi-agent orchestrated architectures: linear sequences, concurrent execution, smart routing. Choose this workshop if you are building programmatic pipelines via the API and Agent SDK; orchestrating interactively in Claude Code, see ENG-002.
Code: ENG-003 | Track: technical | Duration: 0.5 day
RAG and context engineering
Practical guide to building RAG pipelines, optimising retrieval quality beyond naive search, and managing context engineering techniques.
Code: ENG-004 | Track: technical | Duration: 0.5 day
Agentic governance, guardrails and security (tech)
A technical exploration of the agentic threat landscape, enforceable security controls, and red-teaming methodologies for autonomous systems.
Code: ENG-005 | Track: technical | Duration: 3 hr
Multi-team engineering automation hackathon (tech)
Bring your engineering teams together in person for a focused build day - shared tooling briefing, one priority automation per team, and closing demos with peer review.
Code: ENG-HACK | Track: technical | Duration: 0.5-1 day in-person
Built for the people accountable for AI
Boards and SMFs. Risk, compliance, model risk, data protection, security.
Frequently asked questions
Who should attend a non-technical lab?
Investment, risk, compliance, operations, fund finance and legal teams, and the people who support them. No coding is needed: we work on the tasks your team already does, in the tools it already uses.
What do we need ready before a lab?
A short list of the workflows that cost your team the most time, and the access our engineers need in your environment. We send IT a readiness checklist in advance, so accounts, connectors and permissions are in place on the day.
Does the lab run on our own infrastructure?
Yes. We build in your environment, on your keys and with your data, so nothing has to leave your perimeter. Where access is not ready on the day, we leave the workflow deployment-ready for your team to switch on.
What happens after the lab?
Your dedicated engineer stays on call for follow-on sessions to debug, work through lessons learned and plan the next workflow. IT and security receive a runbook and a technical brief.
What do we leave with?
A working workflow on your own tools, scoped to a priority your team chose, and a team enabled to run it. Follow-on calls cover implementation once the lab ends.