Reditus resources
A Day in the Life of a Fractional Revenue Team
Moving beyond founder-led sales in complex B2B.
Introduction
Every client is unique. So is the solution, the market it serves, the message that reaches that market, and the mix of channels that carries the message. Nothing in this paper is a template we copy out of one engagement and paste into the next.
What follows is a representative sample. It describes real work from real engagements selling complex B2B solutions. In any particular engagement some of it applies heavily, some lightly, and some not at all. Sorting out which is which is the first thing we do, and it is not something we presume to know before we start.
We wrote it down because most of this work is invisible from outside the company. A founder sees meetings appear on a calendar and a pipeline begin to fill. The machinery that produced those meetings sits underneath, takes weeks to build, and needs attention every week after that to keep running. Anyone weighing an investment in a revenue system should be able to see the whole of it first.
1. Where Every Engagement Starts
Every engagement starts with RAMP (Reditus Assessment and Market Plan).
RAMP is a custom program, generally five weeks, that establishes where a company actually stands, what work remains, and which gaps from earlier stages are still open. It produces real deliverables and real value on its own, and it carries no commitment to Reditus beyond those five weeks.
We start there because of what the Reditus Startup Lifecycle says about sequence. The Lifecycle describes six stages, each with a purpose, evidence that shows when the stage is finished, and a gate that ought to be cleared before the next stage is worth attempting.
| Stage | What it establishes | Exit gate |
|---|---|---|
| 1. Hypothesis | Who the customer might be and what problem is worth solving | At least one company agrees to a beta in a production environment |
| 2. Market Co-Creation | Whether the solution delivers value the customer will pay for | Beta complete, customer keeps using it, endorses the value, affirms pricing |
| 3. Product-Market Fit | Which ICP, persona, and message combination actually produces demand | Five BANT-qualified leads from the same ICP, persona, and message combination |
| 4. Go-To-Market | Whether that demand converts into revenue repeatably | A functioning early revenue motion plus meaningful closed-won revenue |
| 5. Repeatability | Whether the motion runs without the founder in every deal | Documented process, consistent conversion rates, leadership in place |
| 6. Continuous Improvement | Ongoing refinement and adjacent expansion | None. The stage does not end |
A first deal means something different at each stage. At Hypothesis it means one company agreeing to run a beta in a production environment. At Product-Market Fit it means five BANT-qualified leads arriving from the same combination of ICP, persona, and message. At Go-To-Market it means closed-won revenue produced by a motion that can be run again on purpose. Selling hard before the underlying evidence exists generates activity, and activity at the wrong stage is expensive.
Most conversations that open with “we need sales” are happening somewhere in Product-Market Fit or Go-To-Market. That is where the rest of this paper concentrates.
2. Marketing and Lead Generation
Single-channel marketing rarely works. Several channels have to run at once, and each has to reinforce the others; a cold email lands differently when the recipient can find a credible company behind it, and a cold call lands differently when four emails have already arrived from the same name.
What follows is the set of workstreams that we often deploy to produce qualified conversations. They are described in roughly the order they come online, though in practice several run in parallel and none of them ever really stop.
2.1 Diagnostic and Foundation
Before any outreach happens, we settle who the customer is and what to say to them.
That begins with defining and then refining the ICP and the personas inside it, and developing a positioning and message hypothesis to test. Underneath both sits the PMF Matrix, which maps combinations of ICP, persona, and message. The Matrix is the targeting logic everything downstream depends on. Lists are built against it. Message variants are written against it. Call scripts are written against it. When a combination starts producing qualified conversations, that is the cell we scale; when one produces nothing after a fair test, we stop paying for it.
| ICP 1 | ICP 2 | |||||||
|---|---|---|---|---|---|---|---|---|
| Persona 1 | Persona 2 | Persona 3 | Persona 1 | Persona 4 | ... | |||
| Message A | Testing | – | – | Testing | – | ... | ||
| Message B | Testing | – | Testing | Testing | Testing | ... | ||
| Message C | – | Failed | – | – | Testing | ... | ||
| Message D | – | Testing | Testing | – | Testing | ... | ||
| Message E | ... | ... | ... | ... | ... | ... | ||
Table 1: Sample PMF Matrix
Getting to a Matrix worth building on takes competitive research, market research, and interviews: with existing customers, with prospects, and with closed-lost accounts. It also takes riding along on live sales meetings. Founders usually know their market well. What they rarely have is the specific language buyers use when describing the problem to each other, which is what makes cold outreach read as though it came from someone who understands the business.
2.2 Website and Collateral
By the time a prospect agrees to a meeting, most of them have already looked the company up. Some looked it up before deciding whether to reply at all.
So we develop and publish case studies and testimonials, develop the sales collateral the team will actually use in a deal, and build or update the website itself. This is not brand work. It is the material a buyer checks against before spending an hour of their own time, and the material a champion forwards internally when they have to explain the choice to someone else.
2.3 The Content Authority System
The Content Authority System is built in three layers, each doing a different job.
Layer 0 is the manifesto: the founder’s point of view, written out at length, naming the model and the terminology the company will use from then on. It is the credibility asset everything else points back to. Reditus wrote its own; the Reditus Startup Lifecycle and the Reditus B2B Buyer Model discussed later in this paper came out of that exercise.
Layer 1 is search. It starts with an SEO audit, then keyword and topic research, then a blog topic map, then the posts themselves published on a regular cadence. This builds organic authority over time and, more immediately, gives outbound something real to reference.
Layer 2 is AI visibility: how the company shows up when a buyer asks ChatGPT, Perplexity, Claude or Gemini about the category, the problem, or the competitors. Buyers increasingly research this way, and a company invisible in those answers is invisible at exactly the moment a shortlist gets drawn up.
Alongside all three, LinkedIn posts go out timed to Layer 1 and Layer 2 releases, from the company page and from the founder’s personal profile.
The reason this matters to a first deal rather than to some later brand goal is simple: prospects look you up before they take the call. What they find, or fail to find, is reputation infrastructure, and it is doing work whether or not anyone is managing it.
2.4 Outbound Infrastructure
This is the part no prospect ever sees and the part most likely to sink a campaign without you ever knowing.
We acquire dedicated sending domains, separate from the company’s corporate domain, so that any deliverability damage stays away from the email the business runs on. We configure DNS on each of them: SPF, DKIM, and DMARC, and we forward web traffic to those domains to the company’s.
We provision mailboxes, using a mix of Google and Microsoft accounts. Then we warm them, which is a multi-week process of building sender reputation gradually before any real volume goes out. Once live, deliverability gets monitored continuously: spam testing, blocklist checks, and ongoing inbox health.
Skipping this is the most common reason cold outbound fails, and it fails invisibly. The campaign looks like it is running. Emails go out and nothing bounces in an obvious way. The messages are simply landing in spam folders, and by the time anyone works out why, the domain reputation is already spent.
2.5 List Building and Targeting
Lists get sourced from Apollo and LinkedIn against the ICP and the PMF Matrix, then enriched, verified, and segmented.
Every address runs through ZeroBounce, which does two things: confirms the address is deliverable, and identifies the receiving SMTP provider so that sends can be matched to the right sending mailbox. Exclusion lists get maintained throughout, covering existing customers, anyone on a do-not-contact list, competitors, and partners.
Lists are not built once. As the ICP sharpens against real market response, the list gets refreshed to match.
2.6 Campaign and Sequence Design
Message variants are developed from the PMF Matrix rather than from a template library, then built into multi-touch sequences that coordinate email, LinkedIn, and phone.
The sequences get tested and iterated against reply data. Campaigns are monitored continuously for bounce rates and spam complaints, both of which are early evidence that something upstream needs correcting. Replies are answered manually, by a person, because the point of the sequence is to start a conversation and an automated response to a real reply ends one.
2.7 LinkedIn Connection and Messaging
LinkedIn runs as its own channel with its own target list, its own messaging, and its own monitoring cadence.
It also requires the founder’s own profile to be in order, since a connection request from a thin or outdated profile gets ignored. That review usually happens early, and it is one of the few pieces of this work that a founder notices immediately.
2.8 Founder Network Outreach
The founder’s own network is almost always underused.
We work through it with them to identify people who fit the ICP, then work out how to arrange a warm introduction. These are the highest-converting conversations available to an early-stage company, and they cost nothing but attention. They also run out, which is why they supplement the outbound engine rather than substitute for it.
2.9 Trade Shows and Conferences
Events get vetted against the ICP and the PMF Matrix. The question is the quality of the attendee list, not the size of the show or the prominence of the booth.
Once an event is chosen, preparation covers space, booth and equipment, collateral, and PR. Pre-show outreach starts well before anyone travels, booking meetings with target accounts using the same list and the same campaign engine already running. On-site, the work is lead capture, real-time CRM logging, and a staffing plan that decides in advance who talks to whom, since the founder’s time at a show is the scarcest resource in the building.
Follow-up begins immediately after the show, because event leads go cold within days. Leads route into the existing outbound and CRM pipeline rather than into a separate process, and contacts who are not sales-ready feed back into the list for nurture.
An event is not a separate motion. It is the same system pointed at an in-person moment.
2.10 Revenue Operations
None of the above can be measured without the operating layer underneath it, and we provide that layer as part of the service rather than asking a client to buy and configure it.
Among dozens of tools, Salesforce is set up and configured: stages, fields, ownership rules, and the reporting objects that let a founder see the pipeline without asking anyone. Databox is configured for pipeline and activity dashboards. Apollo.io and ZeroBounce handle contact and account tracking and data hygiene. ConnectAndSell provides the autodialer, with its lists managed alongside the email campaigns rather than separately.
Then a reporting cadence gets established: what is measured, how often, and what each number is supposed to tell us. Without this, whether the work is producing anything is a matter of opinion.
2.11 The Outbound Execution Layer
The cold caller is a person, and sourcing and onboarding that person is its own workstream.
They get trained on the ICP, the message, and the objections they will actually hear. Their call scripts and talk tracks come out of the same PMF Matrix that produced the email variants, so that a prospect who received four emails and then takes a call hears one coherent company rather than two disconnected efforts. Once calls start producing real response data, a QA and coaching loop keeps the calls improving.
2.12 From Lead to Sales
The last piece of the marketing workstream is the handoff.
That means a discovery structure and explicit qualification criteria, and it means a defined process for moving a qualified lead from marketing into sales, with the context intact. Deals lost at the handoff are lost quietly, and they look like marketing produced poor leads when in fact nobody wrote down what a good one was.
The workstreams above are the ones we build most often for early-stage B2B companies. They are not the only ones available. Depending on the company, the diagnostic, and what the market responds to, an engagement might also include digital ads, pay-per-lead vendors, direct mail, PR, channel partners, or other tactics entirely. Which of these belong in a given engagement, and in what mix, gets designed for that company specifically, then measured and modified as real results come in.
3. Sales
Marketing and lead generation get you to a qualified conversation. What happens between a qualified lead and a signed contract is a separate discipline, with its own reason to be difficult.
3.1 The Sales Cycle
The typical cycle runs in five stages, but these can be changed according to a client’s specific product, market and needs.
Stage 1, Qualified. The opportunity meets ICP and PMF Matrix criteria and clears initial discovery on BANT.
Stage 2, Needs Analysis. Structured discovery expands past the first contact to the full buying group, surfacing who else carries consequence on this decision, and why.
Stage 3, Demo. A solution walkthrough built around the specific stakeholders and objections that Needs Analysis surfaced. Not a general product tour.
Stage 4, Proposal. Commercial terms go on the table. This is where a deal stops being about the champion’s enthusiasm and starts running into the buying committee’s real tolerance for risk.
Stage 5, Closed Won. Every required stakeholder’s tolerance has been satisfied at the same time, not just the champion’s.
Closed Lost. Not to be ignored. The cold caller calls back in to learn why so we can update the approach.
3.2 Why Complex Sales Is Complex
Anyone who has sold complex B2B solutions for long has watched a deal that looked finished stall and then slowly die. The value was clear. The champion was engaged. The ROI case held up. No new information arrived and nobody raised an objection out loud. The deal simply stopped moving.
Reditus published a foundational paper on why, the Reditus B2B Buyer Model. Its argument runs roughly as follows.
A complex B2B purchase is, by definition, a committee decision. There is rarely a single decision maker, even when only one person signs. Decision power sits with multiple individuals, each of which personally carries the consequence of the outcome. This is not necessarily who holds the budget or the senior title.
Each of those people evaluates the purchase along two dimensions that have very little to do with ROI or functionality. Selfish Utility is what the decision does to them. Identity Utility is what the decision says about them. In that two-dimensional space, each individual has a tolerance curve, a boundary past which they will not say yes regardless of the merits, and that boundary moves over time.
A deal closes only when every required stakeholder’s tolerance is satisfied at the same moment. When those curves do not overlap, no amount of persuasion, executive sponsorship, or ROI demonstration will force convergence. The system cannot produce an outcome that exceeds what its participants can personally tolerate.
That is the structural reason safer options beat better ones, why deals collapse late without new information, why doing nothing so often wins, and why timing matters more than logic alone would predict.
The practical consequence for a first deal is this: closing is not the product of a good pitch at Stage 3 or Stage 4. It is the product of Stages 1 through 4 having surfaced and managed consequence across the whole buying committee. That is process, and it is the reason the sales stages above are built the way they are.
3.3 Objection Handling and Multi-Threading
Objection handling gets refined from real conversations rather than written in advance from a rebuttal list, and each objection gets tied to the specific stakeholder whose consequence produced it. A procurement objection and a security objection are not the same objection wearing different clothes.
Multi-threading starts at Stage 2, not at the point where the champion goes quiet. Closed-won deals consistently show a significantly higher number of buyer contacts than lost deals do. What closing actually requires, procedurally, is re-engaging the full stakeholder map from Needs Analysis when the proposal lands, rather than re-pitching the person who liked it in the first place.
4. What This Looks Like in Practice
Two views, at different resolutions. One week of activity across a client’s whole engine, and then a single meeting traced from first touch to booked call.
4.1 One Week
The following is a real seven-day rolling window for one client.
| Seven-day rolling activity | Count |
|---|---|
| Cold-call dial attempts | 1,968 |
| Conversations | 53 |
| Answered, no real conversation | 21 |
| Emails sent | 1,448 |
| Meetings booked | 3 |
Three meetings. That is the output of the week, and it is a good week.
The number worth attention is not the ratio, it is the denominator. Almost two thousand dial attempts and roughly fifteen hundred emails are not activity one person can generate alone. They are the output of the list, the campaign engine, the warmed sending infrastructure, the autodialer, and a trained caller, all built beforehand and all running at once.
4.2 One Meeting
Below is the complete activity log behind a single booked meeting: a COO at a target account, from first dial to accepted invitation.
Eight dial attempts and four cadence emails over sixteen days, coordinated between the cold caller and the sales rep, before the contact picked up and the meeting was scheduled.
| Date | Activity | Owner |
|---|---|---|
| Day 1 | Call attempt | Cold Caller |
| Day 1 | Email: #1 in cadence | Sales Rep |
| Day 3 | Call attempt | Cold Caller |
| Day 4 | Call attempt | Cold Caller |
| Day 4 | Email: #2 in cadence | Sales Rep |
| Day 5 | Call attempt | Cold Caller |
| Day 5 | Call attempt | Cold Caller |
| Day 5 | Call attempt | Cold Caller |
| Day 8 | Email: #3 in cadence | Sales Rep |
| Day 11 | Email: #4 in cadence | Sales Rep |
| Day 15 | Call attempt | Cold Caller |
| Day 16 | Call attempt | Cold Caller |
| Day 16 | Call connected. Meeting scheduled | Cold Caller |
| Day 16 | Email: meeting invitation accepted | Sales Rep |
The calls and the emails are not two separate efforts that happened to hit the same person. The emails were arriving between the dial attempts, from a name the contact would recognize by the time the phone finally connected on the sixteenth day.
4.3 The Arithmetic of a First Deal
Two industry averages are useful here.
In B2B, it takes roughly four meetings on average to produce one qualified opportunity. And a qualified opportunity in a complex sale has roughly a fifteen percent chance of closing, higher for shorter cycles and smaller deals, lower for longer and larger ones. A complex deal that does close takes anywhere from three to twelve months, sometimes more.
Run those against the week above and the activity that goes into a program before finding a single closed-won deal, looks like this.
| To produce one closed-won deal | At this run rate |
|---|---|
| Qualified opportunities needed, at a 15% close rate | about 6.7 |
| Meetings needed, at 4 meetings per qualified opportunity | about 27 |
| Weeks at this run rate to generate that pipeline | about 9 |
| Cold-call dial attempts over that span | about 17,700 |
| Conversations over that span | about 480 |
| Emails sent over that span | about 13,000 |
| Average time to close once qualified, on a six-month cycle | plus 6 months |
| Total elapsed time to a first closed deal | roughly 6 to 9 months |
Assumptions. Four meetings per qualified opportunity and a fifteen percent qualified-to-close rate are complex-sales averages, not this client’s own figures. The six-month cycle is the midpoint of a realistic three to twelve month range. Shorter cycles and smaller deals should close at a higher rate than fifteen percent; longer and larger ones lower.
Nothing in that table is unusual. It is what a complex B2B sale costs to produce, and every company selling into this kind of market pays it, whether or not anyone is counting.
5. What This Adds Up To
None of the workstreams above produces a deal on its own.
The infrastructure produces no meetings. Neither does the content or the contact list. A caller working without a list, without warmed domains, without a sequence arriving alongside their calls, and without a CRM to work from produces very few. The deal comes from all of it running at once, for long enough that the arithmetic has room to work.
This article describes a typical complex B2B GTM motion. Your company is not typical; nor is anyone else’s. That is why every engagement begins with RAMP, so we find out what actually applies to you before assuming any of this does.
Get in Touch
If what you’ve read here resonates, begin with a quick check on fit.
No pitch. No pressure. Just context.