Meeting Follow-Up Pack
To Dana Ruiz and Sam Okafor (Brightline Logistics, prospective client), following Tuesday's call about a dashboard pilot for their Midwest region. Goal: recap the call, confirm the case study and pricing by Friday, and lock in the next call date.
1. Main Follow-Up Email
Subject line options:
- Follow-up: Midwest dashboard pilot call
- Next steps: case study, pricing and SOW call
- Great talking with you Tuesday, Dana and Sam
Hi Dana and Sam,
Thanks for walking me through how your ops team handles late delivery reporting on Tuesday. Hearing that it takes around 6 hours a week in manual spreadsheets made the case for a better setup very clear.
Quick recap of what we discussed:
- A dashboard pilot for your Midwest region, with a possible Q3 start
- Dana will review the pilot with your CFO for sign-off
- Sam's question about integrating data from your TMS [confirm system name], which I'm checking with our engineering team
Next steps
From me:
- A case study from a similar logistics client, by Friday, [date]
- A pricing breakdown for the pilot, by Friday, [date]
- An answer on TMS integration once I've spoken with engineering
- A draft SOW once you've reviewed the pricing
From you:
- Review the pricing and share any questions
- Confirm a time for our next call
We agreed to meet again in about two weeks to walk through the SOW. Would [option 1: day, date, time] or [option 2: day, date, time] work for you both? If neither suits, send me a time that does and I'll send an invite.
Looking forward to it.
Best regards,
Mark Chen
Account Manager
Fieldwork Analytics
2. Quick Recap Version
Hi Dana and Sam, thanks for Tuesday's call. As discussed, I'll send a logistics case study and a pilot pricing breakdown by Friday, [date], and I'm checking TMS integration with our engineering team. Once you've reviewed the pricing, I'll send a draft SOW for us to walk through in about two weeks. Would [option 1] or [option 2] work for that call? Thanks, Mark
3. Action Items Table
| # | Action | Owner | Due | Status |
|---|---|---|---|---|
| 1 | Send case study from a similar logistics client | Mark Chen | Friday [date] | Open |
| 2 | Send pricing breakdown for the pilot | Mark Chen | Friday [date] | Open |
| 3 | Check TMS (Oracle?) integration with engineering | Mark Chen / Priya | TBD | Open |
| 4 | Review pricing | Dana Ruiz / Sam Okafor | TBD | Open |
| 5 | Get CFO sign-off on the pilot | Dana Ruiz | TBD | Open |
| 6 | Send draft SOW after pricing review | Mark Chen | TBD | Open |
| 7 | Hold next call to walk through the SOW | All | About 2 weeks out, [date] | Open |
4. Internal Team Recap
Subject: Brightline Logistics – pilot call recap
Hi Priya (and team),
Quick recap of Tuesday's call with Dana Ruiz (Ops Director) and Sam Okafor (Ops Analyst) at Brightline Logistics.
- Pain point: late delivery reporting. Their ops team spends about 6 hrs/week on manual spreadsheets.
- Interest: a dashboard pilot for the Midwest region, possibly starting in Q3.
- Budget: around 10k for the pilot. Dana needs CFO sign-off (possibly Raj, not confirmed).
- Promised: case study and pricing breakdown by Friday. SOW draft after they review pricing.
Priya: Sam asked about integrating with their TMS (they think it's Oracle). Could you let me know what's feasible so I can reply before our next call in about two weeks?
Internal only: our pricing floor for this pilot is 8.5k. Please don't share it externally.
Thanks,
Mark
5. No-Reply Nudge
Send 3–4 business days after the pricing and case study go out if there's no reply.
Hi Dana and Sam,
Just checking you received the case study and pricing breakdown I sent on [date]. I'd like to get our SOW walkthrough on the calendar for around [target week]. Would [option 1] or [option 2] work? A one-line reply is plenty, and I'll send the invite.
Best,
Mark
6. Before You Send – Check These
- "Fri": confirm which Friday's date and fill in [date].
- Next call options: fill in [option 1] and [option 2]. The notes only say "~2 wks."
- TMS name: the notes say "Oracle?". I wrote "[confirm system name]" instead of naming it. Confirm before naming it, or say "your TMS."
- CFO name: "Raj?" is unconfirmed, so the external email just says "your CFO."
- Budget (~10k): left out of the external emails on purpose. Confirm the currency and decide whether you want it in writing. It is in the internal recap.
- Pricing floor (8.5k): this is internal only. It is not in any external email and is marked confidential in the internal recap.
- Q3 start: the notes say "maybe," so the email says "possible Q3 start." Confirm the year if needed.
- Integration: no promise is made. The email only says you're checking with engineering, so confirm Priya is the right person.
- Attachments: none are referred to as included. The case study and pricing will be sent separately by Friday.
- "6 hours a week": this is the customer's own figure from the call. Confirm you're comfortable repeating it back to them.
- Internal recap: decide whether it goes only to Priya or to a wider team.
Made by a Donkley AI worker. AI can make mistakes; please review before you rely on it.