Bring requests together
Give customers one clear way to reach the team.
See how
A portal gathers needs and attachments into a case with a category, owner and visible status.
See an examplePortals and internal tools that bring cases, roles and decisions together.
Clear ownership. Traceable next steps.
An access request moves from portal to role-based review.
Give customers one clear way to reach the team.
A portal gathers needs and attachments into a case with a category, owner and visible status.
See an exampleSee what is waiting, who owns it and what is missing.
Staff sort cases by status and role, then see the next agreed action without searching through spreadsheets.
See an exampleShare relevant status without exposing internal work notes.
A customer portal can show milestones and requested information while internal decisions stay with the team.
See an exampleFollow example AP-204 through a demonstrative portal and case flow.
The portal creates a structured example with the requested access and team.
No steps performed yet.
One user group and one clear job to be done.
Ownership, statuses and access are defined before build.
Sources, direction and error handling are agreed.
Agreed operations, ownership and future priorities.
Products and services we operate
Not always. Standard tools can become expensive when they require manual work, poor processes, or several separate systems. The right scope is decisive, and sometimes the right answer is not to build at all.
Scope drives the work: number of user groups, flows, integrations, and production requirements such as access, logging, and operations. An internal portal against one system is different from a customer-facing product with many integrations. Aprex gives no fixed price without seeing the need; send a description of users, flow, and systems for a concrete assessment.
Start with one clear user group and one core flow. The first version should prove value, not cover every future wish. The prototype tests whether the flow is understood before anything is built for production.
That can be assessed after a technical review. Before further development, code quality, security, deployment, dependencies, and data model should be mapped. Sometimes it is cheaper to build new around a core that is kept.
Keep scope clear, use established frameworks, document central choices, automate deployment, and make debugging and further development straightforward. Aprex chooses boring, proven technology where possible.
The business owns the solution, the code, and the data under agreed terms, with documentation that makes it possible to operate and develop further without being locked to one vendor.
Ready-made AI tools cover general needs, but rarely your exact flow, data, and lines of responsibility. Custom pays off where AI must connect to your own systems with access, logging, and approval. The guide on AI agent versus chatbot shows the difference.
Access control, data minimization, logging, and secure deployment routines are part of the delivery from the first production version. Sensitive data and production-near integrations are clarified before operations. Read more on the security page.
Custom software fits when standard tools create too much manual adaptation, poor data quality, weak integrations, or the wrong workflow. It can also fit when the business has a unique process that becomes an advantage if supported better digitally. The signs are often clear: employees maintain parallel spreadsheets because the system does not show what they need, new hires spend weeks learning workarounds, or management lacks figures because data sits scattered. Before Aprex recommends building, the team always checks whether a standard tool with the right setup or a simpler integration solves the problem more cheaply. Building custom is right when the workflow is the core of the business and the tool must follow it, not the reverse.
Aprex can start with a narrow prototype that tests user flow, data model, integrations, and value. When the first version works, the solution can be extended with access control, logging, operations, performance, security, and maintenance. The prototype is deliberately unfinished in everything except the core flow: it should answer whether users understand the solution and whether it solves the problem, not impress with features. Only once that is confirmed are the production requirements added: roles and permissions, audit logs, backups, monitoring, performance under load, and documented deployment routines. This avoids the classic trap where everything is built at once and nothing gets finished.
AI can be built in where it helps the user: document search, text suggestions, summarization, quality control, report drafts, or agent-based actions. AI should be clearly scoped and tied to responsibility, not added as decoration. In practice that means AI features get their own boundaries: which data they read, what they suggest, who approves, and what gets logged. Users should always see whether content is an AI suggestion or confirmed fact, and the way back to the source should be short. Aprex builds AI into the product flow where it saves time or reduces errors, and leaves it out where rules and good forms do the job better.
Custom software should not become another isolated system. Aprex can connect the solution to CRM, ERP, forms, databases, document storage, email, dashboards, and other tools already in use. Integrations are planned before the data model is locked, so the system speaks the same language as the rest of the business from day one. Each connection gets a defined direction, frequency, authoritative source, and error flow, just like standalone integration projects. The result is that the new solution strengthens the data foundation instead of creating another island with its own figures.
Illustration 1: A trades company replaces paper forms and messages with a simple field portal where employees register hours, materials, and photos per job, while the office approves and sends the basis to invoicing. Illustration 2: A member organization gathers applications, dues, and events in one dashboard instead of three systems and manual reconciliation. Illustration 3: A production team gets a deviation and maintenance tool where floor observations become tasks with owners, deadlines, and history. These examples are illustrations, not descriptions of customer setups.
Step 1, understanding: Aprex maps users, workflows, systems, and pain points together with the people doing the job today. The deliverable is a problem description with a clear user case and measurable signs of value. Step 2, prototype: A clickable or working prototype tests the core flow with real users before anything is built for production. Step 3, first version: One scope is built complete with integrations, access control, logging, and documentation. Step 4, trial operation: The solution runs in bounded operation while errors, performance, and usage patterns are measured. Step 5, operate and develop: Ownership, monitoring, and maintenance are agreed, and new needs are prioritized by measured value instead of wish lists.
Custom solutions rarely live alone. Typical categories they connect to are CRM and case tools for customer and case data, ERP and accounting for orders and finance, identity and login services for secure access, email and SMS for notifications, document storage for attachments, and external APIs for maps, payments, or lookups where needed. Aprex chooses established frameworks and documented interfaces, so the solution can be maintained and extended without depending on one single developer or an obscure library.
Custom fits poorly when the need is covered by a mature standard tool with the right setup, when the budget cannot carry maintenance over time, or when requirements change so fast that a custom-built system is outdated before it is finished. It also fits poorly when the business really needs to standardize its process rather than systematize the exceptions. Aprex will say so when the mapping points there, and help with selection, setup, or integration of standard tools instead. Not building is often the most profitable advice.
Aprex operates products alongside client projects. TapInn is operated by Aprex and brings together check-ins, checklists, HSE, deviations, documentation, and integrations for field employees. Hej CRM is Aprex AS's current CRM product. It replaces the earlier Farled concept. The product was previously named Dealo. 24AI and 24Markets are lab products that demonstrate automated data flow and publishing in production-like operation. Common to all is product discipline: narrow scope, real users early, and extension based on measured value.
Aprex should build software that can handle change. That means clear scope, simple architecture where possible, real user feedback, and honest prioritization of what must be built now and what should wait. Where standard tools are better, Aprex says so rather than building something the business does not need.
Combine tasks, data, documents, and decisions in one work surface for the team, with roles and access control.
Show key figures, operations, status, deviations, and decision support from several data sources with visible sources.
Support workers in the field with check-ins, checklists, images, deviations, and documentation. TapInn is operated by Aprex.
Read moreBuild the first version of a product, test the market, and improve with actual use. Hej CRM is Aprex AS's current CRM product. It replaces the Farled concept, and the product was previously named Dealo.
Read moreCreate internal copilots, document workflows, or AI assistants that sit inside a broader work surface.
Read moreBuild control panels for content, customers, products, cases, offers, or operational work.
How a small business picks the right AI partner.
Read moreThe method behind the deliveries: mapping, prototype, pilot, operations, and improvement.
Read moreTell us where work gets held up. We will explore the options together.