The SaaS Distribution Course #13: How Ragic Moved More Than Half Its Revenue Upmarket Without Outbound

TL;DR: Ragic did not force a horizontal no-code database through a conventional outbound sales machine. Founder Jeff Kuo says the company used consulting to finance the move to SaaS, captured existing demand with content and paid advertising, expanded from one department to the next, and worked with system integrators already trusted by larger companies. He reports that medium-to-large enterprises now contribute more than half of revenue. That number is not audited, but the sequence is unusually clear.

The warning matters as much as the result: “inbound” is not a channel strategy on its own. Ragic's system works because a broad product meets a specific operational problem, produces a visible departmental win, and gives both internal champions and outside consultants something they can extend. Remove that expansion mechanism and content only creates traffic.

What you will build

You will build an intent-to-expansion distribution system for a broad B2B product. It has five operating parts:

1. a paid service bridge that finances learning without pretending to be scalable;
2. a library of problem-led content matched to high-intent searches;
3. one narrow departmental use case with a measurable pass condition;
4. an internal expansion packet that helps the champion sell the next workflow;
5. a partner offer for consultants who already own buyer trust and implementation work.

The output is not a marketing calendar. It is a sequence in which each stage creates the input for the next stage. Your pass condition is evidence that a first use case repeatedly creates either a second department, a second workflow, or a partner introduction. If that never happens, do not buy more traffic yet.

Who this is for, and who should not copy it

This model fits a bootstrapped or capital-efficient SaaS with a flexible product, a buyer who can start inside one team, and a use case that becomes visible to adjacent teams. It is especially useful when buyers already search for the problem, but the product category is too broad for a generic cold pitch.

Do not copy it when one executive must approve a company-wide deployment before anyone can receive value, when the product has no natural second use case, or when demand must be created through a new category narrative. In those cases, founder-led outbound or account-based selling may be the right first motion. Ragic's lesson is not “outbound is dead.” It is “channel follows buying behaviour.”

Case snapshot

Stage	What Ragic did	Evidence	Limit
Cash flow	Delivered TeamSite consulting projects while bootstrapping	Several founder-reported years	No annual service revenue disclosed
Productisation	Moved from third-party service work to Ragic projects, then pure SaaS	Direct founder sequence	No exact transition dates
Acquisition	Used content marketing and paid advertising for inbound demand	Founder says this ran for many years	No spend, CAC, or channel split
Expansion	One department's workflow becomes proof for adjacent departments	Founder explanation plus customer stories	No expansion-rate metric
Partner reach	System integrators fill gaps around ERP and CRM programmes	Founder report and live partner programme	Partner count and sourced revenue undisclosed
Upmarket result	Medium-to-large enterprises contribute more than half of revenue	Founder-reported in May 2026	Not independently audited

The model: search for the pain, land the workflow, distribute the proof

A horizontal tool creates a positioning problem. “Build any database workflow” is powerful after a buyer understands the product, but weak as an unsolicited message. The prospect must do too much work to translate a broad platform into their own urgent problem.

Ragic shifted that translation closer to the buyer. Content and paid acquisition catch someone already naming a spreadsheet, approval, inventory, CRM, or workflow problem. The first department then builds something concrete. Colleagues do not have to believe a category promise; they can see a functioning form, approval path, or database. A consultant can reuse the same proof inside a client relationship.

The causal loop is therefore: named pain → high-intent visit → narrow workflow → visible result → adjacent use case → partner-ready proof. Enterprise packaging makes the final expansion commercially and operationally possible. Traffic is only the first input.

Step 1: finance the learning without confusing service with product

Ragic's first distribution stage was not SaaS acquisition. Kuo says the bootstrapped team acted as a service partner for Interwoven TeamSite. Those projects paid the bills. The company then used Ragic in customer projects before finally reaching a pure SaaS model where customers built applications themselves.

Copy the boundary, not the duration. Sell a service only when it produces reusable product learning: repeated data structures, approvals, integrations, objections, and onboarding gaps. Mark every hour as one of three types: customer-specific delivery, reusable product insight, or repeatable enablement. If customer-specific delivery stays above 60% for eight weeks, you are running an agency rather than a product bridge.

Output: a service-to-product ledger with the buyer problem, manual work, reusable product change, and next self-serve test. Pass condition: three customers can reach the same outcome with less founder labour each time. Stop condition: each new deal requires a new architecture.

Step 2: build an intent library, not a thought-leadership feed

