Meetings Retention Strategy for Legal Tech Using PASTOR

# Meetings Retention Strategy for Legal Tech Using PASTOR **Category:** Productivity → Meetings | **Audience:** Professionals or practitioners using AI for meetings tasks. | **Delivery:** User-specified channel or workflow **Job:** Improve the named business/performance outcome using a measurable, testable intervention. ## SOURCE INPUT Use this source brief as the authoritative task/scenario. Preserve its supplied numbers, constraints, assets, frameworks and requested deliverables. Separate facts from assumptions; never invent missing evidence. > Treat this as the authoritative source brief. Preserve useful specifics; do not invent facts or turn scenario values into verified claims. > > > Act as Senior Meetings Strategist for Productivity (experienced, scaled Legal Tech to 8-figures, experienced technology/product background, generated substantial commercial experience with this system). CONTEXT: Business: Legal Tech - $5M ARR, team 16, targeting B2B founders, stage Seed Current: CAC $99, LTV $2511, churn 8%, traffic 10513/mo, conversion 3.3% Assets: Next.js codebase + Stripe Goal: boost retention 85% in 30 days Constraint: Budget $8k/mo, no-code only Tone: bold contrarian Hormozi FRAMEWORK: PASTOR + structured 4-step. TASK: Complete Meetings system for Productivity / Legal Tech. - common failure modes about meetings for Legal Tech - 5 Whys root cause for boost retention 85% - Hidden cost of failure - Contrarian insight advanced practitioner insight ## Workflow experiment variants > Variant A — SPEED: Optimize the workflow for minimum time and friction. > Variant B — QUALITY: Optimize the workflow for completeness, review and error prevention. > Variant C — SCALE: Optimize the workflow for repeatability, delegation and automation. > Specify steps, inputs, outputs, bottleneck, trade-off and success metric for each. ## EXECUTION Use this category-native workflow: **Desired outcome → current friction → priority → workflow → execution → time/effort controls → review** 1. Identify the key decision/outcome. 2. Use the supplied constraints and diagnose the real problem. 3. Produce the requested result with concrete actions, calculations, examples or decision rules as appropriate. 4. If inputs conflict or are insufficient, flag the issue and state the smallest validation needed. ## OUTPUT Return an immediately usable result, not a description of your process. Include material assumptions and a clear recommendation/next action when relevant. ## QA Check: workflow reduces real friction, steps are feasible, priority is clear, time/effort tradeoffs are explicit, result is actionable. Avoid generic advice, unsupported claims, impossible requirements and unnecessary verbosity. ## CONTROLLED VARIANTS Use variants only as real experiments; never as paraphrases. **A — Speed:** minimize time-to-completion. Preserve core identity/facts. Define the hypothesis, changed variable, expected effect and decision criterion. **B — Quality:** maximize reliability/output quality. Preserve core identity/facts. Define the hypothesis, changed variable, expected effect and decision criterion. **C — Scale:** make the workflow reusable/delegable. Preserve core identity/facts. Define the hypothesis, changed variable, expected effect and decision criterion. ## FINAL GATE Before answering, ask: Is this specific to the supplied scenario? Is every important instruction actionable? Are assumptions labeled? Is the output genuinely usable? Would a professional get a better result from this than from a generic prompt? If not, revise the weakest part before delivering.