The SaaS Distribution Course #18: How Workshop Grew Webinars From 5 to 500 With Ungated Content

TL;DR

Workshop spent about nine months selling an intranet and won roughly three customers. Prospects had started naming internal email as their real problem around month four, but the founding team kept defending the more novel product. When it finally rebuilt around email, Workshop signed 10 customers in 30 days.

That is the clean product-market-fit contrast. The deeper distribution lesson is what Workshop built while the product was still wrong: a weekly newsletter, practical ungated resources, long-tail search surfaces, co-marketing relationships, and a recurring webinar program. Founder Rick Knudtson says the team published about 50 resources in 12 months and grew webinar attendance from five people at the first session to 500 at a recent one.

The reusable system is sales-call research → useful artifact → search and partner reach → recurring webinar → sales pipeline → account expansion. Workshop reports more than $10 million in ARR, just under 1,000 customers, and about 140 employees. Those figures and the channel milestones are founder-reported. No public source discloses content-sourced revenue, CAC, payback, or conversion rates.

What you will build

You will build an evidence-to-audience distribution system for a B2B SaaS before it has reliable inbound demand. Its outputs are a sales-call ledger, an artifact backlog, a long-tail resource library, a partner distribution map, a recurring webinar, a sales-routing rule, and an expansion-friction audit. Every stage has a pass condition so attention cannot be confused with revenue.

Use this system if

• you can speak with at least five relevant buyers every week;
• their problems can become reusable templates, calculators, benchmarks, or checklists;
• the category has practitioners, communities, or newsletters that already aggregate trust;
• one topic can support both a self-serve artifact and a live teaching session;
• your sales process can preserve the topic that created each opportunity.

Do not use it if

• you will publish generic search pages without recent customer evidence;
• you need content to rescue a product buyers repeatedly refuse to pay for;
• your audience definition is broader than your ideal customer profile;
• you cannot run the cadence for at least two quarters;
• you plan to report subscribers or attendees as revenue.

Verified case snapshot

Stage	Evidence	Limit
Early 2021	Day-one Happy Monday Club newsletter started with zero subscribers	Founder-reported; early growth curve is private
First nine months	About three customers bought the intranet product	Founder-reported; contract values are private
30-day rebuild	Ten customers signed for the email product	Founder-reported product-market-fit signal
First 12 months	About 50 ungated resources targeted practical buyer jobs and long-tail searches	Traffic and sourced-pipeline data are undisclosed
Webinar program	Attendance grew from five at the first session to 500 at a recent session	Founder-reported endpoints; attendee quality is unknown
Current newsletter	Happy Monday Club has a reported 50,000 subscribers after five years	Unaudited count; engagement and acquisition mix are private
Current company	About 140 employees, just under 1,000 customers, more than $10M ARR	Founder-reported and unaudited

The primary evidence is the complete September 2026 SaaS Club interview and transcript. Workshop's current resource center independently shows the continuing format mix: templates, original research, guides, customer stories, on-demand events, and upcoming webinars. It cannot establish how many historical assets ranked or converted.

Independent local reporting adds company context. In December 2025, Silicon Prairie News reported that Workshop had passed 100 employees and noted its 2023 Series A plus a later financing. Workshop's own 2023 announcement documented a $12 million Series A after a $5 million seed round. Funding and prior founder credibility matter as advantages; they do not prove the distribution channels caused current revenue.

The model: turn each buyer problem into the next distribution input

Content systems often fail because each channel receives independent ideas. The SEO team writes keywords. The newsletter team fills a calendar. Events invite whoever is available. Sales sees none of the context. Workshop describes a tighter loop.

1. Sales calls reveal repeated jobs and the buyer's language.
2. The team turns one repeated job into a useful, ungated artifact.
3. Search and partners put that artifact in front of a defined market.
4. A webinar teaches the same workflow and captures deeper questions.
5. Qualified intent reaches sales with the originating problem attached.
6. Customer usage reveals where pricing or permissions block internal spread.
7. Expansion conversations create the next research inputs.

The loop works because the output of one stage reduces uncertainty in the next. Calls remove topic guesswork. An artifact gives partners a reason to share. A webinar makes a search topic interactive. Sales receives problem context. Expansion behavior tests whether the product and pricing support broader use.

Step 1: make sales calls your research desk

