The AI Productivity Paradox: Why Faster Work Means Less Free Time

It's 12:30am in Da Nang and my laptop is still open. Not because I'm behind schedule. Because Claude just helped me ship the first version of a BI dashboard for one of my projects in an evening, and a year ago that would have been a week of scoping and hand-wringing. Now I'm looking at it and thinking about the management dashboard that could come next, or the layer on top of it that pulls cross-project data into one view. This is the AI productivity paradox playing out in real time: the promised free hours never arrive. You fill them with more work, and the definition of a normal day keeps ratcheting up.

The promise was straightforward. AI makes you faster, so you work less. Automate the boring parts, reclaim your afternoons, take up a hobby. The beach is fifteen minutes from here. I swim there most afternoons and walk it for about an hour in the evening. That routine has held since I moved here from Koh Phangan last December. It's basically the only part of the day AI hasn't eaten yet, and it holds only because I actively defend it. Which is part of the argument.

Jevons on Your Laptop

The phenomenon has a name, or at least two adjacent names. In 1865 the economist William Stanley Jevons observed that when coal-powered steam engines became more efficient, England didn't use less coal. It used more, because efficiency made coal-dependent industry cheaper and more widespread. This is now called the Jevons paradox: gains in efficiency produce higher total consumption, not lower. Transport planners call the same dynamic induced demand: build more highway lanes, get more traffic, not less congestion.

AI looks like Jevons and induced demand applied to cognitive labor, but with a wrinkle worth naming carefully. Cognitive work isn't one thing. Demand for it splits into roughly three regimes. Demand for marketing copy, landing pages, boilerplate code, basic research syntheses, and translation is highly elastic: drop the price, and buyers commission far more of it. Demand for medical consultations, legal advice, tax work, and most applied expertise is elastic by access rather than by volume per customer: cheaper and faster means more people reach it who couldn't before, but existing patients don't suddenly want ten times more surgery. Demand for narrow top-tier work (M&A counsel for Fortune 500s, strategy for a handful of boards, specialized judgment where the buyer universe is structurally small) is nearly inelastic: the price is set by reputation and trust, not by hourly productivity, and cutting production time doesn't expand the client pool. The Jevons frame fits the first category cleanly, fits the second partially (more volume, not per-client inflation), and fits the third poorly. Most of what's written about 'the AI productivity paradox,' including most of what follows here, is really about the first category, and the data reflects that skew.

Scope-narrowing worth doing before the data arrives. This essay is about knowledge workers, independent builders, and the parts of the economy where AI directly substitutes for cognitive output. The dynamics for nurses, truckers, teachers, and most service workers are real and important, but they're different, and pretending otherwise would be dishonest. I'm writing from a specific vantage within that scope: a serial entrepreneur and solo builder who, for the past year, has been fully focused on AI-assisted development. I design and ship systems (chatbots, CRMs, automated workflows, custom web platforms) for small businesses, and I'm the full execution layer. Before AI, the entry price for building this kind of system was either hiring developers or learning to code yourself. That gate is gone. My vantage is the one someone steps into when they walk through that gate. It shapes what I see. It also explains why some of the claims below will read more sharply for people in AI-native builder positions than for, say, a staff accountant whose workload is capped by a finite client book, or a nurse whose hours are set by a union contract.

The framing matters because it tells you what the argument actually is. The paradox isn't a bug in AI or a moral failing of employers. It's an economic pattern that has shown up every time a general-purpose productivity technology gets deployed at scale in demand-elastic sectors. Treating it as novel is misleading. Treating it as already-understood tells you where to look for both the pattern and its exceptions.

The Berkeley Haas ethnography from February 2026 captured the individual version of this cleanly. Researchers followed a 200-person US tech company for eight months and found that generative AI did not free up time. It expanded what workers felt capable of, and willing, to take on. A single-company ethnography isn't proof at population scale, but the mechanism it describes (possibility becoming obligation) is the Jevons dynamic running in knowledge-worker heads.

One twist worth sitting with, with appropriate caveats. A METR study from 2025 ran a randomized controlled trial on sixteen experienced open-source developers working with AI tools that many of them hadn't used regularly before. The developers felt they were about 20% faster with AI. They were actually 19% slower. The sample is small, the task profile specific, and a tool-unfamiliarity effect plausibly explains part of the gap. You cannot extrapolate from this to 'AI productivity gains are broadly illusory.' You can take it as a narrower finding: self-reports of feeling faster are not a reliable proxy for being faster, which complicates any 'AI freed up my afternoon' claim built on subjective time accounting, including the one in my own opening paragraph. My 'a week of scoping and hand-wringing' is memory, not a stopwatch.

