Suvish Viswanathan retweeted
Sridhar has shared the difficult decision we have taken to skip appraisals this year, given the rising costs and uncertain outlook for the software industry. Every software business will be having this discussion and making difficult choices.
These are real-world situations where there is no single right answer. The decision depends on what we choose to prioritise. These are also decisions AI cannot make for us.
During COVID, we made a similar decision. We offered free licences to customers, even though it meant losing revenue. This time, we had to deal with the sharp increase in server costs. We discussed these options internally.
Lay off employees. While layoffs are common across businesses, we felt it wasn't the right choice when our business is still growing. We have over a million customers to support and products to keep improving. Cutting jobs could affect both employees & customers. Instead, we want to reduce costs by focusing on R&D to make our products and infrastructure more efficient.
Reduce other expenses. We have decided to cut our marketing spend and are looking at ways to improve efficiency across the business.
Increase prices. Customers are already dealing with rising costs and geopolitical uncertainty. So we don't want to add to their burden. We want to first do what is in our control before doing this.
Skip appraisal. This was a difficult decision, but we wanted to avoid layoffs and price increases. So we made this tough decision.
As a private company, we have to take care of our customers and employees. Publicly listed companies also have shareholder expectations to consider.
There is no one right decision in these situations. Ultimately, it comes down to what we choose to prioritise and how we balance the needs of our customers, employees and business for the long term.
The business outlook for software is uncertain and AI has raised costs dramatically with a) massive 4-fold increase in server prices which we need for data centers b) AI usage increasing rapidly, leading to much higher expenses, which we are trying to control.
On top of that is the challenging geopolitical backdrop.
We have cut down on our marketing budget. We have also told our employees that we cannot have our usual pay increase this year. I have apolgized for not being able to avoid this.
We will work hard to avoid mass layoffs but the outlook for software jobs in general is grim. We have not been growing our employee count for 18 months now.
Most of our employees understand the situation. I am thankful to them.
We are in the middle of reinventing ourselves. The next 3-5 years will decide how our reinvention has worked. Please pray for us 🙏
Voice scams are already draining seniors' savings. Now imagine a "grandson" on FaceTime.
And a lifelike face will only deepen emotional dependence on AI, which is already on rise!
Genuinely asking: what use case justifies this risk? 🤔
Introducing Griffin, the first model to pass the video Turing test.
48% of people who talked to it live thought it was a real human. Previous systems have had a pass rate <3%. It is #1 on NVIDIA's benchmark for full-duplex AI video.
It’s the first Human Interaction Model (HIM).
Readers added context they thought people might want to know
The 48% figure and "video Turing test" claim are from Tavus's own study of 54 one-minute calls, not independently verified or using a standard protocol. Griffin-Lite leads NVIDIA's VideoFDB benchmark on their public leaderboard.
cellcog.ai/blog/tavus-gri…
research.nvidia.com/labs/amri/proj…
tech-ish.com/2026/10/02/tav…
58
Suvish Viswanathan retweeted
We'll be spending a lot more time trying to understand the outputs of language models. A few thoughts, tips & tricks:
Writing. Something I've had success with: Ask your LLM to explain something in ASD-STE100, it's a controlled language specification originally developed for aerospace maintenance documentation. LLMs well-versed in this language and it comes with heavy constraints on clean writing style that I often find a lot more readable. Sometimes I've tried to soften it a bit e.g. ask for "80% of the way to ASD-STE100" because the spec is quite stringent. But even better:
Diagrams / images. Instead of writing, ask your LLM to create a diagram. These can be a lot easier to process, parse, and understand. But even better:
Web pages. Ask for output "in HTML" to get a beautiful, interactive webpage. LLMs are getting really good at frontend and can create beautiful experiences, animations, etc. But even better:
Explainer videos. The output format I am most bullish on is fully custom / bespoke explainer videos generated on any arbitrary topic. Experiment with things like "Create a 3b1b style video explainer on X. Use my ElevenLabs API key for audio narration". (you'd need an API key for the latter or you can ask your LLM to find you decent free alternatives that use your local compute). This is actually starting to work!
In summary:
- As LLMs get better, they will do more and more of the legwork autonomously, and a lot more of our work will rise up the abstractions into oversight and understanding.
- Luckily, LLMs can help here too because as intelligence and code are increasingly abundant, you can ask for large, custom, discardable software artifacts (e.g. web apps, video explainers) that would have never made sense to create before. Push the boundaries here and you'll be surprised.
Where does money invested into the AI buildout actually go?
For every $100 flowing into the supply chain:
- $50 to chips
- $20 to power
- $15 to networking
- $15 to cooling, buildings, and land
More charts in State of Markets II: a16z.news/p/state-of-markets…
Introducing our State of Markets pt 2, along with a companion podcast where we unpack the data and discuss what comes next.
Tech is the everything cycle.
Supply: putting the buildout in context, just passed railroads as % of GDP. The wisdom of Elon is real: the factory (or the datacenter!) is the product.
Demand: diffusion is so, so early. Median AI vendor spending in the top 1% of companies is 8x that of the top 10%. Only about 30% of S&P 500 companies report a quantified AI impact, which means there’s a substantial opportunity in connecting models to a company's data and workflows. Diffusion into companies is one of the main themes of the next 5 years.
We’re entering the agent work period. Only a few million users today, but applicable to billions of internet users with massive surplus created. META/GOOG monetize US users at $200+ per year today. Agent opportunity is much higher.
Mega-trends the next 5 years: Consumer agents, Robotics, Autonomy, AI x bio, Personal health, Diffusion into enterprise, New era of American Dynamism.
Much more in our SoM report here - a16z.news/p/state-of-markets…
@a16z @sarahdingwang @aleximm @santiago__rdz
Suvish Viswanathan retweeted
Third question on AI.
A question that also remains unasked is whether the AI boom can continue without leading to a massive increase in inequality.
A recent paper by Stijn Van Nieuwerburgh runs the numbers on how much revenue the AI industry needs to generate to recover its massive investment (summary and a link to the paper can be found here: brookings.edu/articles/finan…).
Van Nieuwerburgh’s arithmetic should make us more concerned. AI investments will average about 3.6% of GDP annually between 2025 and 2032. Van Nieuwerburgh calculates that, using a 10% rate of return, the industry would need to generate annual revenues of about $3.7 trillion by 2032 to recover these costs (growing from its current levels of about $200 billion or so). That is significantly more than 10% of current US national income, and will likely remain around 10% of national income by 2032, even if GDP growth rose from its current level.
A large fraction of this revenue will go to capital income. That means a massive increase in the share of capital in national income, which has already risen substantially over the last 25 years or so – now standing at an all-time high of about 47% (bls.gov/news.release/pdf/pro…).
Capital income is much more unequally distributed than labor income, so a massive increase in the capital share of national income will translate into a very sizable surge in inequality.
The rise in inequality may not stop with the capital share. My work with Pascual Restrepo documents that (automation-driven) increases in the capital share of national income are typically associated with rising labor income inequality as well (see, for example, economics.mit.edu/sites/defa…). The same may happen in the next several years, boosting inequality further.
What is missing from our current debate is any discussion of a fundamental dilemma these numbers pose: can the AI boom avoid both an economically costly crash and a huge increase in inequality?
If the industry reaches these revenues, inequality surges. If the industry does not become profitable, a crash, with substantial costs in terms of lost output and jobs, becomes likely.
My assessment would be that the industry is unlikely to reach levels of revenue Van Nieuwerburgh calculates. First, diffusion has been and will likely continue to be slow. Second, competition from open-weight models, which are getting better, will limit how much proprietary models can charge. Third, despite important advances, I still believe that AI models will not be able to automate entire occupations anytime soon, thus limiting their value to businesses as cost-saving devices.
Whether this leads to a crash or not is more complicated and will depend on whether various AI companies are bailed out and what kind of support they receive.
Nevertheless, even if revenues fall short of these gargantuan amounts and we avoid a dramatic surge in inequality, I expect that the diffusion of AI will push up inequality between capital and labor and within labor.
If inequality does surge, a further question becomes central: can our democracy survive such astronomical levels of inequality?
Suvish Viswanathan retweeted
A Silicon Valley startup raised around $40M and launched a decision model built on almost the same idea I had published a year earlier.
My first reaction was excitement. Frustration came next.
So I wrote a Reddit post with my paper, my GitHub and everything I had done. It blew up, and people asked for a model that could beat the Jev benchmarks. I trained it overnight while travelling back from Trivandrum and published it the next morning. That was 12 to 15 hours of work, sitting on top of years of research.
That became Laya: open source, free to self-host, and #1 trending on Hugging Face.
Full interview with Sudhi Sachdev on AIM Network's FrontPage (YouTube).
Suvish Viswanathan retweeted
What does it mean to pace the frontier?
Over the last month, @random_walker and I have analyzed the loss-of-control incidents at AI companies to understand what technical and policy interventions can improve safety and what companies should do to pace the frontier. The result is a new 13,000 word essay — our most substantial writing on AI safety since AI as Normal Technology.
A summary of our arguments:
1) The polarization between the cybersecurity and AI safety communities is counterproductive. The safety community largely sees these incidents as a crisis for alignment, and worries that these incidents will become more damaging as agents become more capable. Cybersecurity practitioners largely see companies failing to take basic security precautions. We offer a middle ground between these communities as a way forward for improving AI safety.
2) We agree with security practitioners that OpenAI did not take adequate protections for controlling their agents. But this is not just a matter of applying 30-year-old security methods to a new domain. Security for AI agents — AI control — while important, is not a solved problem. While known control methods would have prevented the Hugging Face incident, as agent capabilities continue to advance, we will only be able to control them if we invest adequately in control interventions.
3) We also agree with security practitioners’ implicit position that these incidents are primarily a security story. In the AI safety community, rogue agents are treated as inherently catastrophic because of the assumption that there is an endless list of risks that will arise from their development. We disagree. We have long advocated that the best approach to AI safety is to identify the risks and address those specific risks. Over the last few months, it has become clear that one urgent risk is cyberoffense, because it has unique properties that allow agents to carry it out autonomously. We should similarly invest in defenses against other specific risks, such as biorisk and risks from military AI.
4) We agree with the safety community that there is an urgent need for technical and policy interventions to prevent loss-of-control incidents. But in our view, marginal investments in control are more likely to be effective compared to those in alignment. We view these incidents as illustrating the lack of emphasis on AI control within companies, despite the availability of known techniques. More broadly, there are many common-sense policy proposals that could help promote investments in AI control where we share common ground with the safety community.
5) Organization governance should be a key tool for pacing the frontier. Unfortunately, AI companies are trying to reinvent basic aspects of organizational governance as a problem to be solved by improving the technology. But even developing better control techniques will not be enough if irresponsible individuals or teams within large organizations can choose not to use them. When a single misconfigured RL environment or unmonitored evaluation can cause real-world harm, individual teams should not be able to run potentially dangerous experiments without oversight from legal, security, and other teams. AI companies need processes for reviewing experiments, assigning responsibility for monitoring them, and investigating warning signs deeply before restarting experiments. If putting these processes in place requires pausing some experiments, companies should do so.
6) How should we reason about AI's impact on cybersecurity? It's plausible that advances in agent capabilities upset the offense-defense balance for cybersecurity. We cannot yet be certain, but there is enough evidence that agent capabilities might soon make widespread cyberoffense possible that urgent action is warranted. We discuss potential interventions for tilting the offense-defense balance towards defenders.
7) How our views have evolved over the last year. We take stock of AI progress and share how we have updated our views. In the essay, we did not pay sufficient attention to safety risks that arise during development and evaluation (as opposed to the widespread deployment of models). We were too confident that companies would take basic control precautions and underplayed the importance of jaggedness, which led us to underestimate how quickly capabilities could improve in domains such as cybersecurity.
8) At the same time, many distinctive claims of AI as Normal Technology have held up. In particular, we think recent incidents support our continuity hypothesis — the behavior of "rogue" agents became apparent and widely publicized while they are still incompetent at causing serious harm or hiding their traces. The societal reaction to even the relatively small harms from these incidents has been fierce (and the safety community deserves credit for keeping up pressure on companies). Whether this translates into meaningful changes in companies’ behavior remains an open question, and a test of the usefulness of the AINT framework.
9) In short, we’ve tried to synthesize the AI safety and cybersecurity communities' views into a coherent plan of action: hold companies responsible, invest in control, and strengthen defenses against specific risks.
Suvish Viswanathan retweeted
This week I had the honor of speaking to Princeton’s entire incoming undergraduate class to address their AI anxieties. I had three messages for them — good news, bad news, and a note of optimism. Here’s a condensed version.
The good news
We have enough evidence now to conclude that the shrill predictions of rapid, massive job loss were misplaced. Even in a field like software engineering where AI has been rapidly adopted, its effect has been to shift, not replace the role of the human (see the “decide-execute-deliver” framework normaltech.ai/p/why-ai-hasnt…)
Similarly, the panic about what to major in is also misplaced. There will be enduring demand for computer science, philosophy, and just about everything else. (In fact, AI companies hiring philosophers has been a big recent trend.)
The bad news
AI seems to help senior people much more than juniors. I can use AI for coding because I spent 25 years learning how to code, which lets me supervise coding agents effectively. (See my post on the “growth cycle” vs the “dependence spiral” teapawt.org/random_walker/status/2…)
You are in a bind — you can’t offload your skill-building to AI, but you’ll graduate into a market where employers will expect you to get work done with AI. We never faced this dilemma. As a result we haven’t figured out how to revamp our classes to help you do both. You’ll have to help us figure it out. And you’ll need to somehow resist the constant temptation to turn to the shortcut machine.
The hope
My point is not that AI is bad for learning. It’s an incredibly flexible tool. Is the internet good or bad for learning? Depends — are you using it to find research papers or waste time scrolling? I use AI every day for learning. The key is to use it to increase, not decrease your cognitive load. To learn deeper, not faster. There is no learning without the cognitive sweat. I try to make sure I’m mentally exhausted at the end of the day. I do feel that AI lets me push myself harder than I ever could before, and I have a vision that as AI continues to advance it will enable human-AI “co-superintelligence“. (I talked about this at the end of my ICML keynote. normaltech.ai/p/what-will-be…)
There’s a big, under-appreciated reason why people may have very different experiences and opinions about using AI for work — are they using it for tasks they’re already an expert at, or tasks they can’t do themselves? The former leads to a *growth cycle* and the latter leads to a *dependence spiral*.
When I use AI to do something I’m an expert at, like coding, I treat it as a tool. I can build quickly, maintaining an understanding of the code, knowing that if necessary, I can fix the code myself. It feels empowering. It frees up my time to think about the complex, judgment-oriented parts of software engineering that I can’t or won’t delegate to AI. That means my own skills improve rapidly, and I get to climb the ladder of complexity and develop higher-level skills, much more so than when I write the code myself. I feel in control. I can lock in and achieve a flow state — when AI is working, I’m reviewing, building understanding, and planning the next steps. I never get the feeling that the tool is about to replace me. This is the growth cycle.
(Of course, the growth cycle is not automatic. I still need to exercise agency to use AI responsibly. But it’s the same challenge with any productivity-enhancing technology, and those who’ve navigated such transitions before are well-equipped to navigate it with AI as well.)
On the other hand, if I use it for tasks I don’t understand and haven’t learned to perform myself, I have no choice but to treat it as a superintelligence. If something breaks, the best I can do is ask AI to fix it and hope for the best. I generally can’t evaluate the quality of the output myself. The only way to find out if it's any good is if and when the work is ultimately reviewed by an actual expert. The experience is confusing, unsettling and disempowering. And forget about flow state. By over-relying on AI, I risk losing whatever skill I had at the task in the first place, even if it boosts productivity in the short term. This is the dependence spiral.
It’s no wonder that entry-level workers and students preparing to enter the workforce find themselves in a bind. To compete with the AI-enabled productivity of more seasoned workers, they must adopt AI themselves, but doing so risks the dependence spiral. I have some thoughts on solutions that I will share in later posts, but I think having a clear diagnosis of the problem is a useful first step.
German version of Shinrinyoku or forest bathing is Waldluft or Waldbaden! Historically doctors recommended patients with mining related TB/ Lung infections to the Alps/ Schwarzwald region!
Now, studies also link phytoncides & immunity!
"A scientist in Japan demonstrated that the air inside a forest strengthens your immune system for a full month"
Just yesterday, a visitor from Chennai told me "I feel tired often in Chennai and I feel a lot less tired past 2 days, even after doing a lot of work".
We need to live closer to nature and in harmony with nature.
2
143
2 bows. 2 odysseys. 2 heroes. 2 civilizations, 2 thousand years apart, zero contact with each other, and epic, supernatural fights to win her back!
The bar for “welcome home” was NOT low for either of them. One is celebrated with Diwali and the other with reunion!
1
52
Thank you for the wonderful opportunity to exchange our views on Technology cooperation between the two regions!
Ahead of the EU-India Trade and Technology Council, the @Europarl_EN's Delegation for relations with India #DIN hosted a roundtable this morning on EU-India cooperation on the digital technology agenda.
Chaired by MEP @ANiebler, the exchange brought together India's Minister of State @JitinPrasada, @EU_Commission's Renate Nikolay, and representatives from @Siemens, @nokia, @Zoho, @imec_int, @SAP and @DIGITALEUROPE, with discussions focusing on AI, secure 5G/6G infrastructure, digital public infrastructure and semiconductor cooperation.
A timely discussion setting the stage for #TTC Track 1 talks on strategic technologies, digital governance and digital connectivity.
#EUIndia #parliamentarydiplomacy
@JasinJul @NielsFlemming01 @VPrebilic @EU_in_India
1
104
Suvish Viswanathan retweeted
Ahead of the EU-India Trade and Technology Council, the @Europarl_EN's Delegation for relations with India #DIN hosted a roundtable this morning on EU-India cooperation on the digital technology agenda.
Chaired by MEP @ANiebler, the exchange brought together India's Minister of State @JitinPrasada, @EU_Commission's Renate Nikolay, and representatives from @Siemens, @nokia, @Zoho, @imec_int, @SAP and @DIGITALEUROPE, with discussions focusing on AI, secure 5G/6G infrastructure, digital public infrastructure and semiconductor cooperation.
A timely discussion setting the stage for #TTC Track 1 talks on strategic technologies, digital governance and digital connectivity.
#EUIndia #parliamentarydiplomacy
@JasinJul @NielsFlemming01 @VPrebilic @EU_in_India
Creative Accounting Masked as Earnings 😂
🚨 THE ENTIRE AI BOOM MIGHT BE BUILT ON FAKE REVENUE.
Latest corporate filings show that OpenAI and Anthropic alone make up over half of the entire $2 trillion future cloud backlog held by Microsoft, Oracle, Google, and Amazon.
This massive pipeline is actually being created through a circular accounting trick called a round trip revenue loop.
But how it works ?
A tech giant gives billions of dollars to an AI startup as an "investment". But hidden in the contract is a strict rule forcing the startup to hand that exact same money straight back to the tech giant to rent their computer servers.
Look at the documented case of Microsoft and OpenAI.
When Microsoft invested $13 billion into OpenAI, it didn't just give them cash; it gave them "cloud credits" to use Microsoft servers. OpenAI used those exact credits to train its AI models, and Microsoft then turned around and recorded that server usage as brand new "cloud revenue" from a customer.
The tech giant is literally paying itself with its own money and calling it a sale.
This is why OpenAI’s annual cloud bill has ballooned to over $60 billion, double its actual revenue of $25 billion, kept alive solely by this recycled funding loop.
Anthropic runs the exact same play, spending $2.66 billion on Amazon Web Services in just nine months, which was basically 100% of all the money it earned at the time.
This manufactured demand triggers a second accounting trick where tech giants book massive paper profits. Every time a startup gets a higher value from a new funding round, the tech giant updates the value of its investment on its books and counts that unearned paper gain as direct profit.
In Q1 2026, Alphabet reported a record $62.6 billion profit, but $28.7 billion nearly half, was just a paper markup on its Anthropic investment. In the same quarter, Amazon reported $30.3 billion in profit, but $16.8 billion of it was just an Anthropic paper gain.
While Amazon reported record profits, its actual free cash flow collapsed 95% to just $1.2 billion because it had to spend $44.2 billion in real cash to build physical data centers.
This has created a massive danger where these giant companies rely heavily on just one or two unstable startups. Microsoft has 49% of its $627 billion future backlog tied to OpenAI, while Oracle has an incredible 54% of its entire $553 billion pipeline relying on OpenAI alone.
This perfectly mirrors the 2001 dot-com crash when Global Crossing and Qwest Communications swapped identical fiber-optic network capacity with each other just to book fake sales.
Qwest had to erase $1.4 billion in fake income, and Global Crossing went completely bankrupt.
The only difference is that the dot-com swaps were illegal, but today's AI loop is fully legal under current accounting rules.
This legal loop inflates tech company stock prices, forcing automatic retirement accounts and index funds to buy even more of these tech stocks. It is a self feeding loop where investments, sales, and stock prices all go up on paper without the AI technology ever making real cash profits.
132
Microsoft’s Claude pullback is a reminder that when token costs outrun subscription revenue, bits stop scaling and atoms become the bottleneck!
Enterprise value will come from optimising the denominator. Make atoms produce more tokens!
Image from Nvidia.
1
69
Suvish Viswanathan retweeted
🦔Microsoft canceled its internal Claude Code licenses this week after token-based billing made the cost untenable, even for a company with effectively infinite cloud resources. Uber's CTO sent an internal memo warning the company burned through its entire 2026 AI budget in just four months. American AI software prices have jumped 20% to 37%, and GitHub (owned by Microsoft) is dropping flat-rate plans for usage-based billing across its products.
My Take
The AI subsidy era is ending in real time. The same company that put $13 billion into OpenAI and built the Azure infrastructure powering most of Anthropic's compute just looked at the bill from a competitor's coding tool and decided it was not worth paying. That is not a productivity failure on Anthropic's end. Token-based pricing is forcing every enterprise customer to confront the actual cost of running these models at scale, and the number turns out to be far higher than the flat-rate experiments suggested.
This ties directly to my Gemini Flash post yesterday. Anthropic, OpenAI, and Google all raised effective prices in the last six months. Enterprises that built workflows assuming AI costs would keep falling are now watching annual budgets evaporate in months. Two outcomes look likely from here. Either enterprises scale back AI usage to fit budgets, which slows the revenue ramp the labs need to justify their valuations ahead of IPOs, or the labs cut prices and absorb the losses, which makes the unit economics worse at exactly the wrong moment. Both paths land in the same place, the numbers stop working, and somebody has to take the writedown.
Hedgie🤗
An incisive and illuminative piece! Thank you @pHequals7 👏
Tokenomics will start impacting macroeconomics, as the token driven flows reach scale.
1
79
The way intelligence is being commoditised is mind‑blowing.
The new smart is to spot problems early, apply AI, and rely on human judgment for the decisions machines still can’t make.
Knowing when to trust your gut, and when to let the model do the math is the real edge!
1
73
Lay off software engineers because
“AI can do their jobs”
Then pour hundreds of millions into hiring “Forward Deployed Engineers”.
Seems easier to chase shiny roles than to train the people you already paid to hire.
Innovation™, I guess. 🙃
1
49
I see Indian grapes 🍇 fairly often in European markets lately, but not so much Indian mangoes 🥭. Is it mostly because domestic demand in India is so high that there’s not much left for export?
The other Indian product I spot often here is prawns.
1
108
Checking into a hotel in Stuttgart, a guy spots the @Zoho logo on the shirt: “You work for Zoho? We use you guys – good work.”
15 years ago it was “Zoho? Pogo?”
Me: “Thank you for using us” and thinking Little joys like this make the journey worth.
4
157































