Cases IV ROEPA International

A decade of near-passive maintenance — and the first ten-year warm customer to debut Nexus on.

ROEPA International

Industrial · France + Spain · Director of IT · Developer · Systems maintainer · Since 2016 · ten years and counting

Sector

Industrial · France + Spain

Role

Director of IT · Developer · Systems maintainer

Engagement

Since 2016 · ten years and counting

Industry

Industrial services · France + Spain

The Receipts

The proof that The Method produces relationships

10 yr

Active relationship · continuous · the test of architectural decisions made well

2

Countries — France and Spain · industrial services · multi-site

8 h/mo

Current touch · steady · the relationship is worth more than the hours

Nexus

AI seller demo upcoming — the highest-trust place to debut

A developer engagement, in twenty-sixteen.

Started in 2016 as a developer engagement. A decade later it's still active — at a low-touch, high-trust cadence. The kind of relationship that doesn't show up in a quarterly pipeline but does show up in compounding lifetime value.

The architectural decisions made in 2016 are still load-bearing in 2026. That is the test.

Now the relationship is opening into a new chapter: Nexus AI seller demo, with ROEPA as the ideal ten-year warm customer to debut on.

Slide-deck demos to ten-year customers burn credibility. Build the integration first, then schedule the demo.

ROEPA-Nexus sequencing rule · Internal · 2026

Build well. Stay quiet. Earn the demo.

  1. I.

    Built the Rails + DigitalOcean foundation.

    Maintained for ten years with near-zero drama. The architectural decisions made in 2016 are still load-bearing in 2026 — that's the test of doing it right the first time.

  2. II.

    Stayed near-passive on purpose.

    ~8 hours per month, roughly two hours per week. Routine maintenance. The relationship is worth more than the hours; the relationship is what we protect.

  3. III.

    Earned the right to demo Nexus.

    Ten years of trust equals the highest-leverage place to debut the AI seller. Building Nexus integration points into ROEPA Rails first; the demo happens only after the code works.

  4. IV.

    Set the trigger for the upsell.

    If Nexus lands: ROEPA goes from → –8K/mo, and ROEPA becomes the case study for selling Nexus to other companies. The order matters.

Ten years of architecture ROEPA system topology diagram · drop a sanitized version
— image placeholder · drop a screenshot or photo here —

A decade of trust. A new chapter, sequenced honestly.

  • 10 yr

    Active relationship · continuous · the architectural decisions still load-bearing

  • / hr

    Best $/hr in the portfolio · the relationship is what we protect

  • FR + ES

    Stack maintained end-to-end · industrial services across two countries

  • Nexus demo gated on integration code shipping first · then schedule

What it runs on. Who runs it now.

  • Ruby on Rails
  • DigitalOcean
  • Nexus (AI seller · in dev)
  • HubSpot
Detail: User to add: specific modules built over the decade · key inflection points · French + Spanish org structure · Nexus integration scope and timeline.

— end of chapter IV —

ROEPA International

Engagement led by Brainz · ROEPA International

Same loop. Your team next.

If this pattern fits your room, let's have a conversation.

A single discovery call. Then a written, scoped Companion engagement — or a clean no, with notes on what we saw.