The most direct empirical test of the thesis comes from Jiang, Park, Xiao, and Zhang's 2025 working paper 'AI and the Extended Workday,' which used data from the American Time Use Survey (ATUS) run by the US Bureau of Labor Statistics. ATUS is the most rigorous time-allocation dataset available for this question: it tracks, through detailed time diaries from tens of thousands of Americans, how people actually spend their hours each day. The paper uses a difference-in-differences comparison (which isolates the change in AI-exposed groups against a control of non-exposed groups over the same window) between 2022 (pre-ChatGPT) and 2023. It finds that workers in occupations more exposed to generative AI experienced an interquartile-range increase of about 3.15 additional hours of work per week, paired with a reduction of roughly 3.20 hours in leisure. The effect was stronger in occupations more complementary to AI and in regions with higher AI awareness. AI-exposed workers also reported lower job satisfaction, even when their wages rose.

Two qualifications are worth keeping in mind whenever this number gets cited. First, the paper is still at working-paper stage. It has not yet been through peer review and its difference-in-differences identification strategy has not been externally stress-tested. Second, 2022-2023 is an extraordinarily confounded window. Return-to-office mandates, a sharp tech-sector contraction, rapid interest-rate increases, and post-COVID labor market normalization all hit the same occupations that score high on AI exposure. The DiD design tries to isolate the AI signal from the aggregate shock, but 'AI-exposed occupations' correlates heavily with 'tech-adjacent white-collar work,' which is exactly the segment most affected by every other 2022-2023 shock. Take the 3.15-hour figure as a directional signal worth watching rather than a settled number. The mechanism it describes is consistent with the broader picture. The magnitude will sharpen or soften as the data series extends.

The Three-Layer Paradox

Conversations about the productivity paradox tend to blur three different mechanisms together, which is how the argument goes in circles. Separating them helps.

At the individual level, the paradox is psychological. You see the tool save you time, and because productivity is tied to identity for most builders and knowledge workers, the saved hours become an invitation rather than a gift. You choose to fill them. No one forces this, which is what makes it durable.

At the firm level, the paradox is structural. Companies notice the speedup (directly, or through output quietly rising) and reset expectations, headcount, or both. This doesn't require malice. It requires a quarterly planning cycle and a competitor doing the same thing.

At the market level, the paradox is economic. When everyone in a commoditized segment gets faster at once, supply expands, per-unit prices fall, and the price of entry resets lower. Individual speed stops being an advantage and becomes the baseline.

These layers interact, but they aren't the same thing. Each has its own exceptions. At the individual level, people can refuse the invitation. At the firm level, companies can pass productivity gains through to workers as reduced hours. At the market level, some segments resist commoditization because demand isn't elastic or because the work carries trust, liability, or physical-presence requirements. We'll get to all three exceptions. The paradox is a default outcome when none of them hold, which describes most situations in demand-elastic cognitive work but not all.

The Freelancer Market, Split Three Ways

The market layer shows up most clearly in freelance data, because online labor markets are nearly frictionless and respond to AI adoption within weeks rather than quarters. One caveat up front: much of the data below comes from Upwork, which is both the most-studied freelance platform and an interested party in how this story gets told. Upwork has been pivoting its own business toward AI-specialist matching and premium-tier services during the same period, which means platform strategy and AI substitution are tangled together in the numbers. Keep that in mind throughout.

Hui, Reshef, and Zhou published a study in Organization Science in 2024 analyzing Upwork freelancer data before and after the release of ChatGPT, DALL-E, and Midjourney. They used a difference-in-differences approach. Freelancers in the most AI-exposed categories saw a 2% decline in monthly contracts and a 5.2% drop in monthly earnings. One finding was counterintuitive: the most experienced, highest-rated freelancers were hit harder, not less, by the change. The hypothesis that deep expertise would act as a moat against AI substitution did not hold in the short-term data.