Workshop initially believed a better-designed intranet would win because few employees loved their existing intranet. The sales evidence resisted that thesis. Buyers used “intranet” for different jobs: files, directories, news, or a final attempt to repair communications. There was no shared urgent outcome.

One complaint did repeat. Email remained the main internal channel, but communications teams lacked reliable delivery, governance, brand control, and analytics. At a large enterprise, a cheap marketing-email tool could hit security filters or contaminate marketing data. Sending a critical message to 100,000 employees within minutes was infrastructure work, not only email design.

Workshop heard the signal around month four and waited until roughly month nine to act. Knudtson attributes the delay partly to ego after selling Flywheel. Capital and a network made the seed round easier; they did not make the original thesis correct.

Create a call ledger with these fields:

• job attempted in the last 30 days;
• current tool and manual workaround;
• failure mode, consequence, and frequency;
• words the buyer uses before hearing your category language;
• artifact requested or assembled manually;
• commercial behavior: no action, next meeting, pilot, or payment.

Pass condition: five buyers independently describe the same job and at least two take a stronger commercial action. Stop condition: the complaints share vocabulary but require different products, or interest disappears when a paid next step appears.

Step 2: run the smallest paid contrast

An intranet was difficult to test incrementally because buyers expected a wide product. Email analytics and delivery formed a narrower wedge that the small team could rebuild in 30 days. Workshop then contacted the people who had raised their hands during the earlier calls.

The reported result, 10 email customers in 30 days against about three intranet customers in nine months, was stronger than a survey or a spike in traffic. It compared paid behavior under the same team, market, and period of company development. It was not a perfect experiment, but it was clear enough to concentrate the roadmap.

Define your contrast before rebuilding: the narrow workflow, delivery deadline, buyer list, price, minimum customer count, and decision date. If the new wedge produces only more calls or compliments, you have learned about messaging, not willingness to pay.

Step 3: ship the artifact instead of describing the problem

Workshop did not claim authority because its founders had internal communications job titles. It created authority by listening across many calls. When communicators described planning content in spreadsheets, the team built an internal communications calendar. When they needed a comparison point, it built benchmark material.

Knudtson contrasts this with the traditional gated ebook. The team published the useful object without requiring a form first. About 50 such resources over 12 months created many narrow search surfaces. A person looking for a calendar, template, or benchmark could finish part of the job before deciding whether Workshop was relevant.

Use a six-line artifact brief:

1. Evidence: the repeated call notes that justify the topic.
2. User job: one sentence beginning with a verb.
3. Object: the file, worksheet, benchmark, or calculator delivered.
4. Completion: what the buyer can finish in 20 minutes.
5. Discovery: the exact long-tail phrase and relevant partner audience.
6. Bridge: the next product or sales action that follows naturally.

Pass condition: the asset completes a job without product access and attracts at least five relevant visitors or direct shares. Stop condition: the page exists only to rank, repeats generic advice, or hides the promised object behind a form.

Step 4: pair owned reach with borrowed trust

Workshop launched the Happy Monday Club newsletter on day one. The first readers came through the founders' existing networks. Growth then included co-branded opportunities with newsletters and communities serving the same market. After five years, Knudtson reports 50,000 subscribers.

A prior exit and local network gave Workshop a head start most founders will not have. The useful substitution is specificity. A small operator newsletter can be a better partner than a large founder audience when its readers share one immediate job your artifact solves.

Score possible partners on audience overlap, topic credibility, reciprocal value, and the ability to repeat. Do not ask them to promote a product announcement. Invite them to improve an artifact, compare a benchmark, or teach a workflow. The resource earns the introduction; your product is the optional continuation.

Step 5: convert a proven topic into a recurring webinar

Workshop began webinars during the first year. Five people attended the first one. Instead of treating one small room as a channel verdict, the team kept a monthly cadence, sometimes running two sessions. A recent session reached 500 attendees, according to Knudtson.

Guests were part of the mechanism. Workshop invited practitioners who knew more about the topic and already served an audience. This increased teaching quality and created a co-marketing surface. The current resource center shows that the format continues across research discussions, customer workflows, planning, AI, frontline communication, and newsletter practice.

Run the monthly loop:

1. Select the resource with the strongest qualified engagement.
2. Invite one practitioner whose experience fills a real evidence gap.
3. Teach the workflow with the artifact, not a product tour.
4. Collect registration role, company, active project, and timing.
5. Log questions and unresolved jobs during the session.
6. Route qualified accounts to a human and turn unanswered questions into the next resource.

