· David Rusenko

David Rusenko (Weebly): No-Code Before It Was a Category, and the Acquisition Doctrine

Building for a market that does not yet believe in your category means years of evangelism, distribution through word-of-mouth and product-embedded SEO, and — when the exit comes — remembering that companies are bought, not sold.

no-codesmb-saasm-and-afounder-modebootstrappingword-of-mouthy-combinator0% confidence

Why this is in the corpus

Rare first-hand doctrine on creating a no-code category before it existed and on the mechanics of a strategic acquisition (Square/Weebly 2018): partner-then-acquire, over-invest in integration, and put yourself in a position to say no.

Summary for skimmers

Weebly founder David Rusenko on empowering non-coders, spending 3-4 years convincing the market a "stupid" idea was big, ~80% word-of-mouth growth with no marketing budget, how the CEO job changes once a year, and the acquisition playbook that led to the Square deal.

Briefing

What survives the editorial filter

This page should feel like a smart colleague already listened for you and left only the operating logic worth keeping. Not everything said in the episode makes it through.

Trust signal

Direct episode extraction

Best used for

Decision-grade retrieval metadata not yet added for this episode.

Hold lightly

No explicit downgrade reason stored yet for this episode.

Principles

Durable claims that survive beyond the speaker's biography — each with explicit limits, transferability judgment, and evidence.

Principle

SMB customers see their website as an extension of their ego, so you cannot just build it for them

When the product is an identity artifact, control matters as much as the outcome.

Rusenko found SMB owners had strongly held ideas about their websites and wanted to be involved, so Weebly had to accommodate deep customization while still producing good-looking results.

Design for owner control, not just automated perfection, when the product carries ego.

Principle

Word of mouth was ~80% of adoption with no marketing budget

A love-worthy product plus embedded distribution beats a marketing budget.

Rusenko says word of mouth drove about 80% of adoption over the years, with the remaining 20% split between PR and SEO from footer links on user websites.

Engineer the product to generate its own word-of-mouth and SEO before buying growth.

Principle

Put yourself in a position where you could say no

The best acquisition leverage is a credible ability to walk away.

Rusenko's board member Roelof from Sequoia advised putting the company in a position to say no — keep running the business so the deal is a choice, not a necessity.

Keep the business strong enough that any sale is optional.

Principle

Starting a company is the opposite of risky — it is the best thing you can do for your resume

Founding is asymmetric: bounded downside (great resume) and uncapped upside.

Rusenko reframes the standard fear of quitting a job to start a company: even a failed startup yields world-class experience that makes you more employable, so the expected value is positive regardless of outcome.

Treat starting a company as career insurance, not career risk.

Principle

Build from obsession with a cool idea, not from ambition to build a big company

The best companies start from a cool idea you are obsessed with, not a big-company goal.

Rusenko became obsessed with drag-and-drop website building as a class project, built it because it was cool, showed others who agreed, and the company grew organically from that authenticity.

Optimize early for genuine obsession; ambition can come later.

Principle

When your idea looks stupid or obvious, you must spend years convincing the market it is big

Category creation is 3-4 years of evangelism before the market believes.

Weebly's no-code website idea was seen as stupid because skeptics assumed anyone who needed a website could just learn to code; only sustained growth eventually convinced people it was a massive market.

Budget years of persuasion, not just product, when creating a category.

Principle

Companies are bought, not sold

You cannot sell your company; the acquirer has to decide to buy it.

Rusenko heard the maxim from other founders but only understood it living through the Square process — Square exhausted internal build attempts, then partnered, then concluded it had to own Weebly.

Stop trying to sell; build conditions where a buyer decides to buy.

Principle

The acquirer must reach the conclusion to buy on its own — outbound rarely works

Real deals happen when the buyer independently concludes it must own you.

Rusenko notes large acquisitions come from the business owner deciding to buy after trying to build or partner, not from corp dev — so founders should create the conditions for that conclusion rather than pitch outbound.

Engineer the buyer's conviction; do not pitch the sale.

Principle

The CEO's job completely changes about once a year

At each stage the CEO role redefines itself; last year's competence becomes this year's failure.

