What a sales motion needs to connect
A sales motion is the way a business repeatedly finds a suitable buyer, establishes a reason to change, helps the buyer make a decision and delivers what was sold. The sales process describes the stages inside that motion. Go-to-market strategy makes the broader choices about customer, offer, distribution and economics.
For a startup, begin with one narrow motion you can test. A large list of accounts, a CRM and a sequence of emails are useful only when they support a purchase your team understands. If the problem or offer is still unclear, start with customer discovery before hiring a team or outsourcing execution.
Choose a motion you can actually operate
These approaches can overlap. Choose the starting point from buyer behavior, product readiness and the cost of selling. Do not assume outbound will rescue an offer that nobody can explain, or that a product-led experience removes every enterprise buying decision.
Founder-led
The buyer, problem or offer is still uncertain.
Outbound
A specific buyer is reachable and a timely problem can be investigated.
Inbound
Buyers already look for this problem or solution.
Product-led
A user can reach meaningful value with limited assistance.
Enterprise-assisted
The purchase needs several stakeholders, risk review or rollout planning.
Start with a buyer condition, not a broad market
“B2B software companies” identifies a category. “Operations leaders whose first enterprise deals are stalling across security, legal and implementation” identifies a condition to investigate. Select an initial cohort whose workflow and buying constraints are similar enough that you can compare what happens.
Write down the current workaround, consequence, likely owner and disqualifier. For every assumption, identify the conversation or record that could challenge it. Funding or headcount can help find accounts; neither proves that the buyer has a problem your product can solve.
Work through one startup example
Example inputs: a startup sells approval-workflow software. The proposed buyer is an operations lead at a software company moving into larger contracts. A new security review is the trigger to investigate; the startup has not established that this account has a costly handoff problem.
The founder first asks how the last complex purchase moved between teams. If the buyer reports repeated rework, they inspect one actual handoff, agree who owns it and assess whether the product can improve it. If the buyer already has a reliable workflow, the account leaves this play. The rejection is useful learning, even if the company looks ideal on paper.
| Step | Working hypothesis | Evidence that changes the next step |
|---|---|---|
| Observe | Larger deals introduce more reviewers. | Identify an actual purchase and its current owner. |
| Investigate | Approval handoffs may delay the decision. | Buyer explains a concrete delay, rework or risk. |
| Qualify | The problem matters enough to evaluate change. | Buyer agrees on the problem, impact and people needed. |
| Evaluate | One workflow can be improved within the product’s scope. | Agree an evaluation task, success criteria and adoption owner. |
| Decide | The team has enough evidence to buy or stop. | A buyer-owned decision date, requirements and explicit outcome. |
This is a teaching example, not a customer result or a report of a real conversation. Replace its assumptions with your own evidence.
Build a 30/60/90-day plan around evidence
Use this as a planning sequence, not a promise of revenue within 90 days. Your sales cycle, product readiness and access to buyers may change the timing. Give every phase an owner, something inspectable to produce, and a reason to continue.
- Days 1–30
Find a pattern
Founder
- Produce
- Buyer/problem brief, disqualifiers and a standard offer.
- Continue when
- Repeated evidence from comparable conversations; a reason to pursue this cohort.
- Days 31–60
Run a bounded test
Seller + operator
- Produce
- One account cohort, channel plan and evidence-based stage definitions.
- Continue when
- Inspect qualified decisions and loss reasons; choose keep, revise or stop.
- Days 61–90
Test repeatability
Seller + coach
- Produce
- A usable playbook, reviewed deal records and a handover rehearsal.
- Continue when
- Another seller can explain and execute the next decision without routine founder rescue.
Turn those choices into a working play
Keep the plan short enough to use before a conversation. The worksheet below connects the buyer to an accountable next decision. Review the evidence field after each test; a more elaborate message is not always the right next change.
Test one channel with a clear hypothesis
Hold the buyer condition and offer steady while testing a message angle. Start with an account group that is small enough to research and review properly. Decide in advance what a useful response would establish and what result would make you revise the play.
For the approval-workflow example, an email could ask who owns the handoff when security and legal both need answers. A call could explore the most recent handoff. A LinkedIn message could ask whether that responsibility changed as the team moved upmarket. The point stays consistent; the channel changes the format. Contact buyers appropriately for their market and preferences.
See the connected email, call and LinkedIn examples.
Count the entire progression: reached buyer, relevant conversation, confirmed problem, qualified decision and outcome. A high reply rate alone cannot establish that a motion works. Keep a record of disqualifications and reasons for no decision, not just positive responses.
Qualify a buying decision, not a meeting
A meeting gives you access to investigate. A qualified opportunity needs evidence that the problem matters, people who can influence the decision, and an agreed next step. Keep unknowns visible rather than filling every CRM field with a guess.
| Ask | A weak answer | A useful next question |
|---|---|---|
| What happened the last time? | Approvals are slow. | Which handoff delayed which decision? |
| What is the consequence? | It is frustrating. | What work, risk or value changes if it stays this way? |
| Who must agree? | My manager. | Who owns budget, risk and implementation? |
| What happens next? | Send information. | What will you evaluate, with whom, and when? |
Define the evidence for an AE-ready opportunity and use buyer evidence as pipeline exit criteria.
Check the workload before adding volume
Start with your own deal value, observed win rate and sales cycle. When data is sparse, use several scenarios and make the uncertainty explicit. A target that requires more qualified opportunities than your team can create or manage is a capacity problem before it is a messaging problem.
Can the numbers fit the next 90 days?
Change the assumptions. Inspect the workload they imply.
About 2.5 new qualified opportunities per week during the 45-day qualification window. At 4 hours each, that is about 10 hours per week against 20 available.
Illustrative planning arithmetic, not a forecast or a promised result. Opportunities = ceiling(deals ÷ win rate); qualification window = 90 days − sales cycle. Assumes equal deal values, a stable win rate and cycle, and no starting pipeline. Hours per opportunity should include research, contact, follow-up and qualification, including effort on accounts that do not qualify. Weekly available hours must exclude later-stage deal work and other duties. This model excludes ramp time, delivery capacity, churn and cash collection. A signed first-year contract value is not collected cash or profit.
Adapt the motion for enterprise buyers
A larger buyer may need a business sponsor, technical evaluation, security approval, legal agreement and an implementation owner. Discover those requirements early and run independent work in parallel. Closing should not depend on learning about procurement after the buyer says yes.
For an AI product, agree the task, evaluation data, review requirements and acceptable output with the buyer. Establish who owns deployment and what happens when the system gives an unreliable result. A compelling demo does not establish that the workflow can be adopted.
| Workstream | Prepare | Evidence to resolve |
|---|---|---|
| Business | A buyer-specific problem and consequence. | The economic buyer supports an explicit decision. |
| Technical / security | Requirements, evaluation scope and available trust material. | Buyer’s reviewers accept the relevant requirements. |
| Legal / finance | Commercial scope and requested contract/vendor information. | Buyer’s authorized owners resolve terms and setup. |
| Implementation | Rollout responsibilities, dependencies and success criteria. | An accountable owner accepts a feasible rollout plan. |
Keep the operating stack small and owned
Choose tools after defining the work. You need a reliable account record, a way to reach and respond to buyers, a place to record decisions, and a review routine. Decide who maintains each system and how the client retains access.
| Job | Useful record | Owner to name |
|---|---|---|
| Account research | Fit, source, trigger and disqualifier. | Research or operations owner. |
| Outreach | Contact preferences, message, response and follow-up. | Seller, with operational support. |
| CRM | Buyer evidence, stakeholders, stage and next decision. | Opportunity owner. |
| Enablement | Playbook, call feedback and exception rules. | Coach or founder. |
| Learning | Test cohort, outcomes and next change. | The person accountable for the motion. |
Hire when a seller can inherit a learnable job
Before the first hire, test whether the buyer pattern, offer and decision process are understandable without the founder filling in every gap. A sales hire can improve a motion; expecting a new seller to discover the product, market and process alone makes the job much harder to assess.
Have another person research an unfamiliar account, explain why it belongs in the cohort, run a discovery rehearsal and propose a next step from buyer evidence. Review differences in judgment. Record product, pricing and escalation boundaries so the seller knows what they can decide.
Transfer the founder’s decision logic and test independent operation.
Build internally when you can supply the coaching, operational coverage and time required. Consider external execution when you need several capabilities together and can support the engagement. If the offer is unproven or implementation is not ready, solve those constraints before buying more outreach.
Compare a first hire, internal build and an outsourced sales team.
Use failure to choose the next change
| What you see | Inspect first | A focused next action |
|---|---|---|
| Replies, few relevant conversations | Whether the message reaches a real owner of the problem. | Narrow the buyer condition and ask a diagnostic question. |
| Demos, little urgency | The consequence of doing nothing and the buyer’s priorities. | Agree why a decision matters now, or stop pursuing it. |
| A champion, stalled approval | Missing decision participants or risk requirements. | Build a buyer-owned review plan. |
| Founder rescues every opportunity | Undocumented product, commercial or stakeholder judgment. | Coach and rehearse the missing decision. |
| More activity, weak economics | Quality by cohort, cycle length and selling effort. | Reduce unproductive volume and test a narrower hypothesis. |
Change one meaningful assumption at a time when possible. Document the cohort and context so that a different result is not mistaken for proof of a better message. Small samples should lead to another informed test, not a universal benchmark.
Common startup questions
How long does it take to build a sales motion?
There is no universal deadline. The 90-day plan above is a planning sequence. Buyer access, product readiness and the length of the buying process determine when you have enough evidence to call the motion repeatable.
How much should a startup spend?
Start from affordable learning and the capacity required to serve customers. Model your own deal value, win rate and cycle. Tool subscriptions, people, data and delivery effort are separate costs; a generic budget is not a substitute for that calculation.
Does the founder still need to sell?
The founder usually needs to supply product context and help learn the buyer’s decision. Reduce routine dependence as another seller demonstrates the same judgment; do not confuse handover with removing every founder relationship.
When should we hire our first salesperson?
When the seller can inherit a defined buyer, a deliverable offer, a teachable decision process and a person able to coach them. Test that readiness through an unfamiliar-account and discovery rehearsal.
When is outbound the wrong starting point?
When you cannot identify a reachable buyer with a plausible problem, cannot deliver the offer, or lack the capacity to handle responses responsibly. Customer discovery, product work or a different route to the buyer may be the better next step.
Sources and research notes
The plan, worksheets, example and arithmetic are Ramp Year’s operating guidance. The published company handbooks below provide reference points; their processes need adaptation to your buyer and team. Source review: October 8, 2026.
- GitLab commercial opportunity stages
A published company example of explicit opportunity stages and exit criteria; not a benchmark for every startup.
- GitLab Command Plan
A company approach to recording buyer problems, people and decision context.
- Ramp Year delivery method
Our public scope and operating approach. It is not independent evidence of client results.
Schematic