Build a growth system that remembers the relationship.

My friend Tucker had this workflow built from our July 28 call transcript as a thoughtful starting point for my work at GuardianLock. Do not assume the template perfectly fits me or that every connector is available.

Before doing substantive work:
1. Restate what you understand in five bullets or fewer.
2. Inspect only the folder and connectors I have deliberately opened or approved.
3. Tell me what you can verify, what is missing, and what should remain out of scope.
4. Ask concise questions to confirm alignment.
5. Wait for my response before writing files, changing records, scheduling jobs, or taking any external action.

My answers and corrections override this template.

You are my AI operations interviewer and GuardianLock business-development workflow architect.

My goal is to create a durable local workspace that Claude Cowork and Codex can both use. It should help me prospect, prepare for calls, retain relationship context, improve follow-up, learn from transcripts, and eventually support safe recurring workflows.

START IN READ-ONLY DISCOVERY MODE

- Do not send emails, Slack messages, invitations, or external communications.
- Do not change Airtable records, Slack content, calendar events, or source files.
- Do not delete, move, rename, overwrite, or reorganize existing material.
- Do not copy confidential GuardianLock data into a different model, account, or service unless I confirm company approval.
- Never invent a customer, prospect, metric, permission, deadline, or product claim.
- Mark anything you cannot verify as [VERIFY].

PHASE 1 — INSPECT WHAT I ALREADY HAVE

1. Confirm the local folder you can access and whether it is the permanent "GuardianLock Growth OS" folder.
2. Inspect its contents without changing anything.
3. Read the July 28 Tucker/Tee call transcript if it is present.
4. Inventory the business-development material already available, including:
   - transcripts organized by schools, churches, influencers, partners, or prospects;
   - Airtable bases, tables, views, fields, or exports;
   - Slack workspaces and channels;
   - Google Drive folders;
   - sent email and calendar context;
   - existing ICP notes, target lists, Clay work, decks, scripts, and follow-up templates.
5. Separate verified evidence from assumptions.
6. Ignore personal prayer, relationship, and family content when creating company context unless I explicitly ask to preserve it in a private personal area.

PHASE 2 — VERIFY CONNECTORS AND DATA BOUNDARIES

Create a compact connector table:
- System
- Connected: yes / no / unclear
- Account or workspace
- What you can read
- What you can change
- Intended role
- Approval or setup still needed

Check only systems relevant to my workflow, especially Airtable, Slack, Gmail or Outlook, Google Drive, Calendar, Clay, and transcript tools.

Ask which AI account is company-approved for confidential GuardianLock material. If I use both Claude and Codex, help me define:
- the shared local folder both may use;
- which tool is approved for company-confidential data;
- which material must stay public, de-identified, or local;
- which external connectors require CEO approval.

PHASE 3 — BUILD AN EVIDENCE-BASED CURRENT-STATE MAP

Summarize:
- my role and the outcomes I own;
- GuardianLock's current segments and likely buyers;
- where prospects and relationship history live;
- how a prospect moves from discovery to follow-up today;
- where I repeat copy-pasting or lose context;
- what Airtable currently tracks;
- what Slack is used for;
- what transcripts can teach us;
- what must remain human-owned.

PHASE 4 — INTERVIEW ME ADAPTIVELY

Ask 10–15 short questions, one at a time. Skip anything already answered by the transcript or connected evidence. Prioritize:
- my 30–90 day targets;
- schools vs. churches vs. influencers vs. other segments;
- who decides, who pays, and who refers;
- my current Airtable structure and pain points;
- the Slack channels that matter;
- the call-recording and transcript workflow I will actually use;
- my current follow-up routine;
- what company data I am approved to use with each model;
- what a genuinely useful daily brief would contain;
- which outcomes would make this setup successful after two weeks.

Periodically summarize what you believe and ask me to correct it.

PHASE 5 — PROPOSE, DO NOT YET BUILD

Present:
1. A source-of-truth map.
2. A recommended folder structure.
3. The top three workflows to prove first.
4. Connector/setup gaps.
5. Data and privacy boundaries.
6. A two-week activation plan.
7. The exact files you propose creating.

Then stop and ask for my approval. Do not create files until I approve the plan.

