Mission

Mission, in five years: Recurring missions and retention

Platform leakage kills local service marketplaces. WEVONE's five-year Mission architecture replaces static transaction taxes with programmatic trust and decaying protocol fees.

On a Thursday morning in suburban Lyon, a gardener named Marc completes his eighth bi-weekly maintenance visit for a homeowner named Claire. On a legacy platform like TaskRabbit or Bark, Marc and Claire would have exchanged direct phone numbers by week three. The math of marketplace leakage is predictable: once a buyer and seller verify each other's basic competence and honesty, paying a perpetual 15% to 20% platform tax becomes irrational. The platform served its discovery purpose, and then it became an obstacle.

Marketplace disintermediation is not a bad user habit; it is a rational response to bad platform incentives. When a marketplace extracts the same margin from the hundredth transaction as it did from the first, it invites its own bypass. WEVONE Mission is being built on a counter-hypothesis: retention in local service markets requires an infrastructure that grows cheaper, smarter, and structurally more protective as a relationship matures.

The Leakage Math and the Decaying Protocol Fee

To understand why local service platforms stall at scale, look at transaction lifetime value curves. Benchmark data from European home-services marketplaces between 2018 and 2023 indicates that up to 65% of repeat transaction volume moves off-platform within 60 days of the initial match. The platform absorbs 100% of the customer acquisition cost (CAC) but retains only a fraction of the ongoing gross merchandise value (GMV).

WEVONE Mission addresses this through a dynamic protocol fee model tied to relationship longevity.

  • [FACT] Current single-instance Mission contracts charge a baseline protocol fee of 12% to cover network operations, escrow insurance, and settlement.
  • [IN BETA] The Recurring Mission Engine introduces a fee decay function. For every consecutive successful execution of a recurring contract—whether weekly cleaning, monthly property inspection, or bi-weekly elder care—the platform fee drops. By transaction ten between the same pair, the fee settles at 2.5%.
  • [PROJECTION] Internal financial modeling suggests that reducing protocol friction to 2.5% shifts the risk-reward calculus. Moving off-platform saves the client negligible pocket change while stripping away automated dispute protection, liability insurance, and contribution scoring.

At 2.5%, remaining on-platform acts as cheap insurance rather than an extortionate toll.

Technical Architecture: Escrow, Memory, and Ledgers

Lowering fees is insufficient if the administrative overhead remains high. A recurring transaction must execute with zero manual friction for both parties while maintaining strict cryptographic and financial auditability.

Here is how a recurring Mission contract executes on WEVONE:

  1. Contract Initialization: The client and provider set parameters (frequency, scope, rate, and dispute window) within the Mission terminal.
  2. Escrow Staging: Forty-eight hours before a scheduled mission, WEVONE’s transactional escrow lock-funds from the client's balance. Funds are held in a segmented vault, isolated from platform operational accounts.
  3. Context Injection: Mia—WEVONE’s cross-universe AI infrastructure—retrieves historical performance data and specific operational directives from context memory. The provider receives an automated briefing: entry access codes, specific zone preferences updated from previous visits, and material requirements.
  4. Verification and Settlement: Upon completion, validated via geolocation ping or digital sign-off, a 12-hour dispute window opens. If no anomaly is flagged, the escrow releases funds directly to the provider’s account, recording the completed state to the universe ledger.
  5. Score Calibration: The transaction updates the provider's Contribution Score and adjusts the pair's longevity index, further locking in the decayed fee tier.

By embedding Mia’s context memory directly into the workflow, the platform retains crucial operational knowledge. If Claire adds a specific care instruction for her garden’s irrigation system during week four, Mia preserves that detail permanently. The provider does not need to re-read lengthy chat histories, and the client does not need to re-explain expectations. The platform becomes the repository of operational trust.

Cross-Universe Integration: The Five-Year Horizon

Standalone service apps fail because their context is siloed. A cleaning service app knows nothing about the user’s travel schedule; an event management tool knows nothing about the user’s local vendor network.

WEVONE’s architecture connects these dots across distinct universes:

  • [AMBITION] Automating Mission triggers from Nest and Event states. A short-term rental check-out in WEVONE Nest will automatically generate and dispatch a high-priority cleaning Mission to a preferred local provider, complete with pre-funded escrow drawn from the guest's cleaning deposit.
  • [VISION] Over a five-year horizon, WEVONE aims for 70% of total Mission GMV to derive from automated, recurring contracts spanning multiple universes. A single user profile will maintain recurring home care (Mission), seasonal equipment rentals (Tools), and transport logistics (Pilote) under a unified trust and score ledger.

When a provider builds high reputation scores in Mission, that capital translates directly into lower collateral requirements when renting high-value assets in Tools or hosting listings in Nest. Moving off-platform breaks this feedback loop, stripping the provider of verifiable reputation growth.

The Reality of Early-Stage Friction

We must be precise about where WEVONE Mission stands today. Bluster is the refuge of fragile marketplaces.

Currently, WEVONE is early. Single-instance missions and basic escrow settlements are live and functional across selected European hubs. The Recurring Mission Engine and dynamic fee decay schedules are actively undergoing closed testing in beta.

Several open questions remain unresolved:

  1. Long-Term Dispute Edge Cases: How does algorithmic arbitration handle a dispute on week 24 of a recurring contract where trust breaks down over cumulative, subtle degradation of service rather than a single catastrophic failure? Standard dispute windows are optimized for binary outcomes (done/not done), not gradual quality drift.
  2. Off-Platform Cash Substitution: In regions with high cash usage, even a 2.5% platform fee faces competition from untracked paper money. Our bet relies on the value of reputation visibility—providers must actively choose to trade away quantifiable platform status for unrecorded cash payments.
  3. Liability Limits: As recurring contracts scale to complex services (such as specialized home medical assistance or ongoing structural maintenance), standard platform liability reserves face stricter regulatory scrutiny under EU consumer protection frameworks.

WEVONE does not claim to have eliminated marketplace leakage entirely. Instead, we are engineering an economic landscape where staying on-platform is the most rational, defensible choice a local business or client can make.