Anthropic Draws a Line on Agent Usage — And It Signals a Bigger Shift in AI Economics

Anthropic has made a decisive move that’s already stirring debate across the AI ecosystem. The company has begun restricting agent platforms like OpenClaw from running on standard Claude subscription plans, requiring developers and power users to shift toward usage-based pricing via API keys or add-ons.

At first glance, this looks like a pricing adjustment. In reality, it signals something much deeper: the collision between flat-rate AI subscriptions and agent-driven workloads.

What Changed

Anthropic confirmed that agent-style usage — where tools continuously call models in loops or workflows — will no longer be supported under standard Claude plans.

Instead, users must:

  • Pay separately through API usage
  • Purchase add-ons for extended capacity

According to Boris Cherny, the change is about “managing growth to continue to serve our customers sustainably long-term.”

To soften the transition, Anthropic is:

  • Offering credits equivalent to one month of subscription
  • Providing up to 30% discounts on add-ons
  • Issuing refunds for users who cancel due to the change

Why This Happened

The root issue is simple: agents break subscription economics.

Agent platforms like OpenClaw generate:

  • Continuous background requests
  • High-frequency API calls
  • Long-running workflows

This is fundamentally different from normal human usage. A single agent can generate the equivalent load of dozens — or hundreds — of traditional users.

Flat-rate pricing was never designed for this.

Anthropic’s models have become a preferred backbone for agent tools, which only amplified the imbalance. The result: infrastructure strain, rising costs, and potential degradation for everyday users.

The Backlash

Not everyone is happy.

OpenClaw creator Peter Steinberger criticized the move sharply:

“First they copy popular features into their closed harness, then they lock out open source.”

This taps into a broader concern:

  • Are AI companies benefiting from open ecosystems…
  • Only to later restrict them once scale becomes expensive?

Combined with earlier complaints about stricter rate limits, this decision risks further erosion of goodwill among developers — especially power users who helped drive early adoption.

The Bigger Picture: A Shift in AI Pricing Models

This isn’t just about Anthropic. It’s about the future of how AI is consumed.

We’re now seeing a clear split:

1. Human Usage (Subscription-Friendly)

  • Chatting, writing, coding assistance
  • Predictable, intermittent demand

2. Agent Usage (Consumption-Heavy)

  • Automation pipelines
  • Continuous execution
  • Machine-to-machine interactions

Flat pricing works for the first. It breaks under the second.

Anthropic’s move effectively acknowledges:

Agent workloads are infrastructure problems, not SaaS features.

Competitive Implications

This shift comes at a critical moment.

As Anthropic tightens controls, OpenAI is increasingly positioned as an alternative — particularly for developers building agent-based systems.

The timing matters:

  • Developers are experimenting heavily with agents
  • Tooling ecosystems are forming rapidly
  • Switching costs are still relatively low

Any friction introduced now can redirect entire segments of builders.

Final Take

Anthropic is not wrong — it’s reacting to a real economic and technical constraint.

But the trade-off is clear:

  • Sustainability vs. openness
  • Infrastructure reality vs. developer goodwill

How this balance is handled will shape not just Anthropic’s trajectory, but the broader relationship between AI providers and the emerging agent ecosystem.

One thing is certain:

The era of “unlimited AI” is ending — and usage-based reality is taking its place.

Designing a Modern Finance Library in SharePoint (2026)

Introduction

As organizations move toward data-driven systems, SharePoint is no longer just a document storage platform—it is increasingly used as a lightweight data platform. A well-designed Finance Library in SharePoint can serve as the foundation for tracking invoices, payments, and financial records in a structured, scalable way.

This article outlines a modern approach to designing a Finance Library schema that aligns with best practices in 2026 and supports future system evolution (e.g., migration to SQL, Dataverse, or SaaS platforms).


The Core Principle: Treat Finance as Data, Not Files

Traditional approaches rely on folders like:

  • /Project A/Invoices/
  • /Project A/Receipts/

This model breaks down as data grows.

A modern approach treats:

  • SharePoint Library = Transaction table
  • Metadata = Structured columns
  • Files = Supporting attachments

This shift enables filtering, automation, reporting, and scalability.


Architecture Overview

A clean SharePoint-based financial system should include:

  • Project Register (SharePoint List)
    The master dataset containing all projects (ProjectId as primary key)
  • Project Financials (Document Library)
    A secure library that stores all financial transactions and related documents

Finance Library Schema

1. Project (Lookup) — Required

  • Type: Lookup to Project Register
  • Purpose: Links each financial record to a project

2. Document Type — Required

Choice column:

  • Invoice
  • Payment Receipt
  • Expense
  • Quote
  • Purchase Order
  • Adjustment

This defines the type of financial transaction.


3. Invoice ID

  • Type: Single line of text
  • Example: INV-2026-001

Used for tracking and reconciliation.


4. Transaction Date — Required

  • Type: Date

Represents when the financial activity occurred.


5. Amount — Required

  • Type: Currency

