The Tech Coup Review: Marietje Schaake on Big Tech, Democracy, and Public Accountability

Books / Tech Policy & Democracy

Marietje Schaake’s strongest point is not that technology companies literally replaced government, but that public institutions repeatedly outsourced capabilities and rule-setting power faster than they built the capacity to supervise them.

The Tech Coup argues that governments have transferred too much practical power to technology companies while preserving the appearance that public authority remains fully in control. Platforms shape speech and market access; cloud providers host critical systems; private vendors sell surveillance and cybersecurity tools; and technical standards can function like regulation before legislatures understand the issue.

Schaake writes from unusual institutional experience as a former member of the European Parliament and technology-policy leader. That gives the book a perspective different from the standard founder biography or antitrust polemic. The central problem is state capacity: democratic institutions cannot govern systems they do not understand, cannot audit, and increasingly depend on to operate.

A fair reading should avoid a false public-versus-private binary. Governments can be slow, opaque, coercive, and technically weak. Private firms can innovate quickly and deliver infrastructure that public agencies would struggle to build. The problem begins when dependence becomes unaccountable power—especially when contract terms, lobbying access, or technical opacity prevent meaningful public choice.

This review therefore treats The Tech Coup as a governance-design book. The practical question is how to preserve the benefits of private innovation while ensuring that public institutions retain enough expertise, bargaining power, transparency, and enforcement capacity to set legitimate rules.

Public power can migrate without formal privatization

The Tech Coup uses this issue to expose a governance gap: A government may retain legal authority while depending on private platforms, cloud systems, security vendors, and data infrastructure that shape what choices are operationally possible. The relevant question is not whether private technology is powerful in the abstract, but whether institutions that depend on it still retain meaningful choice, expertise, and authority when interests diverge.

The policy record provides a second lens on Schaake’s argument. Schaake’s book and independent reviews emphasize the gradual infiltration of technology firms into core public functions. In reading The Tech Coup, this matters because democratic control depends on implementation capacity, not merely statutory language. A rule that cannot be audited or enforced is weaker than its headline.

The argument also needs a market-aware qualification: private delivery is not inherently illegitimate; the key issue is whether public bodies preserve alternatives and oversight. Public institutions can fail, and private infrastructure can deliver security, scale, and innovation that would be expensive to reproduce. The governance objective is accountable dependence, not technological autarky.

For practitioners using The Tech Coup, the next step is to map critical government and enterprise functions where a single vendor has practical veto power or irreplaceable knowledge. Make the exit path, audit right, and decision owner explicit before the dependency deepens. That is a concrete way to preserve public or organizational agency without pretending every service must be built internally.

Surveillance procurement creates asymmetric expertise

The Tech Coup uses this issue to expose a governance gap: Public agencies can buy sophisticated monitoring systems from vendors whose capabilities, data practices, and failure modes they cannot fully evaluate. The relevant question is not whether private technology is powerful in the abstract, but whether institutions that depend on it still retain meaningful choice, expertise, and authority when interests diverge.

The policy record provides a second lens on Schaake’s argument. the book highlights technology procurement as a route through which private tools acquire public coercive power. In reading The Tech Coup, this matters because democratic control depends on implementation capacity, not merely statutory language. A rule that cannot be audited or enforced is weaker than its headline.

The argument also needs a market-aware qualification: some surveillance tools are essential for cybersecurity, fraud, and serious crime. Public institutions can fail, and private infrastructure can deliver security, scale, and innovation that would be expensive to reproduce. The governance objective is accountable dependence, not technological autarky.

For practitioners using The Tech Coup, the next step is to require independent technical evaluation, necessity tests, retention limits, audit logs, and explicit rules for secondary use before procurement. Make the exit path, audit right, and decision owner explicit before the dependency deepens. That is a concrete way to preserve public or organizational agency without pretending every service must be built internally.

Platform infrastructure creates rule-making power

The Tech Coup uses this issue to expose a governance gap: A platform can change ranking, access, moderation, fees, or APIs in ways that alter economic opportunity for users and businesses. The relevant question is not whether private technology is powerful in the abstract, but whether institutions that depend on it still retain meaningful choice, expertise, and authority when interests diverge.

The policy record provides a second lens on Schaake’s argument. the book treats platforms as institutional actors, while European regulation increasingly distinguishes systemic platforms and gatekeepers. In reading The Tech Coup, this matters because democratic control depends on implementation capacity, not merely statutory language. A rule that cannot be audited or enforced is weaker than its headline.

