How we work
We describe the technical scope on the service pages. Here we explain how an engagement starts, which model fits a given situation, and how we prepare an estimate.
Direct contact with the person doing the work
From the first message through delivery of the agreed scope, you work with the person who analyzes the problem and is responsible for the technical work. There is no separate handoff between sales, project management, and delivery.
- Direct technical communication — questions and agreements do not pass through intermediaries.
- Decisions in project context — once the environment is understood, we discuss the options in the context of its code, data, integrations, and infrastructure.
- A transparent estimate — it covers the agreed technical work and the necessary coordination, without a separate sales layer.
Engagement models
Technical consultation
When you need a diagnosis, an independent technical opinion, or a clearer definition of the problem before deciding what to do next.
- A brief introductory exchange at no charge — a few messages, or a short call if useful.
- 60-minute paid technical consultation.
- We deduct the consultation fee from the project value if the work continues.
Project or implementation
For work with a defined outcome, such as store changes, migrations, integrations, infrastructure work, or automation.
- We agree the scope and assumptions before work starts.
- We define the stages and deliverables.
- The estimate is based on the agreed scope and assumptions.
Ongoing collaboration
For systems that need recurring maintenance, development, or technical oversight.
- We match the scope to the actual needs.
- We agree priorities as part of the engagement.
- Monitoring, response times, backups, and SLA apply only when explicitly included in the agreed scope.
How we prepare an estimate
You describe the context
Share the problem, desired outcome, current system state, and known constraints.
We clarify the problem together
We identify missing information and decide whether a consultation or discovery step is needed.
We agree the scope and assumptions
We separate the work included in the estimate from dependencies and items outside the scope.
You receive an estimate
We set out the engagement model, cost or billing basis, and conditions for starting the work.
- 1
You describe the context
Share the problem, desired outcome, current system state, and known constraints.
- 2
We clarify the problem together
We identify missing information and decide whether a consultation or discovery step is needed.
- 3
We agree the scope and assumptions
We separate the work included in the estimate from dependencies and items outside the scope.
- 4
You receive an estimate
We set out the engagement model, cost or billing basis, and conditions for starting the work.
What affects the estimate
We do not publish one rate for all work. Similarly named tasks can differ in scope, current system condition, dependencies, and risk. The estimate is based on the agreed scope and explicit assumptions.
- scope and expected outcome
- current system condition and documentation
- integrations and external dependencies
- access, test environment, and acceptance process
- urgency, required availability, and SLA conditions
Choose the technical area
PrestaShop
Store builds, development, integrations, performance, and ongoing maintenance.
DevOps and infrastructure
Servers, containers, CI/CD, monitoring, backups, and security.
AI and automation
Automating repetitive processes and integrating AI tools with existing systems.
IT consulting
Problem diagnosis, solution reviews, and technical decisions before implementation.