Guide

How to Run a Go-To-Market Team of One (A Real Operating System, Not a Tip List)

How to run a go-to-market team of one | dolv (Photo: Ben Iwara / Unsplash)

You are one person doing the job of four. Content, CRM, email, and analytics all report to you, and none of them talk to each other. By Friday you can name three things you shipped and zero things that moved a number. That is not a tools problem. It is an operating-system problem.

This is the fix: a repeatable weekly rhythm that a single operator (or a team of 2-20) can actually run. Not a list of growth hacks. An operating system — plan, run, measure — with the minimum stack to support it and one honest rule for where it breaks.

why "more tools" makes it worse, not better

The default advice for a lean GTM function is to buy tools. So you end up with a CRM you barely populate, an email platform with one broken automation, an analytics dashboard nobody opens, and a content doc graveyard. Each tool holds a piece of the truth. None of them close the loop.

A team of one cannot afford context-switching tax. Every login is a tab, every tab is a decision, and decision fatigue is the real bottleneck for solo operators. The goal is not more surface area. The goal is one loop you run every week without thinking about it.

Here is the loop. Everything below hangs off it: Connect → Execute → Measure. Connect your data so the system knows your funnel. Execute real work against it. Measure what moved. Repeat every week.

the operating rhythm: one week, three blocks

Forget the 40-item content calendar. A GTM team of one needs a rhythm it can survive on a bad week. Three blocks.

monday: plan (30 minutes)

Do not open your content tool. Open your numbers first. Look at last week's funnel and ask one question: where is the leak?

Your funnel has three stages. Top of funnel (TOFU) is people arriving. Middle (MOFU) is people engaging — reading a second thing, clicking, replying. Bottom (BOFU) is people converting — signing up, booking, buying. You do not fix all three at once. You find the stage with the worst conversion and you make that the week's single objective.

Concrete example. Say your funnel this week reads TOFU 60%, MOFU 44%, BOFU 100%. BOFU is not your problem — the people who reach the decision convert. TOFU is fine. The leak is MOFU: people show up and don't take the second step. So this week's objective is lift MOFU, and every task you pick has to plausibly move that one number. That is the whole plan. One number, one week.

