Imagination ThΓ©o Bondolfi, formalized with AI assistance.Learn more · Contribute

Use Case: Taxi Cooperative β€” Competing with Uber Without Surrendering Your Brand

πŸ“‹ Use Case Overview

TypeTransport cooperative migration
Maturityβ­β˜†β˜†β˜†β˜† (concept phase)
User Group(s)Transport User Group
Ring(s)Mobility Ring
Active funders3 (illustrative)
Contracts signed0 (pre-launch)
Cash/Miles ratio25% / 75% (Boost-dependent)
Avg. satisfactionβ€” (pre-launch)
DeploymentLocal
ProgrammeTransport Programme

All figures are illustrative unless otherwise stated.

Table of Contents

1. Context & Problem

Local taxi cooperatives and independent driver unions across the world are losing market share to platform giants like Uber, Lyft, and Bolt. The problem is not primarily the quality of service β€” in many cities, local taxi coops are better regulated, fairer to drivers, and more trusted by long-term clients. The problem is Infrastructure: the app, the payment system, the dispute resolution mechanism, the contracts.

Traditional responses to this challenge have failed:

The fundamental tension: coops want to keep their local brand and identity (Taxi Genève, Taxistas Unidos de São Paulo, etc.) while gaining access to the digital back-office Infrastructure that Uber owns. These are two different things — and WikiDeal separates them.

Key insight: a taxi cooperative does not need to become WikiDeal. It needs WikiDeal's contract Infrastructure in its back-office, while keeping its own name, livery, and client relationships on the front end.

2. The WikiDeal Concept

WikiDeal offers taxi cooperatives a co-opetitive back-office Infrastructure:

The coop keeps its brand, its driver relationships, its local knowledge. WikiDeal provides the contract layer, the payment Infrastructure, and the dispute resolution mechanism.

3. User Journey (7 steps)

Cooperative Registration

The taxi cooperative registers as a WikiDeal user group. The coop's administrator creates an account, declares the number of drivers, and selects the applicable legal jurisdiction. WikiDeal assigns a coop identifier and a dedicated contract template library.

Driver Onboarding

Each driver signs a driver-coop agreement through the WikiDeal interface. The agreement is generated from the coop's template, reviewed by the driver, and signed electronically. All agreements are stored on the WikiDeal decentralized data layer β€” the coop can export them at any time.

Client Registration & Trip Contract

When a client books a trip, a micro-contract is automatically generated: it specifies the service (origin, destination, estimated fare, payment method), the applicable terms, and the dispute resolution mechanism. The client accepts with a single tap.

Trip Execution

The driver completes the trip. The client confirms receipt. The contract is marked "executed." Payment is processed through the WikiDeal payment layer at 1–2% Commission β€” the rest goes directly to the driver and the coop.

Dispute Resolution (if needed)

If a dispute arises (wrong fare, safety issue, lost item), either party can initiate a WikiDeal dispute. A human WikiDeal intermediary contacts both parties, applies the contract terms, and proposes a resolution. The coop's reputation score is updated transparently.

Governance Participation

The coop participates in WikiDeal governance with weighted voting: 1 vote per driver, plus 1 vote for the coop as an entity. Coops can propose changes to the standard contract templates, vote on Commission rate adjustments, and shape the future of the platform.

Community Migration Observatory

The coop's migration is documented in the Community Migrations Observatory. Other coops can see what worked, what didn't, and the measurable impact on driver income and client satisfaction. The knowledge is shared, not siloed.

4. Model Contract (simplified)

πŸ“‹ Driver–Cooperative Framework Agreement (WikiDeal Template)

Article 1 β€” Parties
The Cooperative: [Cooperative Name], registered at [address], represented by [Name, Title].
The Driver: [First Name Last Name], license number [XX-XXXX], vehicle [make, model, plate].
Article 2 β€” Relationship
The Driver is an independent member of the Cooperative, not an employee. The Cooperative provides dispatch Infrastructure, contract management, and payment processing. The Driver retains full ownership of their vehicle and their working schedule.
Article 3 β€” WikiDeal Back-Office
All transport contracts are managed through the WikiDeal platform. The Commission charged by WikiDeal is [1–2%] of each trip's net fare. The Cooperative's internal Commission is [X%], as voted by the Assembly. Both figures are published transparently to all drivers.
Article 4 β€” Data Ownership
All passenger data collected via the platform belongs to the Cooperative. WikiDeal processes data solely for contract execution and dispute resolution. The Cooperative may export all data at any time without penalty.
Article 5 β€” Dispute Resolution
Disputes between Driver and client are referred to the WikiDeal Dispute Resolution Service. Disputes between Driver and Cooperative are referred to the Cooperative's Assembly, with WikiDeal as observer.
Article 6 β€” Termination
Either party may terminate this agreement with [30 days] written notice. Upon termination, all pending trip contracts are honored. The Driver retains access to their Transaction history and contracts for [5 years].

