Inside recurring missions and retention on Mission

On a rainy Tuesday in Bordeaux, a freelance property technician named Marc receives an automated prompt at 07:00. His bi-weekly inspection of three residential rental units under the Nest universe is queued. The client does not need to send a message, approve an invoice, or initiate a bank transfer. The deposit for Instance #14 is already locked in WEVONE’s transactional escrow ledger. By 11:30, Marc uploads three geo-tagged photos and a short audio note confirming structural check-passed status. The funds release automatically 24 hours later when the dispute window closes.

This is a recurring mission in production. In traditional local service platforms, this transaction would have migrated to WhatsApp and cash six months ago. Marketplace disintermediation—where two parties meet via an app but take all subsequent business off-platform to avoid fees—is the primary reason local service marketplaces suffer catastrophic long-term churn. When friction remains constant while trust increases, paying a platform cut on every recurring visit feels like an unreasonable tax.

To solve this, WEVONE does not rely on non-circumvention penalties or legal threats. It relies on platform mechanics that make staying on-platform cheaper and safer than managing cash payments manually.

The Mechanics of Rolling Escrow and Dispute Isolation

When a user converts a one-off service into a recurring Mission—whether for office cleaning, home care, routine maintenance, or weekly tutoring—the system shifts from single-contract logic to a rolling cadence contract. Currently live across our primary Western European test regions, this framework operates on four distinct rules:

1. Rolling Escrow Locks: Funds for the upcoming instance are auto-reserved from the client’s designated payment method 48 hours before the scheduled mission. The provider knows payment is guaranteed before stepping foot on site.
2. Isolated Instance Disputes: If Instance #12 has an issue—say, a missed corner or a late arrival—the client can open a dispute strictly scoped to Instance #12. The dispute window lasts 24 hours post-completion. Critically, this does not freeze Instance #11’s historical payout, nor does it cancel Instance #13. The contract ledger isolates individual events rather than halting the entire working relationship.
3. Tenure-Based Fee Compression: Platform service fees on recurring missions decrease progressively over time. At visit #1, standard service rates apply. By visit #10, the platform commission drops significantly, subsidised in part by lower acquisition overhead and reflected in internal WEVAR fee-rebate calculations.
4. Context Memory via Mia: The AI infrastructure retains historical preferences and technical logs across every session. If a client specified six months ago that the circuit breaker in the basement trips when the laundry unit runs simultaneously, Mia carries that operational context into every subsequent mission briefing provided to the contractor.

A Worked Example: Bi-Weekly Technical Property Care

To understand how the underlying software handles these transactions, consider a three-month recurring contract between a boutique property manager and a certified electrician on Mission.

At agreement setup, the parties define the cadence (every second Thursday), the price per instance (€120), and the service parameters. Mia generates a master recurring contract on the universe-level ledger.

Forty-eight hours before each event, the system executes an automated pre-authorization. If the pre-authorization fails—due to an expired card or insufficient account balance—the provider is notified immediately, and the scheduled mission is paused before labor is expended. This eliminates the universal headache of service providers chasing unpaid invoices after work has been rendered.

When the provider completes the task, they log the job through the application interface. Mia parses any uploaded media, checks timestamp alignment against the location ledger, and initiates the 24-hour dispute counter. If no action is taken by the client, the escrow smart release deposits €120 minus the reduced tenure fee directly into the provider's balance.

Because the provider’s Contribution Score rises with every successfully settled recurring mission, their placement in search results for high-value one-off jobs also increases. Staying on-platform compounds their professional credibility in a way off-platform cash payments never can.

The Realities of Disintermediation and Current Limitations

We must be candid: technology cannot eliminate disintermediation entirely. High-trust, low-frequency relationships—such as a personal relationship between a single homeowner and a house sitter who have worked together for two years—will occasionally exit the ecosystem once absolute interpersonal trust is established.

Our goal is not to police every human interaction with draconian rules, but to ensure the administrative, financial, and safety value of remaining on WEVONE outweighs the modest platform fee.

Currently, our recurring engines handle deterministic schedules exceptionally well—weekly, bi-weekly, or monthly cadence. However, variable-cadence recurring work (e.g., "come by whenever it rains heavily to check the roof") remains in closed beta testing. Tracking irregular events requires dynamic triggers from external data sources—such as weather APIs or IoT sensor integrations—which are scheduled for broader deployment in upcoming platform releases.

Furthermore, cross-border tax calculations for recurring services rendered near European national boundaries (such as between Strasbourg and Kehl) present complex VAT reconciliation requirements that still require periodic manual compliance reviews.

Retention as an Engineering Problem

Retention in gig marketplaces is rarely a messaging problem; it is an incentive alignment problem. By treating recurring work as a specialized architectural primitive—combining isolated dispute windows, progressive fee reductions, and continuous AI context memory—the Mission universe transforms routine labor from a series of high-friction transactions into a stable, verifiable professional history.

When the administrative headache of self-invoicing, chasing late payments, and re-explaining house rules exceeds the cost of a platform fee, staying on-platform ceases to be a rule users begrudgingly follow. It becomes the path of least resistance.