A separate study by Teutloff, Einsiedler, Kässi, Braesemann, Mishkin, and del Rio-Chanona (Journal of Economic Behavior & Organization, 2025) analyzed freelance platform postings across 116 fine-grained skill clusters. They found demand for substitutable skills like writing and translation decreased 20-50% relative to trend, with sharper declines in short-term roles. A third study, by Demirci, Hannane, and Zhu at Imperial College and Harvard (Management Science, 2025, vol. 71 no. 10), analyzed nearly two million job posts across 61 countries. They found a 21% overall decline in demand for 'automation-prone' jobs within eight months of ChatGPT's launch, with writing jobs down roughly 30% and software/app/web development down roughly 20% in subcategory breakdowns.

A reader comparing these numbers will notice the gap. Hui et al. report a ~5% earnings drop; the other two report 20-50% demand drops. The numbers aren't in direct conflict, they measure different quantities. Hui et al. track per-freelancer earnings among those already on the platform, which smooths across who exits, who bids lower, and who shifts into different work. Teutloff et al. and Demirci et al. track raw demand (number of job posts in specific skill categories). A 20-30% collapse in demand for writing postings can coexist with a 5% earnings drop per freelancer if the remaining writers bid down prices to keep utilization, or shift into adjacent higher-value work, or both. Both papers' segmentation data is consistent with that interpretation.

Some of the overall decline reflects post-COVID client budget correction, remote-work normalization, and platform dynamics rather than AI in isolation. What points toward AI as the primary driver of the category-specific pattern is the concentration: declines are sharpest in the exact skills where AI substitutes most directly, not uniform across freelance work. That's what you'd expect if AI were doing the heavy lifting even if the overall level is moving for multiple reasons.

Here's the split that makes the freelance story more interesting than a simple decline narrative. Upwork's own platform data shows AI-specialised freelancers commanding 25-60% higher rates than general practitioners in the same field, with AI-related freelance work crossing $300 million in annualised value by late 2025. Treat those specific figures with the skepticism Upwork's commercial position warrants: the platform benefits directly from the story that AI-specialist freelancers earn premiums on Upwork. The broader directional claim, that freelance demand is bifurcating rather than uniformly collapsing, is supported by the independent academic studies as well.

The floor is collapsing, the ceiling is rising, and the middle is disappearing. Three segments, three different outcomes:

Commodity producers. Those doing work that AI substitutes for directly (basic writing, entry-level copy, simple translation, template-driven design). This segment is getting squeezed by both fewer contracts and lower per-unit prices.

AI-native specialists. Those selling AI implementation, prompt engineering, RAG systems, agent automation, and other work that didn't exist three years ago. This segment is growing and commanding premiums.

The middle. Experienced mid-tier practitioners selling work that's AI-adjacent but not AI-specialist. This segment is feeling the squeeze most acutely. Their reputations and rates were built for a market that's changing under them.

The paradox operates strongly for segment one, breaks entirely for segment two, and looks a lot like segment one for segment three. Which segment you're in matters more than whether you use AI.

Worth naming the other side of this ledger too. When freelance writing prices drop 30%, that's bad for freelance writers. It's good for every small business that can now afford marketing copy, every non-profit that couldn't previously commission design work, every early-stage founder who can now ship a landing page without hiring. Producer loss is consumer surplus. That doesn't make the loss unreal. It does make the picture less one-sided than 'AI devalues labor.'

One more layer the data rarely foregrounds. The freelance population on Upwork and similar platforms is disproportionately non-Western. A 30% drop in writing jobs is an inconvenience for a writer in Brooklyn with savings and alternative employers. It is closer to existential for a writer in Lahore, Manila, or Nairobi whose rate was already a fraction of Western rates and whose local economy does not offer substitutes. The segmentation above plays out across countries as well as across skill tiers, and the pain is not evenly distributed.

The AI-specialist side of the split is also globally distributed, and the growth is fastest outside the West. India, the Philippines, Vietnam, parts of Eastern Europe, and Latin American countries where English freelance labor is already priced globally have large populations moving into AI implementation, prompt engineering, and agent automation work. Some of this is happening faster than the Western shift, because the base incentive is stronger: the jump from $8/hour commodity writing to $40/hour AI specialist work is life-changing in ways the equivalent Western move is not. The bifurcation isn't a story of the Global North eating the Global South. It's a story where both segments exist in every geography, and the pressure to move from commodity to specialist is sharpest exactly where the commodity rates were lowest.