Rusenko describes a cycle of three months doing the job well, three months unknowingly failing at the new job, then six months relearning it — repeating each year as the company scaled.

Assume your CEO job is changing; audit your own performance like a third party.

Frameworks

Reusable systems and operating models — including when they help and when they break.

Framework

Acquisition price reality check: take the low end of the range and cut it in half

The realistic exit price is roughly half the low end of the quoted range.

Rusenko warns that a stated range like $20-50M really means about $10M in practice, and founders who anchor on the top do the math in their heads and get emotionally dragged through the process.

Discount any indicative acquisition range to half its floor before reacting.

Framework

The CEO annual reinvention cycle: 3 months competent, 3 months unknowingly failing, 6 months relearning

Each scale transition follows a predictable competence-then-failure-then-relearn arc with breakpoints at ~25 and ~75.

Rusenko maps the cycle to concrete headcount breakpoints: ~25 employees forces the first management layer and real delegation, and ~75 employees changes how information flows as people begin managing upward.

Watch for the 25- and 75-person breakpoints and assume you are in the latent-failure phase.

Signals

What appears to be shifting, for whom it matters, and what happens if you ignore it.

Signal

Acquisitions flow out of the acquirer's annual planning cycle, clustering at year-end

Serious acquisition conversations cluster around year-end annual planning.

Rusenko had three straight Christmases of deep acquisition discussions, noting deals flow out of annual planning that happens toward the end of the year.

Expect strategic-buyer interest to surface around annual planning and the holidays.

Opportunities

Only included where there is a buyer, a real wedge, and a plausible revenue path — not vague idea theater.

Opportunity

Markets dismissed as "stupid" can be the largest — no-code was hiding in plain sight

An idea everyone calls stupid can mask a very large underserved market.

No-code website building was dismissed because people assumed anyone who wanted a site could learn to code; only sustained growth revealed the massive non-technical market.

Look for large markets hiding behind "obvious" or "stupid" consensus dismissals.

Lessons still worth keeping

Useful takeaways that did not fully clear the bar for durable principle status.

Lesson

Capping your ambition at "25 people then hand off to a real CEO" is the wrong answer

Do not pre-decide to hand off leadership at a tiny scale; you will underestimate yourself and the market.

Rusenko told early investors he would hand the reins to a professional CEO at 25 people — an answer he calls totally wrong in retrospect, since he led Weebly to 350+ employees and an acquisition.

Reject artificial ceilings on company size and your own growth as a leader.

Lesson

"We want to buy your company" is usually just a hook to start a conversation

An opening buy overture is a conversation-starter, not intent.

Rusenko explains the sequence: the opener hooks you, then a range is floated, and both are far softer than founders assume — realism protects you from being dragged.

Treat first acquisition interest as exploratory and keep running the company.

The Plays

Try these this week

Verb-first executable actions — each one tied to a stated outcome in the episode.

Pitch the prospective acquirer to pick a single main partner (then be that partner)

Outcome: Argue the buyer should concentrate on one partner, then earn that slot.

Context: Rusenko pitched Alyssa (his future boss at Square) that choosing one main partner aligns incentives to invest, versus four partners each minimizing effort; Square initially chose four for user choice.

instead of choosing three or four partners, you should really just choose like one main partner, because that partner will have the incentive to invest in the integration
David Rusenko
At partnership-selection stage per
  1. 1

  2. 2

  3. 3

  4. 4

Scripts

Before you start

  • · Direct access to the buyer's product/business owner
  • · A differentiated integration capability

Build press coverage by befriending reporters and offering more than a pitch

Outcome: Earn PR by building real relationships with reporters, not pitching them.

Context: With no marketing budget, Weebly won PR by meeting reporters in person (a Bay Area advantage), becoming friends, and offering value beyond pitches until they wanted to cover the company.

You go out and you meet reporters and you become friends with them and You know, you offer them more than just pitching them. And, and over time you build a relationship and, and then they wanna cover you.
David Rusenko
Months to years; compounds over time per
  1. 1

  2. 2

  3. 3

  4. 4

Scripts