Pass condition: the webinar produces both qualified attendance and a new research input. Stop condition: attendance rises while ICP share, meetings, opportunities, or learning fall for three consecutive sessions.

Step 6: connect attention to sales without pretending it is revenue

Knudtson calls the early community and resource library the seeds of a CRM that could eventually support a sales team. Once Workshop crossed roughly $1 million ARR, the focus moved towards a repeatable sales process, seller training, and reducing dependence on founder selling.

That is a useful boundary. Content does not replace sales for a considered B2B product. It changes the starting point. The seller can know which problem, artifact, partner, and event preceded the conversation.

Use four intent routes:

• Reader: offer another closely related resource.
• Subscriber: invite them to the recurring session for that job.
• Qualified attendee: ask about the active project and timing.
• Opportunity: preserve the originating topic and channel in the CRM.

Report production, attention, intent, and economics separately. Resource count belongs to production. Subscribers and attendees belong to attention. Meetings and opportunities belong to intent. Won revenue, CAC, payback, retention, and expansion belong to economics. Workshop's public story supplies strong production and attention endpoints, but it leaves most economics private.

Step 7: remove the pricing brake on customer distribution

Distribution continues after the initial sale. Workshop observed that customers likely to retain had several departments using the platform every week, along with meaningful automation. Yet an extra-user charge forced a champion to reconsider cost and sometimes reopen procurement before inviting another department.

The company removed that charge. Its pricing is primarily based on audience size, meaning the employees a customer needs to reach, plus the channels purchased such as email or SMS. Knudtson says the goal is to make additional internal users easy and seek expansion through more audience or channels.

Public sources reveal no retention rate or expansion revenue, so do not copy the formula blindly. Run a friction audit instead. Identify the customer behavior most associated with value. Then ask whether your seat, usage, permission, or procurement rules tax that behavior before the customer experiences the benefit.

Your 12-month implementation

Cadence	Output	Decision metric
Weekly	Five call notes and one repeated-job brief	Repeated job plus buyer action
Weekly	One useful ungated artifact	Qualified use and shares
Weekly	One newsletter issue	Qualified replies and return visits
Monthly	One partner-taught webinar	ICP attendance, meetings and new questions
Monthly	CRM source review	Opportunity and revenue by originating problem
Quarterly	Expansion-friction audit	Time to add a department, workflow, or channel

Start with a six-week pilot, but judge the channel over a longer window. In weeks one and two, collect 10 call notes. In week three, ship the first artifact. In week four, recruit a guest. In week five, distribute through owned and partner channels. In week six, run the webinar and route qualified intent. Then repeat the same system with a better topic, not a completely different strategy.

What the Workshop case does not prove

It does not prove that publishing 50 pages creates product-market fit. Workshop found the decisive signal through customer conversations and a paid product contrast.

It does not prove that 500 attendees created profitable pipeline. Registration, attendance quality, meetings, opportunities, wins, and revenue attribution are not public.

It does not prove that every company should ungate everything. An artifact can be open while a benchmark dataset, diagnostic, or high-intent service has a form. The principle is to deliver the promised value before extracting contact data by default.

It does not erase Workshop's advantages. The founders had prior operating experience, network, capital, and a strong marketer in Jamie Bell. A first-time founder should narrow the market and partner set rather than expect the same starting reach.

The lesson

Workshop marketed before the product worked, but it did not use content to defend the wrong product. Sales calls eventually forced the email pivot. Those same conversations then supplied the language and jobs for a resource library. Resources created search and partner surfaces. Recurring webinars deepened the topics. Sales captured active demand. Pricing made it easier for the product to spread inside a customer.

Five attendees did not mean webinars failed. It meant the first iteration was small. The team kept the cadence, improved the subjects, borrowed practitioner trust, and let each cycle improve the next one. The visible milestone is five to 500. The durable advantage is the evidence loop between those numbers.

Sources and evidence limits

• SaaS Club episode 493, full transcript and publisher summary
• Workshop resource center
• Workshop's November 2023 Series A announcement
• Silicon Prairie News, December 2025 company profile

All early-customer, resource-volume, subscriber, webinar, ARR, and current-customer figures are founder-reported unless explicitly qualified. No public source reviewed for this course disclosed organic traffic, newsletter engagement, webinar conversion, content-sourced pipeline, CAC, payback, retention, expansion revenue, or revenue attribution by channel.