MYFRND × VOOV / NOVEMBER 13, 2026

Catch a Vibe, Part II: When AI Becomes the Workflow

The follow-up conversation moved beyond interesting prompts to repeatable actions, accountable owners, connected systems and results people can actually verify.

By Pooya Mohit · Leadership AI Training Follow-Up

THE VIBE ERA OF AI
From a clear brief to work that gets done. The sequel is about everything that happens after the prompt.

THE BIG SHIFT

The conversation is no longer “Can AI do this?”

When we reconvened with the VOOV leadership team on Friday, November 13, 2026, one thing was clear: the most meaningful AI wins are not isolated answers. They are the connected steps that turn a meeting, a client request or a routine process into completed and documented work.

Our first Catch a Vibe workshop explored the possibilities. This follow-up put working examples, implementation bottlenecks and human checkpoints under the microscope.

CARLOS RODRIGUEZ / MEETINGS → ASANA

One conversation. A full action plan.

Carlos described recording an authorized meeting, obtaining a transcript, using AI to summarize decisions and converting the results into Asana tasks with owners, descriptions and follow-ups. A meeting with 20 action items no longer has to mean 20 manual task entries.

Why it matters: meetings create commitments. A useful AI workflow captures who owns each commitment, what happens next and where the team can find it.

ATTENDEE-REPORTED TIME SAVINGS

30–40 min → under 5

Meeting follow-up and task preparation
Carlos described reducing a repetitive workflow to a few clicks and minutes, rather than manually assembling the next steps.

Individual participant estimate, not an independent performance benchmark.

INSIDE TODAY'S FOLLOW-UP

The team behind the workflows.

Our training connected colleagues across the VOOV team for a candid working session: real deployments, questions about trust, bottlenecks and what each department plans to build next.

Screenshot from the November 13, 2026 virtual meeting.

WORKFLOWS ALREADY TAKING SHAPE

The people, the process and the next handoff.

Each example illustrated a different level of maturity: some workflows are actively used, while others are pilots being refined. That distinction matters.

01 / CARLOS RODRIGUEZ

Make meetings actionable.

Record with permission → transcribe → summarize → assign in Asana. Carlos is continuing to save and test the reusable skill so meetings can produce clear owner-specific tasks rather than a transcript nobody revisits.

02 / MANUEL ORELLANA

Put an SOP behind the automation.

Manuel is building context-aware processes that distinguish an existing client from a brand-new one. Prior conversations, approved client data, point-of-contact rules and a request-for-clarification fail-safe help prevent an incorrect welcome email.

03 / GEMA MARTINEZ

Save, test, refine. Repeat.

Gema described reusable skills for daily task reviews, responsibility summaries and PTO tracking that consults calendar entries and updates the tracker. The operating rhythm matters as much as the first prompt: validate the skill, then improve it.

04 / BERTHA SANCHEZ

Connect the inbox to the calendar.

Bertha is bringing together calendar information, email follow-ups and team task status to surface priorities and next actions. The goal is less searching across tabs and more coordinated follow-through.

ONE PROMPT IS THE START / NOT THE FINISH

From a Mailchimp idea to an accountable campaign.

Carlos raised the possibility of creating a Mailchimp campaign directly from chat: choose the audience, develop the email and move it into the platform. We pushed the idea further. What if the same workflow also prepares the subject and preview text, includes approval points, plans the non-opener resend, records the campaign in Asana and a tracker, and briefs the relevant contacts?

That is the difference between generating an email and running an email workflow. The expanded flow below was a proposed design discussed in training, not a claim that every step was deployed or sent.

01 / PREPARE

Identify the approved audience, source material, objective and brand standards.

02 / BUILD

Write subject and preview text, compose the responsive email and prepare a review version.

03 / APPROVE

Check links, audience, sender, compliance and the exact campaign before sending.

04 / FOLLOW THROUGH

Schedule a permitted resend after the agreed number of days and stop on exceptions.

05 / DOCUMENT + NOTIFY

Update the tracker, create complete Asana tasks and email the POCs with actual send status.

Operating rule: a draft is not a send, a plan is not a scheduled campaign, and a scheduled campaign is not proof of delivery.

REAL SYSTEMS, REAL CONSTRAINTS