The same dynamic makes the middle-tier squeeze more brutal abroad. A mid-career writer in a non-Western market typically has fewer adjacent employment options than the equivalent Western writer, so 'learn AI or exit the market' is more binary. The people who adapt move up. The people who can't move down, sometimes all the way out. Both outcomes are happening at scale, simultaneously, and the data from Demirci, Hannane, and Zhu (which spans 61 countries) reflects this more honestly than Upwork-centric commentary does.

From Market to Firm: Survivor and Arbitrageur

If freelancers live mostly at the market layer (where prices collapse and segments split), salaried workers live at the firm layer, where the dynamic has two opposite faces. Which face you encounter depends mostly on visibility: whether the organization you work for can see how much AI is speeding you up, or not.

The inward-facing version is the survivor trap. A company adopts AI tools. Some roles get consolidated, gradually. The remaining team absorbs the workload because the tools make that possible. Headcount drops slightly. Output stays flat or rises. Salaries barely move. You weren't fired, which is the good news. You now do the work of roughly two people, which is the trap.

Fortune's March 2026 piece on AI and the workday quoted operations leader Mike Manos on exactly this pattern: a task that used to take eight hours now takes two, but the team that used to run one such task per week now runs five, and the person at the middle of it is working harder than before even though each individual task is faster. The 'compressed' and the 'expanded' are the same workday.

The Dallas Fed's wage analysis in early 2026 showed that in the 10% of sectors most exposed to AI, employment declined about 1% from late 2022 through early 2026, while wages for workers without deep tacit expertise stayed flat. One percent is modest. The causal attribution isn't clean (labor market cooling and remote work normalization are also in the mix), but the directional effect is consistent with the mechanism.

The outward-facing version is the arbitrageur. When information asymmetry runs against the employer, when a worker absorbs AI into their workflow without anyone upstream noticing, the same person can keep the productivity gain for themselves.

The interesting number isn't the total dual-jobholding rate, which has been roughly 5% of the US workforce for decades and has nothing to do with AI. Plenty of people have always held two jobs because they need the money, or because one is seasonal. The number worth watching is the narrower subset: people holding two full-time jobs simultaneously. The Bureau of Labor Statistics put that figure at roughly 416,000 workers in early 2024, and it has grown in recent years. This configuration was historically rare because two full-time jobs meant eighty working hours a week, which few people sustain. AI changes that math. Some knowledge roles can now be executed in two or three hours a day of actual work, with the rest being availability and meetings. The r/overemployed community, which has passed 400,000 members and serves as informal infrastructure for the pattern, explicitly frames AI-assisted arbitrage as the enabler. None of this is proof. The BLS doesn't track 'are you using AI to hold two full-time jobs,' and a subreddit membership isn't the same as active practice. But the specific growth of the two-full-time-jobs subset, at exactly the same moment when AI tools made certain roles executable in fractions of the stated workday, is a pattern the 'just needing money' explanation doesn't reach.

The arbitrageur isn't a sustainable equilibrium. Monitoring tightens, norms shift, companies notice. But right now, at scale, people are quietly banking the productivity gains that the survivor trap assumes get absorbed back into expectations. Which pattern you experience depends on how visible your speedup is to the person who signs your paycheck.

The Founder's Infinite Backlog

For salaried workers, the pressure arrives from above. For founders and independent builders, it arrives from inside.

There used to be a gap between what you wanted to build and what you could realistically build. Resources were finite. Time was finite. You had to choose. That constraint was painful, but it was also a kind of mercy. It forced prioritization. It gave you an honest reason to leave things undone.

AI removes the constraint. Now you can ship more landing pages, test more ideas, launch more experiments, build more products in parallel. And if you don't while other founders do, there's no one to blame but yourself.

The backlog becomes infinite. The sense of 'done for the day' disappears. What used to be an ambitious quarter is now a slow month. This is not motivation. It's the permanent low-grade anxiety of knowing the tool on your laptop could be doing one more thing if you just opened it.