Core financial value for reporting.


6. Lifecycle Status — Required

Choice column:

  • Draft
  • Submitted
  • Approved
  • Paid
  • Rejected

This supports workflow tracking and dashboards.


7. Client (Optional)

  • Type: Lookup or text

Useful for multi-client environments.


8. Category (Optional)

Choice column:

  • Revenue
  • Expense

Helps separate inflow vs outflow.


9. Fiscal Year

  • Type: Choice or calculated

Supports reporting and grouping.


10. Notes / Description

  • Type: Multiple lines of text

Stores context or additional details.


Recommended Views

Views replace folders and provide dynamic organization.

All Financial Records

  • Sorted by Transaction Date (descending)

Invoices

  • Filter: Document Type = Invoice

Unpaid Invoices

  • Filter:
    • Document Type = Invoice
    • Status ≠ Paid

By Project

  • Group by Project

Current Year

  • Filter: Fiscal Year = current year

Needs Attention

  • Filter:
    • Status = Draft OR Rejected

Security Design

Financial data typically requires restricted access.

Recommended approach:

  • Assign Finance team access at the library level
  • Avoid item-level permissions unless absolutely necessary
  • Keep security boundaries aligned with libraries

This ensures simplicity, performance, and maintainability.


Automation Opportunities

To improve usability and consistency:

  • Automatically set Fiscal Year based on Transaction Date
  • Validate Invoice ID format
  • Default Document Type during upload
  • Trigger notifications for “Submitted” or “Approved” status

These can be implemented using Power Automate.


Why This Design Works

This schema provides:

  • Scalability — Handles thousands of records without relying on folders
  • Consistency — Standardized metadata across all transactions
  • Automation readiness — Easily integrates with workflows and APIs
  • Analytics support — Works seamlessly with Power BI and reporting tools

Alignment with Future Systems

This design mirrors a typical financial data model:

SharePoint ConceptFuture System Equivalent
Document LibraryTransactions Table
Project LookupForeign Key
Document TypeTransaction Type
AmountAmount Field
StatusWorkflow State

This makes future migration to platforms like SQL Server, Dataverse, or a custom SaaS solution significantly easier.


Conclusion

A well-structured Finance Library in SharePoint transforms document storage into a functional financial system. By focusing on metadata, clean schema design, and proper separation of concerns, you can build a solution that is not only effective today but also ready for future growth.

The key takeaway:

Do not organize financial data with folders—design it as a system.

The First AI-Powered “Solo Billion-Dollar Company” Is Here — And It’s Not What You Expect

When Sam Altman predicted that AI would enable a one-person billion-dollar company, many assumed it would come from breakthrough technology or a revolutionary product.

Instead, the first real example looks very different.

From $20K Experiment to $1.8B Trajectory

According to reporting from The New York Times, entrepreneur Matthew Gallagher scaled his startup Medvi from a $20,000 experiment into a business projected to reach $1.8 billion in annual sales.

Even more striking:

  • The company generated $401 million in revenue in its first year
  • The initial build took just two months
  • The core team started as essentially one person

This is not a traditional startup story. There was no large engineering team, no years of R&D, and no massive VC-backed runway.

The Business Model: AI + Execution

Medvi operates in the telehealth space, selling GLP-1 weight-loss medications online.

Instead of building everything from scratch, Gallagher leveraged existing platforms:

  • Telehealth providers like CareValidate and OpenLoop handled doctors, prescriptions, and compliance
  • Logistics and fulfillment were outsourced
  • The business focused on distribution, marketing, and orchestration

This is a key shift: AI didn’t replace the system — it orchestrated it.

The AI Stack Behind the Growth

Gallagher used a combination of AI tools to replace what would traditionally require entire departments:

  • ChatGPT, Claude, and Grok for coding and automation
  • Midjourney and Runway for ad creatives
  • ElevenLabs for customer interaction
  • Custom AI agents for support, workflows, and operations

The result: a lean, AI-augmented operation with minimal human overhead.

Team Size: Almost Non-Existent

After scaling, Gallagher added just one full-time employee—his brother.

Everything else runs through:

  • Contractors
  • External partners
  • AI systems

This is a radical departure from the traditional startup scaling model, where headcount grows alongside revenue.

Why This Matters

This story challenges a common assumption: that massive outcomes require massive teams.

Instead, it highlights a new model:

AI + distribution + execution > large teams + long timelines

And perhaps the most surprising part:

This isn’t a deep-tech AI company.
It’s a distribution business powered by AI tools.

The Real Insight

The breakthrough isn’t the product—it’s the operating model.

  • AI compresses time (2 months to launch)
  • AI reduces cost ($20K to start)
  • AI replaces roles (engineering, marketing, support)
  • Platforms handle infrastructure (telehealth, logistics, compliance)

What’s left is decision-making, direction, and execution.

Final Thought

The first AI-powered billion-dollar company didn’t come from a lab.

It came from someone who understood how to combine tools, platforms, and speed.

