Retainer, fixed price, or hour bucket – which model fits when?

**We work with three models** and pick based on shop maturity and scope stability. - **Fixed price after discovery:** when the goal is clearly defined – a Shopify launch, a WooCommerce migration, a category relaunch, or a performance audit. We cut the project into building blocks and price each block as a package, so the client pays for outcome, not time on a clock. - **Retainer from 10 hours per month, starting at 1,700 euros monthly:** the right form for ongoing support – product maintenance, campaign setup, A/B tests, monitoring, smaller features, monthly reporting. - **Hour buckets:** we use rarely and only for well-scoped small jobs after a main project, because they are hard to plan operationally and push both sides into reactive mode. Most clients start with a fixed-price project for the first tangible deliverable and move into a retainer once the shop is live and a maintenance rhythm forms.

How do you secure quality when we do not build the shop ourselves?

**Outsourcing quality rests on four pillars:** discovery, transparency, review discipline, and measurable KPIs. - **Discovery:** we clarify target picture, audience, catalogue logic, and technical constraints – skipping this step means building past the business. - **Transparency:** access to our project tool, weekly status updates, and a shared repository with commit history – every change is traceable. - **Review discipline:** code goes through pull requests, two pairs of eyes on every change, staging deployments before every release. - **Measurable KPIs:** agreed in a baseline audit at the start – **conversion rate**, average basket, load time by **Core Web Vitals**, return rate, support-ticket volume. We deliver a monthly report with actuals, delta to baseline, actions taken, and recommendations for the following month. Accountability replaces "gut feeling", and the client always sees what the retainer was spent on.

How quickly do you respond to requests and incidents?

**On business days we respond within 24 hours** – default across all channels and retainers. A response is not necessarily the solution, but at least an assessment with next steps and timeline. - **Hard incidents on the shop (checkout down, payment blocked, full traffic loss):** retainer includes a prioritised channel with reaction usually within **two to four hours**. - **Weekends and public holidays:** excluded from the 24-hour rule, because serious support needs planned pauses. - **Genuine 24/7 operations:** we recommend either **Shopify Plus with Merchant Success** or a dedicated on-call rotation inside the client team. - **Communication channels:** primarily our project board and email; **Slack** or **Teams** we set up on request. One important note: we keep communication deliberately asynchronous, because constant chat eats productivity and rarely produces better decisions.

What happens to the know-how if we end the partnership?

**Every handover is prepared from day one** – the best protection against tool and agency lock-in. - **Client ownership:** all shop credentials, app keys, and admin roles belong to the client, not to us. - **Code ownership:** code lives in a Git repository owned by the client, to which we have collaborator access – not the other way around. - **Architectural doc:** every decision captured as a short entry in the project wiki with rationale and affected components. - **Hosting accounts** at **Hetzner**, **Fly.io**, **Raidboxes**, or **Cloudflare** are registered in the client's name; we work through team accounts below them. **Exit in four steps:** a written exit document, a two-hour handover call with the new partner, four weeks of transition support for follow-up questions, and the agreed withdrawal of our access rights on the cut-off date. The client leaves the partnership with a full picture of their own system – no knowledge monopoly left on our side.

GDPR, data processing agreements – how is that handled?

**For every retainer and project in which we touch personal data, we sign a data processing agreement** under **Article 28 GDPR**. - **Access circle:** limited to team members with operational need – usually Martin, Mathias, and Enrico plus any external specialists involved, who are bound to the same agreement. - **EU infrastructure by default:** shop data stays with the client, project tooling runs on providers with EU servers or standard contractual clauses, backups are encrypted at rest. - **Secrets handling:** passwords and API keys travel exclusively through a password manager with audit log, never via email or chat. **Clear boundary:** we are not attorneys and do not replace GDPR legal advice – privacy policy wording, cookie banner texts, access-request processes, and liability questions belong in the hands of a specialised lawyer. We implement the legal framework technically and cleanly; the legal assessment itself remains a lawyer's task.

What typically runs inside an e-commerce retainer?

