Websites and web services
Websites, catalogues, registration, accounts and staff systems.
Development / digital services
Websites, apps and internal systems.
We build interfaces and backends, connect data, payments and notifications, and test the complete workflow from user action to its result.
Discuss developmentFormats
What we build
Mobile apps
Bookings, payments, notifications and work away from the office.
Internal systems
Requests, documents, tasks, statuses, access and reporting.
Architecture
Software connected to your workflow
Before development, we define data sources, who can change records and how the system handles failures.
- Data and rolesRequired fields and permissions for every action.
- StatusesTransitions, cancellations and repeated requests.
- IntegrationsAPIs, reconciliation, errors and recovery.
- OperationsEnvironment, backups and error monitoring.
Development stages
- 01
Discovery
Current workflow, features and first-release criteria.
- 02
Design
Data model, interface, roles and connections.
- 03
Implementation
Working workflows and tests of permissions, data and errors.
- 04
Launch
Acceptance, agreed migration and handover.
Handover
What you receive
- A working release
- Source code and instructions
- Integration documentation
- Acceptance results
Rights to deliverables, support terms and infrastructure responsibilities are documented in the contract. We can start by improving an existing product.
Questions
Before we start
Do we need a complete specification?
You can start with a description of the task and the current process. We help formulate requirements, define the first release and prepare a basis for estimation. If you already have a specification, we check workflow coverage and constraints.
Can you connect our CRM or 1C?
We first check the system version, available API, data format and access permissions. We then define the exchange method, required changes and each party's responsibilities. Connection options depend on the specific configuration.
Who receives the source files?
The contract defines how source code, documentation and rights are transferred. We also list third-party components and services with their own licences and terms of use.
How are timelines and budgets estimated?
The estimate depends on workflows, roles, integrations, source data quality and launch requirements. For areas that remain uncertain, we first agree on discovery or a prototype, which lets us refine the development scope.
How is support arranged?
We agree request handling, updates and connection checks. Infrastructure and access responsibilities are documented separately. New features are assessed against the existing data, roles and integrations.
What needs to work?
Describe user actions and the systems that need to exchange data.
Discuss development