One honest note before the structural argument continues. Part of the reason my laptop is open at 12:30am isn't that someone is forcing me to work. It's that the work is more interesting than most of the alternatives on offer. Building systems with AI right now is genuinely more absorbing than most leisure I could design for myself, and designing good leisure is harder than designing a feature. This isn't a confession of workaholism. It's a recognition that for people in certain parts of the economy, at this specific moment, work has become unusually rewarding and rest has become unusually hard to design well. That's a real thing, and it complicates the clean 'system steals your time' framing. The system isn't only stealing time. It's also offering a more engaging stream of interesting problems than the market for leisure knows how to match, at least for a certain kind of person. The paradox this essay describes is still real, the expectation escalator is still real, the market-level price pressure is still real. But 'I choose to keep working because it's interesting' is part of the picture for a non-trivial share of the builder population, and pretending otherwise would be dishonest.

I don't have a rigorous survey to point to for this section. Indie Hackers threads, YC batch recaps from 2024-2025, and the solopreneur corner of X describe the pattern in similar terms, but I'm not aware of a systematic study that has measured founder psychological load against AI tool adoption. Treat this section as phenomenology from inside one founder's head, pointed at a pattern that seems common in the communities I'm in, not as evidence. A proper study would help. In the meantime, the reason the founder experience is worth naming is that it's the purest expression of the individual-level paradox: when no one is forcing the expectation, the expectation still rises. That tells you something about what we do with freed time, even without an external villain.

One honest caveat on generalization: founders are a small, self-selected slice of the workforce. People who choose unbounded work are not a representative sample of anything. Extrapolating founder psychology to the rest of the economy would be exactly the mistake other discourse keeps making.

Where the Paradox Breaks

The paradox has been treated in popular discourse as a universal law. It isn't. Each layer has conditions under which it weakens or breaks entirely, and those conditions are where any agency lives.

The speedup stays invisible. If your employer can't see that AI cut your task time in half, they can't reset the baseline. This is the information asymmetry the arbitrageurs exploit.

The work resists commoditization. Law, medicine, high-end advisory, trades, care work. Where output depends on relationships, judgment, accountability, or physical presence, the speedup doesn't automatically flatten the price. The AI-specialist freelancer premium is one version of this, but the broader pattern is older: work that carries real liability or real trust resists being substituted.

The workload is naturally capped. A solo in-house HR generalist at a 30-person company doesn't get 3x more candidates because the review process got faster. The shape of the role limits how much work can reasonably show up. (If instead the same person worked at a recruiting agency selling candidate pipeline by volume, the cap disappears: the agency's owner sees the speedup and pushes for more deals or fewer recruiters. Which is the survivor trap under a different logo. The natural cap matters; it's specifically the absence of volume-scaling incentive that protects the time.)

The firm deliberately chooses to pass gains through. Atom Bank moved to a 34-hour week in 2021 with no pay cut and, per the bank's own reporting, no decline in efficiency. Kickstarter and Buffer have run permanent four-day weeks for years. Bolt ran one from 2022 but reversed the policy in May 2025 (eFinancialCareers, Fast Company), with the founder citing 'significant gaps in execution' on return. The 4 Day Week Global trial of 61 UK companies on the 100-80-100 model (full pay, 80% of hours, 100% of output) reported that 92% of participating companies kept the policy afterward, though 'kept' covers a spectrum from full 100-80-100 to modified compressed-hours variants. On April 6, 2026, OpenAI published a policy document titled 'Industrial policy for the intelligence age: Ideas to keep people first,' recommending that governments subsidize four-day workweek pilots with no pay cut. OpenAI has a direct commercial interest in framing AI as a productivity boon that requires policy to redistribute, so the document is better read as lobbying-shaped advocacy than neutral analysis.

You own the upside. If you're running your own business rather than working inside one, the productivity gain flows to you by default. This is the cleanest exception, with the standard tradeoffs of ownership attached.

On scale: per the WEF's October 2025 coverage, more than 2.7 million UK workers (roughly 8% of the workforce) now report working some form of four-day schedule, though the majority of those are compressed-hours arrangements (same total hours across four days) rather than the no-pay-cut model. The genuine no-pay-cut variant covers about 420 UK companies and 12,000 workers through the 4 Day Week Foundation. The exception is real and growing. It's also nowhere near universal.

These exceptions are real. Most people don't currently meet any of them, which is why the paradox feels universal in lived experience even though it isn't. The practical question isn't whether the paradox exists. It's whether any exception is reachable from where you stand.

A Small List of Things That Actually Help

