RT
AI engineering consultancy

AI architecture for systems that cannot stop.

Enterprise harnesses and specialized agents to modernize and maintain legacy systems, support ERPs and speed up engineering teams.

Top-down view of a desk with a notebook of diagrams, a keyboard and coffee

Companies that trusted Rvffers Technologies.

An AI boutique with roots in digital transformation.

We started in 2020, in the middle of the pandemic, helping companies take their operations digital when everything had to change at once. In recent years we went all in on artificial intelligence. Today we are a boutique consultancy that refines how companies put AI to work in real systems.

  1. 2020

    Founded in the middle of the pandemic, supporting companies through digital transformation.

  2. Recent years

    Built deep expertise in artificial intelligence: architecture, agents and enterprise harnesses.

  3. Today

    A specialized boutique: refined AI consulting, depth over volume.

The model is a commodity. The harness is the edge.

Everyone has access to the same models. What separates a pilot from a production system is the engineering around them.

  • Guardrails and permissions
  • Tools and MCP
  • Data and RAG
  • Models and routing
  • Evals and observability across every layer

AI architecture

Models, RAG, routing, cost and security designed like any critical system: with requirements, trade-offs and metrics.

Enterprise harness

Context, tools, permissions, evals and observability standardized so every team runs agents under the same rules.

Hands arranging paper cards into columns on a table

Agent orchestration

Specialized agents that plan, execute and verify, with a human in the loop where the risk calls for it.

Calipers and a ruler on a technical drawing

Is your team ready for coding agents?

Eleven questions on harness, legacy and delivery. In about two minutes, see where agents help and where they add risk.

Legacy modernization

Your legacy systems don't need heroes. They need a harness.

We build a harness for each legacy platform: agents that understand the old code, preserve the business rules and drive the migration end to end.

  1. Map

    Agents read source code, job scripts and data definitions to build the dependency graph and a catalog of business rules.

  2. Lock in

    Characterization tests capture current behavior before anything changes. Nothing migrates without proof of equivalence.

  3. Migrate

    Incremental replacement, module by module, with old and new systems running side by side until cutover.

  4. Sustain

    We stay through post go-live, train your team and hand over the harness so the evolution continues in-house.

Platforms we cover

  • COBOL
  • JCL
  • CICS
  • PL/I
  • Assembler z/OS
  • RPG / IBM i (AS/400)
  • Natural / Adabas
  • Clipper
  • dBase
  • FoxPro
  • Visual FoxPro
  • PowerBuilder
  • Delphi
  • Visual Basic 6
  • Oracle Forms
  • Progress 4GL
  • Informix 4GL
  • Uniface
  • Magic / uniPaaS
  • Gupta SQLWindows
  • DataFlex
  • Clarion
  • GeneXus
  • MUMPS
  • Fortran
  • Access / VBA
  • Lotus Notes
  • Classic ASP

Vibe coding fails silently on legacy code.

In batch jobs, wrong output looks valid, and a generic agent doesn't notice. Our agents fix and extend your legacy systems in place, from mainframe to desktop, inside a harness built for each stack.

An old computer terminal next to a modern laptop
  • Verification

    Generic agent or vibe coding: Reports success without compiling or running anything. Wrong output passes as correct.

    Specialized harness per stack: Compiles every change in a sandbox, never in production, and diffs output against the golden master byte by byte.

  • Context

    Generic agent or vibe coding: Greps for names, misses links between programs, includes and job scripts, then invents plausible definitions.

    Specialized harness per stack: A dependency graph and a business-rule catalog your team signed off on. The agent checks impact before editing.

  • Data layouts

    Generic agent or vibe coding: Guesses the record layout. The program compiles and the file comes out wrong.

    Specialized harness per stack: A data dictionary with layout, packed fields and encoding for every record. The agent checks instead of guessing.

  • Change scope

    Generic agent or vibe coding: Rewrites and reformats far more than the fix needs. Review becomes the bottleneck.

    Specialized harness per stack: Hooks block reformatting, renames and edits outside the declared scope. Minimal diffs, ready for change control.

  • Production access

    Generic agent or vibe coding: With write access to the host, one bad guess becomes an incident.

    Specialized harness per stack: Writes, job submits and deploys need your team's approval and leave an audit trail.

Agility in the AI era starts before the code.

