Home / Conversations / pv-conv-

Conversation Details

CompletedConstruction ops managerWarm · OnlineSession ID · pv-sessi

Session report

Solid warm follow-up — Mark mirrored adoption fear and offered a five-seat pilot. The miss was leaving the next step as email instead of booking the foremen review on the call.

-0.2 vs. last sessionClosing

Trainee

marks.berzins@northwind-digital.example

Session

Aug 28, 2026

02:00 PM · 8m 0s

Messages

4 rep · 4 AI buyer

Performance evaluation

How the call scored

4 rubrics · weighted

Overall 3.8 / 5

Discovery

4.1 / 5

StrengthReopened on the foremen/spreadsheet pain from the demo instead of re-pitching features.
StrengthAsked what week-one success looks like for a foreman — surfaced offline, speed, and anti-corporate-UI needs.

Active listening

4.0 / 5

StrengthPicked up "shelfware" and answered adoption risk before features — buyer felt heard.

Value & pricing

3.7 / 5

StrengthDefused per-seat sticker shock by reframing to a five-seat pilot rather than arguing list price.
GapNever named the pilot price on the call — left Marcus imagining the number in an email.

Closing

3.4 / 5

GapAccepted "send a proposal" — should have booked 20 minutes with the two foremen before hanging up.

Coaching recommendations

What to do next

Specific, scoped actions you can take on the next call.

3 recommendations

Keep doing

Strengths

Tying warm follow-ups to the exact adoption fear the buyer voiced in the demo.

Start doing

Opportunities

State the pilot price and a calendar slot for the foremen review before offering to "send a proposal."

Stop doing

Risks

Ending warm deals on an email thread when the decision makers are already named.

Recommended

Curated resources

Selected by the coach based on this session's gaps.

Playbook: converting "send a proposal" into a multi-threaded foreman review.

Conversation history

Full transcript

8 messages · 8m 0s

00:00:00

Marcus — thanks for hopping on after the demo. Last time you said foremen still live in spreadsheets. Has anything shifted since then?

00:00:40

Same story. I liked the mobile daily reports, but the last tool we bought sat unused after three weeks. I'm not buying shelfware again.

1 note00:01:20

Understood. What would have to be true in week one for a foreman to actually log a report without you chasing them?

Could be betterDiscovery

Excellent week-one success question — follow with "who has to try it first?" to surface the two foremen earlier.

Quoted: What would have to be true in week one

Try: "What would week one look like for a foreman — and which two should we put on the pilot invite?"

00:02:00

It has to work offline on site, take under two minutes, and not look like another corporate app. Also — €45 a seat adds up fast for forty people.

1 note00:02:40

On offline and speed we're aligned — field mode caches the day and syncs when they hit signal. On price, most crews your size start with a five-seat pilot, not forty licenses day one.

MissedValue & pricing

You reframed to a five-seat pilot — name the pilot price here so the proposal isn't a black box.

Try: "Five seats at a flat €600 for thirty days — shall we put both foremen on a 20-minute review Thursday?"

00:03:20

A pilot I can sell internally. Send me a proposal with the pilot price and rollout steps. I'll float it past the two foremen.

1 note00:04:00

I'll send that over today. Ping me when the foremen have looked — happy to jump on a short call with them if useful.

AvoidClosing

"I'll send that over" hands control to email. Book the foremen review while Marcus is on the line.

Quoted: I'll send that over today

Try: "I'll send the one-pager in an hour — and can we lock 20 minutes Thursday with you and both foremen?"

00:04:40

Okay. Talk soon.