Solstice FC
All debates

Scaling Economics

Round:R10Revenue
Result:NEG wins 17-14
AFF:Scale-Now Advocate
NEG:3x Design Advocate
Judge:3-judge panel

Verdict

Verdict — Round R10

Resolution

Resolved: The Solstice FC revenue model should be designed for a 500-club national network from day one, even if it launches with 5 clubs in San Diego.

Judge: Pragmatist Judge

Scores

Category AFF (Systems Thinker) NEG (Community Organizer)
Logic 4 4
Feasibility 3 5
Evidence 3 4
Clash 4 4
Total 14 17

Reason for Decision (RFD)

As a judge who asks "would this actually work for a real club in a real city?", this round was not as close as the logical quality of both cases might suggest. The AFF made a structurally sound argument that collapsed under practical scrutiny. The NEG won by being more grounded in how organizations actually operate.

The AFF's core insight is correct: lock-in is real. Revenue model decisions made at founding do become harder to change over time. The credit union and housing co-op evidence supports this. The DA example, while imperfectly applied, gestures at a real pattern. If this were a debate about whether lock-in exists, the AFF wins.

But the AFF's proposed solution — designing for 500 clubs at the 5-club stage — is impractical in ways the AFF never adequately addressed. The percentage-based assessment requires revenue verification infrastructure. The geographic cost-of-living adjustments require data and adjudication processes. The dormant revenue categories require governance documentation. Each of these is individually modest, but collectively they represent significant operational complexity for a 5-club startup running on $72,000-$75,000 in cooperative revenue. The AFF claims these are "lightweight," but the NEG's cross-examination effectively showed that the difference between the percentage model and the flat model at 5 clubs is $3,000 — an amount that does not justify the verification overhead.

The NEG's strongest argument was the governance debt concept. Every architectural decision made before it is needed generates questions, expectations, and maintenance costs. A 5-club cooperative has perhaps 10-15 people involved in governance (board members, committee chairs, club directors). Those people have limited bandwidth. Every hour spent explaining dormant revenue categories or geographic adjustment placeholders is an hour not spent on the existential priority: proving the model works for the first 750 players. This is not a theoretical concern — it is the primary failure mode of ambitious cooperative startups.

The NEG's cross-examination answer on governance hierarchy was the round's most important moment. When asked about lock-in in founding documents, the Community Organizer drew a critical distinction: principles belong in articles of incorporation (hard to change), operational details belong in policies (easy to change). This resolves the AFF's central concern without requiring premature architecture. If the articles say "the cooperative funds operations through member assessments" and the operating agreement says "$100/player," changing the amount at 50 clubs requires an operating agreement amendment, not an articles amendment. The lock-in risk the AFF warns about is a function of document hierarchy, not architectural complexity.

The AFF's rebuttal made a fair point about 1970s food co-op failures, but the NEG correctly noted that those co-ops failed because they never professionalized — not because they started simple. The distinction between "start simple and evolve" versus "start simple and never change" is the NEG's entire thesis, and the AFF did not adequately distinguish between these two failure modes.

The decisive pragmatic question: A 5-club cooperative in San Diego has one part-time coordinator and $75,000 in cooperative revenue. Does this organization benefit more from a percentage-based assessment formula with geographic adjustments and dormant revenue categories? Or from a simple flat fee, a clear operating agreement, and a governance culture that normalizes evolution? For this judge, the answer is obvious. Start simple. Build the culture of adaptation. Add complexity when demonstrated need — not speculative architecture — demands it.

Spec Implications

  • The revenue model should be designed for the current scale (5-10 clubs) with explicit provisions for periodic review and adaptation, not for 500 clubs from day one.
  • Use flat per-player assessments at launch ($100/player or similar). Simpler, more transparent, harder to game than percentage-based fees.
  • Principles in articles of incorporation, formulas in operating agreements. This governance hierarchy preserves both mission permanence and operational adaptability.
  • Mandatory revenue model review every 3 years or at every doubling of membership (whichever comes first). This institutionalizes evolution without requiring premature architecture.
  • "Design for the next 3x" is the right planning horizon. At 5 clubs, design for 15. At 15, redesign for 50. At 50, redesign for 150. This matches how successful cooperatives actually grow.
  • Geographic cost-of-living adjustments should be deferred until the cooperative has member clubs in at least 3 distinct cost markets. Building the mechanism before the data exists wastes governance bandwidth.

