Implementation and configuration of existing software

You may already have chosen a product or still be looking for one. We start with the people who will use it, the data they need and the steps from receiving a request to completing the work. This establishes what can be configured and what needs additional development.
What can we implement?
- A CMS website. WordPress or DominPress, including content structure, a selected theme, forms and agreed features. The choice depends on how you publish and plan to develop the website.
- An online store. PrestaShop or Magento, including the catalogue, variants, shipping, payments and agreed connections to business software. For an existing store, we first check its version and custom changes.
- CRM or process management software. Data, workflow stages, users, permissions and required reports configured in the chosen system.
These are examples rather than a closed product list. We can also assess software you already use or are considering. Before quoting, we check its features, licence, subscription tier and options for extension.
Connecting tools into a working process
An implementation can include data exchange between a website, store, CRM, warehouse or accounting application. For example, a form could create a CRM case, while an order status change could pass information to the next application.
Feasibility depends on the product's APIs, webhooks, imports and access permissions. We agree the source of truth, direction of exchange and handling of failed operations. See our integration and automation service for details.
From product selection to launch
- Define the first workflow. We agree users, required data and acceptance criteria. If selecting a product requires more investigation, we agree a separate analysis stage.
- Configure the software. We prepare the agreed settings, roles, views and features, with a defined scope for extensions and custom changes.
- Check data and connections. Migration starts with field mapping and a trial import. Integration checks also cover errors and retries.
- Review the result. We walk through the agreed scenarios and hand over the information needed to use the configuration. Launch timing and ongoing support are agreed separately.
Examples of existing foundations and custom features
Ragazza: PrestaShop connected to business software
We built product and image importers for Ragazza and Gatta, an integration with Symplex Small Business and catalogue management tools. This shows an existing store extended for a particular company's work. View the Ragazza project.
EcoChatka: DominPress, a configurator and CRM
DominPress provides the CMS and shared modules. We developed the floor-plan configurator around EcoChatka's quotation process. The configuration and calculation accompany the enquiry into the built-in CRM. This combines an existing platform with custom development; it is not a standard feature of every CMS. Read the EcoChatka case study.
What determines implementation costs?
We consider the initial work and ongoing costs: licences, user accounts, add-ons, hosting, integrations and maintenance. Existing features reduce the need for new code, but adaptation and data migration still take work. With DominPress, we reuse shared mechanisms to reduce repeated development across projects.
If a product's limits obstruct an important workflow, we can propose a custom module or business system. Scope, price, acceptance criteria and working arrangements are agreed before work starts.
Tell us what you want to implement
Name the software if you have selected it and explain what should change in your business. Describe the data sources and applications that need to work together. A description is enough for the first message; access and sample data are arranged separately.
Describe your project
Describe what you want to build or what is not working. Include the programs you use and the outcome you need. You can paste an existing description or summary.