**An average 10 to 20 hour retainer for a Shopify or WooCommerce shop distributes across five activities.** - **Monitoring and maintenance:** platform updates, app compatibility, performance checks, backup verification, security alerts. - **Product and catalogue work:** maintaining product data with the client, refining the category structure, extending metafields and filters, orchestrating seasonal collections. - **Conversion work:** A/B tests on product pages and checkout, campaign landing pages, pop-up logic, email flows in **Klaviyo** or **Mailchimp**. - **Reporting and strategy sparring:** monthly KPI report, quarterly strategy call, prioritisation for the next month. - **Firefighting:** things nobody plans but always happen – broken webhook, payment error, shipping issue. We deliberately reserve **10 to 15 percent** of the retainer as firefighting buffer, because otherwise daily life collapses into reactive mode and strategy dies. The concrete weighting we renegotiate in the quarterly review.

Freelancer, boutique agency, or large agency – what is the difference?

**The market for e-commerce support splits roughly into three camps.** - **Solo freelancers:** cheap, personal, and often technically strong – but everything depends on one person. Illness, holidays, overload, or a career shift stalls the project. - **Large agencies with 50+ staff:** process maturity, redundancy, and broad skill coverage – but typically high fixed overhead for account management, several layers of briefing, and less access to the people who actually build. - **Boutique teams like us:** three to eight people, direct communication with the ones doing the work, specialised on a clearly defined field – for us **e-commerce, Shopify, WooCommerce, web apps**. Prices usually sit closer to freelancers than to big agencies, redundancy closer to agencies than to solo experts. For **SMBs with shop revenue between 500k and 10 million euros**, that is usually the most productive sweet spot, because service keeps strategy and hands-on delivery in one hand.

Which KPIs show whether outsourcing is really working?

**Three layers of metrics decide whether the partnership delivers value.** - **Business KPIs:** net revenue, contribution margin, conversion rate, average basket, return rate. The final yardstick – but they move slowly and also depend on market conditions and product, not only on the partner. - **Operational KPIs:** ticket resolution time, uptime, mobile load time, error rate in order sync, number of A/B tests run, backlog items shipped per month. Shows whether agency work is clean and productive, independent of market noise. - **Communication KPIs:** response time, adherence to agreed deadlines, completeness of monthly reports, number of escalated topics per quarter. Almost nobody tracks this – yet it is the **leading indicator**: when communication slips, the operational problem follows within one quarter at most. We define KPIs in the baseline audit and track them monthly – no dashboard replaces the conversation, but without numbers any conversation turns into opinion against opinion.

Nearshoring versus offshoring – is that worth it in e-commerce?

**Nearshoring and offshoring pay off in e-commerce only in limited cases** – most of the value is not in lines of code. - **Nearshoring (Romania, Poland, Portugal):** legitimate for pure development work and large-scale content maintenance, can save **20 to 40 percent** against DACH rates at volume. - **Offshoring into Asian time zones:** saves more on paper, but in almost every SMB project costs more in coordination overhead than it saves in day rates – time zone, language, and cultural distance halve iteration speed. - **What really matters:** market knowledge, legal context (**GDPR, German GoBD, Austrian consumer protection law**), and fast alignment with marketing, logistics, and accounting. That is exactly our position: we sit in Austria, speak our clients' language literally and substantively, and know DACH trade from merchant perspective. For pure technical sub-tasks with clean briefs, nearshoring can be part of our supply chain as a subcontracted layer; client relationship and accountability stay with us.

How big does our shop need to be for outsourcing to pay off?

**Our retainer minimum sits at 10 hours per month, from 1,700 euros monthly** – roughly two to three bundled working days and the smallest unit in which strategic and operational work coexist. - **Below 10 hours:** overhead from kick-off, context building, and reporting eats too much of the paid volume. - **Translated to revenue:** fits from roughly **200,000 to 300,000 euros annual turnover**. Below that, a targeted workshop plus dedicated focus time often delivers more leverage than an agency engagement. - **One-off projects:** fixed-price migration, shop launch, or audit we take on for smaller shops too, because scope is clearly bounded. - **New Shopify shop builds:** start at **20,000 euros** with us – discovery, theme work, app configuration, data migration, and launch support remain substantial work even in the smallest case. Below that threshold, a WIFI training, a short sparring, and a self-assembled Shopify theme are often the better fit.

