The make-and-sell model looks simple: a company manufactures and sells its own products and is paid by customers. Yet its strengths and its fragility come from the same place. Two axes matter: standalone strength—high quality, low cost, and things rivals cannot do—and the way revenue is earned across the value chain of procurement, processing, and delivery. One ultra-precision parts maker stagnated on mass-production defects, moved its main line to Southeast Asia in the 1990s, and improved defects so thoroughly that it held an operating margin above 10 percent through the 2008 recession and the 2011 earthquake. But quality and profit margin are different things: a supplier that cannot refuse price-cut demands does not recover, and was acquired. The only ways out are to overhaul the value chain or change the model.
Enterprise ontology has split into two currents. The analytical semantic layer unifies metric definitions and supports BI, Text-to-SQL, and LLM grounding in a read-only way; the operational ontology fuses state-change transactions, precondition validation, write-back to external systems, and type-safe OSDK code generation into a runtime for business applications. The offerings from Databricks, Microsoft, and Google Cloud are essentially extensions of the former, while Palantir represents the latter, implementing enterprise-scale CQRS and decision lineage. This article compares their structures, their division of labor in the age of AI agents, and a selection matrix for enterprise architecture.
Using a retail bank loan-switch example, this article shows how Knowledge Catalog and Gemini connect data science with marketing: natural-language data exploration, auto-generated PySpark with zero-copy joins on Lightning Engine, an XGBoost model (90% accuracy, 85% precision), one-click publishing to the catalog, and zero-token BI analysis that compresses months of work into minutes.
Putting a table schema in the prompt does not teach an AI agent what the business means, so it can still return a number that looks professional but is wrong. Drawing on an insurance-industry benchmark where GPT-4's execution accuracy rose from about 16% to about 54%, this article explains the semantic layer built from metrics, an ontology, and documents; how OBDA maps the ontology onto existing data; and how layered resolution balances determinism with flexibility. It also covers AI-drafted, expert-approved ontologies, MCP delivery, identity-aware governance, and five practical recommendations.
A machine cannot tell that "Apple" means a company rather than a fruit, or that three tables all named Customer mean different things, without an explicit semantic model: an ontology. This article traces the idea from philosophy to Gruber's and Studer's definitions, breaks down classes, individuals, properties, and axioms, and covers RDF, RDFS, OWL, and reasoners. It surveys real uses in biomedicine, Schema.org, enterprise data integration, industry and IoT, and the LLM era, then explains how ontology differs from a knowledge graph and how to start building one.
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.
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.
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.
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.
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.
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.
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.