The argument also needs a market-aware qualification: private services need flexibility to manage abuse and improve products; not every product change is public regulation. Public institutions can fail, and private infrastructure can deliver security, scale, and innovation that would be expensive to reproduce. The governance objective is accountable dependence, not technological autarky.

For practitioners using The Tech Coup, the next step is to identify decisions that have quasi-regulatory effects and require notice, appeal, transparency, and portability where the stakes justify it. Make the exit path, audit right, and decision owner explicit before the dependency deepens. That is a concrete way to preserve public or organizational agency without pretending every service must be built internally.

The DMA and DSA solve different problems

The Tech Coup uses this issue to expose a governance gap: European digital regulation separates competition concerns around gatekeepers from systemic platform responsibilities around illegal content, transparency, and risk. The relevant question is not whether private technology is powerful in the abstract, but whether institutions that depend on it still retain meaningful choice, expertise, and authority when interests diverge.

The policy record provides a second lens on Schaake’s argument. official EU materials show distinct obligations and enforcement logics for the Digital Markets Act and Digital Services Act. In reading The Tech Coup, this matters because democratic control depends on implementation capacity, not merely statutory language. A rule that cannot be audited or enforced is weaker than its headline.

The argument also needs a market-aware qualification: regulation can impose compliance cost and may favor incumbents if rules are poorly designed. Public institutions can fail, and private infrastructure can deliver security, scale, and innovation that would be expensive to reproduce. The governance objective is accountable dependence, not technological autarky.

For practitioners using The Tech Coup, the next step is to evaluate each rule against a clearly stated market failure instead of treating “tech regulation” as one policy category. Make the exit path, audit right, and decision owner explicit before the dependency deepens. That is a concrete way to preserve public or organizational agency without pretending every service must be built internally.

State capacity is the hidden variable

The Tech Coup uses this issue to expose a governance gap: Rules matter only when agencies have technical staff, investigative powers, data access, budgets, and institutional memory to enforce them. The relevant question is not whether private technology is powerful in the abstract, but whether institutions that depend on it still retain meaningful choice, expertise, and authority when interests diverge.

The policy record provides a second lens on Schaake’s argument. Schaake repeatedly returns to the mismatch between private technical resources and public oversight capacity. In reading The Tech Coup, this matters because democratic control depends on implementation capacity, not merely statutory language. A rule that cannot be audited or enforced is weaker than its headline.

The argument also needs a market-aware qualification: more staff does not guarantee competence; incentives and procurement rules can still prevent effective action. Public institutions can fail, and private infrastructure can deliver security, scale, and innovation that would be expensive to reproduce. The governance objective is accountable dependence, not technological autarky.

For practitioners using The Tech Coup, the next step is to treat regulator capability, not legislation alone, as part of the investment and compliance environment. Make the exit path, audit right, and decision owner explicit before the dependency deepens. That is a concrete way to preserve public or organizational agency without pretending every service must be built internally.

Lobbying and expertise are difficult to separate

The Tech Coup uses this issue to expose a governance gap: Policymakers need technical information from industry, but the firms supplying expertise also have strong economic interests in how rules are written. The relevant question is not whether private technology is powerful in the abstract, but whether institutions that depend on it still retain meaningful choice, expertise, and authority when interests diverge.

The policy record provides a second lens on Schaake’s argument. the book is skeptical of revolving doors and access asymmetry in digital policy. In reading The Tech Coup, this matters because democratic control depends on implementation capacity, not merely statutory language. A rule that cannot be audited or enforced is weaker than its headline.

The argument also needs a market-aware qualification: excluding industry knowledge entirely would produce worse rules and slower learning. Public institutions can fail, and private infrastructure can deliver security, scale, and innovation that would be expensive to reproduce. The governance objective is accountable dependence, not technological autarky.

For practitioners using The Tech Coup, the next step is to create transparent consultation records, diversify expert sources, and distinguish factual technical input from preferred policy outcomes. Make the exit path, audit right, and decision owner explicit before the dependency deepens. That is a concrete way to preserve public or organizational agency without pretending every service must be built internally.

Cloud dependence is a sovereignty issue