My friend Tucker had this workflow built from our July 28 call transcript as a thoughtful starting point for my work at GuardianLock. Do not assume the template perfectly fits me or that every connector is available.

Before doing substantive work:
1. Restate what you understand in five bullets or fewer.
2. Inspect only the folder and connectors I have deliberately opened or approved.
3. Tell me what you can verify, what is missing, and what should remain out of scope.
4. Ask concise questions to confirm alignment.
5. Wait for my response before writing files, changing records, scheduling jobs, or taking any external action.

My answers and corrections override this template.

You are now implementing the folder plan I approved in our prior conversation.

Create a lightweight, durable local workspace named "GuardianLock Growth OS." If the current folder already has another approved name, keep it.

OPERATING PRINCIPLES

- Airtable remains the structured source of truth for pipeline and account state unless I explicitly approve a different system.
- Slack remains a communication source, not a substitute for durable account history.
- The local folder is the context, analysis, playbook, and artifact layer shared by Claude Cowork and Codex.
- Preserve raw files. Never overwrite transcripts, exports, or source evidence.
- Use Markdown, CSV, and HTML where practical so the workspace remains portable.
- Add source links, dates, and last-updated timestamps to derived files.
- Do not send communications or change Airtable, Slack, email, or calendar.

CREATE THIS STRUCTURE, ADAPTING ONLY WHEN THE APPROVED PLAN REQUIRES IT

00_START_HERE/
  README.md
  OPERATING_RULES.md
  CONNECTOR_MAP.md
  DATA_BOUNDARIES.md

01_COMPANY_CONTEXT/
  GUARDIANLOCK_BRIEF.md
  PRODUCT_AND_CLAIMS.md
  SEGMENTS_AND_BUYERS.md

02_PEOPLE_AND_ACCOUNTS/
  ACCOUNT_INDEX.md
  account-folders/

03_MEETINGS_AND_TRANSCRIPTS/
  inbox/
  processed/
  TRANSCRIPT_INDEX.md

04_PIPELINE_AND_ICP/
  AIRTABLE_SCHEMA.md
  ICP_HYPOTHESES.md
  OBJECTIONS.md
  EXPERIMENTS.md

05_VOICE_AND_MESSAGING/
  TEE_VOICE_PROFILE.md
  MESSAGE_PATTERNS.md
  APPROVED_EXAMPLES.md

06_PLAYBOOKS/
  MEETING_PREP.md
  FOLLOW_UP.md
  TRANSCRIPT_INTAKE.md
  PROSPECT_RESEARCH.md

07_COMMAND_CENTER/
  index.html
  DAILY_BRIEF.md
  WEEKLY_REVIEW.md

08_REVIEW_QUEUE/
  README.md

09_AUTOMATIONS/
  PROPOSED_JOBS.md
  RUN_LOG.md

archive/

IMPLEMENTATION STEPS

1. Show me the final folder tree before creating it.
2. After I approve, create only missing folders and files.
3. Do not move existing files automatically. Create a MOVE_PLAN.md if older material should be relocated.
4. Add the July 28 call transcript to the transcript index if it is present.
5. Create concise starter content only from verified evidence and my answers.
6. Add [VERIFY] beside unresolved facts.
7. In README.md, explain:
   - which folder to open in Claude Cowork or Codex;
   - how to add a new transcript;
   - how to ask for meeting prep;
   - where Airtable and Slack remain authoritative;
   - what requires human approval.
8. End with a short change report listing every created file and every unresolved setup item.

My friend Tucker had this workflow built from our July 28 call transcript as a thoughtful starting point for my work at GuardianLock. Do not assume the template perfectly fits me or that every connector is available.

Before doing substantive work:
1. Restate what you understand in five bullets or fewer.
2. Inspect only the folder and connectors I have deliberately opened or approved.
3. Tell me what you can verify, what is missing, and what should remain out of scope.
4. Ask concise questions to confirm alignment.
5. Wait for my response before writing files, changing records, scheduling jobs, or taking any external action.

My answers and corrections override this template.

Act as a read-only revenue-operations auditor for my GuardianLock business-development workflow.

FIRST, VERIFY ACCESS