What is the most common mistake in e-commerce outsourcing?

**Three mistakes surface repeatedly in projects we inherit from other partners.** - **No baseline audit at the start:** without a documented starting state, after six months nobody can decide which change comes from the partner and which from seasonality – both sides argue from gut feeling. - **Vague scope in the retainer:** "Everything around the shop" in practice means strategy, small tasks, and firefighting compete for the same hours – firefighting wins because it is loud, and strategy stays on the shelf. We therefore agree concretely which work is covered by the monthly volume and when an extra engagement begins. - **Credentials and code owned by the agency rather than the merchant:** anyone discovering at handover that domain, theme repo, or payment accounts sit on agency names experiences a power shift that was avoidable. **Our rule is simple:** the client owns everything, we only get collaborator access – never the reverse.

E-Commerce·8 MIN READ

E-Commerce Outsourcing 2026: Partner Instead of Fixed Cost

Q: Build an in-house team or outsource permanently?

**The answer turns on three questions:** - **Does the shop exceed 2 million euros annual revenue?** - **Is the assortment strongly differentiating?** - **Is the role loaded to at least 80 percent?** **All three yes:** build in-house – deep product knowledge, brand identity, and continuous customer awareness only emerge with permanent presence. **One or two no:** outsourcing serves better. The role is then rarely fully loaded, recruiting takes longer than the project needs, and fixed cost suffocates scaling in weak months. **Hybrid in practice:** an in-house content manager or e-commerce operator owning day-to-day, customer service, and product maintenance, plus an external retainer for strategy, technical development, and sparring. That combines depth and breadth, spreads redundancy risk, and prevents a single person from carrying the entire e-commerce know-how of the company. We support both paths – including building and training an in-house team when a client aims for that.

E-commerce outsourcing 2026 in plain terms: retainer vs. fixed price, response times, data processing, exit path, and KPIs from real Shopify and WooCommerce work.

By Martin Ogris

Founder & Managing Director·12 April 2026·8 min read

In 2026, e-commerce outsourcing is no longer a fallback for shops without budget – it is a deliberate operational lever. A fully staffed in-house team – e-commerce manager, developer, performance marketer, content lead – quickly costs 250,000 to 400,000 euros per year in DACH including overhead, and comes with utilisation risk that a shop below three million euros in annual revenue rarely supports. External support fills that gap with experience from many shops, clean utilisation, and without the recruiting lottery.

At clickpuls we support merchants across Austria, Germany, and Switzerland from exactly that position. Martin, Mathias, and Enrico have worked as a Shopify Partner since 2023 and with WooCommerce experience that reaches further back. Martin is additionally a WIFI trainer for e-commerce and brings a merchant perspective from running his own shop projects. This article covers what models of e-commerce outsourcing exist, how a serious retainer is structured, how we secure quality, and what questions a merchant should clarify before signing. For the concrete shape of a partnership we support through e-commerce consulting and ongoing online shop support.

Why outsource at all? The honest calculation

A shop needs competence in areas that individual employees rarely cover in depth. Technology, marketing, strategy, operations, and data work sit side by side. A full-time e-commerce manager has to orchestrate all five – the reality is that most candidates come out of one field and carry the other four pragmatically at best.

The five fields of e-commerce work

Technology: shop system, hosting, integrations, performance, security, tracking
Marketing: SEO, SEA, social ads, email automation, conversion optimisation
Strategy: assortment, pricing, internationalisation, competitive monitoring
Operations: logistics, customer service, returns, process automation
Data: analytics, reporting, attribution, cohort analysis, test design

