# Context Design Co > We build private AI brains for South African businesses — a system your company > owns that knows your files, emails and history, and answers in plain English. > Internally the knowledge layer is called a Substrate. Operating across South > Africa from Cape Town, Stellenbosch, Bloemfontein, and Johannesburg. Trading > entity: Yield SPM (Pty) Ltd (Reg 2024/185151/07). ## What we do - **We build Substrates.** A Substrate is the structured, governed, business-specific knowledge layer that sits between an organisation and its LLM. The model stays generic; the Substrate is what makes it expert. - **Substrate ladder — four scope tiers (see /pricing/).** Proof (fixed-scope, 6 weeks — one high-value workflow captured and running), Foundation (fixed scope in quote, 8–12 weeks — the full brain for one part of the business, 3–5 systems connected), Practice (fixed scope in quote, 4–6 months — one brain across the whole operation, flagship tier), Federation (by mandate — multi-Substrate operations across business units or group companies). Stewardship (monthly retainer) is a separate ongoing-care offer that follows a live Substrate, not one of the four scope tiers. - **MCP-compatible. Self-hosted. Human-in-the-loop.** Substrates emit structured drafts to operator outboxes; humans approve before anything reaches a customer or system of record. Bring your own LLM (Claude, GPT, Gemini) — we don't lock the model layer. ## Why this exists AI capability is expanding faster than any single business can absorb it. The gap between "AI is impressive" and "AI is useful for *us*" is contextual, not technical. The model doesn't know your customers, your suppliers, your accounting periods, your contracts, your compliance constraints, your tone, your priorities. A Substrate encodes those things — once, well — and then every subsequent model generation makes the Substrate more valuable, not less. We design Substrates so that as Anthropic, OpenAI, Google, and others ship more capable base models, the *same* Substrate becomes proportionally more useful. Custom context is the durable layer. ## Operational IP — the asset framing The Substrate is a **balance-sheet asset**, not a service receipt. At handover the client receives **Operational IP** — codified ontology, runbooks, decision history, integration map, audit log, retrieval graph, DR procedure, training docs. The **Handover Manifest** is the literal deliverables list. MIT-licensed, self-hosted, capitalisable as an intangible asset. Three mechanisms move valuation: key-person risk discount removal, documented operational IP premium, capitalisable software asset. Independent technical due-diligence verification during Stewardship gives the buyer's auditor the sign-off needed to capitalise the substrate as an intangible asset. We name the mechanism, not the magnitude — the auditor and prospective buyer quantify. Full essay: https://contextdesign.tech/notes/operational-ip-now-capital Page: https://contextdesign.tech/operational-ip ## Three showcases that prove the thesis - **[Attesté](https://atteste.art)** — AI art collection management platform. Run by one human and one AI agent on a custom-fit Substrate. The operating model behind the SaaS company. See: https://contextdesign.tech/notes/atteste-operator-substrate - **[Practacular](https://practacular.com)** — AI practice management for South African accountants. An Obsidian graph substrate gives accountants advanced semantic RAG plus flat grep-RAG over their entire practice. See: https://contextdesign.tech/notes/practacular-practice-multiplier - **[BlitzBox](https://contextdesign.tech/blitzbox/)** — the productized substrate. A single-tenant local-first AI substrate that ships on a custom- finished Apple Mac Mini at customer premises. Brain, Financial, Email, and Compliance modules always on. Mothership in `africa-south1` only handles licensing and credential rotation — never customer business data. R30,000 upfront + R15,000/month + R5,000 refundable EFT deposit. Same Substrate pattern, three very different shapes. That's the point. ## Who we work with - **Operating businesses with messy context** — manufacturers, distributors, professional-services firms, asset-heavy operators. The kind of organisation where institutional knowledge lives in spreadsheets, mailboxes, WhatsApp threads, and one person's head. - **Buyer profile** — typically the operator (CEO, MD, Owner) or the technology lead (CTO, Head of IT, Head of Operations). Substrate engagements affect both strategy and infrastructure, so both stakeholders need to be in the room early. ## How we work — engagement structure - **Substrate Proof (6 weeks, fixed price)** — diagnostic + working artefact. By week 6 the buyer has a runnable Substrate that proves AI can be useful for one important workflow in their business. We sign engagement letter + DPA up front; deliverables are MIT-licensed to the client at handover. - **Stewardship (monthly retainer)** — once a Substrate is live, it needs ongoing care: new context as the business evolves, new model capabilities to integrate, occasional architecture revisions. Retainer includes scheduled audit milestones with independent technology partners. - **Bigger engagements** — Foundation (production rollout) and Federation (multi-business-unit) follow Proof when the proof works. We don't sell these cold. ## Operating principles - **Human-in-the-loop by default.** AI drafts; humans approve. Outboxes, not auto-send. We will not ship a Substrate that takes irreversible action without human sign-off. - **MCP-compatible.** Substrates expose Model Context Protocol endpoints so the buyer can plug in their preferred LLM client (Claude Desktop, custom agents, internal tools) without lock-in. - **Self-hosted.** Substrates run on the buyer's infrastructure. We build, document, and hand over the keys. We don't build a SaaS dependency. - **POPIA-aligned.** All engagements involving personal information are governed by a Data Processor Agreement with documented data residency, retention, and breach-notification obligations. ## Operator and entity - **Operator:** Charl le Roux, substrate designer and Deputy Information Officer for the operating entity. - **Entity (current):** Yield SPM (Pty) Ltd · Reg 2024/185151/07 · South Africa, trading as Context Design Co. - **Entity (future):** Context Design Co (Pty) Ltd will be incorporated when monthly recurring revenue passes the trigger threshold; Yield SPM remains the holding entity for the product portfolio. ## Contact - **General:** info@contextdesign.tech - **Engagements / proposals:** info@contextdesign.tech - **Legal / privacy queries:** legal@contextdesign.tech / privacy@contextdesign.tech - **Site:** https://contextdesign.tech ## Resources on this site - [Homepage](https://contextdesign.tech/) - [AI Implementation for South African Businesses — overview](https://contextdesign.tech/ai-implementation/) - [FAQ — cost, POPIA safety, hardware, ownership](https://contextdesign.tech/faq/) - [Key-Person Risk — succession & knowledge capture (essay)](https://contextdesign.tech/notes/key-person-risk) - [POPIA and Private AI (essay)](https://contextdesign.tech/notes/popia-and-private-ai) - [What Is a Private AI Brain? — definitional (essay)](https://contextdesign.tech/notes/what-is-a-private-ai-brain) - [AI Before You Sell — exit & succession readiness (essay)](https://contextdesign.tech/notes/ai-before-you-sell) - [Workflow Automation with a Human in the Loop (essay)](https://contextdesign.tech/notes/workflow-automation-with-a-human-in-the-loop) - [AI for Manufacturers in South Africa](https://contextdesign.tech/industries/manufacturers) - [AI for Distributors & Wholesalers in South Africa](https://contextdesign.tech/industries/distributors) - [Glossary — Substrate, Operational IP, BlitzBox & more, in plain English](https://contextdesign.tech/glossary/) - [Attesté — Operator Substrate (case study)](https://contextdesign.tech/notes/atteste-operator-substrate) - [Practacular — Practice Multiplier (case study)](https://contextdesign.tech/notes/practacular-practice-multiplier) - [Operational IP — asset page](https://contextdesign.tech/operational-ip) - [BlitzBox — overview](https://contextdesign.tech/blitzbox/) - [BlitzBox — Inside the box](https://contextdesign.tech/blitzbox/inside/) - [BlitzBox — Pricing](https://contextdesign.tech/blitzbox/pricing/) - [Operational IP, Now Capital — essay](https://contextdesign.tech/notes/operational-ip-now-capital) - [Privacy Policy](https://contextdesign.tech/privacy) - [Terms of Use](https://contextdesign.tech/terms)