Before you start

  • · Access to reporters (in-person ecosystem helps)
  • · Patience for slow relationship payoff

Embed footer links on user-generated sites to compound SEO

Outcome: Turn every user-created site into a distribution surface via footer links.

Context: Weebly placed links on the footers of user websites, which drove SEO and formed part of the ~20% of adoption not attributable to pure word of mouth.

we had these links on the footers of websites that people could see, And it helped us with SEO and that kind of thing.
David Rusenko
Compounds continuously as users publish sites per
  1. 1

  2. 2

  3. 3

Before you start

  • · Product generates public, indexable user output
  • · Acceptable to display a powered-by/footer link

Over-invest in the integration to become the acquirer's best partner

Outcome: Deliberately over-resource a strategic partnership to become the acquirer's obvious best choice.

Context: Rather than minimizing integration effort like a rational partner would, Weebly put four engineers on the Square integration to become the best partner, positioning itself as the natural acquisition target.

maybe we would've put like half an engineer on the integration. We ended up putting four engineers on the integration and we basically said, we wanna be the best partner
David Rusenko
Sustained over the partnership period (2016-2017 for Square) per
  1. 1

  2. 2

  3. 3

  4. 4

Scripts

Before you start

  • · A credible strategic partner
  • · Engineering capacity to over-invest
  • · Willingness to accept negative short-term ROI on the integration

Decision Moments

Actual decisions, real outcomes

Specific decisions narrated in the episode with their outcomes and transferable lessons.

Square shut down its own online store and chose to partner with several vendors (including Weebly) after failing four or five times to build the capability internally. A rational partner would minimize integration effort given the trickle of users each would receive.

Did: Instead of staffing the integration at the ~half-engineer level the payback justified, Weebly put four engineers on it and explicitly set out to be the best partner Square had, investing above and beyond the expected return.Outcome: After annual planning in 2017 Square concluded the capability was too strategic to partner for and had to be owned; it surveyed the field and chose to acquire Weebly (announced 2018).

When a strategic partner could become an acquirer, over-invest in the integration to become the undeniable best option — position, do not pitch.

Part of an emerging decision pattern across multiple episodes

Weebly was a growing, independent business with prior serious acquisition interest across two earlier years; Square then decided it needed to own the capability and moved from term sheet toward a definitive agreement.

Did: Rusenko engaged the process while keeping the company in a position to say no (per Sequoia board member Roelof), discounted the indicative range, avoided being emotionally dragged, agreed to a term sheet around February, and sold to Square, staying on afterward.Outcome: Weebly was acquired by Square in 2018; Rusenko stayed for a little over three years and enjoyed the company, describing it as a fantastic outcome.

Sell only from a position of optionality and emotional detachment; keep running the business so the deal is a choice, not a necessity.

Part of an emerging decision pattern across multiple episodes

Three Penn State students with no Stanford/Berkeley pedigree, no investor interest, and post-dotcom-bust skepticism had built an early no-code website tool on nights and weekends while interning.

Did: In fall 2006 they applied to Y Combinator, drove out to interview, got in, and moved to San Francisco for a three-to-four-month sprint.Outcome: YC gave them a Silicon Valley stamp of approval — access to mentors (Paul Graham, Paul Buchheit), investors, and press (TechCrunch) — and compressed years of progress into months.

For unpedigreed founders, an accelerator can substitute credibility and network that the market otherwise withholds, compressing progress dramatically.

Part of an emerging decision pattern across multiple episodes

Tensions surfaced

Contradictions and trade-offs the episode raises — judgment calls a thoughtful operator has to navigate.

Tension

Give SMB owners real customization control vs. guarantee good-looking outcomes

Owner control and guaranteed good outcomes pull against each other in SMB product design.

Rusenko frames the recurring design challenge: owners have strong ideas that may not look good, yet demand involvement, so Weebly had to make good outcomes the default while still permitting deep customization.

Resolve the control-vs-outcome tension with opinionated defaults and escape hatches.

Corpus connection

Where this episode fits for retrieval

What kinds of decisions this briefing is best pulled into.

Primary decisions

  • strategic-bet
  • sell-company
  • partner