ORIA BY ARPIA

Build a CRM around your process, not the other way around

Describe how your team actually sells and which systems hold the data. Oria builds the CRM on that: your stages, your figures, your rules, with the permissions of each role.

  • A sales board with your figures: net sales, active customers, ticket per customer, receivables, each compared with the previous period
  • Your stages and your rules, instead of a template the team works around
  • Connected to the invoices, customers and products you already have, with the permissions of each role
SOC 2, audited by A-LIGN ISO 42001 certified, audited by A-LIGN SOC 2 Type IIISO 42001Oria by ARPIA
Start with $100 of credit or send the form and we review your case with you

Describe how your team sells

Stages, the systems that hold the data, what the board should show. A specialist answers.

No commitment. A specialist from the team answers. Your details are handled privately and never sold.

The case, on screen

The sales board of a CRM built around one company's process, on its own invoices and customers.

The sales board of the custom CRM: six figures, net sales, active customers, ticket per customer, top customer concentration, credit-note reversal and receivables, each with its change against the comparable period
SCREEN 1The board, shaped like the company's process. Six headline figures, each compared with the previous equivalent period. The colour marks the ones that moved against the business, so a manager reads the state in one look.
The week-by-week comparison of the current period against the previous one, with net sales, active customers, ticket per customer and credit-note reversal
SCREEN 2The comparison. The current period against the previous one, week by week, with the four figures the sales manager follows. The same period and filters the company uses, with its exclusions respected.

Every screen on this page is an application built with Oria and running on a company's data. Figures are the ones of that company or of a demo; none of them is a promise about yours.

The problem

The team adapts to the CRM instead of the CRM to the team.

A CRM bought off the shelf comes with someone else's process. Yours ends up in spreadsheets beside it.

The result

A CRM with the shape of your process and the data of your systems.

The board shows the figures your management already asks for, computed the way your business computes them, and each person sees what their role allows.

Before
  • A template process, renamed
  • A second copy of customers and sales, drifting from the ERP
  • Management figures rebuilt by hand
  • Changes through the vendor's queue
With Oria
  • Your stages and your rules, written into the application
  • Built on the invoices, customers and products in your systems
  • Net sales, active customers, ticket, concentration, credit notes and receivables, compared with the previous period
  • Changed in a session; the application stays yours
How it works

Three steps, inside your governed workarea.

  1. 1

    Connect the data

    Customers, invoices, products and credit notes from your ERP or accounting system, and the files your sales team keeps.

  2. 2

    Describe the process

    Your stages, your periods, the exclusions you already apply, who sees which accounts and who approves what.

  3. 3

    Oria builds the application

    The CRM opens in your governed workarea. The ERP stays the system of record; the CRM reads it and writes back only through governed actions.

The application complements the systems you already run. It does not ask you to replace the ERP or the CRM: they stay the source of record, and Oria writes back to them only through the governed actions you define.

Why Oria on ARPIA

A business application that is a safe purchase.

Oria is the interface for asking, building and using business applications. ARPIA is the operating system underneath: the data, the models, the permissions, the rules, the audit trail and the infrastructure that make the application safe to run.

Oria is the interface

Your team asks for the application, builds it in a session and uses it. One place for the request, the build and the daily work.

ARPIA is the operating system

It connects your data and systems, the models, permissions, rules, audit and infrastructure. The application runs on it; your systems stay the source.

The model can change

Anthropic, OpenAI, Gemini, open models or your own: assigned by configuration. Change the model and the application keeps working; nothing is rebuilt.

The assets stay yours

Data, business logic, applications and the record of every action remain under your company's control, in your workarea or your datacenter.

Oria is the application layer of the ARPIA Enterprise AI Operating System. How the operating system works, on arpia.ai →

SOC 2, audited by A-LIGN ISO 42001 certified, audited by A-LIGN

ARPIA holds SOC 2 Type II and ISO 42001, both audited by A-LIGN across the platform Oria runs on. The reports are available on request.

Security, control and integration

Six answers before you sign anything.

Where is my data?

In your workarea, on infrastructure ARPIA runs in the region you choose at signup: LATAM, the United States or the United Kingdom. For a higher bar, the platform deploys inside your datacenter. Your systems stay the source; Oria works on a governed reflection of them.

Is it used to train public models?

No. ARPIA runs isolated from the model providers under zero data retention contracts, and each workarea is its own tenant.

What can each user see?

What you define. Every person opens the application with their own permissions inside the workarea: the Pro seat that built it shares it, and each seat sees the data its role allows.

How does it connect to the ERP, CRM, files and APIs?

Oria builds on the systems you already run and the files you provide: databases, exports, documents, APIs. The application reads live data from them and writes back only through governed actions, with approval where you want it.

What is recorded and auditable?

Every action, with who ran it, on what data, with which model and at what cost. Oria never writes to your live systems on its own.

Can I change the model or the provider?

Yes, by configuration. The application is built on your data and rules, not on a model, so a new model does not mean a new application.

Questions about this case

What people ask before they start.

Do we have to leave our current CRM or ERP?

No. Oria builds on the data you already have. The new CRM can run beside the current tools and replace them only when you decide to.

Can it follow our stages and exceptions?

Yes. The stages, the periods and the exclusions you already use, like lines marked as omitted, are part of what you describe, and the application applies them the same way every time.

Who sees which customers?

What you define. Each person opens the CRM with their own permissions inside the workarea, so a seller sees their accounts and a manager sees the whole board.

Can we export the data?

Yes. The board exports to CSV, and the data itself stays in your systems and in your workarea.

Does the sales team need to learn a new tool?

The application follows the process and the names the team already uses. What changes is where the work happens, not how the team sells.

How long until we have the application?

It is built in a session with Oria. How long that takes depends on your data, your rules and how many systems are involved, so we would rather see your process first than promise a number.

What does it cost?

A Pro seat at $50 per user per month to build and share, Basic seats at $15 per user per month to use the application, and a prepaid wallet for the AI that you size and cap. Every new workarea starts with $100 of credit, and nothing is charged until you add billing details. Prices on the home page.

Two ways to start.

Create a workarea and build it yourself with $100 of credit, or send the form and review the case with the team first.

Pricing: a Pro seat at $50 per user per month, Basic seats at $15, and a prepaid wallet for the AI. Nothing is charged until you add billing details.