The honest cost picture: a full-time senior hire in DACH costs 70,000 to 95,000 euros gross plus around 30 percent employer overhead, plus workspace, hardware, training, recruiting, and downtime – realistically 120,000 to 160,000 euros in the first year. If that same role is only 60 percent loaded, the shop pays 40 percent idle time. That idle time funds the outsourcing model in practice: we distribute capacity across several clients and give each client only the hours they truly need.

Three support models compared

The market holds three dominant billing forms: retainer, fixed-price project, hour bucket. Each has a clear use case – and each has traps that tip the model into failure. The table below compares the models by decision factors, not by prices – because real numbers always depend on scope.

Factor	Retainer	Fixed price	Hour bucket
Primary use case	Ongoing support	Well-scoped project	Punctual small jobs
Merchant planability	High – fixed monthly	Very high – fixed total	Low – depends on draw
Scope risk	Medium – firefighting buffer	With the agency	With the merchant
Billing	Monthly flat from 10h	Per block after discovery	Actual hours
Cancellation	Typical 4–8 weeks	After completion	Per order
Typical duration	12+ months	4–16 weeks	Short, 1–10 hours
Strategy share	High	Medium	Very low
Reporting rhythm	Monthly plus quarterly	Project close	Invoice per job
Fit for mature shop	Yes, primary	For defined extensions	Yes, secondary
Fit for new shop	Only after launch	Yes – fixed-price launch	Rarely productive

Primary use case

RetainerOngoing support

Fixed priceWell-scoped project

Hour bucketPunctual small jobs

Merchant planability

RetainerHigh – fixed monthly

Fixed priceVery high – fixed total

Hour bucketLow – depends on draw

Scope risk

RetainerMedium – firefighting buffer

Fixed priceWith the agency

Hour bucketWith the merchant

Billing

RetainerMonthly flat from 10h

Fixed pricePer block after discovery

Hour bucketActual hours

Cancellation

RetainerTypical 4–8 weeks

Fixed priceAfter completion

Hour bucketPer order

Typical duration

Retainer12+ months

Fixed price4–16 weeks

Hour bucketShort, 1–10 hours

Strategy share

RetainerHigh

Fixed priceMedium

Hour bucketVery low

Reporting rhythm

RetainerMonthly plus quarterly

Fixed priceProject close

Hour bucketInvoice per job

Fit for mature shop

RetainerYes, primary

Fixed priceFor defined extensions

Hour bucketYes, secondary

Fit for new shop

RetainerOnly after launch

Fixed priceYes – fixed-price launch

Hour bucketRarely productive

Classification from our own projects across Austria, Germany, and Switzerland. Actual terms depend on the concrete scope.

When a retainer fits

The shop is live; the question is evolution, not build
Recurring tasks like product maintenance, campaigns, A/B tests run monthly
Strategic sparring at eye level should be part of the engagement
The role is not fully loaded for a dedicated employee
Reporting and KPIs should arrive reliably on a fixed cadence

When fixed price fits

Clear target state: new shop, migration, relaunch, audit
Discovery delivers a solid picture of scope and dependencies
A fixed end price matters more than maximal in-flight flexibility
A move into a retainer after the project is planned or being evaluated

When outsourcing does not fit

Shop revenue below roughly 200,000 euros per year with very tight budget
Pure pass-through expectation without a feedback channel for decisions
Business logic is strictly confidential and must not leave the house
Client wants to compare hourly rates rather than outcomes – the basis is missing

How an outsourcing partnership runs with us

A retainer is not a black box. We work in a recurring rhythm that separates strategy, delivery, and reporting cleanly, and ensures the client always knows what we are working on and why.

Discovery

Target picture, team, tech stack, scope, responsibilities

Onboarding

DPA, credentials, password manager, project board, comms

Baseline audit

Measure KPIs, prioritise weak spots, 90-day plan

Sprint rhythm

Two-week cycles, clear backlog priorities

Monthly report

Actuals, delta to baseline, actions, next steps

Quarterly review

Strategy, priorities, scope tuning, growth path