Individual tactics have a ceiling. If the paradox is structural, and most of the mechanisms that would meaningfully counter it are collective (unions, regulation, the four-day week policy movement, platform cooperatives), then the list below is by construction partial. It buys some room at the margin. It does not repeal the dynamic. I'm offering these as directions I try to hold (inconsistently, partially), not as a settled playbook. The framing is 'here's what seems to push back against the dynamic,' not 'here's what reliably works.'

Set a limit and actually stop. AI's defining feature is infinite availability of one more task: the model is always there, the prompt is always one keystroke away, the marginal cost of one more iteration is near zero. That makes stopping harder than it has been for any prior tool, not easier. When AI saves you four hours on a task, explicitly ask where those four hours went. Not answering this is how the escalator climbs without you noticing.

Sell the judgment layer, not the production layer. 'Sell outcomes, not hours' collapses the moment clients realize the outcome is cheap to produce. The durable version: bundle AI speed into delivery, but price for the decisions, taste, accountability, and strategy on top. This only works in segments where the judgment layer is legibly distinct from the production layer, which is not everywhere.

Own a channel, even a small one. An audience, newsletter, Telegram channel, any direct line to the people who might pay you. Channel ownership pulls you out of the race-to-the-bottom pricing dynamic and compounds while the commodity end of your market erodes. It is also a slow, years-long build, not a tactic for this quarter.

Protect unstructured time as a strategic moat. One project, one kind of work, or a daily block where the tools stay closed. Not for lifestyle reasons. For business reasons. The premium work (the part clients will still pay real money for in three years) lives in judgment and original thinking. Those capacities develop in the space where you're not producing. Protecting that space is protecting the part of your offering that doesn't commoditize.

Productive for Whom?

Most AI discourse asks how to be more productive with these tools. The question the paradox forces is different: productive for whom?

The efficiency gains don't stay with the person generating them. They flow outward to the platforms taking their cut, the clients resetting delivery expectations, the competitors pricing against the new baseline, the market redefining normal every six months. Very little of what AI unlocks converts directly into more freedom for the person at the keyboard, unless that person actively fights for it.

A real counter-argument worth stating plainly. Past general-purpose technologies, including electricity, the personal computer, and the internet, were each in their early years predicted to displace labor at scales that largely did not materialize. Erik Brynjolfsson and co-authors have written extensively on the 'J-curve' of general-purpose technology adoption: measured productivity dips first, as firms restructure, skills lag, and complementary investments take time to pay off, and then climbs as the economy adapts. On this reading, the current paradox is a transitional artifact rather than a permanent state. Give it five to ten years, the argument goes, and AI will look like every previous productivity revolution: initially disruptive, eventually broadly beneficial, with leisure and wages rising together once institutions catch up.

This is a serious position and I don't dismiss it. The honest response is that it could be right, and the current discomfort may be a compositional effect of the transition rather than a feature of the endpoint. But three things make me cautious about resting on the J-curve. The speed of AI's deployment is faster than any prior GPT. Compression that historically took decades is happening in years, which strains the 'institutions will adapt in time' story. The distributional question isn't solved by aggregate gains: past GPTs produced wealth that required decades of political struggle to convert into broadly shared leisure (the weekend, the 40-hour week, retirement), and there is no law of nature that says the next round will go faster. And most centrally, whether this iteration resembles the last one is itself an empirical question that won't be settled for a while, which argues for hedging now rather than presuming the happy path arrives on schedule.

AI is an amplifier. It amplifies what you can do, what's expected of you, what you expect of yourself, and what the market considers the floor of competence. If you don't set your own limits, a client, a boss, a competitor, or your own ambition against an infinite ceiling will set them for you. They'll be higher than the ones you would have chosen.

Technology has historically produced real free time. The weekend, the 40-hour week, retirement, childhood as a protected period. These weren't accidents of efficiency. They were efficiency gains plus political struggle that captured some of those gains as leisure. The distribution of productivity gains is always a fight, and usually the workers don't win it by default.

The tactical limits earlier are individual responses to a systemic condition. They help, with a known ceiling. Collective responses (unions, regulators, the four-day week policy movement, platform cooperatives) are where the real leverage sits. Those dynamics, including who captures the productivity gains across the larger economy, where any work is still structurally protected, and what happens when AI starts getting a physical body, are the subjects of Parts 2 and 3 of this series.

For now, one thing is worth sitting with. The free hours you thought AI would give you back never show up automatically. If you want them, you have to take them. The system isn't going to hand them over.