Kuo says Ragic used content marketing and paid advertising for many years. The transcript does not reveal the split or economics, so do not invent a content-versus-paid conclusion. The reproducible decision is to target explicit operational searches rather than distribute a generic platform claim.

Build a 20-row intent worksheet. Each row contains the existing workaround, the failure event, the buyer's search phrase, the smallest workflow that resolves it, and proof required to try. Examples of failure events are “approval lost in email,” “spreadsheet takes minutes to open,” and “ERP does not cover this local process.” Ragic's own ProMedEx story begins with slow Excel files and document delays; the buyer started with one departmental configuration before other functions asked to migrate.

Publish one deep solution page and one proof asset for the same problem. Use paid search only to test whether the intent converts, not to rescue vague copy. Pass condition: at least 20% of qualified demos name the problem covered by the page that brought them. Decision gate: if clicks arrive but buyers cannot name an urgent workflow, narrow the problem before raising spend.

Step 3: design the first workflow as an expansion seed

The founder describes Ragic spreading when another department sees a working form and asks how the problem was solved. Vendor-hosted stories show the same shape. Do it Best reports that one employee's solution spread into logistics, sales, and human resources, reaching more than 30 internal users. ProMedEx describes HR and CRM migrations following an initial departmental deployment.

Make this intentional. Choose a first workflow with a visible before-and-after, a low permission burden, and reusable data for one adjacent team. At kickoff, ask the champion: “Which department will notice if this works?” At day 14, produce a one-page expansion packet with the old delay, the new cycle time, the fields already reusable, the next team's owner, and a 30-minute demonstration.

Metric: expansion-qualified accounts, defined as accounts with a named second use case and owner within 30 days. Pass condition: 30% of successful pilots produce one. Stop condition: the next use case needs a separate buyer, separate dataset, and separate implementation. That is a new segment, not expansion.

Step 4: give partners the loose ends, not the whole platform

Ragic works with system integrators and IT consultancies that already serve larger organisations. Kuo's framing is specific: partners need a flexible tool for the processes left between packaged ERP and CRM systems. The public partner programme supports database building, API integration, scripting, training, workflow optimisation, and maintenance, with commissions advertised up to 20%.

A weak partner pitch says, “resell our platform.” A useful one says, “when your ERP project leaves a spreadsheet-shaped gap, use this deployment pattern.” Create three partner cards, each with a trigger, scope, delivery time, excluded work, commercial model, and customer proof. Train on discovery and implementation, not features.

Pass condition: a partner identifies a qualified gap without your founder joining discovery. Metric: partner-accepted opportunities that reach a scoped workflow. Stop condition: partners only send logo-level introductions but cannot implement or influence the buying process.

Step 5: package the operational requirements of moving upmarket

Internal expansion and partner access fail if the product cannot survive enterprise procurement. Ragic's current enterprise plan starts at $550 per month for ten users and adds annual commitment, service-level terms, volume options, and on-premises deployment. A concurrent-enterprise plan is also listed for organisations with many occasional users. These are not just pricing choices. They remove deployment and procurement blockers created by the distribution loop.

Create an enterprise-readiness matrix before chasing larger accounts: identity and access, audit trail, data residency, support response, procurement paperwork, deployment model, and an owner for each gap. Decision gate: add a requirement only after two qualified accounts block on it, unless security or law makes it mandatory. Otherwise “enterprise readiness” becomes an endless roadmap detached from demand.

What failed, and what merely took time

Outbound was a structural mismatch for Ragic's broad pitch, not necessarily bad execution. Kuo says the team tried it and found a generic product difficult to sell cold, comparing the task to selling Excel through an outbound team. A narrow vertical workflow could have changed that fit; the evidence does not test that counterfactual.

The long consulting period was different. It felt, in Kuo's words, like being in a hole for years, yet it kept the company alive while the product became usable without services. Treat this as a timing cost with a measurable exit criterion, not romantic founder suffering. Services are useful only while product leverage is rising.

Finally, Ragic reports healthy organic growth rather than a guaranteed hockey stick. This system is built for compounding fit, not instant velocity. If your market requires venture-scale speed, the same patience may be economically wrong.

Your 30-day implementation plan

