← Blog··7 min read

Workflow teardown: from a 23-minute discovery call to a signed SOW

A step-by-step breakdown of how one consultant turned a single discovery call into a signed $45K statement of work in under an hour.

Last month I watched a consultant named Priya close a $45,000 engagement in under an hour — from discovery call to signed SOW. Not because she's superhuman, but because her workflow is ruthlessly efficient. Here's exactly how she did it.

The setup

Priya is an independent operations consultant. Her client, a Series B SaaS company, reached out about "fixing our onboarding — it's taking 6 weeks and customers are churning before they see value."

She booked a 30-minute discovery call. Here's what happened next.

12:00 PM — The discovery call

Priya runs the call with her standard discovery framework: current state, desired state, constraints, stakeholders, timeline, budget. She doesn't take detailed notes. She has Otter.ai recording and transcribing in real-time.

Key things she listens for:

  • Pain with numbers. Not just "onboarding is slow" but "average onboarding is 42 days, target is 14, and we're losing 23% of new customers before first value."
  • Who has authority. The VP of CS is on the call, but mentions the CEO wants this fixed by Q3.
  • Budget signals. "We budgeted for operational improvements this quarter" — that's a green light.

The call runs 23 minutes.

12:25 PM — Transcript to structured notes (2 minutes)

Priya copies the Otter.ai transcript — 4,200 words of messy, conversational text with crosstalk and tangents. She pastes it into Struq using the Meeting Synthesis template.

In 15 seconds, she has:

  • Key discussion points: Current onboarding flow (6 steps, 3 handoffs, no automation), churn data, CEO timeline pressure
  • Decisions: Client wants a phased approach, Phase 1 focused on reducing handoffs
  • Action items: Priya to send SOW by EOD, client to share current onboarding flow diagram and Mixpanel access

She reviews it in 30 seconds. Everything's accurate. She saves it.

12:28 PM — Discovery notes to SOW draft (3 minutes)

Now Priya opens a new Struq object with the SOW / Proposal template. But instead of starting from scratch, she takes the meeting synthesis output and pastes it along with a few bullet points she adds:

Meeting notes: [pastes synthesis]. Additional context: Phase 1 = reduce onboarding from 42 to 21 days. Eliminate 2 of 3 handoffs. Automate welcome sequence and checklist. Phase 2 = instrumentation and optimization. Budget range $40-60K discussed. Timeline: Phase 1 complete by end of Q2.

Struq extracts:

  • Project name: Onboarding Optimization — Phase 1
  • Client: [Company name from transcript]
  • Scope: Audit current onboarding flow, redesign to eliminate 2 handoffs, implement automated welcome sequence and progress checklist, establish baseline metrics
  • Deliverables: Onboarding audit report, redesigned flow diagram, automation specs, implementation support (4 weeks), measurement framework
  • Timeline: 8 weeks (2 weeks audit + design, 4 weeks implementation, 2 weeks measurement)
  • Investment: $45,000
  • Assumptions: Client provides Mixpanel access, dedicated PM for weekly syncs, engineering team available for automation implementation
  • Constraints: Must integrate with existing HubSpot workflows, no changes to pricing/packaging

12:32 PM — Review and refine (10 minutes)

Priya spends 10 minutes on what actually requires her expertise:

  1. Adjusting scope. The AI included "implementation support" — she changes this to "implementation oversight and QA" because she's not writing code, the client's engineering team is.
  2. Adding risk factors. She adds: "If Mixpanel data is insufficient, 1-week instrumentation sprint may be needed before audit."
  3. Pricing. She bumps from the $40K low end to $45K because the client's urgency (CEO wants it done by Q3) justifies it.
  4. Payment terms. 50% upfront, 25% at Phase 1 midpoint, 25% on completion.

12:42 PM — Export and send (5 minutes)

She exports the structured SOW as markdown, pastes it into her Google Docs SOW template (which has her branding, terms, and signature block), adjusts formatting for 2 minutes, and emails it.

Total elapsed time from call ending: 17 minutes.

1:45 PM — Signed

The VP of CS replies at 1:45 PM: "This looks great. I shared with [CEO] and we're good to go. Signing now."

Total time from first contact to signed $45K engagement: under 2 hours.

Why this works

Three things make Priya's workflow possible:

1. She doesn't take notes during calls. She's fully present, asking better questions and catching nuance. The transcript captures everything.

2. She uses structured templates, not blank documents. A blank Google Doc is an invitation to overthink. A structured template with defined fields is an invitation to fill in the blanks. The template does the organizing; she does the thinking.

3. She spends her time on judgment, not formatting. Of the 17 minutes between call and sent SOW, 10 were spent on strategic decisions (scope adjustments, pricing, risk factors). Only 7 were mechanical.

The math

  • Traditional approach: 23-min call + 45-min notes + 2-hour SOW draft + 30-min formatting = ~3.5 hours
  • Priya's approach: 23-min call + 17-min SOW = 40 minutes

That's not 5x faster. That's 5x faster while producing a better deliverable — because Priya spent proportionally more time on the strategic decisions that actually matter.

Try it yourself

The SOW / Proposal template and Meeting Synthesis template are both available on the free tier. Record your next discovery call, paste the transcript, and see how fast you can go from call to proposal.

Structure your content now

Paste your raw notes and get polished, structured output in seconds. No signup required to try.

Try Struq free