(Those are dolv's own funnel numbers, by the way. We run our marketing on the same loop we sell. When we looked, MOFU at 44% was the honest bottleneck, so that is what we work on. No dashboard theater.)

tuesday-thursday: execute (the real work)

This is where a team of one usually drowns. You have a clear objective — lift MOFU — and now you have to actually produce the second-touch content, update the CRM stage on the leads who went cold, draft the nurture email, and load the follow-up. For one person that is a full week, and none of it gets measured.

Execution is the constraint. So the operating principle here is: draft in batches, approve in one sitting. Do not write one email, send it, write the next. Draft everything the objective needs, then sit down once and approve or kill each piece. Batching the decision is what makes solo execution survivable — you switch context once, not twelve times.

The pieces that lift MOFU are usually the same three every week: a second-touch asset (a comparison, a teardown, a proof piece) for people who already arrived, a CRM cleanup so warm leads don't rot in the wrong stage, and one nurture sequence that gives the next reason to engage. Ship those three, measured, and you beat the operator shipping ten unmeasured things.

friday: measure (15 minutes)

One question: did the number move? MOFU was 44% on Monday. What is it now? If it moved, keep the play. If it didn't, the play was wrong — not "do more of it," change it. This is the discipline that separates an operating system from a to-do list. A to-do list measures whether you did the task. An operating system measures whether the task worked.

Pick a North Star metric so you're not drowning in dashboards. For an early GTM motion it is almost always one number of real intent — sign-ups, qualified demos, activated accounts. Ours is GA4 sign-ups; last read, 24. Every Friday review rolls up to did that number grow. One metric on top, three funnel stages underneath, nothing else on the wall.

the minimum stack

You need exactly four capabilities. Not four vendors — four capabilities, ideally in as few places as possible.

  1. A funnel view. Something that tells you TOFU/MOFU/BOFU without you doing math in a spreadsheet. If you can't see the leak, you can't plan Monday.
  2. A place leads land and move. A CRM light enough that you'll actually update it — the second it becomes a chore, warm leads rot and BOFU quietly dies.
  3. An execution surface. Where content and emails get drafted and where you approve the batch. The approval step is not optional; it is what keeps a team of one from sending something dumb at scale.
  4. Analytics wired to the funnel. Not vanity views — the specific numbers Friday's review needs, connected back to the three stages.

The trap is buying four disconnected tools and becoming the human integration layer between them — the copy-paste operator. The whole point of the operating system is that Connect → Execute → Measure is one motion, not four apps you reconcile by hand on Friday.

the capture → list → nurture loop

Traffic that arrives and leaves is a rounding error. The loop that compounds is: capture → list → nurture.

Capture: every visitor with intent gets one low-friction ask. Not "book a demo" on a cold visitor — that's a BOFU ask on a TOFU person. Offer the next small step: a teardown, a checklist, a scorecard. Something worth an email address.

List: captured contacts land somewhere you own and can reach. This is the part most solo operators skip, and it's the expensive one. If a lead lands in an isolated tool you can't email from, you don't have a list — you have a spreadsheet you'll never open. Own the list.

Nurture: the sequence that walks a MOFU contact toward BOFU. Two or three touches, each giving a real reason to take the next step. This is exactly the machinery that fixes a 44% MOFU leak — you stop losing the people who already raised a hand.

Run this loop and every week's captured attention becomes next week's pipeline. Skip it and you rebuild your audience from zero every Monday.

where this does NOT fit (the honest part)

This operating system optimizes a go-to-market motion. It does not create one from absolute zero. If you have no product, no positioning, no audience, and no channel connected, a weekly plan-run-measure loop has nothing to plan against — you can't lift a MOFU number that doesn't exist yet.

So if you're truly pre-launch — no traffic, no list, no channel — do that groundwork first: get a page live, get one channel producing arrivals, get the first handful of leads. The moment you have a funnel with actual numbers in it, however leaky, this system starts paying off. It is a multiplier on a motion that exists, not a substitute for starting one.

The same honesty applies to automation. Anyone promising "agents that run your entire funnel while you sleep" is selling you a way to send bad work faster. The right model is human-in-the-loop: the system drafts and prepares the batch, you approve, then it executes and measures. Nothing external goes out until a human says go. That's not a limitation — for a team of one, it's the only version of automation you can trust.

put the loop on rails

You can run all of this by hand. Monday you pull the funnel, Tuesday through Thursday you draft and approve, Friday you check the number. Plenty of operators do exactly that with a spreadsheet and discipline, and it beats the tool-graveyard approach every time.

But the reason a team of one stays a team of one is the copy-paste tax between the four capabilities. That's the job dolv does. It connects your funnel data, drafts the content and CRM updates and nurture emails, holds them in an Approvals inbox where nothing sends until you approve, executes what you greenlight, and reports what moved against your TOFU/MOFU/BOFU. Your OKRs auto-sync from the funnel, so Friday's review is already written. We run our own go-to-market on it — that GA4 sign-up count and the 44% MOFU leak are ours, worked on the same loop this post describes.

If your funnel is leaking somewhere and you're not sure where, start there: grab the free Funnel-Health Teardown — paste your TOFU/MOFU/BOFU numbers and get a graded scorecard back telling you which stage to work on this week. Or if you'd rather just run the loop, start free at app.dolv.work. Don't just plan it. Dolv it.

Related reading

Watch The Loop Close: 30 Days of Dolv Marketing Dolv (the real numbers) HubSpot Is Too Expensive for Your Stage. Here's What a 5-Person Team Actually Needs. The Best Agentic AI GTM Tools in 2026

See dolv run the work

Grounded AI that executes and measures — with you in the loop.

Open dolv → Book a demo

← All articles