A SaaS go-to-market strategy decides who you will serve, what they can credibly expect, and how they will reach a useful result and a buying decision. For a team of one, the plan must also fit the hours you can actually spend. Use this worksheet to choose a provisional motion before you build an outreach list or buy traffic.
Choose how the buyer reaches value
A motion is the path from first interest to use and purchase. In a founder-led motion, you help diagnose the problem, demonstrate the product and guide the buying decision. In self-serve, the buyer can evaluate, start and pay without you. A hybrid puts human help at a specific obstacle while leaving the rest self-serve.
Start with one provisional customer profile: a role, a recurring workflow and a reason to change now. Then name the first-value event in observable terms. Account created is a setup step; a buyer using the output to complete a real task is a more useful candidate. Ask what must happen between those two events.
- Buying friction: can this person authorize the purchase, or must security, procurement or another budget owner participate?
- Implementation friction: can the person supply the necessary data and understand the result without a custom integration?
- Trust: can a demo or sample establish enough confidence to try, or must someone explain permissions and limitations?
- Capacity: how many evaluations and support requests could you handle while maintaining the product?
Keep the promise inside the product's current capabilities
Write one sentence connecting a working capability to the buyer's task. Separate what a person can inspect in the product from the improvement you hope it creates. A tool that shows pending approvals can claim that visibility; faster payment needs evidence of a payment outcome.
Record the current workaround alongside your offer. If a spreadsheet already works well enough, a missing feature elsewhere may not justify switching. Use competitor analysis to collect the facts and the positioning worksheet to decide which difference could matter. Keep price, packaging and willingness to pay provisional until you have relevant evidence.
Worked example: two motions for the same SaaS
Everything in this example is fictional, including the product, observations, prices, hours and dates. These are planning assumptions, not benchmarks, customer results or output from a Soloop task.
Imagine ReviewQueue, a small agency tool that lists deliverables awaiting client approval, shares review links and records approval decisions. It does not create invoices or collect payments. In this invented scenario, the founder has inspected those features in a demo, but has no purchase or retention evidence. Both options below target the same agency operations lead.
For this two-week planning exercise, the founder reserves ten hours for GTM work and caps cash spending at $100. Product maintenance has a separate time allocation. The question is whether a limited assisted evaluation or an unassisted trial is the better next test.
| Dimension | A · Founder-assisted evaluation | B · Self-serve trial |
|---|---|---|
| Buyer and trigger | Agency operations lead preparing an upcoming client review; authority to buy unknown. | Same lead and trigger; authority to buy unknown. |
| Buying/setup friction | Founder explains client access and helps set up one permitted deliverable; approvals still need checking. | Buyer must understand client permissions and set up the deliverable from the product guide alone. |
| First value | Lead views a client's recorded decision on a real, permissioned deliverable. | Same event, reached without founder help; onboarding completion is recorded separately. |
| Offer hypothesis | One assisted 14-day evaluation, then a proposed $39/month workspace; no payment commitment established. | Unassisted 14-day trial with the same proposed $39/month workspace; acceptance unknown. |
| Founder hours | 2 preparation + 2 finding suitable participants + 3 assisting at most two evaluations + 1 support + 2 review = 10 hours. | 4 onboarding guide + 2 instrumentation checks + 2 distribution + 1 support + 1 review = 10 hours. |
| One channel | Founder introductions to agency operators, with permission to follow up. | One educational post in an agency community that permits it, linking to the trial. |
| Cash ceiling | $100 maximum incremental spend; no ads assumed. Record actual costs before further commitments. | Same $100 ceiling; organic distribution only. Reach is unknown. |
| Missing evidence | Whether the lead can invite a client, obtain permission and authorize payment; whether assistance fits three hours. | Whether anyone sees the post, understands access or reaches value unaided; no measured funnel yet. |
| Review date | October 5, 2026: compare actual hours, setup obstacles and observed value events. | October 5, 2026: separate no visits, failed setup and no client decision. |
| Stop rule | Pause new evaluations at ten hours or $100, or if required data permission cannot be obtained. No new integration promised. | Same time/cash caps; pause recruitment if client access is unsafe or unusable. No visits is not proof of no demand. |
Make the plan fit one founder's week
Budget time for preparation, distribution, assistance, support and review. If those commitments exceed the hours available, reduce the number of concurrent evaluations or simplify the offer. Do not assume that a free trial creates free support. Cash and time need separate ceilings.
In the fictional choice above, two evaluations are a capacity limit, not a sample size that proves demand. If assisting one buyer consumes all three reserved hours, stop adding evaluations and inspect why. An onboarding problem, a mismatched buyer and a missing capability imply different next steps.
Copy the SaaS go-to-market plan
Select and copy this worksheet into your own document; no account is required. Fill the plan column first, then identify the evidence that could change it. On a small screen, scroll the table sideways to reach the second column.
| Dimension | Plan for this review period | Evidence or reversal condition |
|---|---|---|
| Buyer / trigger | [Role, workflow, urgency, exclusions] | [Source and date; buying authority unknown if unverified] |
| Alternative / promise | [Current workaround; useful result your product supports] | [Inspected capability; benefit still to establish] |
| Motion / friction | [Founder-led, self-serve or hybrid; where help occurs] | [Observed obstacle; what would remove the need for help] |
| First value | [Observable useful event and how you will record it] | [Required inputs, permission and dependencies] |
| Offer | [Scope, trial terms, proposed price and explicit limits] | [Acceptance, use and payment tracked separately] |
| Capacity / channel | [Hours by task, concurrent limit, one channel] | [Actual time and support work; access to this audience] |
| Budget / review | [Cash ceiling, owner and review date] | [Actual spend and missing evidence] |
| Decision / stop | [Chosen motion, rejected option, stop rule] | [Finding that would reverse this decision] |
Review the motion before scaling the channel
Record what happened at each step: reached a relevant person, understood the offer, started setup, reached first value, and made a buying decision. Preserve counts and source notes; two positive replies cannot tell you a reliable conversion rate. A purchase is different evidence from an expression of interest.
For ReviewQueue, a buyer completing setup unaided would weaken the argument for mandatory assistance. A buyer blocked by an approval requirement would suggest fixing that dependency or changing the target. A client who never receives the invitation leaves a different question from a client who tries the tool and rejects it. Keep these cases separate.
Once the motion is explicit, use the first SaaS customers guide below for prospect selection, outreach and conversations. That execution work should follow the constraints in this plan. Add channels only when you can explain what the existing one taught you and can support the resulting workload.
Bring your product and this GTM brief to Soloop
You can use the worksheet on its own. To continue in Soloop, copy your brief into the conversation: My product is [URL]. Buyer [role], buying friction [facts], first value [event], capacity [hours], budget [ceiling]. Compare [motions], label missing evidence, and propose one next action for review.
The Soloop manual describes planning in the main conversation and separately approved research tasks. Review the scope and cost of any proposed action. Soloop can prepare and launch Google Ads campaigns after you complete the campaign setup and payment steps; this brief does not launch one. The Explore Soloop link opens the public entry, so bring the worksheet yourself.