The Tech Coup uses this issue to expose a governance gap: Critical public and private systems increasingly rely on a small number of cloud and software providers, concentrating operational risk and bargaining power. The relevant question is not whether private technology is powerful in the abstract, but whether institutions that depend on it still retain meaningful choice, expertise, and authority when interests diverge.

The policy record provides a second lens on Schaake’s argument. Schaake’s public-power thesis extends naturally to infrastructure layers that institutions cannot easily replace. In reading The Tech Coup, this matters because democratic control depends on implementation capacity, not merely statutory language. A rule that cannot be audited or enforced is weaker than its headline.

The argument also needs a market-aware qualification: hyperscale providers often deliver stronger security, reliability, and cost efficiency than fragmented alternatives. Public institutions can fail, and private infrastructure can deliver security, scale, and innovation that would be expensive to reproduce. The governance objective is accountable dependence, not technological autarky.

For practitioners using The Tech Coup, the next step is to define exit plans, data portability, multi-region resilience, and minimum internal knowledge before dependence becomes irreversible. Make the exit path, audit right, and decision owner explicit before the dependency deepens. That is a concrete way to preserve public or organizational agency without pretending every service must be built internally.

Procurement can create public options

The Tech Coup uses this issue to expose a governance gap: Governments shape markets not only through bans and fines but through purchasing standards, interoperability requirements, and open technical specifications. The relevant question is not whether private technology is powerful in the abstract, but whether institutions that depend on it still retain meaningful choice, expertise, and authority when interests diverge.

The policy record provides a second lens on Schaake’s argument. the book’s emphasis on public agency suggests procurement as a practical lever for accountability. In reading The Tech Coup, this matters because democratic control depends on implementation capacity, not merely statutory language. A rule that cannot be audited or enforced is weaker than its headline.

The argument also needs a market-aware qualification: poorly designed procurement can freeze technology or create bureaucratic barriers. Public institutions can fail, and private infrastructure can deliver security, scale, and innovation that would be expensive to reproduce. The governance objective is accountable dependence, not technological autarky.

For practitioners using The Tech Coup, the next step is to use outcome-based standards and portability requirements that preserve competition without mandating one technical architecture. Make the exit path, audit right, and decision owner explicit before the dependency deepens. That is a concrete way to preserve public or organizational agency without pretending every service must be built internally.

Transparency is not the same as accountability

The Tech Coup uses this issue to expose a governance gap: Publishing reports or model cards can improve information while leaving affected people without a remedy, appeal, or institution capable of acting. The relevant question is not whether private technology is powerful in the abstract, but whether institutions that depend on it still retain meaningful choice, expertise, and authority when interests diverge.

The policy record provides a second lens on Schaake’s argument. Schaake’s democratic frame pushes beyond voluntary disclosure toward enforceable obligations. In reading The Tech Coup, this matters because democratic control depends on implementation capacity, not merely statutory language. A rule that cannot be audited or enforced is weaker than its headline.

The argument also needs a market-aware qualification: mandatory disclosure can expose security-sensitive information or overwhelm users with unusable detail. Public institutions can fail, and private infrastructure can deliver security, scale, and innovation that would be expensive to reproduce. The governance objective is accountable dependence, not technological autarky.

For practitioners using The Tech Coup, the next step is to tie transparency to a decision pathway: who receives the information, what threshold triggers action, and what remedy follows. Make the exit path, audit right, and decision owner explicit before the dependency deepens. That is a concrete way to preserve public or organizational agency without pretending every service must be built internally.

Civil society expands the oversight surface

The Tech Coup uses this issue to expose a governance gap: Researchers, journalists, watchdogs, unions, and advocacy groups can identify harms that regulators and firms miss. The relevant question is not whether private technology is powerful in the abstract, but whether institutions that depend on it still retain meaningful choice, expertise, and authority when interests diverge.

The policy record provides a second lens on Schaake’s argument. the book presents democratic accountability as an ecosystem rather than a bilateral state-company relationship. In reading The Tech Coup, this matters because democratic control depends on implementation capacity, not merely statutory language. A rule that cannot be audited or enforced is weaker than its headline.

The argument also needs a market-aware qualification: outside actors vary in quality and can be partisan or under-resourced. Public institutions can fail, and private infrastructure can deliver security, scale, and innovation that would be expensive to reproduce. The governance objective is accountable dependence, not technological autarky.

