Two proposals sit open side by side. Both promise a Wikipedia page; both quote four figures; both end in a services agreement you are expected to sign this week. The asymmetry nobody mentions: every vendor publishes terms written by its own counsel to protect its own downside. Nobody has written the buyer-side teardown — the document that tells you, clause by clause, what a fair Wikipedia services contract looks like and where the traps sit.
This is that document, written for the buyer at proposal stage — founder, comms lead, procurement. It assumes one fact: nobody can promise an outcome on a platform governed by volunteers. Everything below follows from how a contract handles that truth.
We sell this service ourselves, so hold us to the same standard: our offer agreement is public, in full, before you ever book a call.
TL;DR
- A Wikipedia contract must price uncertainty honestly. No vendor controls the volunteer reviewers; Wikipedia's own scam warning says guarantees of creation or retention are a fraud signal.
- Run the 3-Contract Test in 60 seconds: (1) is the deliverable "published and surviving" or just "submitted"? (2) does the refund clause use dates and percentages, or adjectives? (3) is WP:PAID disclosure the vendor's written obligation? Fail any one — walk.
- Payment structure is risk allocation. Milestone and escrow models exist in this market, so "100% upfront, non-refundable" is a choice, not a norm.
- Refund clauses are where intent shows. "Non-refundable", "minus research fee" without a number, and refunds conditioned on 5-star reviews are documented market patterns.
- A 90-day survival window is the honest maximum. Longer promises price in things nobody controls.
Why this contract is weird by design
Most service contracts cover work the vendor controls end to end. A Wikipedia vendor controls drafting, sourcing, and disclosure — then hands the result to an independent volunteer community that owes it nothing. Reviewers can decline the draft; any editor can nominate the published page for deletion; no signature changes that.
Wikipedia says this itself. Its scam warning page describes firms that claim to guarantee an article's creation or retention, charge to "protect" pages, or pose as administrators demanding payment — and states that no one can legitimately sell those things. When the platform itself publicly warns about its own vendor market, the contract is not a formality. It is the product.
An honest Wikipedia contract therefore prices uncertainty instead of hiding it: it defines what "done" means on a platform where done can be undone, and allocates the cost of failure in numbers. A contract that reads like certainty — flat fee, no failure clauses, no refund mechanics — is not confident; it is mispriced by design, and the buyer absorbs the gap.
The 3-Contract Test: a 60-second screen
Three checks, answerable from the document alone in about a minute.
1. Does it define the deliverable as "published and surviving" — or just "submitted"? Find the word that triggers final payment. If the contract is discharged when a draft is "submitted", "completed", or "delivered for review", the vendor is paid in full for a page that may never exist. The honest formulation is publication plus survival — the article is live a stated number of days afterward (90 is the standard). "Submitted" is a homework contract. "Published and surviving" is a results contract.
2. Does the refund trigger have dates and percentages — or adjectives? "We will refund a reasonable portion if the project cannot be completed in a timely manner" contains three escape hatches and zero obligations. A real refund clause is arithmetic: if X happens within Y days, we refund Z percent within N business days. Adjectives in a refund clause are not sloppy drafting. They are the drafting.
3. Does it put WP:PAID disclosure in writing as the vendor's obligation? The Wikimedia Terms of Use require paid editors to disclose employer, client, and affiliation. A compliant vendor writes that in: which accounts will do the work, and that those accounts carry paid-contribution disclosure naming the engagement. If disclosure appears nowhere — or appears as your risk to bear — the vendor plans to edit undisclosed, and undisclosed editing is how client pages end up deleted with the client's name attached.
Fail any one: walk. Vendors who pass all three exist; the test is there so you stop reading proposals from the ones who do not.
Payment structures, ranked
Payment structure is risk allocation in its purest form. Four models exist:
| Structure | Your risk | Vendor risk | When it is fair | Red-flag version |
|---|---|---|---|---|
| Full upfront | Maximum — you pay for a promise | None | Small fixed-scope work (e.g., a €490-range notability audit) | "100% before work, non-refundable" on a full page project |
| Milestone (e.g., 50% start / 50% at publication) | Shared | Shared | The sensible default for page creation | Milestones tied to vendor activity ("on draft") rather than verifiable events |
| Publish-contingent | Low | High — vendor absorbs notability risk | Strong-source cases, priced at a premium for the risk transfer | "Pay on publication" via undisclosed accounts — live a week, then deleted |
| Escrow | Lowest | Moderate | High-ticket work with a genuinely neutral escrow agent | "Escrow" held by the vendor or an affiliate |
Escrow is not hypothetical — at least one vendor, Maximatic, advertises escrow-based payment — so "100% upfront, non-refundable" is a vendor's choice, not an industry constraint. Also: tie money to "live after 90 days", not "live". A vendor paid on publication has an incentive to force it through accounts that bypass review, and you inherit the deletion.
The refund clause teardown
Refund language is where a vendor's real expectations leak through. Three documented market patterns:
"Non-refundable." Some vendors write refunds out of existence — WikiVerification's published terms describe payments as non-refundable. Read literally: if the draft never publishes, the vendor keeps everything — a failure the vendor knows is possible, priced at 100% buyer cost.
"Refund minus research fee." Sounds fair — research does cost money. The trap is the missing number. If the fee is not a stated amount or percentage, it is whatever the vendor says it is, and the refund shrinks to a gesture. The fair version states it — "refund less the source-research fee of €X" — and delivers the research dossier you just paid for.
Refund conditioned on a 5-star review. The pattern that ends a negotiation on the spot. Trustpilot reviews of one vendor, Elite Wiki Writers, describe a $499 page that was deleted, with the refund allegedly conditioned on first posting a 5-star review (Trustpilot reviews). We cannot verify individual complaints — but a refund-for-praise mechanism converts your remedy into the vendor's marketing and poisons the review data the next buyer relies on.
The fair alternative is a staged kill fee — a published schedule of what you owe if the project stops at each gate:
| Project dies at... | You pay | You keep |
|---|---|---|
| Notability audit returns "no-go" | Audit fee only | The written audit |
| After source research, before drafting | Audit + stated research fee | The source dossier |
| Draft declined at review after agreed attempts | A stated partial fee | Draft + dossier |
| Published, then deleted within the survival window despite defense | Stated minority share (vendor refunds the majority) | All work product |
Numbers in every row. That is the entire trick.
The guarantee illusion
Vendors sell three different things under the word "guarantee".
A money-back guarantee is a financial remedy. It says nothing about whether the page will exist — and the teardown above shows how often it is booby-trapped into unclaimability.
An outcome guarantee — "guaranteed publication", "guaranteed approval", "your page will never be deleted" — is a promise about decisions the vendor does not make. Nobody controls the volunteer reviewers or the deletion process, which is why the platform's scam warning treats outcome guarantees as a fraud hallmark. A vendor who guarantees the community's behavior is either lying about the risk or planning to cheat the process.
A survival window is the honest middle: the vendor commits to monitor the published page for a defined period, defend it against deletion a defined number of times, and refund a defined percentage if the defense fails. Every element is inside the vendor's control — watching, responding, refunding. A 90-day survival clause is the honest maximum: new-page review and most early deletion activity happen in the first weeks, so that window a vendor can stand behind. Multi-year survival promises price in editor decisions, sourcing drift, and policy changes nobody controls. For the wider catalog of sales claims that end conversations, see how to spot a fake Wikipedia agency.
Clauses that protect you
Five clauses worth redlining in — all reasonable, refused only by vendors with something to hide:
- Deliverables include the source dossier. The graded list of independent sources is the project's most valuable artifact. If the engagement dies, you keep the research and can take it to another vendor.
- Named, disclosed editor accounts. The usernames doing the work, written into the contract or an annex, each carrying on-wiki paid-contribution disclosure naming the engagement — the 3-Contract Test's third question made enforceable.
- A deletion-defense obligation. If the page is nominated for deletion inside the window, the vendor must respond within stated business days, for a stated number of attempts. "We will monitor your page" without response times is decoration.
- Work-product transfer. Drafts, research, and files transfer to you on payment. (Published Wikipedia text is freely licensed; this clause covers pre-publication assets.)
- Indemnity for their compliance failures. If the vendor's undisclosed editing or sock-puppetry gets the page deleted or accounts blocked, that is their breach — refund plus cleanup costs. Whoever chose the method owns its consequences.
Clauses that protect them from scrutiny
The mirror image — four clauses whose only function is to keep you from looking:
- No-username clauses. The vendor will not identify the accounts doing the work. There is one reason to hide usernames from a client: the editing will be undisclosed — a Terms of Use violation you are contractually agreeing not to verify.
- "Proprietary methods." Refusing to describe process as trade secret. The compliant process — disclosed accounts, neutral drafting, review submission — is public and boring. When the method is the secret, the method is usually the violation.
- NDAs covering the vendor's identity. Normal NDAs protect your confidential information. A clause forbidding you from naming your own supplier is backwards — it exists so no public record connects the vendor to the wreckage when a page collapses.
- Review-gag clauses. Penalties for negative reviews, or remedies conditioned on positive ones — the contractual version of the Trustpilot pattern above. A vendor confident in its work does not buy your silence as a term of sale.
Upsells for things that are not for sale
Some proposals carry line items that sound technical and reassuring: "semi-protection setup", "page lock", "fast-track review", "admin escalation". None of these exist as purchasable services. Semi-protection is an admin action against vandalism, not a product — Wikipedia's scam warning specifically flags paid "protection" offers. There is no paid fast lane through Articles for Creation. Administrators do not sell escalations.
A line item for a nonexistent product means the vendor either does not understand the platform or is billing you for theater. Both answers price the rest of the proposal. (For what legitimate line items cost, see our pricing and the full cost breakdown: audit, research, drafting, review, monitoring.)
What WikiBusines puts in writing
This article tells you to demand terms in public, so here are ours. Our offer agreement is on the site — full text, readable before any call, currently marked draft while counsel finalizes wording; an honest draft beats a finished document hidden behind a sales call. The terms that matter:
- 90-day post-publication monitoring is a contract term on every page-creation project, not a marketing line.
- Recovery or refund, in numbers: if a published page is challenged within the window, we attempt restoration up to 3 times; if defense fails, we refund 80% of the project fee. Full mechanics on the guarantees page.
- Scope and price are public: €1,930 for an English-Wikipedia company page, every other edition and service priced openly.
- What we will not write: guaranteed publication or guaranteed survival. We publish a 93% success rate as a track record — a probability, not a promise, because the platform's reviewers do not work for us.
Apply the 3-Contract Test to our documents the same way. That is what they are published for.
The pre-signature checklist
Twelve yes/no questions: eleven or more is signable; under ten, renegotiate or walk.
- Is "delivered" defined as published and live after a stated number of days — not "submitted"?
- Does every refund clause state percentages and day-counts — no load-bearing adjectives?
- Is WP:PAID disclosure written as the vendor's contractual obligation?
- Are the editor usernames named in the contract or an annex?
- Do the deliverables include the source dossier?
- Is there a deletion-defense obligation with response times and an attempt count?
- Is the monitoring window stated in days, with a defined start date?
- Is final payment tied to a verifiable event rather than vendor say-so?
- Is there a staged kill-fee schedule with numbers in every row?
- Does work-product transfer to you on payment?
- Is every remedy unconditional on reviews, testimonials, or silence?
- Is the vendor's legal entity — name, registration number, jurisdiction — on the document?
Then email three questions — written answers are evidence you can hold against the contract later:
- "Which editor accounts will perform the work, and where is their paid-contribution disclosure published?"
- "If the page is deleted 30 days after publication, what exactly do we get back, and by what date?"
- "Will you confirm you will not bill us for page protection, fast-tracked review, or any other Wikipedia-side privilege?"
A vendor who answers all three plainly earns the second meeting. One who answers with a phone call instead of a reply is telling you the answers do not survive writing.
Download: PDFthe vendor scorecard (PDF) — print it next to the two PDFs on your desk and score them row by row.
The contract is the one part of a Wikipedia engagement you fully control. Read what an honest set of terms looks like on our guarantees page — then, if you want our agreement and a written scope for your case, send us the brief. We will put everything in this article in writing, because that is the point.