The rep still makes the call: the whole system on one page
Every call, thread and note becomes a drafted CRM record with the sentence behind each field. The rep approves it in about two minutes, keeps stage, dates and amount, and the system only argues with a quote.
Jared Hawkins-Young · Founder, Lost Star TechnologyOctober 8, 20267 min readPart 1 of 13Key takeaways
- A rep's week is mostly not selling, and the CRM record is typed from memory days later by the person with the most reason to round it up. Salesforce's 2024 survey puts selling at about thirty percent of the week.
- Five steps, in order: capture, write, recommend, trace, act. Evidence fields are drafted with their sentence and approved in about two minutes. Commercial fields come as arguments, never as writes.
- The system's only power over stage, dates and amount is to make an argument and show the quote. The agent's write tool cannot touch those fields, and every write it makes is logged.
- Three things get fixed at once: the week, the forecast, and the handoff when a rep leaves.
Your calls are recorded. Your CRM is still days behind. Reps type the record on Friday from memory, and the forecast you take upstairs is a reflection of how each rep felt walking out of each call. Everything the customer actually said is already sitting in a recording and a thread. This series is about the layer that reads all of it. This first part is the whole system on one page. The twelve that follow take it apart.
One opportunity, under the system
- Current setupHubSpot, four account executives, notes typed on FridaysREC 06:12
- Identified painReps update the CRM from memory; two deals slipped unseen last quarterREC 12:40
- RequirementRecords approved by the rep before anything is writtenREC 14:05
- BudgetApproved for Q4, under $30KREC 27:51
- CompetitorEvaluating the recorder's own CRM syncEMAIL 3
- Economic buyerVP Sales signs under $50K; CFO aboveREC 30:22
- Paper processSecurity review before legal, scheduled for the 14thREC 38:12
- Open issues3 owed by us, 1 by them, all dated4 SOURCES
- Next stepSend the SOC 2 report by TuesdayREC 39:05
- Opportunity amount$30,000Lower to $24,000"We'll start with the four reps, not six." REC 18:02
- StageProposalBack to DiscoverySecurity owner has not been in a room. REC 38:12
- Close dateDec 15Move to Jan 30"The review alone takes six weeks, and we haven't started it." REC 31:14
- Invoice dateDec 20Follows the close dateMoves automatically when you accept the date
- Contract lines6 seats4 seats, onboarding includedScope stated on the call; declined lines are not added back
The left side is evidence. Current setup, the pain in the buyer's words, the requirement, the budget, the competitor, who signs, the paper process, the open issues, the next step. None of it was typed. It was drafted the moment the call ended, and every line carries a timestamp. The rep reads it, approves most of it, edits one line, rejects another, and only then does it land in the CRM. That takes about two minutes.
The right side is judgment. Amount, stage, close date, invoice date, contract lines. The system never writes these. It makes an argument. The amount should drop because the buyer cut the scope on the call, and here is the sentence. The close date should move because the security review has not started, and here is the sentence. Accept both, review one at a time, or dismiss. Dismissals are logged, because a rep who dismisses everything is telling you the extraction is wrong, not that they are difficult.
Five steps, in order
- 1CaptureEvery call, every thread and every rep note goes through one extraction. Today the call gets coached and the rest is storage.
- 2WriteQualification, requirements and next steps arrive as a drafted record with the sentence behind each field. The rep approves it on arrival. Nobody reconstructs a week at nine at night.
- 3RecommendStage, dates and amount stay the rep's. The forecast moves on evidence rather than on how the call felt.
- 4TracePress any value and hear it said. That is the adoption argument, and it is what makes a handoff survivable when a rep leaves.
- 5ActRecaps, open issues, drafted replies, quotes and proposals, an edit list for the demo deck, and the rebuttal while the call is still open. Each one stops at a draft until a person presses send.
What stays yours
A sales team reacts badly to being told what to do by software, and the software is not always right. So the design starts from the boundary. Evidence is drafted and approved field by field. Commercial fields are never proposed as writes, only as arguments. Nothing reaches a customer without a person reading it.
Three things get fixed at once
- The week. Salesforce's 2024 State of Sales survey puts selling at about thirty percent of a rep's week; the rest is admin, internal meetings and research. The record writing itself takes the largest single piece of that admin off the table.
- The forecast. It stops being a reflection of how the rep felt leaving the call, because every number that matters carries the sentence behind it, and the rows where the CRM contradicts the buyer are flagged before the pipeline review, not after.
- The handoff. When someone resigns, the account does not leave in their head. The next rep inherits the quotes and the open issues, not a predecessor's memory.
Where to start
Not with the clever part. Start with the open-issue ledger and the CRM write, because they are the narrowest build with the clearest proof. Then the recap after every meeting. Then the recommendations, once reps already trust the record. The assistant that answers during a live call ships last, because it is the one piece that is not forgiving.
That order is also how a Lost Star engagement starts: a free 15-minute call, then a week inside your CRM, recorder and inbox that ends in a written operating plan. Then you choose: Jared builds it, or your team builds from the plan.
Next in the series
Part 2 opens the capture step: how one extraction reads recordings, threads and rep notes the same way, what a typed signal looks like, and why the whole book becomes something you can query. The series page lists every part in order.
Common questions
- Does the system write to our CRM without approval?
- No. The record is drafted the moment the call ends, with the transcript sentence attached to each field, and the rep approves, edits or rejects it field by field before anything is saved. Stage, dates and amount are never written by the system at all; they arrive as recommendations with the quote behind them.
- Which recorders and CRMs does it work with?
- Fathom, Fireflies, Gong and Zoom recordings on the recorder side; any CRM on the other side, with HubSpot and Salesforce the common ones. It runs on the accounts you already pay for, with scoped permissions. There is no new seat or login for the reps.
- What happens when it gets a field wrong?
- The rep corrects it before it is saved, and the correction is kept as a labelled example. The same fix made repeatedly becomes a pattern and the extraction schema is updated, so the next run gets it right. Part 7 of this series covers that loop.
Sources
Written by Jared Hawkins-Young from the system he builds and runs. Diagrams are drawn from the same specs as the software. Published October 8, 2026. Illustrative numbers are labelled as such; every other figure carries its source.