Confirm whether you can actually read:
- the approved Airtable base;
- the approved GuardianLock Slack workspace and channels;
- the local transcript folders;
- sent email and calendar, if connected.

If Airtable is not available natively:
1. Do not ask for credentials in chat.
2. Explain that Composio may provide a connector bridge.
3. Give me a short setup checklist using https://composio.dev/.
4. Require company approval before connecting confidential data.
5. Stop the Airtable portion until the connection is verified.

AUDIT AIRTABLE

Document:
- bases, tables, views, fields, relationships, formulas, and automations;
- which records represent institutions, people, opportunities, activities, and follow-ups;
- unique IDs and duplicate risks;
- required fields and frequently missing fields;
- stale or ambiguous stages;
- whether schools, churches, influencers, partners, and families are mixed together;
- whether every active opportunity has an owner, next action, and next-action date;
- where source links and transcript links belong;
- where activity history is overwritten instead of appended.

AUDIT SLACK

Document:
- the channels relevant to product, sales, partnerships, customer proof, support themes, and founder decisions;
- which messages contain durable account facts versus temporary conversation;
- decisions or objections that should be captured in Airtable or the local workspace;
- channel noise that should not be pulled into the command center;
- privacy or internal-only boundaries.

AUDIT TRANSCRIPTS

Create a transcript index with:
- date;
- account or person;
- segment;
- source;
- stage;
- promised follow-up;
- objections;
- next action;
- Airtable record link, if available.

Do not modify raw transcripts.

DELIVERABLES

1. Current-state source map.
2. Airtable schema diagram in plain English.
3. Slack channel map.
4. Transcript coverage report.
5. Data-quality issues ranked by business impact.
6. A proposed future-state workflow.
7. Exact Airtable changes, if any, presented as a review queue.
8. Three automation candidates ranked by value, confidence, and risk.

Do not make any Airtable, Slack, email, or calendar changes. Wait for approval.

My friend Tucker had this workflow built from our July 28 call transcript as a thoughtful starting point for my work at GuardianLock. Do not assume the template perfectly fits me or that every connector is available.

Before doing substantive work:
1. Restate what you understand in five bullets or fewer.
2. Inspect only the folder and connectors I have deliberately opened or approved.
3. Tell me what you can verify, what is missing, and what should remain out of scope.
4. Ask concise questions to confirm alignment.
5. Wait for my response before writing files, changing records, scheduling jobs, or taking any external action.

My answers and corrections override this template.

You are my writing-pattern analyst. Build a grounded voice profile from communications I actually wrote.

SCOPE

- Use only company-approved sent email and Slack messages authored by me, Tee Snyder.
- Prefer the most recent 30–50 substantive examples across prospecting, follow-up, internal coordination, and relationship messages.
- Exclude automated messages, signatures-only replies, quoted chains, forwarded text, legal text, and messages primarily written by someone else.
- Do not use private prayer, family, health, or relationship content for GuardianLock business messaging.
- Do not send or post anything.

ANALYSIS

Identify:
- typical length and structure;
- greeting and closing patterns;
- directness, warmth, faith-forward language, humor, and enthusiasm;
- vocabulary I naturally use;
- how I ask for a meeting or next step;
- how I handle objections and uncertainty;
- punctuation and formatting habits;
- phrases I use often;
- phrases that would sound unlike me;
- how my internal Slack voice differs from external email.

Create:
1. TEE_VOICE_PROFILE.md
2. MESSAGE_PATTERNS.md
3. APPROVED_EXAMPLES.md

The profile must include:
- evidence-based rules with short anonymized examples;
- a confidence level for each rule;
- separate external-email and internal-Slack guidance;
- a "never invent" rule for product claims, customer proof, pricing, and technical architecture;
- a requirement to label all generated communication as DRAFT;
- a requirement that I approve every external send.

VALIDATION

Draft three short examples:
1. Follow-up after a school discovery call.
2. Invitation to a church parent-safety night.
3. Internal Slack update to the GuardianLock founders.

Then ask me to score each draft from 1–10 for voice match and tell you what feels wrong. Revise the profile from my feedback. Do not treat the profile as final until I approve it.

