Portals and apps for your process.
Customer portal, internal application or partner area: one place for the case, instead of inbox, phone and lists. Everyone sees what they are meant to see.
The process shapes the interface
Who enters something, who checks it, and what is the next step? These questions become a process in which inputs, documents and status sit together.
From that we create the views for your user groups. We plan design and technology together and test them on the cases that actually occur in your business.
Connected to what you already have
If the application is to work with existing systems, we define purpose, data and permissions for each connection. Roles determine who sees and decides what.
Data migration, external services, operation and later extensions are separate items in the proposal – with requirements and costs, before we build them.
Discover the FACTORY · with Pascal, NeX and AIFly ORACLE
This tour connects our services, products and project steps. You can also open each section directly.
Clarity before the first step.
The answers describe scope, process and limits so you can place your project with confidence.
Describe your projectWhat is it?
Customer portal, internal application or partner area: one place for the case, instead of inbox, phone and lists. Everyone sees what they are meant to see.
Who is it for?
For businesses providing customers, staff or partners with a dedicated digital workspace.
How does it help you?
Inputs, documents and progress are connected to each case. Roles define access and decisions.
What is included?
Who enters something, who checks it, and what is the next step? These questions become a process in which inputs, documents and status sit together. From that we create the views for your user groups. We plan design and technology together and test them on the cases that actually occur in your business. If the application is to work with existing systems, we define purpose, data and permissions for each connection. Roles determine who sees and decides what. Data migration, external services, operation and later extensions are separate items in the proposal – with requirements and costs, before we build them.
How does it work?
Describe your project. Pascal clarifies the goal, starting point and scope. Proposal, approval, implementation, testing and handover follow. Ongoing support is agreed separately.
What does it cost?
Your proposal sets out the work and cost for your project. Hosting, software, AI consumption and any media budget are listed separately.
What are the requirements and limits?
We agree roles, data responsibilities and existing systems first. Migration and each interface have their own scope; access to third-party systems is not assumed.
What can you do now?
Describe your project in the contact form: goal, existing systems and main question. You receive a reference number; an enquiry is not an order.
How would you like to proceed?
Choose the next step that fits your project.