Custom business systems for your whole organisation

When does a dedicated solution make sense?

The same order number goes to several sheets, the status must be determined by phone, and the report depends on the memory of one person. Symptoms like these show where tools have stopped keeping up with the way you work.

We look at recent cases: what information was transcribed, where the decision was pending and what prompted the corrections. On this basis, we choose the area of ​​the first change and the method of assessing its result.

Stages of implementing a dedicated system

After the analysis, we prepare the agreed stage, verify it with examples and plan the migration. Users test normal actions and exceptions, and the technical team checks roles, integrations, and recovery.

• description of the scope and acceptance criteria
• data model and key process prototype
• trial migration and data reconciliation
• implementation, user preparation and maintenance plan

Configuration, integration or a new module?

Not every problem requires building an entire system. First, we check whether our tool can be configured, connected to another one or supplemented with a missing step.

A dedicated solution makes the most sense where the company's way of working requires its own rules and workarounds in a ready-made program become expensive. We compare the scope of change, data to be transferred and subsequent maintenance.

The system should be understandable and usable

Before we start, we determine the scope of rights, sources, documentation and access provided in accordance with the contract. We describe dependencies on licenses, external services and administrative accounts.

We relate receipt to user tasks: a correct document, a found record or a completed order. We also determine how to report bugs, select subsequent changes, and assess their impact on existing work.

• Description of the data model and the most important process rules.
• List of integrations, schedules and responsible persons.
• Instructions for restoring the environment and working with backups.
• Acceptance criteria and agreed scope of care.

System architecture: FileMaker, web and integrations

We can develop the business system in Claris FileMaker or prepare it as a web application with a React interface, server logic and a PostgreSQL database. In a combined solution, each part has a specific task: the office works in FileMaker and the client uses the portal.

We design the integration layer so that the process is traceable: it is known who performed the operation, where the result was saved and how to resume work after an error. We select the scope of technology together with the plan for maintaining and developing the team's competences.

System configurator and self-administration

The scope of changes available to the administrator is determined during design. The configuration panel can allow the team to independently change dictionaries, fields, forms, permissions, process rules and print templates.

A more advanced solution can also provide email and SMS notifications, data queries, service settings and configuration versions. Changes go through permissions checks, previews, and tests before they impact users' work.

• Fields, tables and views tailored to user responsibilities.
• Processes, business rules and notification conditions.
• Document templates, reports and query parameters.
• Change history, configuration versions and the ability to return.

Mobile system for service, sales and warehouse

The app can link the task to a GPS location, navigation to the customer's address, a photo, recording or pickup signature. The code scan identifies the product or order, and the file number allows you to start a conversation and save its findings.

We select FileMaker Go, a PWA web application or a separate interface depending on the devices and working conditions. Access to camera, microphone, location and files requires appropriate permissions; We check network loss and synchronization scenarios on target devices.