Discovery

Target picture, team, tech stack, scope, responsibilities

Onboarding

DPA, credentials, password manager, project board, comms

Baseline audit

Measure KPIs, prioritise weak spots, 90-day plan

Sprint rhythm

Two-week cycles, clear backlog priorities

Monthly report

Actuals, delta to baseline, actions, next steps

Quarterly review

Strategy, priorities, scope tuning, growth path

Retainer rhythm from 10 hours per month

Discovery typically takes two to three sessions. The output is a written scope with named responsibles on both sides, a clear definition of "what is covered by the retainer", and an offer. We show the first proof of concept as a clickable live prototype in the browser whenever design work is part of the scope – decision-makers see immediately how the system behaves, instead of reconstructing reality from static visuals.

Communication, response times, escalation

The second most common friction point in outsourcing relationships (after unclear scope) is weak or unreliable communication. We answer that with three firm commitments.

24-hour business-day response

Every request via project board or email receives an initial response within 24 hours on business days – with assessment, expected start time, and any clarifying questions. Weekends and public holidays are excluded; genuine 24/7 support requires a dedicated on-call model, which we discuss case by case.

Priority channel for incidents

Hard shop incidents – checkout broken, payment blocked, traffic loss – run through a flagged channel. Target reaction: two to four hours on business days. We deliberately separate normal requests from incidents, so firefighting does not suffocate routine work.

Monthly report replaces gut feeling

A monthly report with actual KPIs, delta to baseline, actions taken, and recommendations for the following month. A quarterly strategy call with decision-makers. Every stakeholder on the client side knows what the retainer was spent on, without digging through individual tickets.

GDPR, data processing, and trust

E-commerce support means access to personal data – orders, customer records, payment history, sometimes marketing profiles. That is not a detail but a core part of the partnership and must be contractually clean.

DPA under Article 28 GDPR – standard for every retainer, signed before real data access
Minimal access circle – only team members who need access operationally; external specialists bound to the same DPA
EU infrastructure by default – hosting on Hetzner, Fly.io, Raidboxes, and Cloudflare; project tooling on EU servers
Credentials via password manager with audit log – never via email or chat
Documented deletion processes at the end of the partnership, including revocation of all access on the cut-off date

Boundary note: we are not attorneys and do not replace GDPR legal advice. For privacy policy wording, cookie banner texts, and liability questions, a specialised lawyer belongs in the project plan.

Know-how protection: how the client stays in charge

The most common trap in agency relationships is a slow shift of competence from merchant to agency, which creates dependency. Our counter-model is structurally simple: the client owns everything, we get collaborator access – never the reverse.

Shop admin, domain, hosting account, payment contracts registered to the client
Git repository on the client side, we work as collaborators
Architecture and decision log in the shared project wiki
Monthly reporting documents work done and rationale
Four-step exit at the end: written protocol, handover call, support, access revocation

KPIs: how we make success measurable

Outsourcing without measurable outcomes is trust-based, not a partnership. In discovery we therefore define a three-layer KPI set, measure it in the baseline audit, and track it monthly from then on.

Business KPIs: net revenue, contribution margin, conversion rate, average basket, return rate
Operational KPIs: ticket resolution time, uptime, mobile load time, sync error rate, backlog items shipped
Communication KPIs: response time, deadline adherence, report completeness, escalations per quarter

Default tracking stack: GA4 plus Google Tag Manager, extended on Shopify with Shopify Analytics and UTM discipline for attribution. We deliberately do not promise performance guarantees – neither for revenue nor for rankings. Shopify is a third-party platform, search results follow the Google algorithm, and any guarantee would be dishonest.

Typical retainer content – a month in practice

Abstract model descriptions help little when deciding. Here is a typical month from one of our 15-hour retainers for a Shopify fashion shop, to make reality tangible. Split varies, size is representative.

