project delivery help when your team is full
i take over an agreed part of your client project and keep decisions and handovers moving. need it white-label? i work behind your team. your client relationship stays yours.
talk about agency capacity ↗od / e-commerce delivery
i run e-commerce launches, migrations and integrations for agencies and online stores. you get senior project management for the part that needs it, without hiring anyone full-time.
see how i work with your team01 / pick your situation
i take over an agreed part of your client project and keep decisions and handovers moving. need it white-label? i work behind your team. your client relationship stays yours.
talk about agency capacity ↗i map how your business works. i turn that into clear requirements your contractors can price and build from. and when they deliver, i check the work against those requirements before you accept it. you make the business decisions.
talk about my project ↗02 / here's the math
two buyers, two versions of the same question. these are planning benchmarks, not a claim that every project saves money.
four or eight reserved days can cover a temporary delivery gap. a full-time hire covers more time and costs more between projects. compare the actual scope, not just the rate.
your math: unbilled project contribution per week × weeks the work slips.
do not count all contract revenue as lost. use your own margin and whether the work would truly be delayed or cancelled.a two-week slip at an assumed €10,000 incremental weekly contribution puts €20,000 at risk. it may move later rather than vanish.
your math: expected incremental contribution per week × weeks of delay.
illustration only, not a market average or a saving od promises. an early launch can carry its own costs and risks too.03 / how it works
mapagree on the goal, owners, dates and decisions.
runadd as many issues to the queue as needed. we agree what gets active attention within the reserved time.
reportget a written update and follow-ups in the agreed business-day response window. you make the final business decisions.
04 / ways to work
four ways to work together. prices in eur, excluding vat. exact scope and price are agreed before we start.
01 / option
best when the project is still a pile of opinions.
one-off · two weeks
a two-week diagnostic, not an ongoing pm retainer. we agree a reply window before starting.
02 / option
best when work is underway but keeps drifting.
per month · about four reserved days
response times agreed before we start. not on-call support.
03 / option
best when launch is close and coordination gets heavier.
per month · about eight reserved days
response windows and launch support are agreed before starting. extra launches are scoped separately.
04 / one-off audit
best before you sign off on delivered software and pay the final invoice.
one-off · about one to two weeks
not a penetration test or full code audit. final scope and fee are agreed before starting. excl. vat.
this is part-time project management, not an unlimited subscription. no coding, design, legal or compliance work. you make the final business decisions. monthly work ends with notice and a proper handover.
ask about the right package ↗05 / comparison context
these are different services in different markets. they do not show savings from hiring od.
all figures in eur, excluding vat. compare like-for-like scope and tax treatment when quoting. full-time hiring, recruitment and idle capacity are real planning lines, but not priced here without a buyer's own figures.
sources checked october 2026: fratch germany it pm rates ↗ · malt listed day rate ↗.
06 / who you work with
i manage e-commerce projects across platforms, payments, checkout and logistics. the job is to make ownership clear, get decisions made and hand over working results. no status-meeting archaeology.
experience across e-commerce, payments and logistics integrations.
07 / platforms & tools
platforms and systems i coordinate delivery across. client and vendor names stay private. details come up on a call.
08 / blog
short guides on each building block of an e-commerce system: platform, payments, shipping, erp and crm.
the crm knows the customer, the shop knows the order. connect them without duplicate contacts, lost consent or emails about refunded orders.
read the post ↗the erp owns stock, prices and invoices. the shop displays them. most integration trouble comes from nobody deciding which system wins on which field.
read the post ↗every carrier describes the same few concepts in its own api. here is what to agree on before you integrate dhl, ups, inpost or an aggregator.
read the post ↗09 / personal projects
everybody likes to hear a nice word once in a while. this project started at a supermarket checkout.
read the story ↗10 / quick answers
part-time senior project management - sometimes called fractional pm.
yes, when we agree white-label support. your client relationship stays yours.
i coordinate delivery with developers and vendors. i do not write code or replace your technical lead.
delivery map is a two-week diagnostic. delivery desk has about four reserved days a month; launch lead about eight. exact scope and response windows are agreed first.
one agreed part of a project gets active attention at a time. the rest stays on the list, or we scope another engagement.
11 / next step
a 20-minute fit call: the project, who's on the team and what help would be useful. no sales deck required.