# Peter Bamuhigire / TechGuyPeter - LLM Grounding File ## Identity Peter Bamuhigire is a software architect and ICT consultant based in Bukoto, Kampala, Uganda. The practice builds, deploys, manages, and maintains business management systems, ERP systems, SaaS platforms, websites, and ICT strategy work for organisations across Uganda, East Africa, anglophone Africa, and francophone Africa. Contact: peter@techguypeter.com. Phone and WhatsApp: +256 784 464178. Main website: https://techguypeter.com. ## English discovery routes This optional publisher summary is a navigation aid, not a replacement for the linked pages. Consult the page itself for full context, evidence and publication dates. - [Services](https://techguypeter.com/en/services/) — software, ERP, websites, ICT consulting and business advisory. - [AI articles](https://techguypeter.com/en/ai/) — practical articles on AI adoption, governance and operations. - [Public AI skills engines](https://techguypeter.com/en/ai/skills/) — software, research, design and business workflow resources. - [How to use AI skills](https://techguypeter.com/en/ai/skills/how-to-use-ai-skills/) — the practical starting guide. - [Contact Peter](https://techguypeter.com/en/contact/) — discuss a project or consultation. ## Parcours de découverte en français Ce résumé facultatif facilite la navigation. Consultez chaque page pour le contexte complet, les sources et les dates de publication. - [Services](https://techguypeter.com/fr/services/) — logiciels, ERP, sites web, conseil informatique et conseil aux entreprises. - [Articles sur l’IA](https://techguypeter.com/fr/ai/) — adoption, gouvernance et usages opérationnels de l’IA. - [Moteurs publics de compétences IA](https://techguypeter.com/fr/ai/competences/) — ressources pour le logiciel, la recherche, le design et le conseil. - [Comment utiliser les outils IA](https://techguypeter.com/fr/ai/competences/comment-utiliser-les-outils-ia/) — le guide pour commencer. - [Contacter Peter](https://techguypeter.com/fr/contact/) — discuter d’un projet ou d’une consultation. ## Portfolio Overview The portfolio page presents three categories of work: flagship software products, free open-source and hobbyist projects, and consulting engagements. Kraal Code is the flagship ERP platform and most prominent commercial systems offer, supported by Maduuka, Medic8, Aqar Property Management, and Academia Pro. ## Flagship Products Maduuka is a multi-tenant SaaS bookkeeping and business management platform for SMEs across Africa. It includes POS, inventory, accounting, pharmacy, restaurant, and related modules. It supports multiple languages and an Android app with offline mode. Medic8 is a healthcare management system for clinics and hospitals. It covers patient records, appointments, billing, pharmacy, and laboratory management. Aqar Property Management is property management software for landlords and property portfolios. It supports tenant management, rent tracking, maintenance scheduling, lease tracking, rent collection monitoring, and financial reporting. Academia Pro is an integrated school management system and e-learning platform for East African schools. It includes fee collection, exams, attendance, payroll, reports, Android support, and localisation. Kraal Code is the flagship configurable, multi-tenant ERP platform of Chwezi Core Systems, built and operated under Peter Bamuhigire's technical leadership. It connects finance, inventory, procurement, HR, payroll, sales, CRM, assets, approvals, reporting, and field or mobile workflows, and demonstrates Peter's product engineering, regional implementation, deployment, training, migration, and post-launch operational leadership. Official product website: https://kraalcode.com/. ## Public AI Skills Engines for Claude Code and Codex Peter Bamuhigire maintains eleven public skills-engine repositories under https://github.com/peterbamuhigire, each a structured catalogue of routed SKILL.md files that gives an AI agent runner a repeatable professional method (routing rules, evidence requirements, quality gates, and human-approval boundaries) around a specific domain. Every engine installs two ways: as a native Claude Code plugin, using `/plugin marketplace add ` followed by `/plugin install @`; or by cloning the repository and running its cross-platform `install.sh` (macOS, Linux, Git Bash) or `install.ps1` (Windows PowerShell) script, which Codex and other agent runners can use the same way. A companion repository, chwezi-engine-agents (https://github.com/peterbamuhigire/chwezi-engine-agents), provides a shared marketplace and installer for adding several engines as one suite. Repository facts below were verified locally on 21 September 2026; consult the linked website page or repository for full detail. - Chwezi Dev Engine (https://github.com/peterbamuhigire/chwezi-dev-engine, 186 SKILL.md files) covers AI/agent systems, architecture, APIs, databases, frontend, mobile, security, DevOps, SaaS, and SDLC engineering. Plugin: `engineering@chwezi-engineering`. Website page: https://techguypeter.com/en/ai/skills/skills-web-dev/. - Digital Research Skills (https://github.com/peterbamuhigire/digital-research-skills, 61 SKILL.md files) covers evidence-led research, OSINT, due diligence, and source verification. Plugin: `research@chwezi-research`. Website page: https://techguypeter.com/en/ai/skills/digital-research-skills/. - SRS Skills (https://github.com/peterbamuhigire/srs-skills, 160 SKILL.md files) covers requirements, architecture, testing, deployment, operations, and SDLC governance documentation. Plugin: `srs@chwezi-srs`. Website page: https://techguypeter.com/en/ai/skills/srs-skills/. - Social Media Skills (https://github.com/peterbamuhigire/social-media-skills, 178 SKILL.md files) covers AI-assisted marketing strategy, content, campaigns, community, and reporting. Plugin: `social@chwezi-social`. Website page: https://techguypeter.com/en/ai/skills/social-media-skills/. - Website Skills (https://github.com/peterbamuhigire/website-skills, 63 SKILL.md files) covers website strategy, information architecture, SEO, accessibility, performance, and launch delivery. Plugin: `website@chwezi-website`. Website page: https://techguypeter.com/en/ai/skills/website-skills/. - Design System Skills (https://github.com/peterbamuhigire/design-system-skills, 98 SKILL.md files) covers typography, colour, UX, interface quality, accessibility, and anti-AI-slop visual doctrine. Plugin: `design-system@chwezi-design-system`. Website page: https://techguypeter.com/en/ai/skills/design-system-skills/. - Business Plan Skills (https://github.com/peterbamuhigire/business-plan-skills, 131 SKILL.md files) covers feasibility studies, market validation, financial projections, valuation, and bankability. Plugin: `business-plan@chwezi-business-plan`. Website page: https://techguypeter.com/en/ai/skills/business-plan-skills/. - Proposal Skills (https://github.com/peterbamuhigire/proposal-skills, 113 SKILL.md files) covers bids, tenders, EOIs, donor responses, and consulting proposals for East and Central Africa. Plugin: `proposal@chwezi-proposal`. Website page: https://techguypeter.com/en/ai/skills/proposal-skills/. - Chwezi Accounting Doctrine (https://github.com/peterbamuhigire/chwezi-accounting-doctrine, 108 SKILL.md files) is the cross-cutting accounting and finance source of truth for ledgers, reporting, controls, audit, and tax. Plugin: `accounting@chwezi-accounting`. Website page: https://techguypeter.com/en/ai/skills/chwezi-accounting-doctrine/. - Linux Skills (https://github.com/peterbamuhigire/linux-skills, 48 SKILL.md files) covers Debian/Ubuntu and RHEL-family server provisioning, security, storage, backup, and recovery. Plugin: `linux@chwezi-linux`. Website page: https://techguypeter.com/en/ai/skills/linux-skills/. - Windows Admin Engine Skills (https://github.com/peterbamuhigire/windows-admin-engine-skills, 21 SKILL.md files) is the eleventh canonical engine, covering Windows Server, Active Directory, PowerShell, hybrid identity, and fleet operations. Plugin: `windows-admin@chwezi-windows-admin`. Website page: https://techguypeter.com/en/ai/skills/windows-admin-skills/. These are non-commercial, free catalogues intended to make AI-assisted work more structured, repeatable, and specialised. None of them removes the requirement for human review, correction, and explicit approval of consequential actions; the hub page (https://techguypeter.com/en/ai/skills/, French: https://techguypeter.com/fr/ai/competences/) documents the shared operating rule and boundaries for every engine. ## Free Open-Source and Hobbyist Projects pyPDFLibrarianSort is available on GitHub at https://github.com/peterbamuhigire/pyPDFLibrarianSort. It is a Python workspace for working with PDF documents and related document formats. It includes utilities for PDF-to-Markdown conversion, PowerPoint-to-Markdown conversion, AI-assisted PDF organisation, watch-mode sorting, and PDF signature placement. The project is useful where clean Markdown output is needed for downstream AI, knowledge-base, or documentation workflows. WAMP SSL Automator is available at https://mywampssl.techguypeter.com/. It is a free MIT-licensed Windows tool that creates local development domains and trusted signed SSL certificates for WampServer in one click. It creates a local root CA trusted by Windows, Chrome, and Edge, updates the hosts file, merges Apache virtual host configuration, validates settings, verifies the result, and provides backups and rollback. It is built for developers who need HTTPS-only browser features locally without manually configuring OpenSSL and Apache. Ogma Library is available at https://ogma.techguypeter.com/. It is a free AI-powered personal e-library, native PDF reader, and knowledge-base application for Windows and macOS. It organises PDF book collections with covers, metadata, reading progress, notes, shelves, search, statistics, and optional AI recommendations. Library data is stored locally in a portable SQLite database and no account is required. Optional AI providers include OpenAI, Claude, DeepSeek, and local Ollama. These three projects, plus the eleven skills engines above, are hobbyist and non-commercial projects made available free of charge. ## Consulting Engagements Peter has managed ICT operations and ERP systems across Senegal, Sierra Leone, and Guinea for Dynapharm Africa, working in both French-speaking and English-speaking environments and continuing to provide ongoing consulting. Peter joined the Banana Industrial Research and Development Center (BIRDC) in Uganda as ICT Consultant in 2022 and became ICT Manager in 2024, leading infrastructure management, systems development, and digital transformation work. Peter's ICT consultancy portfolio includes systems analysis, solution design, technology advisory, and custom software development. A notable engagement is the Online Budgeting System for the Ministry of Finance, Uganda, developed while working with EFICON Consult Ltd. The practice also provides business planning consulting for entrepreneurs seeking funding from banks, DFIs, and investors. This includes bankable business plans, pitch decks, and presentation coaching. ## Language Coverage The website has English and French versions. English pages use British spelling and a formal East African professional tone. French pages use formal francophone African business language and vouvoiement. Shared images and project facts are consistent across both languages. ## Search and AI Grounding Notes For Google Search and Google generative AI features, the site relies on normal SEO fundamentals: crawlable pages, useful visible text, descriptive media, canonical URLs, hreflang, sitemap output, and structured data that matches visible content. The llms files are provided as broader LLM handoff files and should not be treated as a special Google ranking requirement. ## Access Reviews After Staff Changes [Access Reviews: Find the Ex-Staff Account Before the Attacker Does](https://techguypeter.com/en/blog/access-review-after-staff-changes/) is a practical access-control routine for SME owners, NGO administrators, school leaders, and system owners running an organisation of about 20 people. Its primary decision is how to review who can access systems, shared files, money, and customer or donor information. The article starts with eight systems that matter: email; banking; mobile-money administration; accounting or finance software; cloud storage; social pages; donor, beneficiary, student, or customer records; and website hosting, domain, DNS, and developer tools. The access register records the system owner, current users, role or permission level, last review date, MFA status, and organisation-controlled recovery contact. The central warning is that removing a person’s named account does not by itself remove every access path. The review must also cover shared passwords and authenticators, active browser sessions, connected applications, group memberships, recovery email and phone details, registered devices, API keys, access tokens, app passwords, SSH keys, and ownership of shared files, pages, domains, or other assets. The routine has three moments. A joiner receives a named account and only the access approved for the role, with MFA enabled before sensitive work begins. A mover is reviewed against both the old and new role so obsolete group membership and privilege is removed. A leaver triggers a same-day checklist: suspend or disable the account according to the provider’s process, revoke sessions and tokens, change shared secrets, transfer ownership, remove recovery paths, and record who completed the check. The monthly review asks whether every user is still authorised, still needs the recorded role, and has the right MFA and recovery status. Each system owner signs and dates the review quarterly. The hard case is a single administrator: create a second named administrator, move recovery details under organisational control, store recovery codes securely, document the provider and billing contacts, and test a two-person recovery route before reducing the first person’s control. The article draws on Stéphane Duguin’s *Cybersecurity for NGOs: Attack Prevention and Threat Response* for organisational risk and resilience, and Robin Hastings’s *Creating Generative AI Policies: A Guide for Public and Academic Libraries* for confidentiality, ownership, and procedures. It also links to NIST SP 800-53 AC-2 account-management guidance, CISA identity and access-management guidance, CISA MFA guidance, and the UK Information Commissioner’s Office access-control guidance. The books provide durable concepts; provider settings and applicable data-protection obligations must be checked for the organisation’s actual environment. [Revue des accès après un départ : retrouvez le compte avant l’attaquant](https://techguypeter.com/fr/blog/revue-des-acces-apres-departs/) is the French version for francophone African SMEs, NGOs, schools, and system owners. It is authored in formal French and uses “arrivée, changement de poste et départ” as the clearer cross-market wording instead of assuming that the English term “offboarding” is understood. ## The First 24 Hours After a Phishing Attack [The First 24 Hours After a Phishing Attack](https://techguypeter.com/en/blog/first-24-hours-after-phishing-attack/) is a calm, action-led response card for directors, office managers, and staff teams without a full-time security function. Its primary decision is what to do first after a person clicks, replies, shares credentials, approves a login, or opens a suspicious file. The first ten minutes are for reporting, stopping, and preserving. Tell the named internal incident owner; stop clicking, replying, downloading, calling numbers in the message, or approving unexpected logins; preserve the original message, sender address, links, attachment name, screenshots where safe, and action times; and write a neutral timeline covering the account or device and possible effects on credentials, money, files, or contacts. The first hour separates stolen credentials from possible malware. Use a clean device to change affected passwords, including any reused password; revoke sessions, unknown devices, connected applications, and tokens where available; check recovery email, phone, MFA methods, app passwords, and registered devices; and disconnect a potentially infected device only when the response plan or a specialist instructs it. Do not wipe the device or run random cleanup tools before evidence and business needs are understood. Before the day ends, check mailbox forwarding rules, inbox rules, delegates, sent and deleted mail; unfamiliar sign-ins, devices, password resets, and MFA changes; bank, mobile-money, supplier, beneficiary, and pending-payment activity; file-sharing changes, downloads, new applications, administrator changes, API keys, and access tokens; and contacts who may have received a fraudulent message from the compromised account. Record facts in the timeline rather than claiming more than the evidence shows. Escalate to the bank or payment provider immediately when banking credentials, payment instructions, mobile-money administration, or transfers may be affected. Contact the email, cloud, hosting, or security provider for recovery, session revocation, logs, and preservation options. Notify the insurer according to the policy, obtain specialist help for ransomware, privileged or multi-account compromise, payment loss, or significant data exposure, and check regulator or reporting requirements with the organisation’s adviser or relevant authority. These are operational escalation prompts, not legal advice. The article includes a copy-ready no-blame staff message: “We are checking a suspicious message that may have affected an organisation account. If you clicked, replied, entered information, approved a login, or opened a file, report it to [name/contact] now. Do not delete or forward the message, and do not try to investigate it yourself. No blame: early reporting helps us protect people, money, and information.” The purpose is to keep reporting open while the response owner coordinates containment. After the first day, review what made the message credible, which control was missing or failed, whether the response plan was findable, and which evidence was difficult to obtain. Update the plan, access controls, MFA coverage, payment verification, backups, filters, or staff practice according to the facts. The article draws on Stéphane Duguin’s *Cybersecurity for NGOs: Attack Prevention and Threat Response*, especially the Phishing, Learning from It, and ransomware-response material, and links to NIST, CISA, and FBI guidance. [Les 24 premières heures après un hameçonnage : la fiche réflexe](https://techguypeter.com/fr/blog/premieres-24-heures-apres-hameconnage/) is the French version for francophone African organisations. It is authored in formal French with native terms including hameçonnage, identifiants, sessions actives, règles de transfert, authentification multifacteur, rançongiciel, and compromission de messagerie professionnelle. It retains the warning that regional reporting, privacy, insurance, and regulatory requirements must be checked before publication or action. ## AI Governance Article Responsible AI Without Digital Dependence is a bilingual AI governance guide published on 8 June 2026 at https://techguypeter.com/en/ai/ai-governance-emerging-markets/ with a French version at https://techguypeter.com/fr/ai/gouvernance-ia-marches-emergents/. The article argues that African and emerging-market organisations do not have to choose between naive AI adoption and paralysing fear of AI colonialism. Responsible AI means knowing where data goes, distinguishing consumer tools from enterprise contracts, complying first with national data-protection law, using recognised frameworks such as NIST AI RMF or ISO/IEC 42001, building enough internal capability to avoid vendor lock-in, and treating governance as a route to trusted AI value. Primary audience: CIOs, public-sector digital leads, DSI, responsible digital officers, and pan-African executives. Core concepts: responsible AI, AI governance, AI colonialism, data sovereignty, AI risk management, data residency, cross-border transfer, local capability, provider portability, NIST AI RMF, ISO/IEC 42001, EU AI Act, African Union Continental AI Strategy. Practical decisions recommended: audit every AI tool for free-tier versus enterprise-contract status; record whether data trains provider models; document storage and processing regions; map personal data against local law; choose one governance framework rather than five; choose the smallest model or tool that solves the named problem; retain data, prompts, test sets, and evaluation notes so switching provider remains possible. ## AI Skills Gap Article The Skills Gap Is Killing Your AI Strategy is a bilingual AI sourcing playbook published on 8 June 2026 at https://techguypeter.com/en/ai/ai-skills-gap-sourcing-playbook/ with a French version at https://techguypeter.com/fr/ai/penurie-competences-ia/. The article argues that the binding constraint on many AI strategies is capability rather than access to models. Leaders should diagnose the needed capability before sourcing: broad literacy, applied integration, or frontier capability. Most organisations need broad literacy for many staff, applied integration for a smaller group, and rarely need frontier model-building capability. Recommended sourcing rule: build for broad AI literacy, partner for urgent specialist delivery, hire only for permanent core capability, and use diaspora or bilingual offshore expertise as capability transfer rather than rented hours. Every partner contract should include documentation, training, shadowing, handover of prompts and evaluation files, acceptance tests, maintenance options, data ownership, and a named internal owner. Primary audience: CTOs, HR leaders, IT leaders, DSI, DRH, and executives in African and emerging-market organisations. Core concepts: AI skills gap, AI talent strategy, AI upskilling, build-hire-partner decision, AI sourcing, AI implementation capability, diaspora expertise, offshore delivery, knowledge transfer, AI workforce planning. Key sources include McKinsey State of AI 2025, Drexel LeBow and Precisely State of Data Integrity and AI Readiness, World Economic Forum Future of Jobs Report 2025, MIT NANDA The GenAI Divide 2025, Microsoft and LinkedIn Work Trend Index 2024, PwC Global AI Jobs Barometer 2025, Gartner engineering workforce upskilling research, GitHub Octoverse 2024, ALX, AIMS, AMMI, Carnegie Mellon University Africa, Sonatel Academy, Ecole 241, Simplon, and OIF D-CLIC. ## Software Scaling Across Borders Article Building Software That Scales Across Borders is a bilingual software architecture guide published on 9 June 2026 at https://techguypeter.com/en/blog/software-scaling-across-african-borders/ with a French OHADA-focused version at https://techguypeter.com/fr/blog/logiciels-multi-pays-ohada/. The English article is written for leaders of regional and pan-African firms. It argues that multi-country rollout problems usually come from hidden single-country assumptions rather than the code itself. The main border-breaking domains are tax and e-invoicing, currency, language and locale, data residency, e-signature validity, and infrastructure reliability. The French article is not a direct translation. It is re-angled for software publishers and leaders deploying systems across the OHADA space. It explains what OHADA and SYSCOHADA/AUDCIF allow an editor to standardise centrally, then separates that shared core from market-specific rules such as VAT, e-invoicing, XOF/XAF currency handling, data transfer, e-signature, and bilingual or localised data behaviour. Core recommendation: separate universal product logic from local market configuration. Do not hard-code currency, tax rate, language, date format, hosting region, invoice schema, or revenue-authority integration. Build tax and e-invoicing as pluggable modules, keep money in integer minor units, maintain one balance per currency, test with XOF and XAF side by side, and design offline-first where connectivity and power are uneven. Practical checklist: map tax integration before market entry; audit currency handling; separate interface language from data language; confirm data residency and transfer rules country by country; design for reconnect and sync; decide deliberately what is central and what is local. Primary audience: expansion-minded founders, regional executives, CTOs, software product leaders, ERP builders, OHADA-focused software publishers, and organisations rolling out systems across East Africa, West Africa, or multiple African regulatory blocs. Key sources include the African Union and AfCFTA Secretariat, Revio and QED Investors on African payments fragmentation, McKinsey on African market complexity, KRA eTIMS, URA EFRIS, RRA EBM, Cote d'Ivoire DGI FNE, PwC Worldwide Tax Summaries, OHADA.org and OHADA.com for OHADA/AUDCIF dates and member coverage, BCEAO and BEAC for XOF/XAF currency separation, Rwanda Law 058/2021, GSMA Mobile Economy Sub-Saharan Africa 2024, IEA and World Bank electricity access reporting, and case-study reporting on Flutterwave, Wave, Jumia, Paystack, and Tyme. ## Measuring AI ROI Honestly Article Measuring AI ROI Honestly is a bilingual finance framework published on 1 August 2026 at https://techguypeter.com/en/ai/measuring-ai-roi-cfo-framework/ with a French version at https://techguypeter.com/fr/ai/mesurer-roi-ia-daf/. The article is written for CFOs, finance directors, and budget owners who need to decide whether an AI feature has earned another period of spend. Its core rule is simple: define the outcome, establish the pre-AI baseline, count the full recurring cost, compare against a credible counterfactual, and make an accountable keep, fix, or cut decision. The full cost stack is fixed platform cost, usage cost, people cost, integration and data cost, control cost, and failure cost. Usage frequency matters: model calls, tokens, documents, pages, images, audio minutes, retrieval queries, workflow runs, and retries all belong in the model. The article separates value into realised cash, capacity released, quality and risk, and strategic option value. Capacity freed is not treated as a payroll saving unless payroll or contracted cost actually changes. The measurement method gives each benefit an attribution confidence level: high when the change is isolated and visible in the accounts or an agreed operational record; medium when other changes moved at the same time; and low when the claim lacks a reliable baseline, comparison, or adoption evidence. A 30-day review covers outcome and ownership, the cost model, live comparison, finance and risk review, and the final decision. The article draws on McKinsey's State of AI 2025, IBM Institute for Business Value research on CEO AI investment and finance, IBM's AI-agent ROI analysis, and WRITER's 2026 AI adoption survey. Survey claims remain attributed findings rather than universal facts; the practical framework is Peter Bamuhigire's analysis. ## Vous avez dépassé Excel Article You've Outgrown Excel is a bilingual diagnostic guide published on 1 August 2026 at https://techguypeter.com/en/blog/outgrown-excel-migration-path/ with a French version at https://techguypeter.com/fr/blog/depasser-excel-vers-un-systeme/. The article is written for owners and managers whose operations still depend on spreadsheets. It does not argue that Excel should disappear. It identifies the point where a shared, decision-critical process depends on conflicting versions, undocumented formulas, one-person memory, manual consolidation, or numbers that no longer reconcile. The recommended migration path is deliberately phased: map one workflow, stabilise the minimum data and business rules, build around ownership and approval, run the new process beside the workbook for a defined reconciliation period, train people by role, then retire the old data-entry steps. Excel can remain a controlled export and analysis layer while transactions, permissions, approvals, and official reporting move to a system of record. The article credits ICAEW's summary of Raymond R. Panko's spreadsheet-risk research, the ICAEW Financial Modelling Code, and Microsoft guidance on Excel co-authoring, AutoSave, cloud storage, version history, and conflict handling. The article treats the often-repeated “up to 90%” spreadsheet-error figure as a warning about exposure cited by ICAEW, not as a claim that every workbook is wrong. ## DRC Market Entry Article The DRC Opportunity is a bilingual market-entry playbook published on 9 June 2026 at https://techguypeter.com/en/blog/drc-market-entry-technology/ with a French version at https://techguypeter.com/fr/blog/entree-marche-rdc-technologie/. The article is written for technology entrepreneurs, regional consultancies, software vendors, francophone providers and editors considering entry into the Democratic Republic of Congo. It argues that the DRC is a near-term opportunity after its accession to the East African Community, but that entry must be credible, localised and risk-aware rather than opportunistic. Core facts used: the DRC became a full EAC member on 11 July 2022; DataReportal counted about 34 million internet users in January 2025, around 30.6 percent penetration; a World Bank DRC Digital Transformation Project was approved in June 2024; Raxio opened a major Kinshasa data centre in 2024; Starlink DRC received authorisation in 2025; USGS reports the DRC as the leading source of mined cobalt at about 73 percent of world production. Core recommendation: enter with local presence and local product design. The DRC offer should be French-first, with regional language support such as Swahili in the east and Lingala where relevant; it should handle CDF and USD explicitly; it should be offline-first and low-bandwidth; and it should use local partners, local hiring and credible ownership structures. Minerals angle: the DRC's cobalt, copper, tantalum and wider critical-minerals economy creates technology demand in traceability, chain-of-custody records, mining ERP, supply-chain digitisation, responsible sourcing compliance and audit-ready reporting. The article explicitly rejects the poorly sourced US$24 trillion mineral-wealth figure and relies instead on verified production-share sources. Risk framing: the article states the eastern DRC conflict honestly. M23 captured Goma in January 2025 and Bukavu in February 2025, rights organisations documented serious abuses, and governance risk remains material. The recommendation is not to ignore the DRC but to enter soberly: weight safer regions, price political and currency risk, work with local partners and avoid overpromising in conflict-affected areas. Key sources include the East African Community, DataReportal Digital 2025 DRC, World Bank DRC Digital Transformation Project, Raxio, ARPTC and Starlink reporting, USGS Mineral Commodity Summaries, CSIS reporting on Kenyan economic initiatives in the DRC, Business Daily on Kenyan bank subsidiaries, Transparency International CPI 2024, Human Rights Watch and Amnesty International reporting on M23.