Kapital Buys Woz for $30M, Silent on Its Claude Code Plugin

If your developers installed WOZCODE to cut their Claude Code bill, its maker is being bought by a Mexican bank, both founders are taking bank jobs, and nobody has said whether the plugin survives. Treat it as an at-risk dependency now: record what it saves you today, pin the version you run, and work out what your Claude Code spend looks like without it.

Kapital announced on October 19 that it has agreed to acquire Woz for $30 million in cash and stock. Woz CEO Ben Collins becomes Kapital's Head of AI, CTO Brad Eckert becomes Kapital's CTO, and the whole AI team moves across. The release calls WOZCODE Woz's "flagship product" and repeats the claim that it has saved customers more than $2.5 million. It does not say whether WOZCODE stays on sale, gives no closing date and does not split the cash from the stock.

What Kapital Actually Bought

Kapital bought an engineering team, and the stated plan puts that team to work on banking. The announcement says the companies will build "next-generation AI models and products for enterprise financial applications" on Kapital's OctavIA suite, which runs live scoring, underwriting, risk and customer intelligence. Nothing in that list is a coding tool for someone else's engineers.

The buyer calls itself "a global AI-powered financial institution." Dealroom reports that Kapital serves more than 300,000 clients with about 3,700 staff, mainly in Mexico, Colombia, the US, Puerto Rico and Spain, and that the deal landed alongside a $130 million equity and debt raise that values it at $2 billion. Kapital's own release puts the September financing at $125 million, from Tru Arrow Partners and Fasanara Capital among others.

Woz is small. Its Y Combinator profile lists a Winter 2025 batch, a 2024 founding, a team of eight in San Francisco, and a one-line pitch: a Claude Code plugin that "reduces token consumption and cost by 50%." That 50% is the vendor's figure, as is the $2.5 million. Neither has been independently measured.

Kapital does say it plans to keep growing the San Francisco team over the next year, which commits it to hiring and says nothing about the product.

What WOZCODE Does, and What It Touches

WOZCODE is a Claude Code plugin that swaps Claude Code's built-in file tools for its own versions designed to use fewer tokens. The GitHub repository installs it with /plugin marketplace add WithWoz/wozcode-plugin and /plugin install woz@wozcode-marketplace, then has the developer sign in with /woz-login. When we checked on October 22, 2026, the repository had no tagged releases, and an unpinned plugin source follows the repository's default branch, per Anthropic's marketplace reference.

The pricing on wozcode.com, checked the same day:

Plan	Price	What you get
Free	$0	Savings capped at $100 a month, or $200 with a corporate email
Pro	$20 per seat per week	Uncapped savings, priority support
Enterprise	Custom	SSO, team management, volume pricing

The site still carries no acquisition or continuity notice.

Two things about the design matter in a change of control. The first is that a signed-in plugin depends on its vendor's account service. A pinned copy of the code protects you from a bad update, but it can't help if the backend that checks your plan goes away.

The second is telemetry. The homepage says WOZCODE runs locally, does not proxy or store code, prompts or outputs, and sends usage telemetry to PostHog: operational numbers such as token counts and tool calls, "tied to your account." The privacy policy repeats that code and prompts are excluded, describes no opt-out for usage data, and says plainly: "If we are involved in a merger, acquisition, or sale, data may be transferred as part of that transaction." So your developers' account and usage records can pass to a bank, under the policy you already accepted.

---

What the Contract Gives You

Very little, and the terms of service were written that way. They were last updated March 23, 2026, and they let With Woz, Inc. revise the terms from time to time, with continued use counting as acceptance. Fees are "non-refundable except where required by law." When the service ends, so does your access to updates and services. Disputes go to binding arbitration under California law. We found no assignment or change of control clause.

That is normal for a seed-stage developer tool sold by credit card. It also means an engineering org on Pro or Enterprise has no written right to continuity, notice, or a refund if the new owner switches it off. If you signed an Enterprise order form, read it for anything stronger; the public terms offer nothing.

How These Deals Usually End for Plugin Users

The most relevant precedent is the plugin that got bought for its team. When Anysphere bought Supermaven to strengthen Cursor, CEO Michael Truell said in November 2024 that the existing Supermaven plugins would keep being maintained, with Cursor as the team's main focus. On November 21, 2025, Supermaven announced it was sunsetting. Subscribers got prorated refunds, VS Code users were pointed to Cursor, and existing Neovim and JetBrains users kept free autocomplete.

That deal had a public maintenance promise and still ended in a sunset a year later. Woz has made no promise. The acquirer also has no coding product of its own to move you onto, which removes even the Supermaven-style migration path. We have seen versions of this with Harness taking Augment's Cosmos and with Harvey buying the Guardrails team after its Hub went dark.

