Editor’s Picks
Editor's picksCategories
ChannelsLatest Articles
Latest stream
Why "Business Model" Became a Keyword in the 1990s: From Dell and PlayStation to Toyota and Softbank
Why did "business model" become a keyword? This article traces the term's earliest uses in the Japanese business press: the 1995 coverage of Dell and its direct sales plus build-to-order model, the 1997 feature on how PlayStation rejected Nintendo's business model, and later talk of an existing model no longer working as Japan's chip industry came under pressure. It then turns to Toyota — the two pillars of Just-in-Time and jidoka, the flaws of push production, the pull system inspired by American supermarkets, and why Ford-style mass production was overkill in Japan. It closes with Masayoshi Son's time machine management and the idea that there is no single right angle on a business model.
Enterprise AI Adoption: Getting a Demo to Run Is Only the Starting Line
Using the Tencent Research Institute's FDE report as a lens, this article lays out four problems that recur in enterprise AI adoption: mistaking a working demo for a shippable product, building an AI application without choosing a high-value scenario, assuming AI can do what employees already do well, and confusing individual productivity with organizational productivity. Drawing on AI customer service and ERP examples, it explains the gap between demo and production and why tacit knowledge must be turned into usable context, then offers three fixes: don't measure the adoption cycle by demo speed, organize small teams where business and technology share accountability, and have senior leadership personally drive process, responsibility, and assessment changes.
The Jev Model That Gave Up Chatting: Why a Decision-Only Model Is Faster and Cheaper
TypeSafe AI's Jev does not write; it returns decisions and their probabilities. In official tests it is up to about 193.6 times faster than a general-purpose LLM and about 444.6 times cheaper, at $0.042 per million input tokens with free output. Called with a state and a question, it answers as Noul, Choice, or Score, and is trained with RLCD so its calibrated probabilities can drive automatic routing—a division of labor among judging, generating, and executing.
Three Systems All Show 100 in Stock. So Why Can't You Promise the Customer 80?
The warehouse, e-commerce, and procurement systems each show 100 units, but adding them up does not mean you can deliver 300. Palantir splits a real business decision into Data, Logic, Action, and Security, describes the business world with Object, Property, and Link, and lets AI actually execute within enforced boundaries. Using an inventory example, this article explains the core of the Ontology and how its philosophy maps onto skills and MCP in the LLM era: build agents first, and let the Ontology grow with complexity.
Breaking Development into why and action: A Proposal to Rebuild the Runtime Around a Judgment Engine
Starting from JVE, a judgment engine that appeared in 2026, this post abstracts development into a key-value pair of why and action and imagines a new runtime driven by the current state: it takes in "now," decides which why-actions to prioritize and in what order, then runs them. A reaction after each action becomes new input that triggers the next Y; browser use watches "now," and an interview helps people build their own why-action database. The scope narrows to a small "find you a job" example in three steps.
From Revenue to Net Income: How to Read a Company's Earning Power
Higher revenue does not necessarily mean stronger earning power. This article moves from revenue, cost of sales, and SG&A down to operating profit, then through the five profit layers of the income statement: gross profit, operating profit, ordinary profit, pre-tax profit, and net income. Using Mazda and Mercari, it explains the gross-versus-net revenue distinction, along with gross margin, restaurant FL cost, why industries emphasize different profit measures, and how EBIT and EBITDA work. The lesson: compare companies by understanding the business model and accounting basis behind each number.
Reading Revenue and Profit: Why Two Income Statements Can't Be Compared at Face Value
Revenue and profit are the go-to numbers for comparing companies, yet how they are calculated differs sharply by industry and by company. Using manufacturing as an example, this article walks through the ladder from revenue, cost of goods sold, and SG&A to operating profit, ordinary profit, and net profit. It then shows how much revenue can differ in substance, from Mercari booking only its roughly 10 percent commission to construction's revenue recognition and the unpredictable earnings of securities and game companies. It explains the three sources of high gross margins and why trading companies watch net profit, Nippon Yusen watches ordinary profit, and SoftBank Group watches NAV, along with business profit, EBITDA, and EBIT.
The Real Mass Adoption of AI May Have Nothing to Do With Saving Time
a16z's seventh report reveals a contradiction: nearly half of U.S. consumers have used AI, but only about a quarter use it daily and just 4.5% pay for ChatGPT, Gemini, or Claude—while the top 1% of payers spend $903 a month. For three years AI has been understood as a time-saving productivity tool, yet the consumer products that reached billions made people want to spend time in them. Tracing personal agents and subscription economics, the piece argues consumer AI must shift from efficiency to experience.
Reading 9 Business Models Through a Single Transaction Map
This article uses a single 'transaction map' to organize business models along two axes: value creation (the power of a single product, of combination, and of alliance) and revenue capture (value chain, recurring, and the three-party market). It then walks through nine models — manufacturing, distribution and retail, combination, recurring, freemium, installed base, advertising, matching, and platform — showing how even complex businesses reduce to basic moves and how the map works as a tool for reading strategy across industries.


