Frequently asked questions

What does signalrev actually do?

Three packages, each bought on its own. Position works out what your customers are actually buying, puts it into words your team can use, and gives your web person the copy and wireframes to build from. Presence takes that onto LinkedIn and into your first outreach. Inspection tests your live deals against six gates so you can run them yourself, and a weekly review is available as a separate block. Your next sales hire inherits the system, not a pile of hunches you never wrote down. Ongoing support after delivery is optional.

How do I know who my real buyer is?

Your real buyer is the person who has the problem you solve and the authority to pay to fix it. In many B2B businesses, that is a business-side executive rather than the technical team who championed the purchase. Map how the decision gets made. Find the person who approves it and build your pipeline around them.

My ideal buyer definition feels too broad. How do I narrow it without cutting off too much opportunity?

Start with your best customers, not your aspirational ones. Look for the pattern in the three or four deals you are most proud of: industry, company size, the specific problem, the role of the person who bought, how quickly they decided. That pattern is usually narrower than founders expect. Narrow targeting makes outbound efficient and the messaging specific enough that the buyer recognises themselves.

Why does my pipeline dry up when I get busy with delivery?

This is the feast-or-famine cycle: sell hard, land the work, disappear into delivery, then panic when the project ends and the pipeline is empty. It happens because the pipeline lives in your head, not in a system. That is what founder-led selling looks like while you are still the only person who can sell it. The fix is a documented buyer definition and a weekly review rhythm that runs whether you are busy or not.

What is a pipeline review, and how often should I do it?

A pipeline review is a structured look at every active deal: what has moved, what has stalled, and what you are doing next. Weekly is the right cadence for a founder-led business. Your own solo review is a short block of time, same time each week. The point is decision, not reporting. One concrete action comes out of every session. A quiet week still gets reviewed. A deal that didn't move is evidence too, and it's usually the one that needs the decision.

How do I know if a deal in my pipeline is real?

A deal is real when the buyer has confirmed the problem, you understand how they make the decision, and there is an agreed next step with a date. Anything missing one of those elements is a prospect, not a deal. CRMs default to showing activity (meetings held, emails sent) rather than progress (evidence of fit, decision process mapped, path to close). The two are not the same.

How do I manage multiple active sales opportunities as a solo seller?

Write down the next step and the date the moment a call ends, before three deals blur together by the end of the week. The weekly review becomes a check against what's already written, not a memory test. A system holds which deal is where. You hold the judgement on what happens next.

What is the difference between sales activity and sales progress?

If your calendar is full of sales calls but revenue isn't moving, you're measuring activity, not progress. Activity is meetings booked, emails sent, and calls made. Progress is evidence that a deal is closer to closing: the buyer confirmed the problem, you mapped the decision process, and there is an agreed-upon next step. CRMs default to measuring activity because it is easy to count. A full calendar and an empty pipeline are not contradictions. They are the most common pattern in founder-led sales.

What is a revenue operating system?

A revenue operating system is the methodology layer that runs on top of a CRM. The CRM records what your team did; the revenue operating system defines what each deal must show to advance, what the unit of measurement is, and when stale deals get flagged out. Without it, a CRM is a list with status fields.

How is a revenue operating system different from a CRM?

The CRM is infrastructure: it stores deals, stages, contacts, activity. A revenue operating system is methodology. It defines what counts as a real stage transition, how each deal connects to a buyer's problem, and when stale deals get flagged. The two work together; neither replaces the other.

My CRM is a mess and I don't trust what's in it. Do I clean it up or start over?

The mess is a symptom of missing methodology, not a data problem. A CRM fills with dead deals and untouched fields when there's no rule for what counts as progress and no rule for when a stale deal gets flagged out. Wiping it and starting fresh without installing those rules just produces a cleaner-looking graveyard on the same timeline. Fix the rules first: what a deal has to show to advance, and when it gets flagged stale. Then the cleanup usually takes days, not a rebuild.

Why do founders need a revenue operating system at the 5 to 100 person stage?

Sales works fine when you run every deal yourself. It falls apart the moment you hand deals to someone else, because the judgement never transfers with them. At the founder-led stage, judgement about deals lives in the founder's head. As the team grows, that judgement has to be transferred or systematised. A revenue operating system makes the qualifying happen in the system rather than in memory, which is what enables the founder to step out of every deal review without losing accuracy.

What are the three defaults founders fall into before they install a revenue operating system?

I'm Richard, and the founders I work with try the same three fixes, and each one stalls the same way. First a spreadsheet to track deals. Then a senior hire to run them. Then a CRM to systematise the work. Each is a response to the symptom of the previous failure. None of them is wrong. Each just needs the methodology written down first, so the spreadsheet, the hire and the CRM have something to run on.

