Web AppShut Down

newCo

newCo was Ben Tossell's no-code education product before Makerpad. The case is useful for independent developers because it shows how early revenue can still hide focus, pricing-model, and product-scope problems.

View original story

Product snapshot

What it was

newCo was Ben Tossell's no-code education product before Makerpad.

Who it was for

no-code learnersaspiring makersfounders learning to build without code

Problem / value

It helped learners understand no-code tools and build practical projects faster.

Core workflow

Learners followed no-code education material, applied tool tutorials to practical projects, and paid for access to a focused learning product.

Core dependency

The product needed a clear paid learning outcome and a focused scope before expanding.

Product form

web appeducation productno-code learning product

Competitors or alternatives

free no-code tutorialsmaker communitiescourse platformstool-specific documentation

What happened

Summary

newCo taught people how to build no-code internet businesses and side projects.

Outcome

Founder interview and founder profile sources describe newCo as a no-code education product that reached paying customers but was shut down after focus and positioning drift.

Core risk

Lack Of Focus And Weak Recurring Model

Before you build

Primary check

Keep the paid learning outcome narrow before expanding no-code education into a broader product or community.

Checklist

  • Can you name the first buyer segment and the repeated job they need solved?
  • Can you reach that segment without relying on one fragile channel?
  • What evidence would disprove the lack of focus and weak recurring model risk?

Relevant if

  • You are building a similar web app with public-source distribution risk.
  • You need to validate who will repeatedly pay before investing in product polish.

Less relevant if

  • You already control a reliable acquisition channel for the exact buyer segment.
  • The product is an internal tool with no need for public distribution.

Pre-build tests

  • Run a landing-page or concierge test with the narrowest buyer segment before building the full workflow.
  • Ask users to commit to a paid pilot, not only to join a free waitlist.