Frequently asked questions

We start with your business goal, users and current process. We agree on what should launch first, dependencies and missing information. Then we define stages, an estimate and responsibilities.

No. A description of the problem, examples and your current workflow are enough to begin. If a specification is needed, we prepare it during discovery and review it together.

Deliverables are defined in the project proposal and contract. Depending on scope, they may include flows, design, developed code, configuration, documentation, access and usage instructions. Each stage states what is handed over and how it is accepted.

We work in stages with review points. We show what is ready, what comes next and which decisions are needed. Changes to scope or timing are estimated and approved before implementation.

We prepare production, check the agreed workflows and hand over relevant access. We plan release so someone can verify critical functions and coordinate any immediate fixes.

Maintenance can cover updates, monitoring, backups, fixes and support. Frequency, response times, included hours and any SLA are agreed separately based on the project’s criticality.

We define role-based access, protect data in transit and configure environments for the project. We review dependencies, backups and access at launch. Special compliance or audit requirements belong explicitly in the project scope.

Ownership of deliverables and access transfer are defined in the contract. We recommend that the client owns the domain, infrastructure accounts and third-party services, granting the team access for delivery and support.

The portfolio shows delivered features and suitable measures for each project: enquiries and form completion for a property website, processing time and adoption for a CRM, and orders for an online store. We do not publish growth percentages or hours saved without before-and-after data validated by the client.

Yes. Providers with documented APIs or modules include maib and Paynet for payments, and Poșta Moldovei and Nova Post for delivery. An order can reach the CRM, receive payment confirmation, create a shipment and update its status. Feasibility depends on merchant agreements, the store platform and API access; we review these before quoting.

Sources

• maib e-commerce
• Paynet for merchants
• Poșta Moldovei API
• Nova Post API

We discuss the goal, users, current workflow and bottlenecks. We review existing data and systems, map the main journeys and prioritize a first stage. The outcome is a clearer project scope, proposed features, dependencies and an indicative estimate; exact deliverables are agreed in the proposal.

Sending forms to a CRM is different from two-way synchronization of customers, orders and sales automation. The calculator uses €7,000–€15,000 as a reference band for connected business processes, but an isolated integration can cost less. Timeline and final quote depend on APIs, data quality, workflows and the current website.

The warranty period, covered defects and reporting process are defined in the project contract. Maintenance for updates, monitoring, backups or new features is agreed separately. If you need contractual response times or out-of-hours support, we discuss an SLA suited to the project.

An existing CRM can launch faster if your workflow fits the features and integrations available in the chosen subscription. A custom system gives more control over flows and data but requires discovery, development and maintenance. We compare total cost, integration limits, team adoption and who operates the system.

A useful first stage is often a fast website with property pages, clear filters and forms that send enquiries into a simple CRM. Each enquiry can be assigned to an agent and tracked through a viewing. A full ERP or large custom platform only makes sense when the volume and workflow require it.

An informational website explains your offer and collects contacts. A connected platform stores data, roles and statuses, assigns tasks and synchronizes orders or customers with CRM/ERP. That adds integration, administration and maintenance; choose based on what the team must do after an enquiry arrives.