AFF Constructive

AFF — The Systems Thinker

Resolution

Resolved: The Solstice FC revenue model should be designed for a 500-club national network from day one, even if it launches with 5 clubs in San Diego.

AFF Constructive

Value Premise: Structural Integrity

The central value I uphold is structural integrity — the principle that a system's foundational architecture determines its trajectory more than any subsequent optimization. Revenue models are not neutral containers that can be swapped out at will. They embed assumptions about incentives, governance, and resource flows that become progressively harder to change as the system grows. Getting the architecture right at the beginning is not premature optimization — it is the single most leveraged decision the cooperative will make.

Value Criterion: Path-Dependency Resistance

The criterion for evaluating this debate is path-dependency resistance — the degree to which early design decisions preserve the cooperative's ability to scale without requiring fundamental restructuring. A revenue model that works for 5 clubs but breaks at 50 imposes a "structural tax" at every growth milestone — forced renegotiation, member disruption, governance crises. The superior model is the one that scales continuously without phase transitions.

Contention 1: Revenue Model Lock-In Is Real and Documented

Cooperative networks consistently demonstrate that financial architecture set at founding becomes nearly impossible to change after the first 3-5 years. Credit unions that launch with a particular fee structure find that changing it requires member votes, regulatory filings, and system migrations that take 18-24 months. Housing cooperatives that set maintenance fee formulas at incorporation discover that changing those formulas requires supermajority amendments to articles of incorporation — a process so onerous that most simply live with increasingly dysfunctional formulas for decades.

The specific lock-in risks for Solstice FC are identifiable today. If the cooperative launches with a flat per-player assessment of $100 and that revenue funds one part-time coordinator, the entire operational model is built around that staffing level. When the cooperative grows to 50 clubs and needs a professional staff of five, it cannot simply raise the assessment from $100 to $300 — doing so requires a member vote, and the 45 clubs that joined at $100 will resist tripling their contribution. The assessment amount, the allocation formula, the governance process for changing it — all of these become locked in within the first few operating cycles.

The Development Academy's collapse illustrates this precisely. The DA launched with a fee structure designed for its initial scale, then found itself unable to adjust as it grew. Clubs that joined at one cost basis resisted increases needed to fund expanded operations. The financial architecture that worked for 70 clubs could not scale to 150, and the resulting tension contributed to the system's fragility.

Contention 2: Scale-Designed Models Can Be Lightweight at Launch

The NEG will argue that designing for 500 clubs creates unnecessary overhead for a 5-club startup. This conflates architectural design with operational weight. A revenue model designed for 500 clubs does not mean hiring a 500-club staff at launch. It means:

  • Assessment formulas that scale: Instead of a flat $100/player, a tiered formula — say 4% of player fees — that automatically adjusts with both fee levels and membership growth. At 5 clubs with $2,400/player average, the cooperative collects $96/player ($72,000 total). At 500 clubs, it collects the same percentage but generates $7.2 million. No member vote required to change the assessment.

  • Governance thresholds that anticipate growth: Revenue model amendments require a supermajority at any scale, not just when the cooperative is large enough for politics to emerge.

  • Revenue diversification hooks: The cooperative's financial structure should include categories for sponsorship revenue, facility income, and technology licensing from day one — even if those categories generate $0 initially. Adding new revenue categories retroactively requires amending financial governance documents, which is far harder than activating a dormant category.

  • Regional cost-of-living adjustments: A flat fee works in one city. A national network spanning San Diego, Detroit, and rural Kansas needs a cost-adjustment mechanism. Building this into the founding formula (even if it defaults to 1.0x for San Diego) avoids the politically explosive task of introducing geographic fee variation after clubs in different markets have already joined.

Contention 3: The 5-to-500 Transition Kills Organizations That Are Not Prepared

The most dangerous phase in cooperative growth is the transition from "everyone knows everyone" to "we need institutional processes." Organizations that fail to anticipate this transition experience what cooperative governance scholars call the "founder's crisis" — the point where informal arrangements that worked with 10 members create chaos with 100.

For Solstice FC's revenue model specifically, the transition risks include: assessment disputes between founding members and new entrants, geographic cross-subsidization conflicts, revenue allocation fights between operational spending and scholarship funds, and executive compensation debates. Every one of these conflicts is easier to resolve if the cooperative's founding documents include explicit formulas, thresholds, and processes — even if those provisions are dormant at launch.

