149 posts tagged with "Playbook"

Anthropic's Claude 5 launch is really three separate launches with one shared story: capability is moving down the price ladder faster than most teams' architecture assumes. Opus 5 landed on 24 July 2026 at the exact same price as the outgoing Opus 4.8 — $5 input / $25 output per million tokens — while offering Fable-adjacent performance on several benchmarks. If your Claude cost model still assumes "the good model is expensive," it's already out of date.

Claude Code is easy to misread as "chat that writes files." It isn't. It is an AI coding agent with an agentic loop, a context window, tools, and a permission system — you steer it through Explore → Plan → Code → Commit, then harden the workflow with CLAUDE.md, skills, subagents, MCP, and hooks.

"Sovereign AI" gets used loosely enough in vendor marketing that it's worth being precise about what Cohere's Command A+ actually offers versus what the phrase implies. Command A+ (218B and 25B, Apache 2.0) is built specifically for enterprises and governments that need to run a capable model entirely within their own infrastructure boundary — not as a philosophical statement, but as a concrete set of deployment, data-residency, and control guarantees that a hosted API fundamentally cannot provide, regardless of that API vendor's compliance certifications.

Technical specialists who want to consult rarely lack skills. They lack a commercial operating system: niche, offers, discovery, proposals, pricing, delivery rhythm, and a pipeline that does not depend on luck.

This page is that map. It expands the open Consulting Handbook (MIT) curated for data engineers, software engineers, analysts, and data scientists—then layers a recommended study order, Free/Paid labels, and deep links into this playbook’s consulting articles.

Consulting lead generation is the process of identifying organisations with important problems, earning their attention, starting credible conversations, and converting those conversations into qualified consulting opportunities.

It is not simply:

• Posting frequently on LinkedIn.
• Sending hundreds of cold emails.
• Attending networking events.
• Asking everyone whether they “need consulting.”
• Offering a free call without a clear reason.
• Producing generic reports about popular topics.

Those activities may create visibility, but visibility alone does not create a consulting pipeline.

A consulting lead is generated when five conditions come together:

Relevant problem × credible expertise × access to the buyer × commercial urgency × clear next step

Consulting is also different from selling a standard product. The client is usually buying an uncertain future outcome rather than a predefined object. Before engaging a consultant, buyers often need to believe that:

1. The problem is significant enough to address.
2. The consultant understands the problem.
3. The consultant can navigate the organisation.
4. The consultant can reduce delivery and political risk.
5. The expected benefit is greater than the cost.
6. The consultant will not create additional problems.
7. The consultant is more suitable than internal delivery, another consultancy, or doing nothing.

This means consulting lead generation is fundamentally a trust-building and problem-development process.

DeepSeek's real contribution to the 2026 model landscape isn't any single model — it's three specific technical ideas that the rest of the industry has since absorbed to varying degrees: Multi-head Latent Attention for cheaper KV-cache memory, Mixture-of-Experts done at extreme sparsity, and Group Relative Policy Optimisation as a reinforcement-learning method that made reasoning-focused training dramatically cheaper. If you understand those three ideas, you understand why DeepSeek mattered, and you'll recognise the same ideas (in variant form) inside half the other models in this series.

A go-to-market strategy for an AI solution is not simply a marketing plan. It is the coordinated design of:

For AI products, the “trust” component is particularly important. A technically impressive solution can still fail because the buyer cannot establish:

• Who is accountable for its outputs.
• Where customer data is processed.
• Whether the model can hallucinate.
• Whether regulators will accept it.
• Whether employees and customers will use it.
• Whether its financial benefits exceed implementation and operating costs.

In EMEA, the challenge is greater because EMEA is not one market. An AI solution sold in the UK, Germany, the UAE, Saudi Arabia and South Africa may require different hosting, contracting, languages, regulatory controls, partner models and sales motions.

This guide explains the complete process and then applies it to a detailed hypothetical case study: an AI customer-service platform for regulated banks.

Financial modelling is the process of translating a business idea, investment, product, project, or company into numbers.

A financial model helps decision-makers answer questions such as:

• How much will the AI solution cost?
• How will the solution generate financial value?
• When will the investment break even?
• How much cash will be required?
• What happens if adoption is slower than expected?
• Is it cheaper to build, buy, or partner?
• Which AI architecture provides the best combination of cost, quality, latency, and risk?
• What is the company or AI product worth?
• Should the organisation approve, delay, redesign, or reject the investment?

For an ordinary software project, financial modelling usually connects customers, prices, employees, and infrastructure costs.

For an AI solution, the model must connect several additional variables:

For example:

The most important principle is:

Do not measure only cost per token, request, model call, or GPU hour. Measure cost and value per successful business outcome.

Examples of meaningful AI financial units include:

• Cost per successfully resolved customer enquiry
• Cost per approved insurance claim
• Cost per qualified sales lead
• Cost per completed legal review
• Cost per detected fraud case
• Cost per accurate document extraction
• Cost per software feature delivered
• Cost per clinical document summarised
• Revenue per AI-assisted customer
• Gross profit per AI agent session

Cloud FinOps applies the same fundamental relationship to AI as to other cloud services:

However, AI introduces unusual quantities such as input tokens, output tokens, model calls, GPU time, retrieval operations, evaluation runs, agent steps, tool calls, and human-review events. FinOps therefore recommends connecting cloud costs to business-unit economics rather than viewing infrastructure spending in isolation.

Artificial intelligence models are improving at a remarkable pace. A model released only six months ago can quickly appear less capable, less efficient and less reliable than a newer generation. It is tempting to assume that every new model is smarter because it contains more parameters — but modern frontier systems such as Claude Fable 5, Claude Opus 5, GPT-5.6, Gemini 3.6 Flash and Kimi K3 are improving through a much broader stack of advances.

Most models in this series added agentic and coding capability on top of a general-purpose foundation. GLM-5 is positioned the other way around: an architecture and training programme explicitly aimed at agentic software engineering — multi-step tool use, long-running autonomous tasks, and code-heavy reasoning — as the primary target, with general chat capability as a secondary consequence rather than the main event. That inversion of priorities is the thing actually worth evaluating here, not a benchmark score.