Code got cheap. Choosing what to build didn't. Scrum organizes delivery, but with agents the bottleneck becomes deciding, reviewing and validating. We complement Scrum with Kanban, continuous discovery and portfolio bets.

A hand moving a sticky note on a kanban board

How we run projects with agents.

  1. Kanban with WIP limits

    People and agents on one board, with WIP limited by human attention on review and testing. Forecasts come from cycle time and throughput, not story points.

  2. Discovery with Opportunity Solution Trees

    The product trio talks to customers every week and maps opportunities, solutions and assumption tests. AI speeds up synthesis without replacing real customers.

  3. Dual-track: discovery and delivery

    Disposable AI-built prototypes test value and usability with real users (build to learn). Only what passes that filter enters the delivery flow.

  4. Venture-style bets

    Each initiative becomes a bet with a hypothesis, metered funding and kill criteria. Cheaper experiments make room for more, smaller bets.

  5. Specs and small batches

    Agents get a spec with executable acceptance criteria, not just a user story. Small batches keep every PR reviewable by a human.

How we measure delivery.

  1. Deployment frequency

    How often value reaches production.

  2. Change lead time

    From commit to user, with no hidden queues.

  3. Change failure rate

    How much of what ships needs fixing.

  4. Recovery time

    How long it takes to get back to normal after a failure.

  5. Rework

    Unplanned deploys to fix the previous one.

Specialized ERP support, with AI working next to your team.

Support, customization and reporting for the main ERP families on the market. Agents connected to your data with the same permissions your users have.

  • Close and reconciliation

    Agents cross-check ledgers, flag mismatches and prepare the close for human review.

  • Natural language questions

    ERP queries over MCP that respect the access profile of whoever is asking.

  • Assisted customization

    SuiteScript, ABAP, X++ and AL written with a dedicated harness, tests and review.

  • L2 and L3 support

    Ticket triage, root cause analysis and fixes with full traceability.

An archive with shelves of binders and a person reading a ledger
  • NetSuite
  • E-Business Suite
  • JD Edwards
  • PeopleSoft
  • Oracle ERP Cloud
Training

Full-team training in agentic engineering.

Harness engineering, context engineering, agentic RAG, MCP, multi-agent orchestration, evals and AgentOps. Your team comes out building and running agents in production.

  • A team in a workshop around laptops, with a whiteboard of diagrams behind them
  • Harness fundamentals

    • Agent loop and ReAct
    • AGENTS.md and CLAUDE.md
    • Skills, hooks and subagents
    • Harness versus model
  • Context engineering

    • Context rot and compaction
    • Progressive disclosure
    • Prompt caching
    • Cross-session memory
  • RAG in production

    • Chunking and embeddings
    • Hybrid search and reranking
    • GraphRAG
    • Agentic RAG
  • Tools and protocols

    • MCP: servers and OAuth
    • A2A between agents
    • AG-UI
    • Tool design
    • Computer use
  • Multi-agent orchestration

    • Planner, executor and verifier
    • Topologies and handoffs
    • Deterministic workflows
    • Parallelism with verification
  • Evals

    • Golden datasets
    • LLM-as-judge
    • Trajectory evals
    • Eval gates in CI
  • Guardrails and security

    • Prompt injection
    • Lethal trifecta
    • Sandboxing and permissions
    • OWASP Top 10 for LLMs
  • AgentOps: observability and cost

    • Tracing with OpenTelemetry GenAI
    • Token budgets
    • Model routing
    • AI gateway
  • Model customization

    • Fine-tuning with LoRA and QLoRA
    • SFT, DPO and RFT
    • Distillation
    • When not to fine-tune
  • Spec-driven development

    • Spec, plan and tasks
    • Specs versioned in the repo
    • Verifiable acceptance criteria
    • Reviewing agent-generated PRs
    • AI-native SDLC
  • AI governance

    • Data privacy for LLMs
    • EU AI Act
    • ISO/IEC 42001
    • Usage policy per team

Spec-Driven Planner.

Turns requirements into versioned specs, plans and atomic tasks ready for coding agents.

A printed specification document next to a closed laptop

Tell us about your setup.

The person who replies is an architect, not a sales script.

Systems involved, timeline and what you already tried help a lot.

We only use your details to follow up on this request. Privacy policy