Create Reusable Business and Meeting Context

Why this decision matters

The business profile says what the host offers, whom it fits, what proof is approved, what claims are prohibited, and which next steps are available. The meeting request contains only the current person or company identifiers, date, objective, known context, and selected private inputs. Versioning matters because offers and proof change. A run records the profile version it used so later reviewers can reconstruct the advice.

This lesson advances the same capstone used throughout the course: the Meeting Preparation and Follow-Up Agent Pack. The learner is not collecting ideas for later. The workbook record created here becomes an input to the next module and must be specific enough that another operator could review it. Where evidence is incomplete, the artifact should show the gap instead of smoothing it over.

Source evidence and limits

C7-S3 requires reusable seller context, approved proof, limitations, call type, and profile version. C7-S4 supplies workflow-first questions and anti-fit boundaries.

The sources support the operating method stated above. They do not prove universal performance, guaranteed savings, complete market coverage, causal impact, or a client result. Any date-sensitive product, platform, competitor, legal, pricing, or policy fact must be checked against a current primary source before publication or operational use.

Continuing fictional example

Example: Northstar Operations, Cedar Workshop, and operations lead Jordan Lee are fictional. The meeting concerns inconsistent enquiry handling.

Northstar's fictional profile says it offers process mapping and recommendations, with software implementation separately scoped. It has no approved numerical savings claim. Jordan's fictional request says enquiries arrive by form and phone and asks for more consistent follow-up.

Example boundary: The fixture contains no live person, address, email, profile, company, meeting, or customer result. Its source excerpts exist only to test the course method.

Workbook application

Use Workbook Section 2: Create Reusable Business and Meeting Context. Complete Workbook Section 2. Write the profile, supported proof, prohibited claims, anti-fit cases, next-step menu, meeting request, privacy classification, and profile version.

1. Write the current evidence or input before adding interpretation.
2. Apply the lesson's decision rule and state the reason for the classification.
3. Mark uncertainty, missing information, and the human owner for the next decision.
4. Check that the result stays inside the course boundaries and can be tested.

Failure modes to inspect

Copying a past prospect into stable context; inventing testimonials; putting private notes in public searches; failing to record profile version; and treating a seller claim as buyer evidence.

A polished output can still fail if its evidence, permissions, identity, denominator, source date, or action boundary is wrong. Review the underlying record rather than grading tone alone. The correct repair may be to narrow the scope, gather a permitted source, label an unknown, or stop the proposed action.

Decision rules

Stable context describes the host. Per-run context describes the meeting. Buyer statements remain attributed. Unsupported numerical proof is excluded.

Record the rule in the workbook in language two reviewers can apply consistently. A rule that depends on intuition alone cannot support a deterministic fixture. If reviewers disagree, preserve both readings, identify the missing evidence, and revise the rule before automation.

Three application checks