Meeting 2 — Langrand: Operations, finance, and business development
Opening + Natalie's hard-costs rundown
7 min · 0:00 – 0:07
The intake gave us the rate side of the economics ($200–$250/hr blended Brand, "higher for Innovation") and the top-time-consuming surfaces (proposals, content, meetings, internal ops) — but only the people-time half of the picture. The hard-cost ledger (production, vendor / contractor passthroughs, software subscriptions, media spend) is an open gap, and finance is the right place to source it. This anchors the rest of M2 by giving us the cost framework to map Section 1's Hive utilization probe and Section 2's RFP-vs-proposal economics against.
- Quick orient: Langrand asked us to focus on Brand for the exercise, M2 leans on ops / finance / biz-dev, today's session is the operating economics behind delivery.
- Natalie — when Langrand delivers a typical Brand-division engagement, what's in the hard-cost ledger beyond people-time? Production, vendor / contractor passthroughs, software and subscriptions, talent, media spend? (probe — new ground; intake confirmed top_hours but not the cost mix)
- How does that hard-cost shape differ across service lines — does a paid-media campaign carry meaningfully different cost weight than a PR program or a web build? (probe — services framing)
- And on the Innovation/Transformation side — quick contrast: how is the cost shape different? (probe — firm_notes / blended_rate_other; not the audit's focus substantively, but in-scope for orienting)
Section 1 — Hive: time, utilization, and the gaps
16 min · 0:07 – 0:23
Hive is the central PM and time-tracking rail for Brand, owned by Sarafina Riskind, and it shows up at multiple steps in the campaign-development walkthrough (project request, resource request, billing flow). The intake confirmed the tool but not the data quality, entry discipline, or what utilization analysis Langrand actually runs from it — until we know whether Hive data is trustworthy and where the gaps are, anything sized on time / utilization is shaky.
Ask Sarafina to screen-share Hive directly — actual utilization views, a recent time-entry compliance report, and any place where the data is patchy or actively worked around — so we see the gaps firsthand rather than hearing them described.
- Walk us through how a typical week of time entry happens in Hive — who enters when, is it daily / weekly / end-of-month, and what does compliance look like across the team? (probe — tool_time_other)
- When you look at Hive utilization data, what do you trust and what do you not? Where are the known gaps — categories of work that don't get captured, people who don't enter cleanly, client structures that don't fit Hive's model? (carry-forward: user-asked "where are the gaps")
- What can you not do with Hive today that you wish you could? Is there a shadow spreadsheet running somewhere because Hive can't deliver it? (probe — surfaces latent ops needs)
- How does Hive connect (or not) to QuickBooks for billing on one side and to HubSpot on the other — anything automated, anything manual? (probe — surfaces integration friction)
Section 2 — New business: proposals, RFPs, and the HubSpot funnel
16 min · 0:23 – 0:39
The intake named RFPs as the structural bottleneck, distinguished from proposals which "typically go smoothly." HubSpot is both CRM and lead tracking on one platform, owned by Natalie Vuckovic, but the intake confirmed only the tool — not the process or whether it's trusted. This section needs to land RFP unit-economics (analogous to media reporting decks in Meeting 1) and a clear picture of how HubSpot connects upstream and downstream.
Ask Natalie to screen-share the HubSpot pipeline view alongside one recent proposal and one recent RFP (the actual working files) so we see the deal flow and the proposal artifacts side-by-side — surfaces where the funnel breaks faster than describing it.
- Take one recent standard proposal and one recent RFP and walk us through each end-to-end. Where do they diverge — in who's involved, in the surfaces the work moves across, in where the time goes? (probe — proposal_bottleneck / proposal_time)
- Roughly how many RFPs per quarter? Average hour-cost on an RFP vs. on a standard proposal? Hit rate on each? (carry-forward: RFP cadence and effort)
- Sensitive-adjacentOn RFPs specifically — the intake mentioned senior-strategist availability tends to compress against the deadline, with "a lot of cooks in the kitchen." Structurally, where does that bite hardest — in scoping, in writing, in review? Frame system-level, not person-specific. (carry-forward: roadblocks.md → RFP senior-contributor timing)
- How do leads get into HubSpot today — manual entry, form submissions, both? What does the pipeline look like stage by stage, and who moves deals through it? (probe — tool_crm / tool_leads)
- Is HubSpot the source of truth for what's in the funnel, or is there a parallel spreadsheet or doc that leadership actually trusts for forecasting? (probe — surfaces shadow-system risk)
Section 3 — Scope, staffing, and account transitions
16 min · 0:39 – 0:55
Two Sensitive-adjacent patterns from the intake live here — the role-based-overstaffing critique and (touched lightly) the senior-strategist availability concern. Knowledge transfer wasn't addressed in the intake at all, but the intake did confirm knowledge lives across Dropbox, Slack/Teams, Hive, and email simultaneously — which is exactly where transitions break. Both pattern-clusters need system-level framing.
- Scope creep — does it show up on the same engagement types repeatedly, with specific client structures, on certain work surfaces (creative, media, PR)? How often per quarter does an engagement noticeably blow past scope? (probe — bottlenecks)
- Sensitive-adjacentThe intake noted role-based engagements can lead to overstaffing. Where is that most concrete — at the proposal phase (work gets scoped to a full team that doesn't all stay essential), in active engagements (people remain on a project past their contribution window), or both? (carry-forward: roadblocks.md → staffing-model critique)
- When an account transitions — someone leaves, a new lead steps in, an internal reorg — what actually transfers, and what gets lost? How often does this happen? (probe — fully new ground)
- Walk us through how a new lead gets up to speed on an existing account. Is there a handoff packet, a working session with the outgoing person, both, neither? Where do they have to dig — Hive, Dropbox, Slack threads, the previous lead's inbox? (probe — surfaces knowledge-transfer gaps)
Wrap
5 min · 0:55 – 1:00
- Anything we didn't ask that you wanted us to hear about?
- Meeting 3 — confirm date and the right attendee mix for the closing meeting.
- Quick reset on anything from Meeting 1 that bleeds into M3.
Coverage appendix
Sections rely on (rather than re-ask) the following prior-touchpoint findings:
- Section 1: Hive as the central PM + time-tracking system; Sarafina Riskind as owner; Hive's role across multiple campaign-flow steps (project request, resource request, billing). [analysis.md finding #11; intake form, tool_pm_other / tool_time_other / tool_pm_owner / time_walkthrough]
- Section 2: The proposal-vs-RFP distinction ("typically go smoothly" vs. "a lot of cooks in the kitchen"); the senior-contributor-timing pattern on RFPs; "more than two days" baseline proposal effort; HubSpot as combined CRM / lead-tracking tool owned by Natalie Vuckovic. [analysis.md finding #4; intake form, proposal_bottleneck / proposal_time / tool_crm / tool_leads / tool_crm_owner]
- Section 3: The role-based-overstaffing critique; the structured bottleneck list (client feedback, reviews, scheduling, unclear briefs, context-switching); the Dropbox + Slack/Teams + Hive + email knowledge-location set. [intake form, hand_off / bottlenecks / knowledge_location]
Covered in Meeting 1
- Campaign workflow walkthrough, lead-strategist / AD pairing, brief translation friction
- Media reporting decks — 7-people / multiple-days hand-off candidate
- Brand voice across industries; AI-adopted use cases for content
Sensitive handling reminder
Two Sensitive-adjacent items live in this meeting — RFP senior-contributor timing (Section 2) and the role-based-overstaffing critique (Section 3). Both were openly raised by Langrand in the intake form, but both must be framed system-level (process design, not individual performance) in the meeting itself and in any downstream rendering.