Should I build a sales system before I hire my first salesperson?

Advisers often recommend hiring, and for many companies they're right. Bessemer's playbook says your first seller should be someone who can sell directly and build repeatable sales processes. What they can't build is the part that lives with you: why your customers actually buy. Work that out first, or alongside the hire, and they have something to build on.

When is a startup actually ready to hire its first sales hire?

Customer count is the usual marker, and whether there's a system to hand over matters as much. First Round says at least ten customers, probably closer to twenty five. Bessemer says founders should drive the first twenty or so themselves. Both say those customers shouldn't all come from your own network. Familiar connections produce false signals of fit. Bessemer's marker for a VP of Sales hire is ideally approaching $1M ARR, with strong retention. That hire comes later than this one. By then the product is proven, the budget is real, and the founder is at maximum urgency to get the system out of their head. Hire before that point and the new person spends their first months building the basics.

Why do first VP of sales hires often struggle?

Because the sales motion still lives in the founder's head when the hire starts. The new hire gets a title, not a system: no buyer definition, no stage gates, no weekly rhythm. Months get spent rebuilding what should already exist, and the board starts asking why pipeline hasn't moved. If you already made this hire and it did not work out, the cause is often not the person. They arrived before there was anything written down to build on.

How do I prospect consistently without a sales team?

By running a repeatable weekly motion instead of random acts of sales, the sporadic bursts of outreach that feel productive for a week and then vanish. Define three to five target accounts at a time, not fifty. Use LinkedIn to understand the buyer before you contact them. Reach out once with something relevant and direct, follow up once, and move on if there is no signal. Quality of targeting and clarity of message matter more than volume.

What is the difference between network-dependent selling and repeatable outbound?

If every deal you've closed came from someone who already knew you, and that well is starting to run dry, this is the shift you're avoiding. Network-dependent selling closes deals with people who already know you. It works until the network is exhausted. Outbound reaches buyers who do not know you yet, using a defined buyer profile, a researched message, and a consistent cadence. Network selling runs out. Targeted outbound is what replaces it.

How do I qualify sales conversations without using heavy frameworks?

Two things tell you whether a conversation is worth pursuing: the person has the problem and the authority to fix it. If both are present, find out whether there is a reason to move now. You don't need the full BANT or MEDDIC checklist for that. Ask directly, listen carefully, and move on quickly if either is missing. That's the entry test. A deal is real once you also understand how they decide and there's an agreed next step with a date.

How do I create clear decision points in sales conversations?

Ask one question at the end of every conversation: what happens next, and when? A deal progresses when the buyer agrees to a specific next step with a date. If a prospect goes dark right after a call that felt great, that is rarely a follow-up problem. It means the call ended on enthusiasm instead of an agreed next step with a date. If they will not commit to that, the deal is not moving regardless of how well the conversation went. Decision points are about clarity for you and for the buyer, not pressure.

How do I build a sales process as a founder who is also running the business?

Start with buyer definition, not tooling. The founders I work with usually try to fix the sales motion by adding a CRM or a sales hire first. Neither works until the positioning, the buyer map, and the messaging are written down somewhere other than your head. Once those exist, the tools hold the knowledge and the process follows from it.

Which tools does the system use?

Tools that are the right size for founder-led sales. Your CRM (HubSpot or the one you already use) holds the pipeline, Notion holds your decisions, and Claude helps me draft, sort and flag. The judgement, the sessions and every call with you are mine. Recording your own sales calls is optional. All are free or low-cost to start, and simple enough that one person can run them. If you already use other tools, we work with what you have.

Do I need LinkedIn Sales Navigator?

No. The methodology works with LinkedIn free, standard LinkedIn, or Sales Navigator. If you are on free or standard, we start there. The prospecting motion mostly runs on search, profile views, and direct messaging, which work at any tier. If you are already on Sales Navigator, the system uses its advanced search and lead lists to sharpen your targeting. If you are not on Sales Navigator yet, we will tell you when upgrading makes sense for your situation, usually once your buyer definition is precise enough that the filtering is worth paying for. You do not need to buy anything before we start.

What sales tools do I actually need at seed stage?

The founders I work with almost always assume they need a sales stack before they can sell properly. You don't need to buy one before we start. The core system runs on a CRM such as HubSpot, Notion and Claude. A call recorder is optional. Tool subscriptions are yours, and most start on free or low-cost tiers. If you are already using other tools, the methodology adapts. If you use Teams for calls or an existing CRM, we work with what you have and recommend changes only when they make a practical difference.

Do I need to be technical to use the system?

No. If you can use email and a spreadsheet, you can run this system. Each package sets up the tools it needs as it goes. You learn the tools by using them on real deals, not by studying documentation. Inspection is where much of the learning happens, and that is a conversation, not a software exercise.

