IVRYN vs Matters for product, technology and AI work

Read the two public positions first

On the French official page reviewed on 15 August 2026, Matters uses the position “Studio Produit, Tech & IA” and presents routes for prototype or MVP work, evolving an existing product, innovation, Product or Tech support, FinOps, Tech or UX due diligence and AI. The reviewed page was in French. This breadth makes the first scoping question important: which route is being proposed and what does it exclude? Confirm the team and deliverables instead of assuming that every listed discipline participates in one engagement.

IVRYN publicly describes itself as an independent Paris product studio that designs, engineers and operates its own products and a few for others. Its public methodology separates implementation evidence from adoption or commercial outcomes. The public site does not publish a universal package, fixed price or guaranteed availability, so those points require a project-specific written proposal.

Compare the engagement, not the slogans

Do not compare a due diligence assignment with a product build or an AI exploration with ongoing Product or Tech support. Write the decision that the engagement must enable, the artefacts required, the system access allowed and the end condition. Ask Matters to map its proposed service track to those requirements. Ask IVRYN to map its design, engineering or operating responsibilities to the same brief. If an existing product is involved, include current architecture, telemetry, incidents, debt and internal owners so both proposals start from equivalent facts.

Treat every statement on either studio’s website as a disclosure to verify, not as an independent test result. Ask for the current named team, written scope, repository and provider-account ownership, acceptance evidence, maintenance responsibility and exit route. A polished portfolio or a stated delivery window does not show how the exact people, constraints and risks of your project will be handled.

Inspect ownership and operating proof

FinOps, due diligence, AI and product delivery each create different authority boundaries. A review may only advise, while a delivery team may change code or infrastructure. An AI component may touch sensitive data or make consequential suggestions. Require Matters and IVRYN to state who may inspect, decide, implement, deploy, approve spend, access data and respond to failure. Keep client organisations in control of repositories and provider accounts where the client owns the product, and define how recommendations become authorised changes.

Keep source control, domains, stores, analytics, cloud organisations and production credentials under explicit organisational ownership. Grant scoped, revocable access and rehearse handover before the final invoice. The supplier label matters less than whether another authorised person can inspect, deploy, recover and continue the product.

Run one comparable first engagement

Select the riskiest decision and test it with the same access and evidence request. For an existing product, the first engagement could inspect one critical journey and produce prioritised findings plus a verified corrective slice. For AI, it could define representative evaluations, human review and safe failure before any production integration. For a new product, it could test a thin end-to-end outcome. Ask each studio to say what the result proves, what it cannot prove and what would justify continuing.

Use the same bounded first engagement for both candidates. Give each the same problem, non-goals, user context, decision owner and evidence request. Compare the questions asked, assumptions recorded, scope removed, risks raised and artefacts left behind. Do not compare two vague sales calls or ask one candidate for discovery while asking the other for a fixed build.

Choose for this product and recheck

Matters may fit the shortlist when its published product, technology, AI, support, FinOps or due diligence routes align with a clearly named decision. IVRYN may fit when the buyer wants to evaluate an independent builder-operator model with explicit public boundaries around implementation and outcomes. Neither public position proves sector knowledge, individual availability or execution quality for this brief. Compare the named experts, access level, service track, artefacts, acceptance, operation, data authority and handover in writing.

There is no defensible universal winner. The useful result is a documented fit decision for one product, one stage and one operating model. Recheck mutable information on the official sites and in the final proposal before signing. Availability, staffing, pricing, timelines and service details may change after this review date.

Decision criteria

Use the same questions for every option before choosing.