The follow-up note that keeps a promising business meeting useful
A Dual Party Capital perspective from Shane Ian Murphy on turning discussion into a defined next step.

A promising commercial meeting can leave everyone feeling positive while producing very different recollections of what happens next. One participant believes a proposal is being assessed. Another is waiting for a document. A third understood the discussion as an initial introduction. The follow-up note is where those interpretations can be brought back into view.
This is an educational company perspective from Shane Ian Murphy, co-founder and partner of Dual Party Capital. It concerns the preparation of commercial discussions rather than a particular mandate or completed transaction. It is not an offer of investment, financing or a commitment from any counterparty. The examples describe hypothetical situations.
Record the stage reached
Imagine a first meeting about an asset-backed proposal. The team has explained its intended commercial purpose, and a prospective participant has asked to see supporting material. That is a meaningful next step, but it does not establish that terms have been agreed or that funding has been approved. The note should describe the request at the stage actually reached.
Ordinary language helps. A sentence explaining that a participant requested further information can be more accurate than a broad statement that the project is moving forward. The first records an observable event. The second leaves readers to supply their own interpretation, which may become more confident each time the message is forwarded.
Separate discussion from decision
A meeting often contains suggestions. Someone may describe an alternative timetable, ask about a different amount or propose another route for review. Those ideas are worth recording, but the note should distinguish them from decisions accepted by the relevant people. Attribution preserves the difference between an option raised and an action agreed.
A practical structure is to identify the matter discussed, the position reached and the question still open. That need not make the document long. It makes the short version more useful because a person reading it later can recognise which parts of the conversation were exploratory.
Give the request an owner
A request for more information should identify who can provide it. Technical scope, commercial authority and supporting records may have different owners. Asking one person to answer everything can create delay or encourage a response beyond their actual responsibility. A clear note routes the question to the appropriate participant.
It should also describe the expected response. Is the recipient preparing an explanation, supplying an existing document or checking an assumption? Each is a different action. Specificity helps the owner understand what would count as completing the request and helps the next reviewer understand what they are receiving.
Explain timing through dependencies
A proposed response date is more useful when its basis is clear. If a document depends on an outside review, that dependency belongs beside the target. A date presented without context can begin to look like an unconditional commitment, even when everyone in the original meeting understood otherwise.
The note can preserve both momentum and realism. It can state the intended timing while identifying what must happen first. If an input is delayed, the team has a shared basis for revisiting the plan rather than treating the change as a surprise with no recorded cause.
Keep versions recognisable
The supporting proposal may change after the meeting. An amount may be revised, an assumption clarified or an attachment replaced. The follow-up should identify which version is being discussed and explain material revisions. A later participant should not need to reconstruct the history from filenames scattered across several messages.
That discipline is particularly useful when a summary travels further than its original attachments. Consistent terms and dates help ensure that the opening description still relates to the evidence available for review. Where a condition remains unresolved, it should remain visible in the shorter account as well.
End with a usable next step
The best follow-up note is not a performance of certainty. It gives participants a common account of the conversation and a clear way to continue it. A readable request, an identified owner and an understandable review point can keep useful interest from dissolving into a chain of ambiguous messages.
In the commercial preparation perspective I associate with Dual Party Capital, that is practical progress. A well-recorded introduction does not guarantee an outcome. It makes the work needed for assessment easier to see, and it gives everyone a better chance of discussing the same proposal at the next meeting.
Illustration: supplied promotional portrait of Shane Ian Murphy. It does not document the hypothetical meeting described in this article.
About the Creator
Shane Murphy
Shane Ian Murphy: co-founder/partner, Tri-Party Tokenisation; founder/CEO, Global Secure Technologies (planned 2027 launch); co-founder/partner, Dual Party Capital. Partner, RougeN International Corp. Formerly of Limitless Mobile.
Enjoyed the story? Support the Creator.
Subscribe for free to receive all their stories in your feed.
Comments
There are no comments for this story
Be the first to respond and start the conversation.