The alternative is a series of governance crises at every growth milestone, each one consuming leadership attention, eroding member trust, and risking defection of clubs that feel disadvantaged by ad hoc decisions.

AFF Rebuttal

The NEG's case reduces to one argument: startup agility. The Community Organizer claims that heavy architecture kills startups, and that the cooperative should stay lean and figure out scale when it gets there. This is seductive but historically catastrophic for cooperatives.

The NEG cites food co-ops and community organizations that started simple and grew. But they omit the failure cases — and there are far more of those. For every food co-op that successfully transitioned from a buying club to a multi-location operation, dozens collapsed during the transition because their founding financial structures could not accommodate growth. The natural food co-op movement of the 1970s produced hundreds of small cooperative stores; fewer than 10% survived past 15 years, and the primary cause of failure was not lack of demand but inability to professionalize financial management within structures designed for volunteer governance.

The NEG's strongest point — that a 5-club startup should not act like it has 500 clubs — is a straw man I never advanced. I am not arguing for 500-club operations at launch. I am arguing for 500-club architecture at launch. The difference is the difference between building a one-story house on a foundation designed for ten stories versus building a one-story house on a slab. The first costs marginally more at construction; the second makes expansion impossible without demolition.

The NEG never engaged with the lock-in evidence. If the assessment formula, governance thresholds, and revenue categories are hard to change after year three, the cooperative's founding decisions are permanent decisions. That is the core argument, and the NEG left it standing.

Cross-Examination

Cross-Examination — Round R10

Resolution

Resolved: The Solstice FC revenue model should be designed for a 500-club national network from day one, even if it launches with 5 clubs in San Diego.

NEG Cross-Examination of AFF (The Community Organizer questions The Systems Thinker)

Q1: You propose a percentage-based assessment (4% of player fees) instead of a flat per-player fee. How does the cooperative verify each club's actual player fee revenue? Do clubs self-report, or does the cooperative audit?

A1: The cooperative would receive standardized financial reports from member clubs as a condition of membership — similar to how franchise systems require franchisees to report revenue. At 5 clubs, this is a simple spreadsheet exercise. At 500 clubs, it requires a financial reporting system, which is exactly the kind of infrastructure the cooperative should plan for now. Self-reporting with periodic audit is the standard model for percentage-based cooperative assessments. The gaming risk is real but manageable through clear reporting standards and the mutual accountability that comes from cooperative culture.

Q2: You argue that adding revenue categories retroactively is "far harder than activating a dormant category." Can you name a specific legal or procedural barrier to adding a new revenue category to a 501(c)(3) operating agreement at the 50-club stage?

A2: The barrier is not primarily legal — it is political. Adding a new revenue category at 50 clubs means 50 clubs must agree on how that revenue is allocated, who controls it, and what governance applies. With a sponsorship revenue category, for example: does sponsorship revenue get distributed equally to all clubs? Proportionally to player count? Retained centrally? At 50 clubs with diverse interests, this negotiation is contentious and time-consuming. If the category and its allocation formula already exist in the founding documents, endorsed by the original 5 clubs who shared a vision, the 45 clubs that join later accept those terms as a condition of membership. They are joining a defined system rather than negotiating a new one.

Q3: Your percentage-based model generates $72,000 for the cooperative at 5 clubs. Your flat-fee alternative that I am proposing would generate $75,000 at $100/player. The difference is $3,000. Is the architectural elegance of a percentage-based system worth the operational complexity of revenue verification for a $3,000 difference?

A3: The $3,000 difference at 5 clubs is irrelevant — I concede that. The relevant comparison is at 50 clubs. At $100/player flat, the cooperative collects $750,000 regardless of whether average player fees have risen to $3,000 due to inflation or market changes. At 4%, the cooperative collects $900,000. Over 10 years with modest fee inflation, the cumulative difference is in the millions. Percentage-based assessments are self-adjusting; flat fees require periodic renegotiation, which is precisely the lock-in risk I am warning about.

AFF Cross-Examination of NEG (The Systems Thinker questions The Community Organizer)

Q1: You advocate designing for "the next 3x of growth." At 5 clubs, that means designing for 15. What specific revenue model elements would you change when transitioning from 15 clubs to 50? And how do you propose making those changes without alienating the original 15 clubs who joined under different terms?

