How do you run a six-week GTM sprint for a pre-seed startup?

A pre-seed founder runs a six-week GTM sprint by spending the first two weeks deciding who to sell to, what to say and which two channels to run, then four weeks sending, reading the replies and writing down what the numbers say to do next. It produces a tested first channel, a pipeline with live conversations in it, and a written guide that lets someone else run that channel from week seven. The plan below is the one I run with founders and ran on my own consultancy this autumn, and it rests on more than ten years in growth across 30+ clients in Germany, Belgium, the Netherlands, Austria, the UK and the US, three companies I co-founded by 23, and the first marketing seat at Fangage, which I held through its acquisition by Triller.

The first-channel guide has the week-by-week overview. This piece is the manual underneath it: what to do each week, what to count, and what goes wrong.

A GTM sprint is a fixed block of weeks in which a founder tests one or two growth channels with their own hours, counts acceptances, replies and meetings, and ends with a written decision on what to run next and who should run it. Before product-market fit, it runs on the founder's hours and no ad budget.

What does a six-week GTM sprint produce, and what does it cost in founder hours?

It produces five things on paper and one in the pipeline: a named segment, a one-page positioning in the buyer's words, a target list with a decision maker on every account, two tested message variants with their numbers next to them, a channel guide with a 90-day plan, and a pipeline board with the first conversations on it. It costs the founder around four hours a week plus the sales calls it books, the figure I use in the first-channel guide, and weeks one and two run heavier because the interviews do not compress.

Product-market fit and the first hire both come later; the sprint produces the reading that tells you which of the two to work on next. CB Insights went through 431 VC-backed companies that shut down since 2023: 70% cited running out of capital and 43% poor product-market fit, and the report calls running out of capital "almost always the final cause of death, not the root problem" (CB Insights). The week-five numbers show that root problem while there is still capital to act on it.

How do you decide the segment, the message and the two channels in weeks one and two?

You decide by interviewing the last customers and the last lost deals before you write a word of copy, then scoring channels on whether you can start them this week, read them inside six weeks and find your buyer there. Both decisions are made in writing by the end of week two, and the list is built before the first note goes out.

Week one is the interviews and the page.

1. Pull every closed and lost conversation from the last two quarters into one document: who signed, who blocked, what nearly stopped the deal.
2. Book ten interviews, half with people who paid and half with people who said no. Ask what they were doing before, what they compared you with, who else had to agree, and how long the decision took.
3. Write the one-page positioning in the buyers' words: the segment, the problem as buyers state it, who signs, who blocks, the cycle length.
4. Score the channels with the table in the first-channel guide: two cheap channels, one fast (founder-led outbound) and one slow (an answer page, a template, or a partner), and the fast one gets the first three weeks.

Week two is the list and the two notes.

1. Build the target list from the sources the interviews pointed at: companies that have written the need down in a job post or a brief, companies in the segment that fit the profile, and people you have met. Pick enough accounts to cover the sending weeks at the daily cap.
2. Name the decision maker on every account, away from the platform where you found the need. A posting names a team or a reporting line; an enrichment tool gives you the person who owns that budget.
3. Write two message variants. For a connection note, under 300 characters: one observation lifted from the account's own posting, one question a busy person can answer in a sentence. Variant A opens with the observation, variant B with the problem sentence from the interviews. No deck, no calendar link.
4. Set the daily cap in the outreach tool, set up the board with a stage field and a lost-reason field, and read both variants aloud to one person who matches the segment.

The gate at the end of week two: a decision maker named on every account, and both notes read aloud. If you cannot name who signs on more than half the list, you have a database export, and week three will tell you so at the cost of a week.

How do you run founder-led outbound and start the slow channel in weeks three and four?

Send at the daily cap every working day, read every reply yourself within the day, and rewrite the weaker variant after the first batch of replies. In week four, launch the slow channel beside it, one answer page or template download or one partner conversation, and expect nothing from it inside the sprint.

