Software
Corporate websites, internal applications and data flow between systems. The scope of the software takes shape around everyday workflows.
Software within the workflow
Recording a request, approving it and passing it to the relevant team are parts of the same process. Software design considers the links between these steps as well as the screens. Data sources, user roles and existing applications define the scope of the solution.
Foundations of the design
Designed for everyday use
Screens and task flows are designed around the needs of the person doing the work. Mobile use and performance are considered within this scope.
Connections to existing systems
The data source, destination system and update method are considered together. Connections are designed as part of the workflow.
Access and permissions
Who can access information and perform actions is defined during design. User roles are considered alongside everyday workflows.
Designed for long-term use
Principles we follow
Accessibility
- Interfaces fully usable with a keyboard
- Sufficient colour contrast and readable text sizes
- Meaningful headings and labels for screen readers
Security
- Encrypted connections by default
- Role-based permissions and least privilege
- Regular updates of the libraries in use
Personal data
- Collecting only the data that is needed
- Practice consistent with the privacy notice
- Defined retention periods and access
Performance
- Pages and screens that open quickly
- Images delivered at suitable sizes
- Smooth use on mobile connections too
Sustainability
- Widely used, long-lived technologies
- A documented structure and handover notes
- Solutions with few dependencies that are simple to manage
Considered in every project
- Accessibility
- Security
- Personal data
- Performance
- Documentation
- Sustainability
Areas of software development
Web and application development, process automation, data and integration, and AI can form one project or separate pieces of work. The starting point is the task to be carried out, the information it needs and the role of existing systems in that workflow.
Business processes and users
Verimel Software
Data and infrastructure
Web & App Development
From the screen to the daily workflow
Corporate websites and internal applications; end-to-end development, from the choice of static or dynamic architecture to performance and mobile responsiveness.
Corporate websites and internal business applications
Content structure, user screens and task flows are designed together. Static or dynamic architecture, mobile responsiveness and performance are considered according to the application's purpose.
Architecture choice and management after launch
Static or dynamic structure, hosting and update needs are chosen with the site's whole lifetime in mind. The decision depends on who updates content and how often.
Process Automation
The flow of recurring tasks
Automating repetitive business processes with software: simplifying manual data entry, reporting and approval flows.
Automation for data entry, reporting and approval flows
Capturing information, checking it and passing it to the relevant person are considered as one flow. Automated steps and points requiring human approval are defined during process design.
Moving from spreadsheets to an application
Spreadsheets updated by several people are moved to an application according to data entry, permission and reporting needs. The familiar spreadsheet view is kept through export.
Data & Integration
Information flow between systems
Data flow between different systems (API connections, integration with ERP and operational software) and tools built for the organization.
Data exchange between applications and tools tailored to the organization
Data flow between operational and management applications is designed around the connections available. Data mapping, updates and tools tailored to the organization are considered within this scope.
Orderly data flow through APIs
Data mapping, the direction and frequency of transfers, failure handling and the permissions of the account used are written down before the connection is built.
Artificial Intelligence
Tools that work with organizational knowledge
We integrate AI-assisted search, querying and automation into existing business processes. We deliver the work in a secure, sustainable structure that fits the organization's own systems.
AI-assisted search and querying within existing processes
AI-assisted tools for search, querying and process automation using the organization's own information sources. Data access and connections to existing systems are part of the solution design.
Data order comes first
Sorting current documents, archiving old versions and checking access permissions come before any AI tool. Answers are shown together with the source they rely on.
Example scenarios
The scenarios below are general examples of how the software areas can work together; they do not describe a specific organisation's project.
Example scenario
A request and approval flow
Where requests from several departments are tracked through email and spreadsheets, they are brought into a single application. Each request is routed to the person in charge, requests above a set amount go to a manager for approval and every step is recorded.
- One record
- Request, approval and history in one place
- Role-based
- Who sees and approves what is clear from the start
Example scenario
A field team application
Where field teams report faults and jobs on paper forms or by message, records are opened from a phone, photos are attached and the person in charge at the centre is notified immediately.
- Mobile
- The same screen on phones and tablets
- Immediate
- A notification as soon as a record is opened
Example scenario
Reporting automation
Reports that are put together each month by hand from data exported from several systems are compiled automatically, with data taken from the source at regular intervals. The report is ready when it is needed.
- Automatic
- Data taken regularly from its source
- Traceable
- Where each piece of data came from is recorded
Example scenario
Integration between applications
Where the same information is entered separately into sales, stock and accounting applications, the applications are connected through APIs. A record is entered once and passed to the related systems; if a transfer fails, the person in charge is notified.
- Single entry
- The same information is typed once
- Failure handling
- Notification and retry when a transfer fails
The starting point for your software needs
A new application, a recurring task or information that needs to move between systems. The initial discussion covers the current workflow, the applications in use and the expected outcome. A brief description of your needs in the contact form is the starting point for discussing the scope of the work.