5. Concrete Scenario

πŸš• Example: Taxi GenΓ¨ve Cooperative, Geneva

Situation: Taxi Genève is a cooperative of 85 licensed drivers operating in Geneva. In 2024, Uber captured 40% of the market. Taxi Genève's drivers earn 15% less than in 2019. The coop has no app, no electronic contracts, and loses drivers to Uber every month.

The challenge: Build or buy a digital platform without destroying the cooperative's identity and independence. Budget: CHF 50,000 (two years of accumulated reserves). Uber's licensing fees for a comparable white-label solution: CHF 80,000/year.

WikiDeal Migration:

  1. Taxi Genève registers as a WikiDeal user group. Setup fee: CHF 500 (one-time). Monthly fee: CHF 200 (Infrastructure maintenance — shared across all coops on the platform).
  2. 85 drivers are onboarded over 3 weeks. Each signs a digital driver-coop agreement. Average onboarding time: 12 minutes per driver.
  3. WikiDeal generates the Taxi Genève contract templates — transport agreements in French, English, and Portuguese (for tourist clients). The coop's logo appears on all contracts.
  4. After 6 months: average driver income up 12% (Commission reduced from 18% to 3% total). Client satisfaction score: 4.6/5 (up from 4.1/5 with paper contracts).
  5. Taxi Genève presents its migration at the WikiDeal Community Migrations Observatory. Three other Swiss coops (Bern, Zurich, Basel) begin the same process.

Total cost (year 1): CHF 2,900 (CHF 500 setup + CHF 200 Γ— 12 months). Savings vs. status quo: CHF 47,000 (Commission reduction for drivers).

6. Frequently Asked Questions

Does the coop need to change its name or branding?
No. The coop keeps its name, livery, and client relationships entirely. WikiDeal is invisible to passengers β€” it's the back-office Infrastructure, not the front-end brand.

What happens if WikiDeal disappears?
WikiDeal is built with planned obsolescence in mind. All contracts are stored in portable formats (JSON + PDF). The coop can export everything at any time. The contract templates are published under CC BY-SA β€” any legal professional can maintain them independently.

Is 1–2% Commission sustainable?
Yes. WikiDeal's Commission covers Infrastructure costs only, not profit extraction. The formula is published and auditable. As more coops join, the unit cost decreases further.

How does WikiDeal handle regulated markets (taxi licensing)?
WikiDeal does not replace local licensing requirements. It handles the contract layer on top of existing regulations. The coop remains responsible for ensuring all drivers hold valid licenses for their jurisdiction.

Can drivers from multiple coops work together?
Yes. Co-opetition allows coops to share overflow demand during peak periods under inter-coop service agreements β€” standard WikiDeal templates exist for this.

πŸ“Š Success Indicators

Key performance indicators for the Taxi Cooperative marketplace use case. These targets are indicative and community-modifiable as the programme matures.

Active Driver-Members
β‰₯ 25 per city
Minimum cooperative viability threshold per urban territory
Average Ride Commission
≀ 2%
Effective platform Commission rate on ride value
Driver Satisfaction Score
β‰₯ 4.2 / 5
Quarterly survey of driver-members on working conditions and income
Passenger Rating
β‰₯ 4.4 / 5
Average passenger rating of rides over rolling 90 days
On-Time Rate
β‰₯ 90%
Percentage of pickups within 5 minutes of estimated arrival
Driver Income vs. Platform Average
+15%
Target: driver take-home income 15% above equivalent platform average
Dispute Rate
< 1%
Rides resulting in a formal complaint or dispute
β†’ See also: WikiDeal Socio-Economic Success Criteria

βœ… Quality Criteria

ISO-inspired quality standards for the Taxi Cooperative use case. Standards are reviewed annually by the community.

StandardDimensionCriteriaTarget
QS-TAXI-001 Vehicle Safety All cooperative vehicles inspected annually. Safety certificate required. Vehicles failing inspection suspended until remedied. 100% valid certificates
QS-TAXI-002 Driver Standards All driver-members hold valid professional driving licence. Criminal background check renewed every 2 years. 100% compliance
QS-TAXI-003 Service Quality Passenger rating system active. Drivers with average below 3.8 over 30 days enter performance support programme. All drivers β‰₯ 3.8 average
QS-TAXI-004 Cooperative Governance Driver-members vote annually on pricing, rules, and officer elections. Quorum β‰₯ 51%. Results published. Annual democratic process
QS-TAXI-005 Environmental Cooperative tracks and publishes fleet COβ‚‚ per km annually. Target: 20% improvement per 3-year cycle. COβ‚‚ reduction roadmap active
β†’ See also: WikiDeal Socio-Economic Success Criteria