Days	Work	Output	Checkpoint
1-3	Review ten wins and ten losses by problem, trigger, first workflow, and source	Intent and expansion worksheet	One problem appears in at least three wins
4-7	Interview three customers about the search phrase and first visible result	One narrow solution page brief	Buyers use the same problem language
8-12	Publish the solution page and proof asset; run a capped intent test	Qualified-intent report	Do not scale if conversations stay generic
13-18	Instrument the first workflow and name one adjacent team	Expansion packet template	Second use case has an owner and reused data
19-24	Recruit five consultants around one loose-end deployment pattern	Three partner cards and one enablement call	One partner scopes the problem independently
25-30	Review blockers, enterprise requirements, and channel economics	Keep/kill/modify decision	Each retained stage feeds a measured next stage

Lead Scorer implementation: reproduce the research and approval loop

Lead Scorer can reproduce the research, qualification, drafting, and feedback parts of this motion. It cannot manufacture product expansion, publish the X Article, activate a campaign without review, or prove that a broad product should avoid outbound. Keep the human decision gates.

1. Separate problem audiences before enriching anyone

Run the icp-offer-context skill with one product and one narrow workflow. Create separate lists for spreadsheet replacement, approval workflow, and ERP/CRM loose ends; do not combine them in a generic “operations” list. Use daily-vertical-prospecting only after the segment and disqualifiers are explicit. Score company fit before spending contact-discovery credits.

Define an ICP for teams losing time to one spreadsheet-based approval workflow. Disqualify buyers that need a company-wide replacement on day one. Keep separate lists by workflow and industry.

Pass condition: at least 70% of a 20-account sample shows the same observable pain pattern. Human approval is required before enrichment.

2. Build evidence for content and partner conversations

Use signal-research-dossier to require two dated, sourced signals per account. Store the recurring objections and workflows in Content Studio. Use daily-topic-briefs to turn those patterns into evidence-backed solution briefs. When a relevant LinkedIn post or event exposes people discussing the problem, create_audience_source can capture that signal audience for qualification. A source is not permission to contact everyone.

Find two dated sources proving the company uses a spreadsheet workaround or is changing ERP/CRM. Skip the account when the evidence is generic. Summarise the loose end in one sentence.

Stop condition: fewer than half the accounts produce two strong signals. Rewrite the segment rather than weakening the research threshold.

3. Draft narrow outreach only where the category becomes specific

If a vertical workflow turns the horizontal platform into a concrete offer, use lead-enrichment-pipeline for approved keepers, then cold-email-first-touch for one message per lead. Run outreach-qa-audit and review every draft. The system stays in draft until a human approves the claim, recipient, and ask.

Draft one email about the verified workflow gap. Use one sourced signal, one proof point, and one small ask. Do not claim a company-wide transformation. Leave every message in draft.

For partners, keep a dedicated list with relationship type, client segment, implementation capacity, loose-end pattern, and commercial fit. A consultant that cannot identify or deliver the workflow is not partner-qualified, even if the firm has enterprise logos.

4. Turn replies into the next content and qualification rule

Use reply-triage to classify interested, timing, wrong person, objection, and no. Review the drafted response before sending. Every ten replies, feed repeated objections back into Content Studio, update the ICP scoring rubric, and create a new signal audience around the most useful proof. That closes the same loop Ragic's system implies: real workflow language improves discovery; better discovery attracts a narrower user; that user's result creates the next proof asset.

Saveable checklist

• Use services only when reusable product learning rises each month.
• Map content to a named operational failure, not a broad category keyword.
• Measure qualified problem conversations before scaling paid acquisition.
• Name the adjacent department during the first workflow, not after renewal.
• Give partners one loose-end deployment pattern they can recognise and deliver.
• Package enterprise requirements only when qualified deals expose the blocker.
• Keep outbound as a testable channel-fit decision, not an ideology.
• Mark founder-reported numbers as founder-reported.

Sources and evidence limits

The core chronology, channel choices, failure of outbound, and revenue mix come from Jeff Kuo's May 2026 Software Spotlight interview. The full 60,167-character transcript was audited from start to finish. The “more than half of revenue” milestone is founder-reported and has no public audit or channel-attribution table.

Ragic's current enterprise-plan documentation verifies enterprise packaging. Its partner programme verifies the implementation channel and advertised commission structure. Vendor-hosted stories for ProMedEx and Do it Best illustrate departmental expansion, but they are marketing evidence rather than independent studies.

G2's independent review corpus corroborates the product's multi-workflow flexibility, with a small sample of 19 reviews at the time of research. It does not verify acquisition attribution or revenue mix. No source publishes Ragic's CAC, paid budget, partner-sourced pipeline, net retention, or exact enterprise revenue percentage. Those gaps define what you should not copy blindly.