For practitioners using The Tech Coup, the next step is to support independent access to platform data and audit mechanisms while protecting privacy and legitimate security constraints. Make the exit path, audit right, and decision owner explicit before the dependency deepens. That is a concrete way to preserve public or organizational agency without pretending every service must be built internally.

Enforcement matters more than statutory symbolism

The Tech Coup uses this issue to expose a governance gap: A celebrated law that produces no investigations, remedies, or behavior change can create political theater rather than governance. The relevant question is not whether private technology is powerful in the abstract, but whether institutions that depend on it still retain meaningful choice, expertise, and authority when interests diverge.

The policy record provides a second lens on Schaake’s argument. EU implementation experience makes enforcement capacity a distinct variable from legislative ambition. In reading The Tech Coup, this matters because democratic control depends on implementation capacity, not merely statutory language. A rule that cannot be audited or enforced is weaker than its headline.

The argument also needs a market-aware qualification: early enforcement can be slow because institutions are building precedent and technical methods. Public institutions can fail, and private infrastructure can deliver security, scale, and innovation that would be expensive to reproduce. The governance objective is accountable dependence, not technological autarky.

For practitioners using The Tech Coup, the next step is to measure regulatory effectiveness through cases, compliance changes, market entry, appeal outcomes, and user remedies—not press releases. Make the exit path, audit right, and decision owner explicit before the dependency deepens. That is a concrete way to preserve public or organizational agency without pretending every service must be built internally.

Democratic control requires reversibility

The Tech Coup uses this issue to expose a governance gap: Institutions lose meaningful authority when technical dependence makes policy alternatives prohibitively costly. The relevant question is not whether private technology is powerful in the abstract, but whether institutions that depend on it still retain meaningful choice, expertise, and authority when interests diverge.

The policy record provides a second lens on Schaake’s argument. Schaake’s core warning is ultimately about path dependence: temporary convenience can harden into structural dependence. In reading The Tech Coup, this matters because democratic control depends on implementation capacity, not merely statutory language. A rule that cannot be audited or enforced is weaker than its headline.

The argument also needs a market-aware qualification: some infrastructure naturally has high switching costs and cannot be made perfectly contestable. Public institutions can fail, and private infrastructure can deliver security, scale, and innovation that would be expensive to reproduce. The governance objective is accountable dependence, not technological autarky.

For practitioners using The Tech Coup, the next step is to for every critical technology dependency, preserve at least one credible exit, migration, or public override path before a crisis makes it necessary. Make the exit path, audit right, and decision owner explicit before the dependency deepens. That is a concrete way to preserve public or organizational agency without pretending every service must be built internally.

An operating checklist inspired by The Tech Coup

• Map critical vendor dependencies in public and regulated workflows
• Require portability and exit terms before procurement
• Separate DMA-style competition questions from DSA-style systemic-risk questions
• Fund internal technical expertise instead of outsourcing all judgment
• Create appeal mechanisms for consequential platform decisions
• Diversify expert input during rulemaking
• Tie transparency reports to enforceable remedies
• Measure enforcement outcomes, not statute count
• Use procurement standards to preserve interoperability
• Maintain at least one credible migration path for critical infrastructure

Questions readers are likely to ask

What is The Tech Coup about?

Schaake argues that technology companies have accumulated forms of public power while governments have often lacked the expertise and capacity to hold them accountable.

Is the book anti-private-sector?

Its concern is not private innovation itself but unaccountable dependence, especially when public institutions cannot audit, replace, or meaningfully govern critical technology.

How do the DMA and DSA fit the argument?

They illustrate different regulatory approaches: the DMA focuses on gatekeeper competition, while the DSA addresses platform responsibilities, transparency, and systemic risks.

Who should read it?

Policy leaders, technology executives, public procurement teams, regulators, investors, civil-society organizations, and anyone managing critical platform or cloud dependencies.

Sources and further reading

• Princeton University Press/JSTOR — The Tech Coup
• Kirkus Reviews — The Tech Coup
• McKinsey Author Talks — Marietje Schaake
• The Guardian — interview with Marietje Schaake
• Council of the EU — Digital Markets Act
• Council of the EU — Digital Services Act
• European Commission — DSA implementation
• European Commission — DMA gatekeeper compliance

Editorial review prepared for Millionaire Lesson on The Tech Coup. Book-specific arguments, external evidence, and broader analytical inference are intentionally distinguished.