And that raises an uncomfortable but important question:

How many “impossible” businesses are now just execution problems?

https://www.nytimes.com/2026/04/02/technology/ai-billion-dollar-company-medvi.html

Jack Dorsey’s Bold Bet: AI Replacing Middle Management

In a striking vision of the future of work, Jack Dorsey—co-founder of Twitter and CEO of Block, Inc.—has put forward a provocative idea: AI can replace middle management.

This isn’t just theory. It’s already being tested in practice.


The Shift at Block

Earlier this year, Block reduced its workforce by over 4,000 employees—more than 40% of its staff. According to Dorsey, this wasn’t a reaction to financial distress, but a deliberate move toward an AI-first organization.

The company is restructuring around a leaner, more focused model where traditional management layers are no longer central.

Instead, Block now defines its workforce across three roles:

  • Builders – individuals who create products and systems
  • Problem Owners – those accountable for outcomes and results
  • Player-Coaches – experienced contributors who guide and mentor others

This model removes the need for conventional middle managers whose primary role has historically been coordination.


Why Dorsey Thinks AI Can Replace Managers

Dorsey’s argument is rooted in how modern organizations already operate—especially remote-first ones.

At Block, nearly everything is documented digitally:

  • Decisions
  • Product designs
  • Internal discussions
  • Strategic plans

This creates a rich dataset—a living “world model” of the business.

According to Dorsey, AI systems can now:

  • Track and interpret this information in real time
  • Route insights and updates across teams
  • Identify bottlenecks and inefficiencies
  • Provide decision support at scale

In short, AI can perform one of the core functions of middle management: information flow and coordination—but faster and without organizational friction.


The Bigger Picture: A New Organizational Model

Dorsey’s thesis reflects a broader trend:

Lean, AI-first teams vs. traditional, layered enterprises

In traditional organizations:

  • Information moves slowly through hierarchies
  • Decision-making is fragmented
  • Accountability is often diffused

In AI-enabled organizations:

  • Data is centralized and continuously analyzed
  • Decisions can be made closer to the work
  • Teams operate with greater autonomy

This could lead to:

  • Faster execution
  • Lower operational overhead
  • More direct ownership of outcomes

The Risks and Open Questions

Despite the promise, this shift raises important concerns:

1. Trust in AI Decision-Making

Organizations may hesitate to rely fully on AI for coordination and judgment—especially in high-stakes environments.

2. Loss of Human Context

Middle managers often provide:

  • Emotional intelligence
  • Conflict resolution
  • Cultural alignment

These are areas where AI still has limitations.

3. Organizational Stability

Flattening structures too aggressively can lead to:

  • Role ambiguity
  • Burnout among high performers
  • Gaps in leadership development

What This Means for Professionals

If Dorsey’s model gains traction, the implications are significant:

  • Execution > Coordination: Value shifts toward building and delivering
  • Ownership becomes critical: Individuals are accountable for outcomes, not just tasks
  • AI fluency is no longer optional: Understanding how to work alongside AI becomes a core skill

For engineers, architects, and platform-focused professionals, this may actually be an advantage—especially those already working close to systems, automation, and outcomes.


Final Thought

Dorsey’s vision challenges a long-standing assumption: that organizations need layers of management to function effectively.

Instead, he proposes a future where:

AI becomes the connective tissue of the company, and humans focus on creation, ownership, and growth.

Whether this model scales across industries remains to be seen. But one thing is clear—the role of middle management is being fundamentally re-evaluated in the age of AI.

https://block.xyz/inside/from-hierarchy-to-intelligence

OpenAI Largest venture funding round in history

OpenAI just raised $122B at an $852B valuation — the largest venture funding round in history — and it’s signaling something much bigger than just capital.

This is a strategic shift toward an “AI superapp.”

What stands out:

  • Amazon, Nvidia, and SoftBank anchored ~$110B of the round
  • Amazon reportedly included an AGI-trigger clause — a fascinating signal about where this is headed
  • Revenue has reached $2B/month, growing at a pace 4x faster than early-stage Alphabet and Meta
  • Enterprise now drives 40%+ of revenue, on track to match consumer soon
  • ChatGPT, Codex, and agent tools are being merged into a single unified platform
  • Meanwhile, side efforts like Sora are being deprioritized

Why this matters:

This isn’t just about scale — it’s about focus.

The real story is the enterprise shift. When nearly half of revenue is coming from enterprise (and rising), it tells you exactly where the durable value is being built.

We’re watching the transition from:
➡️ AI tools →
➡️ AI platforms →
➡️ AI operating systems for work

The “superapp” direction suggests a future where:

  • Development, automation, and decisioning live in one interface
  • Agents become first-class coworkers
  • AI moves from assistive → operational

If this trajectory holds, the next phase of the AI race won’t be about who has the best model — it will be about who owns the workflow layer.

And that’s where the real competition begins.

https://openai.com/index/accelerating-the-next-phase-ai