2–3 hours monitoring and maintenance: Shopify updates, app compatibility, Core Web Vitals, backup logs, alerts
3–4 hours product and collection work: new articles, category sharpening, metafield maintenance, seasonal landing pages
3 hours conversion optimisation: evaluate running product page A/B test, prepare next test, review checkout analytics
2 hours email automation: refine Klaviyo flows, rework segmentation, tune newsletter template to collection
1–2 hours reporting: assemble KPI report, write commentary, derive recommendations for next month
1–2 hours sparring and call: monthly stand-up with client team, priorities for the next four weeks
1–2 hours firefighting buffer: broken webhook, misfired voucher, ad-hoc campaign

If the firefighting buffer exceeds 20 percent of volume in three consecutive months, we actively raise a scope adjustment. An overloaded retainer is not a sign of productivity but a signal that either scope is too narrow or structural shop problems produce ongoing unresolved issues.

Partner selection: what merchants should check before signing

Picking an outsourcing partner is not a pure price conversation. Five checkpoints decide whether the relationship holds or tips after six months.

Reference call instead of reference PDF: a 15-minute call with a current client of the partner tells more than any case-study page
Scope clarity in the offer: concrete wording of what is covered and what is not – vague "all-round support" is a warning sign
Exit path from day one: DPA, credential ownership, and code repository on the client side must be addressed in the contract
Access to the builders: direct communication with the people delivering, not only account management
Inspect a reporting sample: an anonymised example report from a live engagement shows what actually arrives each month

Hybrid model: in-house plus external retainer

For shops between 1 and 10 million euros annual revenue, the most productive setup is in our experience rarely pure in-house or pure external. What we see in practice:

In-house role

Day-to-day, customer service, returns process
Product data maintenance, collection releases
Content production, simple landing pages
Internal alignment with buying, logistics, accounting

External retainer

Strategy, sparring, quarterly review
Technical development, integrations
Performance tuning, A/B test design
KPI reporting, benchmarking, vendor management

The in-house person knows product and culture, the external partner brings experience from many shops and an independent perspective. The model halves the single-point-of-failure risk, allows growth without abrupt headcount jumps, and protects against a single person carrying the entire e-commerce know-how of the company.

Bottom line: outsourcing is a focus game, not a cost game

The decisive question is not whether e-commerce outsourcing is cheaper than a dedicated hire – in almost every SMB scenario the answer is yes. The decisive question is whether the partnership delivers strategy, execution, and reporting without the merchant losing control of their shop. The answer is clear: only when credentials belong to the client, communication is committed, KPIs are measurable, and the exit path exists from day one.

If you are considering which model fits your shop – fixed-price project, retainer, or hybrid – let us talk briefly. In the first hour we sketch which format adds up financially and which stumbling blocks are real in your situation.

Is e-commerce outsourcing right for your shop?

We analyse revenue, team setup, and pipeline together and give an honest recommendation: retainer, fixed price, or hybrid – whichever gives the most leverage. Retainers start at 10 hours per month, fixed-price projects after discovery.

Schedule a non-binding conversation

Frequently asked questions about E-Commerce Outsourcing 2026

We work with three models and pick based on shop maturity and scope stability.

Fixed price after discovery: when the goal is clearly defined – a Shopify launch, a WooCommerce migration, a category relaunch, or a performance audit. We cut the project into building blocks and price each block as a package, so the client pays for outcome, not time on a clock.
Retainer from 10 hours per month, starting at 1,700 euros monthly: the right form for ongoing support – product maintenance, campaign setup, A/B tests, monitoring, smaller features, monthly reporting.
Hour buckets: we use rarely and only for well-scoped small jobs after a main project, because they are hard to plan operationally and push both sides into reactive mode.

Most clients start with a fixed-price project for the first tangible deliverable and move into a retainer once the shop is live and a maintenance rhythm forms.

Outsourcing quality rests on four pillars: discovery, transparency, review discipline, and measurable KPIs.