The base text for week three is still Paul Graham's essay on unscalable work: "You can't wait for users to come to you. You have to go out and get them" (Paul Graham). Lenny Rachitsky's survey of the founders of about twenty hyper-growth B2B companies on how they found their first ten customers lands in the same place: "Only three sourcing strategies account for every B2B company's very early growth", the founders' own network, going to where the customers already gather, and press, which he calls rare as a start. One founder quoted in it set "a target of 15-18 net new IT folks / different companies to talk to every month for the first 6 months" (Lenny's Newsletter). That is the kind of weekly sending target week three runs on.

The week-three routine, every working day:

1. Send the day's batch at the cap, about 20 requests a day on my profile.
2. Answer every acceptance with the second touch the same day: one thing from their reply or their posting, one question. Two touches, then stop, and the account gets a re-check date.
3. Log every reply on the board with a stage, and tag the interested ones.
4. On Friday, count acceptance per list source and replies per conversation started, by variant.

On my own consultancy, between Aug 10 and Oct 23, 2026, I sent 300 connection requests across seven lists and 63 were accepted, 21.0%. By list source: the cold database lists, five segments together, 199 requests, 20 accepted, 10.1%. The lists built from companies that had just posted a job or a brief, 51 requests, 10 accepted, 19.6%. The founders I had met in person, 50 requests, 33 accepted, 66.0%. The three sources add up to the 300. The segment-by-segment breakdown is in the acceptance-rate piece.

The week-three decision follows from that order. When acceptance on a list sits under 10%, the note was not read, so the list source changes first and the note second. The weakest list I ran was US startups weighing European market entry, contacted cold: 81 requests, 6 accepted, 7.4%. The note shape was the same as on the event list. The only difference between the 7.4% list and the 66.0% list was that I had met the second group.

Week four adds the slow channel without pausing the fast one.

1. Take the one question buyers asked most in the week-one interviews.
2. Ship one page that answers it, with the template they would download and your contact inside the file rather than a form in front of it. Or hold one partner call with a company whose customers overlap yours.
3. Put a 90-day re-check date on it and go back to sending.

The slow channel starts in week four because of how long it takes. At a resource-planning SaaS, the founder produced planning templates, I did the keyword research and built the download pages, and the first months showed almost nothing. The pages later grew to roughly 10,000 monthly organic visits. I left before the final results were in, so I quote the traffic and no revenue figure.

Which numbers do you read in week five, and what thresholds decide the next move?

In week five you read six numbers off the board, in this order: acceptance per list source, replies per conversation started, interested per reply, meetings per hundred contacts, meeting-to-next-step, and founder hours per conversation. The lines in the table are the ones I use, and the readings next to them are from my own autumn sprint, so each line has real counts behind it.

Two rules sit around the table. Read acceptance before replies, because a bad list hides a good note. Do not read a list under 50 requests, because the first acceptances on any list are its warmest accounts.

What not to read in week five: anything with a denominator you do not have. a16z's list of GTM metrics calls net new weighted pipeline "a bogus number early on" (a16z). With a dozen conversations on the board I weight nothing.

If the product has users, week five also takes the one product reading with a published threshold. Ask them how they would feel if they could no longer use the product. Sean Ellis, who built that survey, benchmarked nearly a hundred startups and "found that the magic number was 40%" answering very disappointed; Superhuman started at 22% and built its roadmap around the gap (First Round Review). Below 40%, "double on one channel" means keep it running at the current cap while the product work happens.

What does the week-six handover contain so the channel survives without you?

The handover is a channel guide, a dashboard, the pipeline board with its stages and lost reasons, and either a hiring brief or a fractional scope for the next quarter. It is written for someone who was not in the room: a contractor sending next month, a first hire next year, or the founder after a fundraise.

The channel guide, in the order I write it:

1. The segment decision with the reasoning: the segments considered, the one chosen, the ones dropped, and the lost reasons that dropped them.
2. The one-page positioning from week one, rewritten in the replies' words where they differed.
3. The list sources ranked by acceptance, with the figure from the Friday counts next to each.
4. The winning note and the second touch, verbatim, with the reply figure next to each, and the two-touch rule.
5. The daily routine: the cap, the send block, the same-day reply rule, the Friday count.
6. The dashboard: the six numbers from the week-five table, updated weekly.
7. The objections, grouped, with the answer that worked for each.
8. The 90-day plan: which channel gets the quarter, what the slow channel needs each month, the re-check date.
9. The hiring brief or the fractional scope: the channel named, last quarter's numbers, the targets for the next two quarters.

Every account sits in the company's name from week one: the outreach tool seat, the enrichment tool, the board, the domain. The cost comparison has the switching checklist. What usually goes missing at a handover is access to those accounts.

What goes wrong in each phase, and how do you catch it early?

Each phase has one failure I see more than any other, and each is visible a week before it costs anything if you know which number to look at.

The week-three failure costs the most, because the founder is working hardest while it happens. An ABM campaign for a publicly listed industrial technology company turned $2,000 into $640k of pipeline value, and the list behind it was short and chosen account by account.

When should you buy the sprint instead of running it yourself?

Buy the first two weeks when you cannot write down who signs and who blocks, when two founders disagree on the segment and nobody can settle it, or when the last ten lost deals have never been read in one sitting. Run weeks three to six yourself whenever you can give the hours, because the founder has to hear the objections first-hand.

Growth Marketing Solutions sells two things that map onto this plan. The GTM Sprint, from $3,500, 2 weeks, fixed price, is weeks one and two of this article done with me: an ICP decision with the reasoning written down; positioning and messaging rewrite; a buyer map per segment (who signs, who blocks, cycle length); a channel plan and 90-day experiment roadmap; an outbound system spec ready to build. You get a written plan and a working session, and you run weeks three to six on it. The Pipeline Build, price on request, 6 weeks, is "the GTM Sprint, then the build: account lists, LinkedIn sequences, founder content, demo booking, CRM hygiene and handover", which is all six weeks of this article run by GMS with you. After either, the Fractional Head of Growth engagement, price on request, 3 to 6 months at about two days a week, covers the quarter when the chosen channel needs building out and the hiring brief needs writing. The offers are on the pricing page. The first step is a call where I go through your pipeline and your last ten lost deals.