You've got a reply waiting on LinkedIn, a customer question buried in email, and a follow-up you remember agreeing to send. The date may be in a notebook. It may also be in the special brain-based filing system known as “I’ll remember that.”
This can work while you have three conversations happening at once, but it gets expensive when you forget to reply to somebody who was ready to pay. Therefore, early go-to-market operations should give you a clean and clear place to see who you are speaking to, what happened and what needs to happen next.
Try not to get bogged down into over-complex tools on the market that'll take you longer to set up than it will to respond to those outstanding emails. A spreadsheet, Notion table or lightweight customer relationship management systemCustomer relationship management software. A CRM stores information about people, companies, conversations and sales opportunities. The software only helps when its records reflect the current situation. (CRM) like Folk can all do this; the software matters much less than the info inside it being up-to-date and easy to access
Start with the smallest place
Your first system doesn’t need automated scoring, twelve dashboards or a field for every thought you've had since 1997. It needs to hold the few details that change what you do next.
| If this is where you are | A sensible starting point | Move when |
|---|---|---|
| You handle a small number of conversations yourself | A spreadsheet | Follow-ups are being missed or records are duplicated |
| You already run your work in Notion | A simple Notion database | The views and manual updates become harder to maintain |
| Several conversations move at once, or another person needs the information | A CRM | The current CRM no longer supports the process you use |
Whichever option you choose becomes your system of recordThe place treated as the current answer for a specific type of information. In this chapter, it is the table or CRM you check for customer conversations and next actions., meaning the place you check when you need the current answer. If you still trust your inbox or memory more, the record is either out of date or asking you to maintain too much.
The three-record GTM system
People and opportunities, activity and experiments, and decisions and learning are three connected records. The people record owns the next action.
- People and opportunitiesOwns the next action
Who am I speaking to, what happened and what happens next?
State · last interaction · next action · date - Activity and experiments
What did I try, and what did customers do afterwards?
Date · channel · my activity · customer response - Decisions and learning
What did I decide, why and when will I review it?
Decision · evidence · date · review condition
Connected records, not one enormous database.
Decide who gets a row
A person belongs in the record when they enter a real conversation, show clear buying interest or become a customer. If you sell to businesses, the company and its buying process may need their own details, too.
A website visitor doesn’t become a sales opportunityA person or company considering a purchase. Interest should be supported by customer behavior such as asking for details, discussing price or involving another decision-maker. because your analytics tool noticed them. For a self-serve consumer product, the people worth logging individually may be interview participants, customers who ask substantial questions or somebody who messages before buying. Anonymous visits and product behavior belong in your analytics; we’ll cover those in Measuring what matters. Fifty website visits and five people who asked about price are different facts.
Keep seven details about each conversation
You can add fields later; these seven are enough to tell you what has happened and what you should do next.
| Field | What goes in it |
|---|---|
| Person | The person you spoke to |
| Company | The business involved, when relevant |
| Source | How they first found you |
| Current state | The furthest point the conversation has reached |
| Last meaningful interaction | The latest reply, call or substantive exchange |
| Next action and date | The specific action somebody has agreed to take |
| Note | Their main question, concern or objection |
For a considered B2B purchase, a few more details may change how you handle the sale.
| Optional B2B field | What it tells you |
|---|---|
| Likely value | How much the customer may pay, based on a product and price already discussed |
| Expected decision date | When the customer says they expect to decide |
| Decision-maker status | Whether the person who can approve the purchase is involved |
| Budget status | Whether the customer has confirmed money is available |
Record the original sourceThe first known route through which somebody found you, such as a referral, post, search result or cold email. “Unknown” is a valid source when the information is unavailable. when you know it, such as a LinkedIn post, referral or cold email, because this helps you to double down on the channels that are most productive for you. You can also record what prompted the latest action: somebody may first discover you on Reddit, join your email list and eventually book a call after a customer story. “Unknown” is still more accurate than awarding the sale to whichever channel you checked most recently.
Use states that describe what happened
A sales stage is the label attached to the current point in a buying conversation, but it only helps when you can describe the customer action that puts the person there.
| State | What has happened |
|---|---|
| New | The person has entered the record, but no substantive exchange has happened yet |
| Conversation started | They replied, booked a call or discussed the problem with you |
| Considering | They asked for details, discussed a purchase or involved another person |
| Customer | They paid or entered the agreed paid engagement |
| Stalled | The conversation has no agreed next step or has received no response after the relevant follow-up |
| Closed | They declined, chose another route or no longer fit the product |
Your buying process may need different words. The way a person enters this process matters more than the label; two records in “considering” should represent roughly the same stage.
“StalledA conversation with no agreed next step, or no customer response after the relevant follow-up. Stalled records can be reopened later without appearing active in the meantime.” deserves its own state because an old conversation shouldn’t remain active forever, and you want to record that the person was once interested so you can re-activate the relationship at a later date.
Give every active conversation a dated next action
An active record needs a specific action, the person responsible and a date. “Follow up” leaves this too ambiguous.
| Too vague | Specific enough to act on |
|---|---|
| Follow up | I will send the security answers by September 21 |
| Check in next month | I will ask whether the budget review happened on October 3 |
| Waiting for reply | Sam will confirm the two pilot users by September 24 |
The next actionA specific action assigned to a person and date. It may belong to you or the customer, although you still need a date to review anything the customer agreed to do. can belong to you or the customer. If the customer has agreed to do something, the record should still say when you will review it. Otherwise “waiting for reply” can become a permanent state of anxiety. An automated email doesn’t update the date of the last meaningful interactionA reply, call or substantive exchange with a customer. An automated message you sent is activity; it does not show that the customer responded. — it instead records something you sent. A reply, call or substantive exchange is the meaningful point to record.
An active conversation needs a next action
The vague record says open and follow up, with no owner or date. The actionable record says considering, send security answers, owned by me, due September 21.
Vague record
- Status
- Open
- Note
- Follow up
- Owner
- Blank
- Date
- Blank
Actionable record
- State
- Considering
- Next action
- Send security answers
- Owner
- Me
- Due
- September 21
An active record needs an action, an owner and a date.
Separate your activity from customer response
Posting, emailing and attending an event tell you what you did; replies, sign-ups, trials and payments represent your customers’ actions following. Keeping both in the same short activitySomething you or your business did, such as publishing a post, sending an email or attending an event. Activity becomes commercial evidence when a customer responds through an action such as replying, registering, trying or paying. log makes the relationship between the two — the cause and effect — visible.
| Date | Channel | What I did | What customers did |
|---|---|---|---|
| September 18 | Published a post about manual reporting | Two relevant replies; one walkthrough request | |
| September 20 | Cold email | Sent ten researched emails | One reply asking about integrations |
| September 22 | Community | Answered a question about weekly reports | One private request for the worksheet |
Time or spend deserves a column when it affects your decision. You don’t need a conversion dashboard for three replies, and a percentage built from a tiny sample won't tell you much. The measurement chapter will handle rates, benchmarks and attributionThe method used to connect a customer action with the channel or activity that contributed to it. Early records can preserve the original source and latest prompt without attempting to assign a precise percentage of credit. in detail.
Record decisions before you forget why you made them
The decision logA short record of a commercial decision, the evidence available when it was made and the condition that would cause it to be reviewed. can be extremely short. It needs the decision, the why, and the condition that would make you review it.
| Decision | Evidence | Date | Review when |
|---|---|---|---|
| Focus the next 30 days on finance consultants | Four of six relevant conversations came from this group | September 18 | After ten more conversations, or after 30 days with no qualified replies |
This gives an early decision a fair assessment without turning it into something that might not be true forever.
Clean the record once a week
A good rule of thumb is a 15- to 20-minute weekly clean-up for an early system. This doesn't have to be manual - rope in an AI agent to help you - and treat it as a starting point based on a small number of active conversations. The time is enough to:
- add missing next actions and dates;
- move inactive conversations to stalled or closed;
- correct missing sources;
- record decisions made during the week; and
- check what is due in the next seven days.
If the clean-up regularly takes much longer, remove fields before adding software. Your cash, available time and delivery capacity should also change how you work. A list of 40 follow-ups isn't viable if you can only complete eight, and six new customers aren’t good news if you can only support two.
Automate after the manual process works
Automation helps when the same repetitive actions keep taking your time. Before handing it over, you should be able to answer five questions.
| Question | Example |
|---|---|
| What starts it? | A recorded customer call ends |
| What information does it use? | The approved transcript and existing customer record |
| What does it produce or change? | A draft note and suggested next action |
| Who reviews it? | You |
| What happens when it fails? | Nothing changes until you correct or approve the draft |
AI can prepare admin work for your review, while customer communication and material changes remain yours to rubber-stamp.
| AI can prepare | You approve before anything changes |
|---|---|
| A summary of notes you supplied | Any customer message |
| Suggested record updates | A change to somebody’s state or likely value |
| A list of records with no next action | Updates to the live record |
| A weekly summary | Any decision to close or abandon a conversation |
The model can’t know that a polite “interesting” means a $20,000 opportunity, no matter how enthusiastically it fills the field.
Manual first, then automation
Before automation, define the trigger, input, output, review and failure behavior. Customer communication and material record changes wait for the founder.
- Trigger
What starts the task?
- Input
What information does it use?
- Output
What does it produce or change?
- Review
Who checks it?
- Failure
What happens when it goes wrong?
Three conversations after one week
Suppose you sell RelayReport, a fictional reporting tool for small marketing agencies. Three people enter your record through different routes.
| Person | Source | What happened | State | Next action |
|---|---|---|---|---|
| Michael | LinkedIn post | Asked for security details and invited his ops lead to the next call | Considering | Send security answers by September 21 |
| Dwight | Community introduction | Explained that the agency can’t review new software until its November planning round | Stalled | Ask whether the review happened on November 12 |
| Pam | Cold email | Replied that the agency renewed its current tool for another year | Closed | None; record the reason |
This represents one progressing conversation, one possible later opportunity and one clear no. Calling all three “open” would make the pipeline look nicer while telling you very little.
If you sell a self-serve consumer product, the individual record will probably be smaller. You might record research participants or design partners, substantial support conversations and people who ask a buying question; your product analytics will count anonymous visits, sign-ups and repeat use.
Prepare your GTM operations record
Use the GTM operations record with any customer notes, channel activity and decisions you already have.
Prepare your GTM operations recordShow or hide prompt
I am preparing my GTM operations record. Use only the material I supply.
Don't contact anybody, send messages, connect accounts, change a live CRM or
invent missing customer information.
1. Recommend one place for my record based on the number of conversations I
handle, the tools I already update and whether anybody else needs access.
2. Build my people and opportunities table. Use these starting fields: person,
company where relevant, source, current state, last meaningful interaction,
next action and date, and the main question or objection.
3. Add likely value, expected decision date, decision-maker status and budget
status only where my B2B sales process needs them.
4. Classify each record as new, conversation started, considering, customer,
stalled or closed. Cite the supplied customer action behind the state. Mark
any state that can't be supported as unknown.
5. Create an activity log that separates what I did from what customers did.
6. Create a decision log with the evidence, date and review condition for each
supplied decision.
7. Create a seven-day view of my dated next actions. Don't invent follow-ups
where none have been agreed.
8. Prepare a weekly clean-up checklist and draft AI permissions. Keep all
external communication and material record changes subject to my approval.
Return standard Markdown in my first person. Separate supplied facts,
assumptions and unknowns. Stop with the prepared record for my review.The record is prepared when the three tables exist, each active conversation has a dated next action or a marked unknown, and the seven-day view shows what you have committed to do. The next chapter covers how to keep in touch when somebody is interested and still not ready to buy.
Glossary
Glossary11 terms
The meanings carried by the highlighted terms in this chapter.
- Activity
- Something you or your business did, such as publishing a post, sending an email or attending an event. Activity becomes commercial evidence when a customer responds through an action such as replying, registering, trying or paying. Go-to-market operations: remember what happened and what happens next
- Attribution
- The method used to connect a customer action with the channel or activity that contributed to it. Early records can preserve the original source and latest prompt without attempting to assign a precise percentage of credit. Go-to-market operations: remember what happened and what happens next
- CRM
- Customer relationship management software. A CRM stores information about people, companies, conversations and sales opportunities. The software only helps when its records reflect the current situation. Go-to-market operations: remember what happened and what happens next
- Current state
- The furthest point a person has reached in your buying process, supported by something they did. Sales teams often call this a pipeline stage. Go-to-market operations: remember what happened and what happens next
- Decision log
- A short record of a commercial decision, the evidence available when it was made and the condition that would cause it to be reviewed. Go-to-market operations: remember what happened and what happens next
- Meaningful interaction
- A reply, call or substantive exchange with a customer. An automated message you sent is activity; it does not show that the customer responded. Go-to-market operations: remember what happened and what happens next
- Next action
- A specific action assigned to a person and date. It may belong to you or the customer, although you still need a date to review anything the customer agreed to do. Go-to-market operations: remember what happened and what happens next
- Opportunity
- A person or company considering a purchase. Interest should be supported by customer behavior such as asking for details, discussing price or involving another decision-maker. Go-to-market operations: remember what happened and what happens next
- Source
- The first known route through which somebody found you, such as a referral, post, search result or cold email. “Unknown” is a valid source when the information is unavailable. Go-to-market operations: remember what happened and what happens next
- Stalled
- A conversation with no agreed next step, or no customer response after the relevant follow-up. Stalled records can be reopened later without appearing active in the meantime. Go-to-market operations: remember what happened and what happens next
- System of record
- The place treated as the current answer for a specific type of information. In this chapter, it is the table or CRM you check for customer conversations and next actions. Go-to-market operations: remember what happened and what happens next
Sources
- Alice Bull, internal GTM operating frameworks: Founder Commercial Operating Rhythm, GTM Operating Rules 2026, CRM Hygiene, Process Design and Tool-Stack Coherence, checked September 18, 2026.