Discovery: we clarify target picture, audience, catalogue logic, and technical constraints – skipping this step means building past the business.
Transparency: access to our project tool, weekly status updates, and a shared repository with commit history – every change is traceable.
Review discipline: code goes through pull requests, two pairs of eyes on every change, staging deployments before every release.
Measurable KPIs: agreed in a baseline audit at the start – conversion rate, average basket, load time by Core Web Vitals, return rate, support-ticket volume.

We deliver a monthly report with actuals, delta to baseline, actions taken, and recommendations for the following month. Accountability replaces "gut feeling", and the client always sees what the retainer was spent on.

On business days we respond within 24 hours – default across all channels and retainers. A response is not necessarily the solution, but at least an assessment with next steps and timeline.

Hard incidents on the shop (checkout down, payment blocked, full traffic loss): retainer includes a prioritised channel with reaction usually within two to four hours.
Weekends and public holidays: excluded from the 24-hour rule, because serious support needs planned pauses.
Genuine 24/7 operations: we recommend either Shopify Plus with Merchant Success or a dedicated on-call rotation inside the client team.
Communication channels: primarily our project board and email; Slack or Teams we set up on request.

One important note: we keep communication deliberately asynchronous, because constant chat eats productivity and rarely produces better decisions.

Every handover is prepared from day one – the best protection against tool and agency lock-in.

Client ownership: all shop credentials, app keys, and admin roles belong to the client, not to us.
Code ownership: code lives in a Git repository owned by the client, to which we have collaborator access – not the other way around.
Architectural doc: every decision captured as a short entry in the project wiki with rationale and affected components.
Hosting accounts at Hetzner, Fly.io, Raidboxes, or Cloudflare are registered in the client's name; we work through team accounts below them.

Exit in four steps: a written exit document, a two-hour handover call with the new partner, four weeks of transition support for follow-up questions, and the agreed withdrawal of our access rights on the cut-off date. The client leaves the partnership with a full picture of their own system – no knowledge monopoly left on our side.

For every retainer and project in which we touch personal data, we sign a data processing agreement under Article 28 GDPR.

Access circle: limited to team members with operational need – usually Martin, Mathias, and Enrico plus any external specialists involved, who are bound to the same agreement.
EU infrastructure by default: shop data stays with the client, project tooling runs on providers with EU servers or standard contractual clauses, backups are encrypted at rest.
Secrets handling: passwords and API keys travel exclusively through a password manager with audit log, never via email or chat.

Clear boundary: we are not attorneys and do not replace GDPR legal advice – privacy policy wording, cookie banner texts, access-request processes, and liability questions belong in the hands of a specialised lawyer. We implement the legal framework technically and cleanly; the legal assessment itself remains a lawyer's task.

An average 10 to 20 hour retainer for a Shopify or WooCommerce shop distributes across five activities.

Monitoring and maintenance: platform updates, app compatibility, performance checks, backup verification, security alerts.
Product and catalogue work: maintaining product data with the client, refining the category structure, extending metafields and filters, orchestrating seasonal collections.
Conversion work: A/B tests on product pages and checkout, campaign landing pages, pop-up logic, email flows in Klaviyo or Mailchimp.
Reporting and strategy sparring: monthly KPI report, quarterly strategy call, prioritisation for the next month.
Firefighting: things nobody plans but always happen – broken webhook, payment error, shipping issue.

We deliberately reserve 10 to 15 percent of the retainer as firefighting buffer, because otherwise daily life collapses into reactive mode and strategy dies. The concrete weighting we renegotiate in the quarterly review.

The market for e-commerce support splits roughly into three camps.

Solo freelancers: cheap, personal, and often technically strong – but everything depends on one person. Illness, holidays, overload, or a career shift stalls the project.
Large agencies with 50+ staff: process maturity, redundancy, and broad skill coverage – but typically high fixed overhead for account management, several layers of briefing, and less access to the people who actually build.
Boutique teams like us: three to eight people, direct communication with the ones doing the work, specialised on a clearly defined field – for us e-commerce, Shopify, WooCommerce, web apps.

Prices usually sit closer to freelancers than to big agencies, redundancy closer to agencies than to solo experts. For SMBs with shop revenue between 500k and 10 million euros, that is usually the most productive sweet spot, because service keeps strategy and hands-on delivery in one hand.

