Skip to content
Ordinvel

Business software · Automation · Switzerland

Intelligent softwareto simplify complex operations.

We design business software and explore process automation for companies and financial institutions — with a focus on account opening, KYC/KYB and document handling.

A 15–20 minute exploratory conversation. No confidential information required.

Account opening: from overload to control

Conceptual illustration

Conceptual illustration. An employee handles an account opening; requests pile up until the workload becomes hard to control: documents to verify, missing information, files on hold. Software then structures the information: documents grouped by file, missing documents flagged, clarifications prioritised. Sensitive decisions are still taken by a person.

Conceptual illustration: documents grouped by file, gaps flagged, decisions taken by people.

Technical experience

We design and build software.

Hands-on experience in application development — applied to financial operations.

Real experience

  • Developed

    Business software & operations management

    Designing management modules within a business application.

    • Inventory management
    • Accounting tracking
  • Developed

    Administrative workflow automation

    Organising and tracking administrative tasks within the application.

    • Administrative management
  • Developed

    Document handling & KYC

    Identity verification features and management of supporting documents.

    • KYC features
    • Supporting documents

Directions

What we are exploring for financial institutions

  • Under study

    File completeness checks

  • Under study

    KYC/KYB file preparation

  • Under study

    Account opening tracking

  • Under study

    Support for compliance review preparation

Experience gained by our founder on a business application still in development. No client or project names are mentioned. This is not a commercial banking solution.

Where we are today

A young company. Working in the open.

No commercial product and no clients yet. We start by listening to practitioners — then we design.

  1. First step

    Discovery interviews

    With operations, onboarding and compliance teams.

  2. Next

    Needs analysis

    Recurring friction points, their cost and constraints.

  3. Then

    Co-designed pilots

    Only where the case is clear.

Our mission

Less administrative friction. More time for judgement.

Checking, chasing and re-keying information takes a large share of operational time. We help institutions reduce that friction — applying technology only where the benefit is clear and verifiable.

  • Needs first

    We start from the process, not from a tool.

  • People decide

    Automation supports staff. It never replaces their judgement.

  • Measured

    Every gain is quantified with the teams concerned.

Areas of focus

Five areas of study.

Fields of research — not products.

  • Document Intelligence

    Reading, sorting and checking incoming documents.

    Key question

    • Which documents create the most manual work?
  • KYC & KYB Workflows

    Collecting and verifying client and company information, including beneficial owners.

    Key question

    • Which checks are repeated across teams?
  • Client Onboarding

    From a first request to an opened business account.

    Key question

    • Where do files stall, and why?
  • Operational Automation

    Repetitive tasks between systems: re-keying, routing, follow-up.

    Key question

    • Which tasks are high in volume, low in judgement?
  • Compliance Workflow Support

    Complete, well-structured files for compliance review.

    Key question

    • What makes a file ready for review?
  • Another process in mind?

    These areas will evolve with what we learn.

    Tell us about it

Our approach

Four steps. None without your teams’ agreement.

  1. 1. Understand

    Map the process as it really runs, with its constraints.

    Outcome

    A shared process map

  2. 2. Evaluate

    Measure where time, cost and risk accumulate.

    Outcome

    Quantified friction points

  3. 3. Design

    Propose a proportionate solution — sometimes simply a better process.

    Outcome

    A concrete proposal

  4. 4. Validate

    Test the expected gains with the teams concerned.

    Outcome

    Evidence to decide

Built for financial institutions

Designed for regulated environments.

Confidentiality, security and accountability are design requirements from the very first conversation.

  • Confidentiality

    Our work does not depend on access to client data.

  • Traceability

    Every automated step leaves a clear record.

  • Security

    Solutions fit each institution’s architecture and policies.

  • Human oversight

    Decisions with regulatory or client impact stay with people.

Let’s talk

A 15–20 minute exploratory conversation.

Responsible for operations, onboarding or compliance at a Swiss institution? We would value your perspective. Nothing to buy, nothing to prepare.

Who we would like to hear from

  • COOs and heads of operations
  • Onboarding leads
  • Compliance and KYC managers

What we would discuss

  • Where time is lost
  • Where files stall
  • What would help your team

Please do not send client data, documents or confidential information — we do not need any for this conversation.

Prefer email?

Write to us atcontact@ordinvel.com

Request a conversation

Required

A few words are enough. Please do not include client or confidential information.