A1: At 15 clubs, the cooperative is still small enough for direct governance — everyone knows everyone. The transition to 50 would require professionalizing the financial function: hiring a part-time CFO, implementing standardized financial reporting, and potentially moving from flat assessments to tiered assessments based on club size. These changes would be proposed by the board, discussed at a member meeting, and voted on. The original 15 clubs would have a voice in shaping the new terms, and because they have seen the cooperative grow and understand the need, they are far more likely to support changes grounded in demonstrated need than theoretical projections. Real data is more persuasive than founder speculation.

Q2: You cite REI, credit unions, and agricultural co-ops as examples of cooperatives that started simple and evolved. REI nearly went bankrupt in 1976 because its financial structure could not handle growth from a local to a national operation. How is that a success story for starting simple?

A2: REI's 1976 crisis was caused by rapid physical expansion — opening too many retail stores too fast — not by its founding financial architecture. The lesson of REI is not "design for scale from day one" but rather "do not expand faster than your operational capacity." Solstice FC's growth would be organic, driven by clubs seeking membership, not by the cooperative aggressively opening new markets. The growth pattern is fundamentally different. And REI survived its crisis precisely because it could restructure — something that would have been harder, not easier, with rigid founding architecture.

Q3: You say "add complexity when demonstrated need arises." But the cooperative's founding documents — articles of incorporation, operating agreement, bylaws — are the hardest documents to change once filed. If the revenue model is encoded in these documents at the simple stage, and complexity is needed later, doesn't your approach create exactly the lock-in problem I described?

A3: The founding documents should define principles, not formulas. The articles of incorporation should state that the cooperative funds operations through member assessments, maintains a scholarship fund, and may pursue additional revenue sources as approved by the membership. The specific assessment amount, allocation formula, and governance process should live in the operating agreement or policies, which are easier to amend. The AFF's mistake is conflating constitutional-level documents with operational-level documents. Principles lock in; operational details should not. A well-designed governance hierarchy preserves adaptability where it matters most.

NEG Constructive

NEG — The Community Organizer

Resolution

Resolved: The Solstice FC revenue model should be designed for a 500-club national network from day one, even if it launches with 5 clubs in San Diego.

NEG Constructive

Counter-Value: Organic Legitimacy

The central value I uphold is organic legitimacy — the principle that a cooperative's financial architecture should emerge from the lived experience of its members, not from the projections of its founders. Revenue models designed in a conference room for a future that may never arrive carry two fatal risks: they solve problems that do not exist while creating overhead that does, and they embed assumptions about scale that may be wrong in ways the founders cannot foresee.

Counter-Criterion: Startup Survival Rate

The proper criterion is startup survival rate — the likelihood that the cooperative reaches year five with a functioning, growing membership. A revenue model optimized for 500 clubs is worthless if the cooperative dies at 12 clubs because it was too complex, too rigid, or too expensive for its actual scale. Survival first, scale second.

Attack on AFF Contention 1: Lock-In Is Real But Overrated in Early-Stage Cooperatives

The AFF argues that revenue model decisions become locked in within 3-5 years. This is true for mature cooperatives with hundreds of members, established bureaucracies, and regulatory entanglements. It is not true for a 5-club cooperative where the founders know each other by name, meet monthly, and can amend bylaws over a Zoom call.

The AFF's credit union and housing co-op examples are misleading because those entities operate under regulatory frameworks (NCUA for credit unions, state housing law for co-ops) that impose change-management requirements. Solstice FC, as a 501(c)(3) nonprofit cooperative, faces far less regulatory friction. Amending its assessment formula at the 5-club stage requires a board vote and an updated operating agreement — a process that takes weeks, not months. The lock-in risk the AFF describes is real but temporally distant. It becomes acute around 50-100 clubs, not 5-10. The cooperative has a substantial window to learn from experience before lock-in constrains adaptation.

The DA collapse analogy is also misapplied. The DA's financial problems were not caused by early-stage design decisions that locked in; they were caused by US Soccer's decision to mandate participation requirements that clubs could not meet. The DA's fee structure was not the binding constraint — the competitive mandate was. The AFF is attributing to financial architecture a failure that was actually about governance overreach.

Attack on AFF Contention 2: "Lightweight at Launch" Is an Oxymoron

