Lesson 1Entity: Company/Account — key fields with data types and reasons (company name, domain, industry, size, billing address, account owner, etc.)This section defines the Company or Account entity for agencies in Zimbabwe, outlining key identification, grouping, and ownership fields, plus address and billing data that support area planning, invoicing, and long-term account management.
Core identity fields and uniqueness rulesDomain, website, and enrichment optionsIndustry, size, and firmographic tagsBilling and shipping address modellingAccount ownership and territory logicParent child and group account structuresLesson 2Normalisation vs denormalisation trade-offs for performance and reportingThis section analyses normalisation and denormalisation strategies in CRM, explaining how to design tables and fields for speed, reporting, and connections while avoiding duplication, inconsistency, and unnecessary complexity in Zimbabwean setups.
Normalisation goals and normal formsCommon denormalisation techniquesPerformance impacts and indexingReporting and analytics trade offsIntegration and data sync concernsGuidelines for pragmatic modellingLesson 3Entity: Activity/Interaction — key fields with data types and reasons (type, subject, date/time, outcome, related entity, notes, duration)This section explains the Activity or Interaction entity, defining key fields, data types, and reasons that capture emails, calls, meetings, and tasks, ensuring a complete engagement history across leads, contacts, and opportunities in local contexts.
Activity types and controlled vocabulariesSubject, description, and note takingDate, time, and time zone handlingOutcomes, statuses, and follow up rulesLinking activities to related CRM recordsDuration, effort, and productivity metricsLesson 4Entity: Contact — key fields with data types and reasons (first/last name, email, phone, role, linked account, preferred contact method, etc.)This section defines the Contact entity, covering personal and professional fields, communication preferences, and links to accounts and opportunities, enabling precise targeting, personalisation, and relationship tracking in Zimbabwe.
Identity fields and name formattingEmail, phone, and channel detailsJob role, seniority, and influencePreferred contact times and methodsLinking contacts to accountsContact roles on deals and projectsLesson 5Entity: Opportunity — key fields with data types and reasons (name, value, currency, stage, close date, probability, product/service type, sales owner)This section details the Opportunity entity for software agencies in Zimbabwe, covering essential fields, recommended data types, and design reasons that support forecasting, pipeline visibility, revenue attribution, and consistent sales reporting.
Core identification fields and naming rulesMonetary fields, currency, and exchange handlingStage modelling and sales process alignmentClose date, probability, and forecasting logicProduct or service classification structuresOwnership, teams, and access controlLesson 6Entity: Lead — key fields with data types and reasons (source, status, score, created date, owner, etc.)This section focuses on the Lead entity, detailing fields, data types, and reasons for capturing new prospects, tracking source and status, scoring intent, and preparing clean conversion into contacts, accounts, and opportunities locally.
Lead capture fields and validation rulesSource, campaign, and attribution dataLead status, stages, and SLA policiesScoring models and intent indicatorsOwnership, routing, and assignmentConversion mapping to core entitiesLesson 7Entity relationship patterns and cardinality (one-to-many, many-to-many via junction table, polymorphic activities)This section covers CRM relationship patterns, including one to many, many to many via junction entities, and polymorphic activities, explaining when to use each pattern and how they affect reporting, automation, and data integrity in Zimbabwe.
One to many relationships and ownershipMany to many via junction entitiesModelling contact roles on opportunitiesPolymorphic activity relationshipsLookup versus master detail choicesImpact on reporting and rollup fieldsLesson 8Overview of canonical CRM entities and purpose (Lead, Contact, Account/Company, Opportunity, Activity/Interaction)This section introduces canonical CRM entities used in software agencies in Zimbabwe, clarifying the distinct purpose of Leads, Contacts, Accounts or Companies, Opportunities, and Activities, and how they work together in the revenue lifecycle.
Lead versus Contact distinctionsAccount or Company core purposeOpportunity as revenue containerActivity as engagement historyTypical lifecycle from lead to clientCross entity data flow and handoffsLesson 9Entity extension points: custom fields, picklists, formula fields, calculated fieldsThis section explores entity extension options, including custom fields, picklists, formulas, and calculated fields, showing how to add agency specific data while preserving usability, performance, and upgrade safe configurations in local systems.
When to add custom fields and whyDesigning picklists and option setsFormula and calculated field patternsUsing rollup and summary calculationsManaging technical debt in metadataGovernance, naming, and documentation
