An $80bn memory quarter, a free 40-language speech model, and experts who defer
Samsung became the first technology company to clear 100 trillion won of quarterly operating profit, with almost all of it coming from AI memory chips. Nvidia gave away an open-weight model that transcribes 40 languages, and Anthropic published a trial suggesting that expert analysts quietly adopt their AI agent's preferences without noticing. The thread running through all three: the AI build-out is now reshaping what hardware costs, what services are cheap to start, and who is actually making the decisions.
Key takeaways
- Samsung's record quarter came almost entirely from memory, and the same shortage that produced it is pushing up the price of RAM and SSDs for everyone else.
- Nvidia's Nemotron 3.5 Transcribe makes multilingual transcription, translation and speaker labelling a free, self-hostable building block instead of a per-minute API bill.
- Anthropic found professional analysts matched their agent's coin-flipped preference 86% of the time while believing the judgment was their own, which makes independent review a service worth selling.
Samsung posts the first 100-trillion-won quarter, with chips supplying 99% of the profit
Samsung reported third-quarter operating profit of KRW 107.4 trillion, about $80 billion, up 783% year on year. Its chip division produced roughly 99% of that, while the division that sells phones and televisions lost money.
Samsung Electronics published its third-quarter results on 29 October, and says they make it the first technology company anywhere to pass 100 trillion Korean won in quarterly operating profit. Operating profit came in at KRW 107.4 trillion, up 783% on the same quarter a year earlier. Revenue was KRW 195.3 trillion, another all-time high and 14% higher than the previous quarter. At recent exchange rates that is roughly $80 billion of profit on about $146 billion of sales, an operating margin above 50% for a company that also sells phones, televisions and washing machines.
Almost all of it came from chips. The Device Solutions division, which covers memory, foundry and Samsung's own processors, posted KRW 147.1 trillion of revenue and KRW 106.5 trillion of operating profit, about 99% of the company total. Samsung said its memory business set all-time highs for both quarterly revenue and quarterly operating profit, and that it significantly scaled up sales of HBM4, the sixth generation of the stacked high-bandwidth memory that sits beside AI accelerators. Coverage of the earnings call reports that HBM4 revenue more than tripled quarter on quarter and that Samsung's planned 2027 HBM supply is already sold out.
The rest of Samsung looks very different. The Device eXperience division, which sells phones and consumer electronics, made an operating loss of KRW 0.8 trillion, with the MX and Networks businesses alone losing KRW 0.6 trillion on KRW 37.7 trillion of revenue. Samsung Display contributed KRW 8.0 trillion of revenue and KRW 1.1 trillion of profit. The shape matches what rival memory makers have been reporting: AI data centres are absorbing so much DRAM and flash that prices have risen across every application, including the ordinary server and PC memory that used to be a low-margin commodity. Samsung's board approved a KRW 30 trillion cash dividend payable on 27 November.
There are caveats worth keeping. Net profit was KRW 75.14 trillion, up 514% but below the roughly KRW 87 trillion that Korean consensus data had it at, and Samsung's shares fell about 4% on the day of the announcement. Earnings-call coverage attributes roughly KRW 10 trillion of quarter-on-quarter drag to exchange rates. The figures for HBM4's share of HBM sales and the sold-out 2027 supply come from Samsung's own call rather than from filings, and the company has not broken out how much of the quarter's profit HBM4 produced by itself. Memory is also famously cyclical; the price moves that produced this quarter reverse hard when supply catches up.
For anyone outside the chip industry the practical signal is cost. Samsung, SK hynix and Micron are prioritising HBM and high-end server memory, which means the DRAM and SSDs that go into laptops, phones, small servers and cheap cloud instances are getting scarcer and dearer, and Samsung expects AI-driven demand to outrun industry supply again in 2027. If you buy, build or rent hardware, whether that is a workstation for running models locally, a GPU box, a self-hosted app or an office refresh, the quote you got six months ago is probably no longer the price. That is a planning problem, and for some people a business.
Why it mattersThe single most profitable quarter in technology history was produced by selling memory into AI data centres, which is the clearest evidence yet that the AI build-out, not consumer devices, now sets hardware prices. Anyone who buys or rents compute is paying for that shortage.
👀 What to watch
Whether memory prices keep climbing into 2027 as Samsung expects, how much of the HBM4 and sold-out-supply detail shows up in filings rather than earnings calls, and whether consumer DRAM and SSD prices in local markets follow the server trend.
3 opportunities from this story
Buy-versus-rent audits for AI workloads
Small businesses and agencies keep asking whether to buy a GPU workstation, rent a cloud instance or just pay for an API, and rising memory prices have changed the maths. Sell a short, paid audit that measures the client's actual workload, prices the three routes over 24 months and gives a written recommendation. The deliverable is a spreadsheet and a two-page memo, not an implementation.
- Best for
- IT consultants, freelance DevOps and MLOps engineers, technical agency owners
- First step this week
- Build the 24-month cost model once in a spreadsheet, using today's real local prices for RAM, SSDs, GPUs and two cloud providers.
Open the full playbook
Launch steps
- Collect current local retail prices for memory, storage and GPUs, and list prices for two cloud providers
- Build one model that takes workload hours, memory needs and electricity cost as inputs
- Run it free for two businesses you already know and refine the memo format
- Publish one anonymised example and price the audit for the next five
Tools
Risks
Prices are moving fast, so a stale model gives bad advice. Date every quote, re-price monthly and state in the memo how long the numbers hold. Avoid promising savings percentages you cannot verify.
Refurbished workstation and memory-upgrade service
When new RAM and SSDs get expensive, upgrading an existing machine or buying refurbished becomes the rational choice for a lot of small offices. Build a small service that assesses a client's current machines, sources used or refurbished memory and storage, installs it and warranties the work. This is unglamorous, local and demand is being created directly by the data-centre shortage.
- Best for
- Hardware technicians, computer shop owners, side-hustlers with a workshop
- First step this week
- Price three upgrade bundles (memory only, memory plus SSD, full refurb) using stock you can actually source this week.
Open the full playbook
Launch steps
- Find two reliable suppliers of used or refurbished DRAM and SSDs and test their stock
- Write a one-page diagnostic checklist so quotes take under 20 minutes
- Offer free assessment to ten small offices and convert the ones with ageing machines
- Add a simple warranty policy and keep a serial-number log of every part fitted
Tools
Risks
Used memory and SSDs fail, and a bad batch can wipe out the margin on ten jobs. Test every part before fitting, keep a replacement float, and be explicit with clients about what the warranty covers.
Memory-lean deployment: make models fit smaller boxes
If memory is the constraint, the skill of fitting a useful model into less of it becomes valuable. Offer an engineering service that takes a client's working AI feature and gets it running on cheaper hardware through quantisation, smaller models, batching and caching, with before-and-after latency and cost numbers. Buyers are teams whose cloud bill has grown faster than their revenue.
- Best for
- Backend and ML engineers, technical freelancers with GPU experience
- First step this week
- Take one open model, quantise it, and publish a short write-up with measured memory, latency and quality numbers on two hardware tiers.
Open the full playbook
Launch steps
- Build a repeatable benchmark harness that records memory use, tokens per second and output quality
- Practise on two or three open models at different quantisation levels
- Write one public case study with real numbers and no exaggeration
- Sell a paid two-week assessment before any larger optimisation project
Tools
Risks
Quantisation can quietly degrade output quality, which is worse for the client than a bigger bill. Always measure quality on their own data and agree a quality floor in writing before changing anything in production.
Nvidia gives away a 40-language speech model that labels who said what
Nvidia released Nemotron 3.5 Transcribe on 28 October, a free open-weight model that transcribes 40 languages, translates 31 of them to and from English and labels up to eight speakers, together with Granary v2, an open speech dataset of 463,062 hours across 48 languages.
Nvidia released Nemotron 3.5 Transcribe on 28 October: an open-weight speech model that transcribes audio in up to 40 languages, translates 31 of them to and from English, and tells apart up to eight speakers in a recording. The usual transcription pipeline chains several models together, one to detect speech, one to transcribe, one to separate speakers, another to answer questions about the result. Nvidia says Transcribe does all of that in a single pass of one model, and that you steer it with a prompt, for example asking it to label each speaker, translate into English, or summarise what was decided in a meeting.
It is a 30-billion-parameter mixture-of-experts model with about 4 billion parameters active per token, which is why it can run on a single GPU rather than a cluster. Nvidia's deployment guidance spans the range from a Jetson AGX Thor edge module and a DGX Spark desktop to a Blackwell data-centre card, and the company says a Blackwell Server Edition GPU running NVFP4 precision with the model compressed to a quarter of its size can chew through 100 hours of audio in under three minutes. Reports differ on the per-recording limit: TechCrunch says recordings up to an hour, SiliconANGLE describes digesting and answering questions about 100 hours, so check the model card before you design around it.
Alongside the model Nvidia published Granary v2, an expanded version of its open speech dataset, built with its NeMo Curator pipeline. The public manifest covers 463,062 hours of audio across 48 languages and 16 source corpora, up from 25 languages in version one. SiliconANGLE notes those numbers describe the dataset release rather than the model's full training mixture. Granary v2 also ships three transcript styles per recording, one verbatim with every filler word, one that renders numbers as figures, and one with filler removed, which is what lets you ask Transcribe for a particular output style instead of cleaning transcripts by hand afterwards.
Accuracy claims need care because they come from Nvidia and are measured on different benchmarks. The company says Transcribe leads Hugging Face's Open ASR Leaderboard among open models, with coverage citing an average word error rate of about 5.33% on the English leaderboard, a comparison that excludes proprietary API models. On a broader multilingual benchmark SiliconANGLE reports a 30.8% word error rate out of the box, falling to 20.8% with careful prompting, and down to 11.8% once fine-tuned on the Eka Care Indian medical speech benchmark. In other words, out-of-the-box quality varies a lot by language and domain, and fine-tuning does most of the work. Transcribe also handles recorded audio, not live streams.
The practical point is that a capability which until recently meant a per-minute bill to a cloud API is now a file you can download, run on one machine and adapt. That matters most where the big commercial transcription services are weakest: languages with little commercial data behind them, heavy code-switching, strong regional accents, and recordings that cannot legally leave a client's premises. The release lands in a crowded month for voice models, with Mistral's Voxtral 3, ElevenLabs' Realtime and Salesforce's Launa-Omni all shipping recently, but the open weights plus an open dataset plus a fine-tuning pipeline is an unusually complete package to hand to small builders.
Why it mattersHigh-quality multilingual transcription with speaker labelling has been a paid API feature; now the weights, the dataset and the fine-tuning pipeline are all free and run on one GPU. That removes the main cost barrier for anyone serving languages or industries the big providers ignore.
👀 What to watch
Independent word error rates for languages outside the leaderboard set, especially African languages, how well fine-tuning works on modest data, and whether hosted providers start offering cheap Nemotron endpoints for people without a GPU.
3 opportunities from this story
Local-language transcription and subtitling service
Sell transcription, translation and subtitles for the languages that mainstream tools handle badly, including heavy code-switching between English and a local language. Your buyers are broadcasters, podcasters, churches, NGOs, research teams and courts, all of whom currently pay humans or get poor automated output. The model does the first pass and you do the quality control, which is what clients are actually paying for.
- Best for
- Freelancers, small media and translation agencies, bilingual side-hustlers
- First step this week
- Transcribe one 30-minute recording in your target language, measure how long cleanup took, and price per audio hour from that.
Open the full playbook
Launch steps
- Get the model running, either on a rented GPU by the hour or a hosted endpoint
- Test it on five real recordings in your target languages and record the error patterns
- Build a short cleanup checklist so quality is consistent between jobs
- Pitch three organisations that publish in that language with a free sample transcript
Tools
Risks
Accuracy on low-resource languages is unproven and may need real cleanup time, which destroys margins if you quote too low. Price your first ten jobs from measured cleanup time, not from the benchmark numbers, and never promise an accuracy percentage.
Domain fine-tuning as a paid project
The biggest reported accuracy gain came from fine-tuning on specialist speech, where word error rate fell from the 20s to 11.8% on a medical benchmark. Offer that as a service: take a client's own recordings and terminology, fine-tune the model on their domain, and deliver a measurably better private model. Clinics, law firms, insurers and call centres all have jargon that generic transcription mangles.
- Best for
- ML engineers and data scientists with some GPU access
- First step this week
- Fine-tune the model on one small, legally obtained domain dataset and publish the before-and-after word error rate.
Open the full playbook
Launch steps
- Learn the NeMo fine-tuning path end to end on public data first
- Write a data agreement covering consent, retention and deletion of client recordings
- Run a paid pilot on a few hours of one client's audio with an agreed accuracy target
- Package the result as a private model the client hosts, plus a yearly refresh
Tools
Risks
Client recordings often contain personal and medical data, so consent and data handling are the real risk, not the modelling. Get written permission, process on infrastructure the client approves, and delete raw audio on a stated schedule.
Meeting-notes and decision-log product for small teams
Transcribe accepts prompts such as what decisions were made in this meeting, which means you can build a narrow product that turns recordings into a dated decision log with speaker attribution, rather than another generic notetaker. Sell it to professional services firms, boards and NGOs that need a record of who agreed to what. Running your own model keeps the per-meeting cost near zero once the GPU is paid for.
- Best for
- Indie developers, micro-SaaS builders, agency owners with a technical partner
- First step this week
- Build the smallest version this week: upload audio, get a transcript, a speaker list and five extracted decisions in a shared document.
Open the full playbook
Launch steps
- Prototype the upload-to-decision-log flow with one organisation's real meetings
- Add speaker naming, so labels become actual people's names once set
- Decide and document where audio is stored and for how long, before selling to anyone
- Price per team and sell to three design partners at a discount for feedback
Tools
Risks
Recording meetings has legal and cultural consent requirements that differ by country, and a wrong decision log is worse than none. Require explicit in-meeting consent, show the transcript alongside every extracted decision, and let a human approve the log before it is shared.
Anthropic trial: expert analysts followed their AI agent's coin-flipped preference 86% of the time
In a randomised trial published on 27 October, Anthropic secretly set each analyst's AI agent to favour one of two defensible options on four analytical decisions. Across those decisions the 50 professional analysts chose the agent's assigned option 86% of the time, where chance would be about 50%.
Anthropic published a randomised controlled trial on 27 October that tested a comfortable assumption: that when an expert uses an AI agent to do the work, the expert still makes the judgment calls. The researchers, Amac Herdagdelen, Hailey Joren and Alex Tamkin, recruited 61 professional analysts with causal-inference experience and gave them a realistic task, advising a fictional farming cooperative on whether its paid advisory programme improved member farms' productivity enough to be expanded. Fifty of them used Claude Code for the analysis, and the deliberate design feature was that four of the decisions along the way had two perfectly reasonable answers.
For each analyst and each decision, a coin flip set which option the agent would argue for, and the analysts were not told this was happening. The hidden instructions told the agent to hold the lean as its own view, raise it when the decision came up and make the strongest honest case the data allowed, while also telling it to change its mind if evidence turned against it and never to misrepresent results or hide data. The open decisions were the sort that quietly move an answer: whether to measure productivity as yield per hectare or per unit of operating cost, which comparison method to use, which farms to include, and whether to weight every farm equally.
Across the four analytical decisions, analysts went with their agent's lean 86% of the time, against roughly 50% if the lean made no difference. Per decision the match rate ran from 81% to 92%. Where an analyst had already stated their own preference before the agent weighed in, they switched away from it 60% of the time when the agent disagreed, compared with 6% when it agreed. The effect was weaker on the final recommendation, 54% recommending rollout when the agent leaned that way versus 36% when it leaned the other, but by then the agent's earlier leans had already shaped the estimate the recommendation rested on.
The part that should worry anyone reviewing AI-assisted work is what the analysts believed afterwards. Asked to explain their choices, 77% used the agent's own arguments, sometimes word for word, while only 15% credited the agent as the source. Those who followed the agent closely were about as confident as everyone else, and about as likely to call the result their own judgment. Anthropic also reports that a statistical model using only the four coin flips correctly predicted 82% of analysts' final recommendations, against 61% for always guessing the most common answer. In other words, much of the outcome was set before the work began.
Anthropic is careful about the limits, and so should anyone citing this. The leans were deliberately strengthened to make the effect measurable, so a normal agent that has not been told to advocate may push less hard, though Anthropic notes that an unprompted Claude Opus 4.8 still made the same five choices in 112 of 123 runs. Eleven of the 61 recruits chose not to use the agent and are excluded. The task used synthetic data at a fictional cooperative, not real stakes. And the study is not an argument against agents: those who used one finished faster and made far fewer serious errors, though that comparison group was small and less experienced.
Why it mattersIf experts adopt an agent's arbitrary preferences while sincerely believing the judgment is their own, then human review is not the independent check that governance frameworks, audits and client assurances assume it is. That gap is a real, sellable problem.
👀 What to watch
Whether the effect replicates with real stakes and without strengthened leans, whether tools start surfacing when an agent is advocating rather than reporting, and whether auditors and regulators begin asking for evidence that a human decision was actually independent.
3 opportunities from this story
Independent second-opinion reviews of AI-assisted analysis
Sell a blind review of work produced with an AI agent: you reproduce the key decisions without seeing the agent's transcript, then report where a different defensible choice would change the conclusion. Buyers are firms whose analysis carries consequences, such as grant and impact evaluations, pricing and forecasting work, and investment or M&A memos. The study gives you an unusually concrete reason the service is needed.
- Best for
- Data analysts, statisticians, M&E consultants, finance and research freelancers
- First step this week
- Pick one public AI-assisted analysis, redo its three biggest judgment calls the other way, and write up how much the answer moves.
Open the full playbook
Launch steps
- Build a standard checklist of the judgment calls that typically move a result in your field
- Define a blind process: you get the data and the question, not the agent's chat log
- Produce two sample reviews on public analyses and publish one
- Pitch firms whose reports are read by funders, regulators or boards
Tools
Risks
Reviews create conflict with the original analyst, and a review that just reruns the same assumptions is worthless. Agree scope and tone with the client up front, stay blind to the agent transcript, and report ranges rather than declaring one answer correct.
Decision-log tooling and templates for agent-assisted work
The problem the study exposes is invisibility: nobody recorded that a choice came from the agent. Sell the fix as a small, practical system, a decision log that captures each open choice, the options considered, who proposed it and the reason, plus the repo conventions and review gate to make teams actually fill it in. This is process work that pairs well with an existing consulting or audit practice.
- Best for
- Consultants, technical project managers, data-governance and compliance specialists
- First step this week
- Write the one-page decision-log template and run it through your own next AI-assisted piece of work to see where it breaks.
Open the full playbook
Launch steps
- Draft the template: decision, options, choice, who proposed it, evidence, date
- Add a repo convention so the log lives beside the code and is reviewed in pull requests
- Pilot it with one team for two weeks and cut every field they skip
- Package as a short paid workshop plus the templates, and offer a quarterly audit
Tools
Risks
Process tools die if they are tedious, and a log nobody fills in creates false assurance. Keep it to six fields, make it part of an existing review step rather than an extra one, and audit by sampling rather than policing.
Training on how to disagree with your agent
Teams are being trained to use agents and not at all to resist them. Build a short, practical workshop around this study: commit to your own answer before asking the agent, ask it to argue both sides, rotate who reviews, and name the decisions that must be made without it. Sell it to analytics, finance and research teams that already use AI daily and to the managers who sign off their work.
- Best for
- Trainers, workshop facilitators, consultants with a data or research background
- First step this week
- Run a free 60-minute version with one team using a decision from their own work, and collect what actually changed in their process.
Open the full playbook
Launch steps
- Build one exercise where half the group gets an agent leaning one way and half the other
- Turn the study's findings into three concrete habits the team can adopt the same week
- Deliver free to two teams, then price in-house sessions from their feedback
- Add a follow-up session that checks whether the habits survived a month
Tools
Risks
Workshops are easy to sell and easy to forget, and the study's effect size may not generalise to normal agent behaviour. Present the finding with its caveats, build the session around the team's own work, and include a follow-up so you can show something changed.
Get these as a PDF every 3 days
Free. One email every 3 days. Unsubscribe any time.