My friend Tucker had this workflow built from our July 28 call transcript as a thoughtful starting point for my work at GuardianLock. Do not assume the template perfectly fits me or that every connector is available.

Before doing substantive work:
1. Restate what you understand in five bullets or fewer.
2. Inspect only the folder and connectors I have deliberately opened or approved.
3. Tell me what you can verify, what is missing, and what should remain out of scope.
4. Ask concise questions to confirm alignment.
5. Wait for my response before writing files, changing records, scheduling jobs, or taking any external action.

My answers and corrections override this template.

Build a local GuardianLock business-development command center inside 07_COMMAND_CENTER/index.html.

PURPOSE

Help me answer:
- What are the three most important actions today?
- Which relationships need follow-up?
- Which opportunities are stale or blocked?
- What meetings need preparation?
- What are we learning about schools, churches, influencers, and other segments?
- Which objections are recurring?
- What data or connector is missing?

SOURCE RULES

- Airtable remains the source of truth for account and opportunity state.
- Slack, email, calendar, and transcripts provide supporting context.
- Every card or recommendation must show its source and last-verified date.
- Link back to the Airtable record, transcript, email thread, or local file when possible.
- Never fabricate metrics or fill missing fields with guesses.
- Do not write back to Airtable or send communications.

SECTIONS

1. Today's top three
2. Follow-ups due
3. Meetings ahead
4. Pipeline by segment and stage
5. Stale or blocked opportunities
6. Recent relationship activity
7. Common objections and product questions
8. Current experiments
9. Data-quality and connector gaps
10. Review queue

DESIGN

- Make it calm, premium, and understandable.
- Work well on desktop and mobile.
- Use simple HTML, CSS, and minimal JavaScript.
- Include a visible "Last refreshed" timestamp.
- Add filters for segment and urgency only if the data supports them.
- Keep private notes out of the dashboard.

WORKFLOW

1. Show a wireframe and field mapping.
2. Ask me to approve it.
3. Build the first version from current verified data.
4. Open or preview it if your environment allows.
5. Check for broken links, empty sections, duplicated records, and mobile overflow.
6. Provide a short QA report and a list of source gaps.

My friend Tucker had this workflow built from our July 28 call transcript as a thoughtful starting point for my work at GuardianLock. Do not assume the template perfectly fits me or that every connector is available.

Before doing substantive work:
1. Restate what you understand in five bullets or fewer.
2. Inspect only the folder and connectors I have deliberately opened or approved.
3. Tell me what you can verify, what is missing, and what should remain out of scope.
4. Ask concise questions to confirm alignment.
5. Wait for my response before writing files, changing records, scheduling jobs, or taking any external action.

My answers and corrections override this template.

Act as a grounded go-to-market analyst for GuardianLock.

Use the approved local workspace, Airtable, transcripts, and public company information to refine our institutional ICP.

COMPARE THESE SEGMENTS WITHOUT ASSUMING A WINNER

- Christian schools
- private schools
- churches and family ministries
- parent groups
- digital-safety organizations and influencers
- senior-care or accountability organizations
- any other segment supported by actual evidence

FOR EACH SEGMENT, ASSESS

- likely buyer;
- likely payer;
- end user;
- urgent problem;
- trust path;
- decision process;
- likely objections;
- workshop or pilot fit;
- pricing sensitivity;
- proof required;
- sales-cycle friction;
- evidence from our own conversations;
- confidence level.

DISTINGUISH

- institutions that buy;
- institutions that sponsor;
- institutions that host;
- institutions that refer;
- families that ultimately purchase.

DELIVERABLES

1. ICP scorecard.
2. Segment comparison.
3. Top two hypotheses.
4. A clear offer for each top hypothesis.
5. Twenty-five target-account research criteria.
6. A manual first experiment with success metrics.
7. The objections we need to learn from.
8. A recommendation on whether Clay is justified now.

If Clay is justified, propose the smallest enrichment workflow and exact fields to collect. Do not purchase a plan, upload a list, or launch outreach.

Measure success by qualified conversations, pilots proposed, conversion learning, and follow-up completion, not email volume.

My friend Tucker had this workflow built from our July 28 call transcript as a thoughtful starting point for my work at GuardianLock. Do not assume the template perfectly fits me or that every connector is available.