Finance workflows demand a different kind of confidence.

CELIA MCCOY / CONNECTED FINANCIAL TOOLS

Integrations are useful. Speed still has to be earned.

Celia shared how she is using Composio with a Grok-based bot to connect with financial and operating tools, including QuickBooks, Town Bank, Capital One, Google and RingCentral. She also offered an essential reality check: one seemingly simple workflow took much of a day to complete.

That is a performance problem to diagnose, not a reason to promise effortless automation. Model selection, tool permissions, secure-site restrictions and steps competing for resources can all affect the result.

JOSELIN AVENDANO / PAYROLL PILOT

Prepare the payroll. Protect the approval.

Joselin discussed the team’s plans to explore Claude for payroll review, identifying differences, preparing information and reducing manual entry. Batch-payment preparation is an area for testing, not an automatic authorization to transfer funds.

The team emphasized keeping a clear human review immediately before sensitive financial submissions and measuring whether the pilot actually saves time.

Manuel’s research tip: explore GitHub and community discussions for patterns other builders have already solved. Adapt them to your own security, permissions and approval requirements.

SERGIO TIFFER / THE NECESSARY COUNTERWEIGHT

AI can draft the work. People still own the judgment.

Sergio challenged the team to treat large language models as capable junior associates, not unquestionable decision-makers. Asking the same question twice can produce different answers. An articulate response is not proof that the facts, calculations or judgment are sound.

His message was especially relevant to financial analysis, client communications and any action with downstream consequences: use specific inputs, defined instructions, checkable outputs and the right review step. Hallucinations are possible, and quality control cannot be optional.

Ground the answer

Use approved documents, current records and exact instructions before asking for analysis.

Design the stop sign

Pause when the context is missing, a client category is unclear or an external action requires approval.

Verify the outcome

Check the actual task, sent message, published page or uploaded file—not merely the assistant’s assertion.

My addition during the session: a new AI conversation should never be assumed to know every instruction from an older one. Give it a reliable, reusable skill with the brand, process, sources, boundaries and expected output. Then improve that skill after each real test.

BRANDON M. / THE SKILLS QUESTION

One master workflow, or several micro-skills?

Brandon asked whether it is better to build small specialized bots or one all-in-one prompt. Both approaches can work. A parent workflow is useful for coordinating the complete job; smaller skills make recurring parts—such as source verification, formatting and approval—easier to test and update. The right structure depends on the tools, context and handoffs supported by the chosen platform.

EXAMPLE / REUSABLE ASSET

A white-label Gmail signature builder.

The workshop’s signature-builder prompt is a concrete illustration. Rather than asking AI to “make a nice email signature,” it defines the brand, the expert role, the recipients, the authoritative approved HTML, light/dark variants, responsive Gmail-safe tables, separate contact links and a complete installer package.

It also specifies what cannot change: people’s identities, contact details, individual links, original logos and compliance language. QA checks cover layout, links, accessibility, fallbacks and the actual installation process.

THE REUSABLE PATTERN

B.R.A.I.N.

Brand
Role
Audience
Instructions
Non-negotiables

Then use V.I.B.E. to visualize, identify, break down, execute and evaluate the connected work.

The complete white-label signature brief is an example of how to specify a workflow. It is not evidence that a signature package was built or installed during this follow-up.

COPY & ADAPT / FULL PROMPT TEMPLATE

The full HTML signature-builder prompt.

The sample below is the complete reusable white-label instruction set discussed during the training. It covers brand fidelity, responsive Gmail HTML, multiple people, light/dark themes, interactive installation, links, image hosting, required deliverables and quality assurance.

How to use it: expand the panel, select and copy the prompt, and supply your own approved source HTML and original brand assets. It is a specification for building the signature package, not a claim the package already exists.

Expand the complete White Label HTML Email Signature Builder prompt

# White Label HTML Email Signature Builder

ROLE: Expert email signature designer, brand identity specialist, and HTML email developer.

BRAND: Use the brand identity, logos, typography, colors, imagery, and contact information provided in the attached approved reference HTML and supporting assets. The solution must be fully adaptable to any company, industry, and number of individuals.

SOURCE OF TRUTH: Treat the attached final approved HTML file as the authoritative source for all existing visual elements, personnel identities, job titles, contact information, credentials, regulatory disclosures, logos, profile photographs, links, and compliance language.

