NO / EN
Tell us what you want to build →
Contact

Contact Aprex about AI, automation and software.

Send a short description of the workflow, systems, and problem you want to solve. Aprex can respond best when the message includes concrete details about process, data, users, and desired outcome.

Send a request →Requests that fit well ↓

Last updated: September 22, 2026

Send a request.

Briefly describe what you want to solve. We assess the need and reply with a concrete next step. You do not need a finished specification.

Your information is sent to Aprex to follow up this request. Avoid sensitive information. How we handle your information.

You can also email post@aprex.no.

  1. 01

    When should you contact Aprex?

    Contact Aprex when a manual process takes too much time, when data needs to move between systems, or when you want to test whether AI can be used safely in a specific workflow. Good first requests often involve document flow, internal assistants, field work, reporting, customer follow-up, or integrations.

  2. 02

    What should the first request include?

    Describe who uses the process, which systems are involved, how often the task happens, where errors or waiting occur, and what a successful pilot should prove. It does not need to be long. A couple of sentences is enough to start the conversation.

  3. 03

    What happens after contact?

    Aprex first assesses whether the problem is suited for a scoped pilot. If it is, we define scope, data needs, risk, integrations, and a realistic first version before larger work starts.

Overview

Requests that fit well

Aprex is most useful when the task has clear operational value and can be tested in a narrow first version.

AI pilot

Internal copilots, RAG, agents, or document flow for one concrete process.

Automation

Notifications, approvals, reports, case flow, and repeatable tasks that can be systematized.

Integrations

APIs, webhooks, CRM, ERP, forms, databases, and systems that should exchange data.

Custom software

Portals, dashboards, field tools, and internal systems built around the workflow.

FAQ

FAQ

Can we send sensitive information in the first email?
Do not send secrets, passwords, API keys, or sensitive personal data in the first request. Describe the type of data and need at a high level instead.
Do we need a finished requirements document?
No. A clear problem description is often enough. Aprex can help narrow the scope and shape a pilot that tests real value.
Does Aprex take small pilots?
Yes, when the problem is concrete enough. A good pilot should have a clear workflow, defined users, and a measurable signal of value.
Trust

Contact and privacy

First contact should stay at a level that does not require sharing confidential data. If the project moves forward, access, data processing, providers, and responsibilities must be clarified before production-near data is used.

Send the first signal

Briefly describe what you do today, what takes time, and which systems or data sources are involved.

Send a request →