04 / Applications & experiences
Custom applications. Connected portals.
Make business systems easier to use for employees, customers and vendors. ArcticTech designs Power Apps, Power Pages and custom software around the workflow and data behind each experience.
- People
Employees and external users
- Experience
Tasks, forms and self-service
- Access
Identity and data permissions
- Systems
Connected business records
The starting point
When standard screens leave a gap
A focused application or portal can give people a simpler way to submit information, check progress or complete a task. It is especially useful when the underlying ERP or CRM is right for the business but the user experience needs to be different.
Examples to explore include customer request intake, vendor submissions, internal approvals and status tracking. The right design starts with who needs access, what they should be able to do and where the business record belongs.
How we help
The work around the platform.
- Employee applications
Design Power Apps, model-driven applications or custom interfaces around a defined task. Simplify forms and handoffs while retaining the relevant business rules.
- Customer & vendor portals
Plan Power Pages or custom web experiences for external users. Define registration, sign-in, page access and record-level permissions before exposing business information.
- Extensions & connected workflows
Connect the application to CRM, ERP, documents and reporting where appropriate. Agree validations, status updates, errors and the responsibilities of each system.
The approach
Follow the task from screen to system
Understand the users
Identify user groups, the tasks they need to finish and the information they can access.
Choose the approach
Compare Power Apps, Power Pages and custom development against the experience, integration and licensing requirements.
Build & verify
Test usability, business rules and permissions with representative users and records.
Prepare to operate
Agree content ownership, support responsibilities, deployment and changes after launch.
Plan with the right information.
What shapes scope & cost
User groups, identity requirements, screens, permissions, integrations and document handling shape the work. External-user licensing and ongoing administration need to be considered alongside development.
Bring to the first conversation
- The task and the people completing it
- Source systems, sample records and documents
- Who may view, create or change each record
Before you begin
Questions about Applications & portals.
Should we use Power Apps, Power Pages or custom software?
Choose around the users and the task. Power Apps can suit internal business applications, while Power Pages supports external web experiences using Dataverse. Custom software may be appropriate when the experience or integration needs a different approach. Review fit and licensing together.
Can customers see only their own information?
That needs to be designed and tested. In Power Pages, table permissions and web roles govern access to Dataverse records. Define the relationships and access rules for customers or accounts, then test permitted and prohibited actions with separate users.
Can we start with one workflow?
Yes. A defined first release can focus on one task, such as request intake and status visibility. Agree the data model and access boundaries with future needs in mind, then use feedback to decide which additional capabilities are worthwhile.
Talk with ArcticTech
Give people a clearer way to get things done.
Bring the task, the users and the systems involved. We’ll help choose an application approach that fits.