2026-03-30_weekly-kick-off-update

Internal (CSO notes)

Sources used

• Linear: Team GlobalVetLink (GLO). list_issues (50, by updatedAt), list_projects with milestones (no projects returned).
• Transcripts (last 7 days, 2026-03-23–2026-03-30): None under knowledge/clients/globalvetlink/transcripts/; none in knowledge/clients/unassigned/transcripts/ naming GlobalVetLink. Supplementary (outside window): knowledge/clients/globalvetlink/transcripts/2026-03-21_globalvetlink_figjam_workflow_working_session.md; prior client-facing draft knowledge/clients/globalvetlink/meeting-notes/2026-03-23_weekly-kick-off-update.md.
• Slack: Slack MCP slack_search_public_and_private, query in:client-globalvetlink after:2026-03-23. Supabase MCP: not configured in this environment.
• Key links (from prior draft / context): FigJam / Figma project, GDrive folder, Data Platform Documentation sheet.

Recommendations

• Client block: Do not paste internal Slack re renewal bonus, Eden deck, or “pitch without sales.” Keep the update to delivery: tracking plan, Pendo alignment, funnel view, and scheduling review with Kat.
• Tool recommendation: Greg’s Slack noted a recommendation toward Amplitude; keep client wording at “tool recommendation one-pager” until the review call unless you want to preview the direction in email.
• Contract / scope: Internal thread said the modeled workflow may meet delivery without extra instrumentation; if you say that to the client, use their words (certificate creation + properties for type) and confirm with legal/commercial before sending.

Gaps

• Linear issue states are stale (last updates mostly mid-March); board does not reflect the latest Slack status (PM answers, near-final tracking plan).
• No transcript capture for the PM milestone confirmation meeting Greg mentioned in Slack.
• Pendo access and demo role status unknown from this pull; carry forward if still open.

---

Date: 2026-03-30
To: Kat Gillis and GlobalVetLink stakeholders (cc as you prefer)
From: Gregory Stoutenburg, Brainforge
Subject: GlobalVetLink — Weekly kick-off update (product analytics design sprint)

Summary

We closed the loop with your PM on the remaining milestone questions, finished a first-pass event tracking plan aligned to the FigJam model (certificate creation as one workflow with certificate type carried in properties), and built a primary-workflow funnel view in Pendo so you can see the shape of activation reporting before we finalize the written spec and tool recommendation. This week we want to schedule a review with you early in the week, incorporate any last tweaks, and hand over the Workstream 1 package for sign-off.

Timeline / Milestones

• Design sprint (Workstream 1): Draft tracking plan + violation/trim view + tool recommendation + strategy summary per SOW; client sign-off gating optional Workstream 2. (No dated milestones returned from Linear projects API.)

Last week’s achievements

Event data design & strategy

• PM sync: Confirmed open items on customer milestones so the tracking plan matches how you actually ship value (not generic checkout assumptions).
• Event tracking plan (draft): Turned the FigJam agreement into a concrete plan: shared steps across certificate flows, metadata for certificate type, and room for Smart Engine measurement notes where Pendo allows.
• Pendo: Added a funnel chart for the primary workflow so stakeholders can preview reporting before implementation decisions.

Program

• Kept shared artifacts in the usual places (GDrive folder, Data Platform Documentation sheet).

This week’s focus

Event data design & strategy

• Review session with you (Kat): Walk through the draft tracking plan, Pendo mapping / trim list, and funnel logic; lock any final product nuances.
• Deliverables package: Finalize master tracking plan, tool recommendation one-pager, and data strategy deck / discovery summary for Workstream 1 sign-off path.
• Light HubSpot framing: Keep instrumentation notes aligned with your automation roadmap without expanding implementation scope in this sprint.

Blockers

Access (if still unresolved)

• Pendo: Stable access for the shared analytics identity so audit and charts stay accurate.
• Demo / roles: If the full payment or signing path still cannot be exercised under the current demo role, we may need a short paired session or a permission tweak to ground-truth licensure and billing edges.

Action items

Owner	Action	Due
Brainforge	Send meeting invite for Kat review (tracking plan + recommendations); finalize Workstream 1 written deliverables after feedback	This week
GlobalVetLink (Kat)	Review draft package; confirm Pendo access for globalvetLink@brainforge.ai if not already done	This week
GlobalVetLink (Kat)	If needed: demo role adjustment or 30 min working session for payment/signing validation	As needed

Questions or discussion topics

1. After you see the funnel and event list, do you want activation story to lead with time-to-first-signed-cert, license validated, or first billing-related activity (knowing segments differ)?
2. For Smart Engine, should reporting prioritize compliance risk (submissions without checks), UX friction (why people turn it off), or both in one view?

Next sync

Proposed: Review call with Kat early this week (times to follow in thread or invite).

Channel: Shared Slack or email; we monitor globalvetLink@brainforge.ai.