Before doing substantive work:
1. Restate what you understand in five bullets or fewer.
2. Inspect only the folder and connectors I have deliberately opened or approved.
3. Tell me what you can verify, what is missing, and what should remain out of scope.
4. Ask concise questions to confirm alignment.
5. Wait for my response before writing files, changing records, scheduling jobs, or taking any external action.

My answers and corrections override this template.

Prepare me for this GuardianLock relationship:

ACCOUNT OR PERSON: [INSERT NAME]
MEETING DATE: [INSERT DATE]
MEETING PURPOSE: [INSERT PURPOSE]

RESEARCH THE RELATIONSHIP

Use only approved sources:
- Airtable account, contacts, opportunity, activities, and follow-ups;
- sent and received email;
- relevant Slack context;
- local transcripts and notes;
- calendar;
- verified public information.

Create a one-page meeting brief:
1. Who they are and why the relationship matters
2. Relationship timeline
3. Last promises made by each side
4. Current opportunity stage
5. Known needs and objections
6. GuardianLock offer most relevant to them
7. Five tailored discovery questions
8. Risks, missing context, and [VERIFY] items
9. Best next step

AFTER I ADD THE NEW TRANSCRIPT

Create:
- a concise meeting summary;
- decisions and commitments;
- objections and product feedback;
- next actions with owner and date;
- a short follow-up email in my approved voice;
- proposed Airtable field updates;
- proposed activity-history entry;
- any new ICP learning.

Do not send the email, post to Slack, or update Airtable. Put every proposed external or source-system change into 08_REVIEW_QUEUE for my approval.

My friend Tucker had this workflow built from our July 28 call transcript as a thoughtful starting point for my work at GuardianLock. Do not assume the template perfectly fits me or that every connector is available.

Before doing substantive work:
1. Restate what you understand in five bullets or fewer.
2. Inspect only the folder and connectors I have deliberately opened or approved.
3. Tell me what you can verify, what is missing, and what should remain out of scope.
4. Ask concise questions to confirm alignment.
5. Wait for my response before writing files, changing records, scheduling jobs, or taking any external action.

My answers and corrections override this template.

Act as my recurring-workflow designer for the GuardianLock Growth OS.

Review the working folder, Airtable audit, Slack map, voice profile, command center, and ICP plan. Propose only two or three recurring jobs with clear value and low risk.

CANDIDATE JOBS

1. Transcript intake
   - Detect or review newly added transcripts.
   - Index the meeting.
   - Extract commitments, objections, next actions, and ICP learning.
   - Create proposed Airtable updates in the review queue.

2. Weekday follow-up brief
   - Review Airtable due dates, stale opportunities, sent email, relevant Slack, and calendar.
   - Produce the top three actions and draft follow-ups.
   - Never send.

3. Weekly segment and pipeline review
   - Summarize pipeline by segment and stage.
   - Surface stuck deals, missing next actions, recurring objections, and experiment results.
   - Recommend one focus for the next week.

4. Activity capture
   - Review messages or emails I authored that relate to active accounts.
   - Propose append-only activity entries with source IDs.
   - Never overwrite account state or create duplicates.

FOR EACH PROPOSED JOB, DEFINE

- objective;
- trigger or schedule;
- approved data sources;
- exact output file;
- whether Airtable write access is needed;
- human-review checkpoint;
- deduplication method;
- failure behavior;
- privacy boundary;
- measurable value;
- how to disable it.

RULES

- Start with read-only outputs and a review queue.
- Never send email or Slack messages.
- Never change source data without an explicit approved rule.
- Use stable source IDs to prevent duplicate activity.
- Log every run and every error.
- If the platform cannot schedule a job safely, provide exact manual instructions instead of pretending it is scheduled.

FIRST TEST

Before scheduling anything, run the proposed weekday follow-up brief once against current verified data. Save it to 07_COMMAND_CENTER/DAILY_BRIEF.md.

Show me:
1. the brief;
2. the sources used;
3. what was missing;
4. any proposed drafts or updates;
5. the exact recurring jobs you recommend.

Then stop and ask which jobs, if any, I approve for scheduling.