Never invent, substitute, or interchange personal information, contact details, profile links, or regulatory identifiers between individuals.

## OBJECTIVE

Recreate every approved email signature variation from the source HTML while preserving brand fidelity, functional links, responsive behavior, and compatibility with Gmail.

Deliver a professional, reusable email signature package supporting multiple individuals and light/dark themes.

## DESIGN REQUIREMENTS

Reproduce the approved source as accurately as possible, including:

- Brand colors, typography, imagery, spacing, alignment, and proportions.
- Compact, responsive, three-column layout when applicable.
- Approved decorative rules, separators, borders, and padding.
- Circular profile photographs with approved borders or rings, linked to each individual's designated profile.
- Prominent individual names, job titles, professional identifiers, and contact information.
- Email, telephone, website, and social media icons with individually verified links.
- Approved company logo and primary call-to-action button.
- Footer branding, tagline, business address, and compliance disclosures.
- All approved light and dark theme variations.

Use the reference HTML for exact dimensions and styling. Where no explicit source specification exists, use these defaults unless they conflict with the approved design:

- Fluid 100% outer wrapper with a maximum width of 600px.
- Three-column proportions of approximately 21% / 51% / 28%.
- 4px top accent rule.
- Main content padding of approximately 18px / 15px / 15px.
- Profile photographs up to 108px, maintaining their original aspect ratio.
- 8px profile photo ring when applicable.
- Individual names at approximately 22px, bold.
- Primary logo up to 80px.
- Social media icons approximately 21px.
- Primary CTA approximately 128px wide, with rounded corners.
- Footer logo approximately 132px.

Do not introduce vertical dividers unless they are present in the approved reference.

Preserve portrait proportions, prevent unnecessary text wrapping, and ensure email addresses and website addresses remain readable at typical desktop widths.

## EMAIL HTML DEVELOPMENT

Build production-ready signature HTML using:

- Nested presentation tables.
- Inline CSS.
- Explicit image and table width attributes.
- Fluid layouts with controlled maximum widths.
- Email-safe fonts and fallback font stacks.
- Accessible image alt text.
- Legible color contrast.
- Properly linked contact information.
- Responsive behavior appropriate for desktop and mobile email clients.

Avoid relying on external stylesheets, JavaScript, unsupported CSS, or browser-specific rendering features inside the signature itself.

Do not redraw or approximate approved brand artwork when original assets are available.

## BRAND THEMES

Create light and dark themes using the brand's approved palette.

If the source does not specify separate theme colors, derive accessible light and dark variations from its established brand colors while preserving brand recognition.

Do not assume that email clients will automatically switch signature themes.

Each theme must be independently selectable and usable.

## INTERACTIVE INSTALLER

Create a browser-based installer featuring:

1. Individual selector supporting every approved person.
2. Light/Dark appearance selector.
3. Live signature preview.
4. Rich HTML Copy Signature functionality.
5. Plain-text clipboard fallback.
6. Select-and-copy fallback where rich clipboard support is unavailable.
7. Clear Gmail desktop installation instructions.
8. Guidance on selecting the appropriate theme.
9. Instructions for verifying a test email before deployment.

Keep all interactive controls, installer scripts, and interface styling outside the HTML copied into Gmail.

The installer should remain reusable when additional individuals or signature variations are added.

## REQUIRED DELIVERABLES

Produce:

1. A master browser-based HTML installer.
2. Standalone HTML signature files for every individual and theme combination.
3. High-resolution PNG previews of each variation.
4. A complete package containing original approved assets and source files.
5. A ZIP archive of the complete deliverable package.
6. A brief installation and troubleshooting guide.

Use descriptive, consistent filenames that identify the individual and theme.

## LINK AND CONTENT VERIFICATION

Validate every destination against the approved source, including:

- Email links (mailto:).
- Telephone links (tel:).
- Company websites.
- Individual profile pages.
- Social media profiles.
- Map/address destinations.
- Call-to-action and application links.
- Regulatory and compliance links.

Ensure every link belongs to the correct individual or organization.

Preserve all required licensing information, regulatory identifiers, disclosures, addresses, and compliance language exactly as provided.

