Workflows

type Workflow = {
  category: "Discovery";
  steps: 5;
}

1. Record the call with an approved notetaker (e.g. Fathom, Granola).
2. Paste the transcript into your AI tool with the 'deal summary' prompt.
3. Ask it to list every assumption not stated by the customer.
4. Fix gaps, then generate a 5-bullet brief for your AE and a follow-up email draft.
5. Log the brief in CRM and set next-step dates.

type Workflow = {
  category: "Discovery";
  steps: 5;
}

1. Collect the company's site, latest 10-K or press releases and the attendees' LinkedIn roles.
2. Prompt: summarize business model, likely priorities, recent changes.
3. Generate 10 discovery questions ranked by importance.
4. Flag 3 'not a fit' signals to watch for.
5. Save it as a one-page call plan.

type Workflow = {
  category: "Demo prep";
  steps: 5;
}

1. List the top 3 pains from discovery.
2. Prompt the demo-story template to map pain → feature → outcome.
3. Generate fake but realistic demo data as CSV and load it into your sandbox.
4. Run the 'pre-mortem my demo' prompt as the skeptical buyer.
5. Record a 3-minute Loom of the flow for async stakeholders.

type Workflow = {
  category: "POC";
  steps: 5;
}

1. Draft the scope with the POC prompt (objective, criteria, timeline, owners).
2. Pressure-test each success criterion for measurability.
3. Review with the champion; agree on pass/fail before kickoff.
4. Turn the timeline into a shared checklist with dates.
5. Send a recap email confirming criteria in writing.

type Workflow = {
  category: "POC";
  steps: 5;
}

1. Pick one narrow task and collect 20–50 real example inputs (with permission).
2. Build the first version with an agent framework (e.g. LangGraph, OpenAI Agents SDK).
3. Write expected outputs and run them through an eval tool (e.g. promptfoo, DeepEval).
4. Trace failures with an observability tool (e.g. Langfuse, LangSmith).
5. Report pass rate against the agreed criteria, not vibes.

type Workflow = {
  category: "Security";
  steps: 5;
}

1. Gather your approved security docs (SOC 2 summary, DPA, architecture).
2. Prompt the AI to answer only from those docs and mark gaps NEEDS REVIEW.
3. Route NEEDS REVIEW items to security/legal owners.
4. Store final answers in your RFP tool (e.g. Loopio, Responsive) for reuse.
5. Track turnaround time per questionnaire.

type Workflow = {
  category: "Implementation";
  steps: 5;
}

1. Reproduce the issue and capture logs, request/response and environment.
2. Paste logs into the triage prompt for ranked root causes.
3. Test the top hypothesis with Postman or a small script.
4. Document the fix as a runbook entry.
5. Share a plain-English summary with the customer.

type Workflow = {
  category: "Implementation";
  steps: 5;
}

1. Feed scope, team size and success criteria into the 30-60-90 prompt.
2. Generate a risk register and add customer-specific risks.
3. Assign customer-side owners for every dependency.
4. Review in the kickoff meeting and get explicit agreement.
5. Turn milestones into weekly status-update headings.

type Workflow = {
  category: "Stakeholders";
  steps: 5;
}

1. Keep a running notes doc per customer during the week.
2. Friday: paste notes into the status prompt (RAG status, done, next, blockers).
3. Check every owner and date is real.
4. Send it and pin it in the shared channel.
5. Escalate any red item with the escalation prompt the same day.

type Workflow = {
  category: "Implementation";
  steps: 5;
}

1. Export the relevant thread(s).
2. Prompt the AI to produce a numbered runbook with checks and rollback.
3. Follow the runbook yourself once on a test environment.
4. Fix steps that fail, then publish to your wiki.
5. Link the runbook in future tickets.

type Workflow = {
  category: "Stakeholders";
  steps: 5;
}

1. After win/loss, paste notes into the debrief prompt.
2. Extract product gaps with customer quotes you actually heard.
3. Group gaps by theme and deal size.
4. Share with product monthly in a single doc.
5. Track which gaps ship and tell the customer.

type Workflow = {
  category: "Stakeholders";
  steps: 5;
}

1. Export usage metrics and outcomes for the period.
2. Prompt the EBR outline using only the provided numbers.
3. Add one customer story and one adoption gap.
4. Propose a specific expansion next step.
5. Rehearse with the champion before the exec meeting.