Three layers of metrics decide whether the partnership delivers value.

Business KPIs: net revenue, contribution margin, conversion rate, average basket, return rate. The final yardstick – but they move slowly and also depend on market conditions and product, not only on the partner.
Operational KPIs: ticket resolution time, uptime, mobile load time, error rate in order sync, number of A/B tests run, backlog items shipped per month. Shows whether agency work is clean and productive, independent of market noise.
Communication KPIs: response time, adherence to agreed deadlines, completeness of monthly reports, number of escalated topics per quarter. Almost nobody tracks this – yet it is the leading indicator: when communication slips, the operational problem follows within one quarter at most.

We define KPIs in the baseline audit and track them monthly – no dashboard replaces the conversation, but without numbers any conversation turns into opinion against opinion.

Nearshoring and offshoring pay off in e-commerce only in limited cases – most of the value is not in lines of code.

Nearshoring (Romania, Poland, Portugal): legitimate for pure development work and large-scale content maintenance, can save 20 to 40 percent against DACH rates at volume.
Offshoring into Asian time zones: saves more on paper, but in almost every SMB project costs more in coordination overhead than it saves in day rates – time zone, language, and cultural distance halve iteration speed.
What really matters: market knowledge, legal context (GDPR, German GoBD, Austrian consumer protection law), and fast alignment with marketing, logistics, and accounting.

That is exactly our position: we sit in Austria, speak our clients' language literally and substantively, and know DACH trade from merchant perspective. For pure technical sub-tasks with clean briefs, nearshoring can be part of our supply chain as a subcontracted layer; client relationship and accountability stay with us.

The answer turns on three questions:

Does the shop exceed 2 million euros annual revenue?
Is the assortment strongly differentiating?
Is the role loaded to at least 80 percent?

All three yes: build in-house – deep product knowledge, brand identity, and continuous customer awareness only emerge with permanent presence.

One or two no: outsourcing serves better. The role is then rarely fully loaded, recruiting takes longer than the project needs, and fixed cost suffocates scaling in weak months.

Hybrid in practice: an in-house content manager or e-commerce operator owning day-to-day, customer service, and product maintenance, plus an external retainer for strategy, technical development, and sparring. That combines depth and breadth, spreads redundancy risk, and prevents a single person from carrying the entire e-commerce know-how of the company. We support both paths – including building and training an in-house team when a client aims for that.

Our retainer minimum sits at 10 hours per month, from 1,700 euros monthly – roughly two to three bundled working days and the smallest unit in which strategic and operational work coexist.

Below 10 hours: overhead from kick-off, context building, and reporting eats too much of the paid volume.
Translated to revenue: fits from roughly 200,000 to 300,000 euros annual turnover. Below that, a targeted workshop plus dedicated focus time often delivers more leverage than an agency engagement.
One-off projects: fixed-price migration, shop launch, or audit we take on for smaller shops too, because scope is clearly bounded.
New Shopify shop builds: start at 20,000 euros with us – discovery, theme work, app configuration, data migration, and launch support remain substantial work even in the smallest case.

Below that threshold, a WIFI training, a short sparring, and a self-assembled Shopify theme are often the better fit.

Three mistakes surface repeatedly in projects we inherit from other partners.

No baseline audit at the start: without a documented starting state, after six months nobody can decide which change comes from the partner and which from seasonality – both sides argue from gut feeling.
Vague scope in the retainer: "Everything around the shop" in practice means strategy, small tasks, and firefighting compete for the same hours – firefighting wins because it is loud, and strategy stays on the shelf. We therefore agree concretely which work is covered by the monthly volume and when an extra engagement begins.
Credentials and code owned by the agency rather than the merchant: anyone discovering at handover that domain, theme repo, or payment accounts sit on agency names experiences a power shift that was avoidable.

Our rule is simple: the client owns everything, we only get collaborator access – never the reverse.

← Back to overview View related service