There is a fair case for doing nothing. The plugin runs locally, the code is public, and Kapital could keep it alive as a recruiting showcase for its San Francisco office. If WOZCODE keeps working until a sunset notice and the notice comes with a refund, a team that did nothing loses little. The risk is the silent version: a backend change, a stale plugin that breaks on a Claude Code update, or a login that stops working in the middle of a sprint.

---

What Your Claude Code Bill Looks Like Without It

Your exposure is the gap between what Claude Code costs you now and what it would cost unplugged, and you can price that gap this week. Anthropic's own cost documentation puts the average across enterprise deployments at about $13 per developer per active day and $150 to $250 per developer per month, with 90% of users staying under $30 per active day.

Take a 100-developer team inside that range, at $200 a month each, or $20,000. If WOZCODE really halved the bill, as Woz claims, your unplugged cost is $40,000 a month, and losing the plugin is a $240,000 annual budget event. If it saved 20%, unplugged is $25,000 and the hit is $60,000 a year. Pro also costs money: $20 a week is roughly $1,040 per seat per year, about $87 a month. At $200 of monthly spend, WOZCODE has to save about $87, roughly 30% of the unplugged bill, just to pay for its own seat. Those gross figures shrink by the seat fees you would stop paying: about $104,000 a year for 100 Pro seats, which turns the 20% case into a net saving. Measure your own number before you rely on the vendor's.

Where the savings land depends on your plan. On API and cloud provider billing, they show up as lower invoices. On Claude Team and Enterprise seats, the same documentation notes that usage inside the seat allowance is not metered in dollars, so the plugin buys headroom before developers hit their five-hour and weekly limits. Losing it there shows up as more limit errors and more usage-credit spend.

Claude Code's built-in tools have also improved. Per the same cost documentation, the /usage screen now attributes recent usage to individual plugins and MCP servers, shows prompt cache hit rates, and lists ranked recommendations such as trimming an oversized CLAUDE.md. Our earlier analysis of where coding agent tokens go found cache reads dominate, which is why prompt cache hygiene can recover part of what a plugin like WOZCODE claims to save.

What to Do Before the Deal Closes

This Week:

1. Find every install. Ask developers to run claude plugin list, or turn on the claude_code.plugin_loaded OpenTelemetry event with OTEL_LOG_TOOL_DETAILS=1 so third-party plugin names come through unredacted, per Anthropic's plugin admin guide. On the Enterprise plan, the plugin analytics endpoint gives per-plugin install counts.
2. Capture the baseline before anything changes. Have each WOZCODE user export /woz-savings and /usage for the last seven days. That is your evidence for the decision and for any refund argument later.
3. Send Woz one email. The privacy policy names founders@withwoz.com. Ask three things in writing: will WOZCODE stay on sale after closing, will Enterprise customers get notice and a refund if it does not, and will account and usage data move to Kapital.

This Month:

1. Freeze the version. Turn off auto-update for the Woz marketplace ("autoUpdate": false in a managed extraKnownMarketplaces entry), or move the plugin into an internal marketplace whose entry pins a full commit sha, as the marketplace reference shows. The repository links a LICENSE file without naming the license on its front page, so have counsel read it before you fork. Then check your git host actually honours the pin; a pinned commit can still be a branch.
2. Run one unplugged week. Pick a pilot group, disable WOZCODE for them, and compare per-developer spend against a matched group still using it. Route it through your existing AI spend attribution, or a gateway such as LiteLLM if you run Claude Code on Bedrock or Vertex.
3. Pre-write the off switch. Draft a managed settings policy with "woz@wozcode-marketplace": false in enabledPlugins and a blockedMarketplaces entry for WithWoz/*. Do not ship it yet. Keep it ready so a sunset notice takes one deploy, not a week of Slack messages.

Before Renewal:

1. Do not prepay. Keep Pro weekly and push any Enterprise order to monthly terms until the new owner publishes a product plan.
2. Ask for a change of control clause. If you renew Enterprise, require notice, a right to terminate and a prorated refund on any sale or discontinuation. The public terms give you none of the three.

The Bottom Line

Small tools that patch a gap in a big platform tend to end one of two ways: the platform closes the gap, or someone hires the team. Supermaven went the second way and was gone a year later. WOZCODE now belongs to a lender whose stated plans cover scoring and underwriting, and a plugin your developers run every day appears nowhere in them.

Measure what it saves this week, so you know whether its sunset costs you $60,000 a year or $240,000 in gross Claude Code spend, before any seat fees you drop.

Continue Reading

• Harness Buys Augment's Cosmos With No Word on Augment Contracts
• Guardrails' Hub Died Aug 25. Harvey Bought the Team.
• The Pinned Commit Was a Branch. Check Your Git Host.
• One PR Billed 156M Tokens. Cap the Reads, Not the Rate.
• Prompt Caching Savings: One Timestamp Turns 80% Into 6%
• Adobe Took Rilo's Team. Its Slack Token Never Expires.