More roles and connected workflow stages.
A theme designed and coded for your brand, with its own layout and components.
We create a custom theme: layout, typography, colours and components for the agreed pages. We implement it on your chosen platform within the package scope. Additional features and integrations follow the offer description.
A process description, required data and clear first-phase acceptance criteria.
We describe the workflow, required data and user steps. This forms the basis for the agreed scope and acceptance criteria.
Access to screens, data and actions according to the user's role.
We define which screens, data and actions each role can access, based on your team's agreed workflow.
Data exchange with an agreed external service.
We connect the system to the agreed service. Before quoting, we check its documentation, authentication and data exchange scope.
Features built for your business process and way of working.
We build the features needed for the agreed process. Their behaviour and acceptance criteria are set out in the scope.
Instructions and team onboarding for the completed system.
We provide instructions for the delivered features and train the people who will use them.
New features delivered in phases, each with its own scope and quote.
We plan new features as separate phases, agreeing each phase's scope, price and schedule before work begins.
Prices exclude VAT and cover the stated scope in one language. Every package includes a custom theme created for the project. The client supplies content and a prepared product catalogue. Hosting, domains, paid licences, copywriting, advertising spend and integrations not listed in the package are charged separately. We confirm the scope and price before work begins.
We describe the workflow, roles and data, then define what must work in the first phase.
We prepare the data model, dashboard and agreed business rules.
We check the agreed scenarios, provide documentation and launch the solution.
Describe what the system should do, who will use it and which services it should connect to.
We will reply with a proposed scope, price and schedule.
[email protected]
Package limits, materials and costs beyond the build.
The package comparison and selected plan details define the scope and limits. We confirm the views, features, materials and price before starting. Work outside that scope needs a separate agreement.
Yes. We define the core workflow and first-stage scope. Further features can be developed after the system has been used in practice.
We first check API availability, documentation and provider terms. Data exchange, error handling and limitations are confirmed before quoting an integration.
We define roles and who can read, add and change data. Permissions form part of the agreed scope and are checked before handover.
We can scope a migration after reviewing the export. We need sample data, field definitions and mapping rules. Data cleanup and unusual formats are quoted according to scope.