How long does it take?

Position runs weekly by default, 5 to 8 weeks. Twice a week gets it done in about 3 weeks. Presence runs 5 to 7 weeks, then you run the 30, 60 and 90 day plan yourself. Inspection is weekly and runs 3 to 4 weeks. The weekly review is a separate block.

How do I know if I need positioning?

If buyers ask what you do after reading your site, if referrals describe you as something else, or if you pitch differently on every call, position is likely to help. If your message is already clear and buyers understand it, but you are not reaching enough of them, start with presence instead. We work out which on a 30 minute call.

What do I have at the end?

Position: a buyer definition, a positioning statement in one paragraph a stranger can repeat back, the customer results and stories that back the claim, four pages of website copy with wireframes for your web person to build from, and your LinkedIn headline and About section rewritten to match. Presence: a starting list of 10 accounts with the people to contact and the reason they might be in the market, five follow-up sequences, six posts, your LinkedIn profile, and a launch plan you run over the 30, 60 and 90 days after the engagement. Inspection: six gates that test each deal, from the buyer's problem to whether you can reach the person who says yes. If you add the weekly review: a weekly review protocol, stage-velocity flags, and your CRM pipeline stages and fields set to match the review.

What happens after the engagement?

What's yours when the engagement ends: everything built during the engagement. You can run all of it independently. The system doesn't depend on us. What you built stays in your accounts, and your next hire starts from it. Founders who want to keep the weekly review going afterward can, through optional ongoing support.

Is this sales training?

It's coaching on your real pipeline, with a system left behind. No slides, no course modules, no frameworks taught in the abstract. You learn by working your actual pipeline with a system underneath you. Every session looks at real deals and real conversations. What happened and what to do differently. The founder who finishes has not completed a programme. They have built and run a revenue system, and they have got better at selling by using it.

Can I build this system myself without signalrev?

Yes. The tools are not proprietary and the approach is not a secret. The hard part is what you put into them, the positioning, the buyer map and the messaging that moves your buyers, and then running it on your own deals until it holds. signalrev compresses that from months of trial and error into 3 to 8 weeks per package.

VP of sales vs fractional CRO vs sales consultant, what does a seed-stage founder actually need?

Depends on what's missing, and many founders end up with one of them. A VP of Sales runs and grows a sales team. A fractional CRO brings senior judgement part time. A coach or consultant improves how you sell, and we do some of that too, on your real pipeline. Whichever you choose, they work faster from a written buyer definition and a weekly review than from what's in your head. That's the part we build.

How is this different from hiring a fractional CRO?

It isn't either-or. Plenty of founders at your stage use one, and a good one brings judgement you don't have. What they usually don't start with is why your customers buy you, or a weekly review you run yourself. We build those, so whoever you hire walks into something they can use.

Is signalrev right for me if I already have some sales process?

Possibly. If your process is inconsistent, or deals close but you cannot explain why, then yes. signalrev is most useful when there is real commercial activity to work with. If you are pre-revenue, get a few customers first. If you have a repeatable system that is performing well, you probably do not need it.

Does this work for services businesses, not just SaaS?

Yes. The fit is a founder-led B2B company of 5 to 100 people with a relationship-led sale, whether you sell software or services. What matters is whether a founder owns the revenue decision and needs a buyer definition, stage gates, and a weekly rhythm installed under it. High-volume or ecommerce-style selling is the one shape this doesn't fit.

Who is signalrev not for?

If you have no paying customers yet, want someone to run the pipeline for you, need outbound at volume, can't make a weekly decision, want a training course, or already have a sales leader running a working machine. Enterprise RevOps builds and custom CRM sprawl aren't in scope either.

What happens to my data?

Your data stays in your accounts, apart from recordings of our own calls and the working copies I hold while we work, and any call content I send through Claude for analysis. Your CRM and your other tools run on your own subscriptions, and I work in them with access you grant. When the engagement ends, I hand over everything I built, delete my copies within 30 days, and you remove my access. If you choose ongoing support, I keep only what that work needs, and delete it within 30 days of stopping. Our calls together are recorded in my own account. I delete those recordings within 30 days of the engagement ending, or sooner if you ask. I don't use your recordings or data to train AI models.

Are my calls recorded, and what do I tell people?

I record our calls together, so in position, what you say feeds your buyer definition, guide and writing skill. Recordings of your own sales calls are optional, and without them we work from your notes and your CRM. If you want them, I suggest a recorder in your own account. You choose it and run it, and I don't set it up. When I use AI to analyse recordings, it runs through Claude under my own paid account, with training on your data switched off. You make sure your buyers know a call is being recorded, under the rules that apply where you and they are. Some recorders appear on the call where everyone can see them. If yours doesn't, you say so at the start.