Process is not a mood board of sticky notes. It is the sequence that turns a market, a content model and lawful data access into a WordPress system your team can run. Skip a stage and you usually pay for it twice — once in the rush, again in the cleanup.
Delivery sequence
Each stage has an exit condition. “We will figure it out in build” is not an exit condition.
Market, language, content model, data access, who publishes and what must work on day one. If those answers are vague, the later quote is fiction wearing a number.
What ships in the launch, what stays out, acceptance checks and the price of changes after lock. A scope document is not bureaucracy — it is the only defence against “while you are in there”.
Foundations first, then the adaptations the brief actually needs. Speculative features do not hitch a ride inside a fixed launch. That habit is how weekends disappear and launch dates lie.
Deploy, smoke checks, handover of the operating paths your editors will touch. A launch is not a ZIP in Slack and a hope that DNS forgives you.
Updates, monitoring and further features under a separate care scope. Launch support is not infinite free labour disguised as goodwill.
Client side of the deal
We configure approved credentials. We do not rent you someone else’s keys and call it delivery.
API access, feeds, brand assets and production accounts you own or are licensed to use. Shared donor logins are a refusal, not a negotiation point.
Scope lock, content samples, review feedback and go/no-go calls. Silence is not approval. It is calendar damage.
A production host capable of the agreed stack. A €3 coupon VPS with “we will optimise later” is not a hosting plan — it is a future incident report.
A useful filter
Borrowed API keys. Copied content farms. Full custom websites priced under the launch floor. Fantasy deadlines that assume discovery and scope never happened. If that is the brief, you are not our client — and that is a cleaner answer than a polite maybe.
Affiliate Launch Pack projects start at €3,000 once access and scope are ready. Custom work and ongoing care are quoted from the written scope — not from a wish list typed into chat at midnight.
If the Standard foundation already covers the brief, we will say so before inventing a custom adventure.
Once hosting, access and scope are ready, an Affiliate Launch Pack typically moves from installation to production in 1–2 weeks. Discovery and waiting on client inputs are not part of that clock.
No. Build without a locked scope is how “small tweaks” become a second project inside the first invoice.
You do. We configure approved credentials. We do not ship shared donor access or include third-party Pro licences in the launch floor unless the proposal says so.
Handover of the operating paths, then care under a separate agreement if you want ongoing updates, monitoring or new features.
Only by cutting scope — not by skipping discovery. A fake calendar is still a fake calendar when it is written in bold.