Never fabricate credentials, license numbers, rates, professional titles, business information, or regulatory statements.

Flag missing, conflicting, or unverifiable information for review rather than filling gaps with assumptions.

## IMAGE HOSTING AND PRODUCTION DEPLOYMENT

Use the original approved image assets.

For production Gmail signatures, use the approved public HTTPS image URLs rather than relying solely on embedded image data, which may be stripped or mishandled by email clients.

Do not upload, publish, replace, or externally host brand assets without explicit authorization.

Identify any missing production image URLs and clearly distinguish between preview-ready and deployment-ready assets.

## QUALITY ASSURANCE

Before delivering:

- Compare all variations against the approved reference.
- Verify every person's details and links independently.
- Review light and dark themes.
- Test narrow viewport widths for clipping, overlap, distorted imagery, and unwanted wrapping.
- Validate the copied HTML independently of the installer interface.
- Confirm the functionality of the copy and fallback methods.
- Inspect contrast and accessibility.
- Check that compliance information remains complete and legible.
- Test a sent email in Gmail when an authorized sending workflow is available.

Do not promise pixel-identical rendering across every email client, operating system, or device.

## FINAL DELIVERY STANDARD

The final result must be visually faithful to the supplied brand references, technically dependable, easy for nontechnical users to install, and scalable across multiple employees or team members.

Priority order:

1. Accuracy of individual information and compliance.
2. Preservation of approved brand assets.
3. Functional links and compatibility.
4. Visual fidelity.
5. Responsive usability.
6. Ease of installation and future maintenance.

When the reference source is incomplete, preserve what is known, document what is missing, and never silently invent or replace approved information.

Select the prompt text to copy it. Replace the approved HTML reference and company assets for your own brand before running the workflow.

THE ASSIGNMENT / BRING SOMETHING REAL

Choose one departmental workflow. Then make it repeatable.

The team agreed to return with practical, multi-step workflows instead of hypothetical demos. The next session was discussed for approximately three to four weeks later; a firm date had not been confirmed.

1. MAP IT

Define the trigger, current manual steps, sources, systems, people and final deliverable.

2. PROTECT IT

Identify approvals, exceptions, client differences, access rules and fallback paths.

3. TEST IT

Build a draft version, compare the result with the manual process and record what failed or improved.

Workshop action items: Carlos will continue testing his meeting-to-Asana skill; Manuel will research reusable solutions; Joselin and Celia will investigate payroll and finance workflows; Gema will refine validated skills; Bertha will review calendar and inbox priorities; and the facilitators will coordinate the next session. Each participant is encouraged to prepare one documented workflow to share.

QUICK ANSWERS / AI WORKFLOW FAQ

A few things worth clarifying.

What is the difference between a prompt and an AI workflow?

A prompt specifies an instruction. A workflow defines the steps, approved sources, connected applications, decisions, review points and proof that the requested action actually happened.

Can AI turn meeting notes into Asana assignments?

Yes, when the relevant recording or transcript and Asana access are available. The workflow should identify owners, task details and deadlines from the source, flag unknowns and respect consent and privacy rules for recording.

Can ChatGPT create and send a Mailchimp campaign in one workflow?

Connected tools may support campaign creation, audience selection and approved send or scheduling actions. The exact abilities and account permissions must be verified. A prepared campaign is not automatically a sent one.

Should AI submit payroll or payments on its own?

The VOOV discussion favored using AI to review, compare and prepare financial information while keeping human verification and approval before consequential submissions. Secure-site and tool limitations must also be tested.

What makes a saved AI skill dependable?

A clear source of truth, explicit instructions, stable brand rules, exception handling, review points, tested integrations and feedback from repeated real use.

KEEP THE VIBE MOVING

Build one workflow that actually saves your team time.

Today’s best examples did not end with a clever response. They ended with a clearer owner, a checked result and a process worth doing again. Thank you to the VOOV team for the candid demonstrations, smart questions and practical follow-through.

Read the November 6 workshop recap · Explore the end-to-end content workflow

Written by Pooya Mohit for MYFRND. Recap based on the November 13, 2026 VOOV follow-up, participant reports and the Catch a Vibe workbook. Workflow examples reflect the stage and claims described by participants, not independently audited performance results.