The AFF proposes percentage-based assessments, geographic cost-of-living adjustments, revenue diversification hooks, and scale-anticipating governance thresholds — and claims these are "lightweight." They are not.

A percentage-based assessment requires the cooperative to have auditable visibility into each club's player fees — which means either clubs self-report (creating gaming incentives) or the cooperative audits (creating administrative overhead and trust erosion). A flat per-player assessment is simpler, more transparent, and harder to game. The AFF's preference for percentage-based fees is architecturally elegant but operationally heavy.

Geographic cost-of-living adjustments require the cooperative to define cost regions, determine multipliers, and adjudicate disputes — all before a single club outside San Diego has joined. This is not "building a foundation for ten stories." This is building an elevator in a one-story house because you might build more stories later. The elevator costs money, takes up space, and serves no one today.

Revenue diversification "hooks" — placeholder categories for sponsorship, facility income, technology licensing — are harmless in theory but corrosive in practice. They signal to the founding clubs that the cooperative's leaders are focused on a hypothetical future rather than the present. Community organizers know that movements die when leaders skip ahead to the victory celebration before winning the first battle. Founding members need to see their leaders solving today's problems, not designing dormant revenue categories.

Independent Argument 1: Premature Architecture Creates Governance Debt

Every architectural decision made before it is needed creates governance debt — the accumulated cost of maintaining, explaining, and defending structures that serve no current purpose. At 5 clubs, every hour spent on geographic cost adjustments, revenue category management, and percentage-based assessment auditing is an hour not spent on the work that actually matters: coaching quality, player development, family experience, and community building.

The AFF assumes governance debt is free because dormant provisions "just sit there." But governance structures are not code; they are social contracts. Every provision in the operating agreement creates expectations, invites interpretation, and generates questions. "What does the sponsorship revenue category mean?" "Why is the geographic adjustment set to 1.0?" "When will the technology licensing revenue materialize?" Founding members ask these questions, and answering them consumes leadership bandwidth that a 5-club startup does not have.

Independent Argument 2: The Cooperative Movement's Success Stories Are Bottom-Up

The most successful cooperative networks in American history — agricultural co-ops, credit unions, food co-ops, worker co-ops — all started with financial structures matched to their actual scale and evolved as they grew. The Farm Credit System started as local lending circles before federating into a national network. Credit unions started as single-employer savings pools before developing the complex financial products they offer today. REI started as a mail-order catalog with a simple membership fee before building the sophisticated revenue model it has now.

Not one of these succeeded by designing for national scale at founding. They succeeded by solving an immediate, local problem so well that others wanted to replicate the model. The financial architecture evolved in response to demonstrated demand, not in anticipation of it.

Solstice FC's revenue model should follow the same pattern: prove the model works for 5 clubs in San Diego, then evolve the financial architecture as growth demands. Design for the next 3x of growth, not the next 100x.

NEG Rebuttal

The AFF's rebuttal calls my position "historically catastrophic for cooperatives" and cites the 1970s food co-op failure rate. But the AFF's own evidence undermines this claim. The food co-ops that failed did not fail because they started simple — they failed because they never professionalized at all. They kept volunteer governance when they needed professional management. They kept informal financial practices when they needed audits. The failure was not in starting lean; it was in staying lean past the point where complexity demanded structure.

My position is not "never add complexity." My position is "add complexity when demonstrated need arises." There is a critical difference between "design for 500 from day one" and "design for 5 today, redesign for 50 at club 20, redesign for 500 at club 100." The AFF assumes redesign is catastrophic. History shows it is normal and healthy — provided the cooperative builds a culture of adaptation rather than a culture of rigidity.

The AFF's foundation metaphor — building on a slab versus building on a ten-story foundation — is persuasive but misleading. Buildings are physical structures where foundations cannot be replaced. Organizations are social structures where foundations are replaced all the time. Amazon's original revenue model (online bookstore) bears no resemblance to its current model (cloud computing, marketplace, advertising). Organizations that survive long-term are the ones that can reinvent their financial architecture, not the ones that guessed correctly at founding.

The decisive question the AFF cannot answer: if the 500-club model is wrong — if Solstice FC grows to 200 clubs, not 500, or grows nationally but through regional federations rather than a single network — the premature architecture becomes a constraint that must be unwound. My model adapts to any trajectory. The AFF's model bets on one.