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 storyProduct snapshot
What it was
newCo was Ben Tossell's no-code education product before Makerpad.
Who it was for
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
Competitors or alternatives
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
Why it matters
newCo was Ben Tossell's no-code education product before Makerpad. The useful pre-build question is whether no-code learners, aspiring makers, and founders learning to build without code will repeatedly use and pay for learn no-code tools and build without writing code through a channel you can keep reaching.
Primary check
Keep the paid learning outcome narrow before expanding no-code education into a broader product or community.
Checklist
- Who owns the budget for this problem?
- What repeated event triggers the buyer to use this every week or month?
- Which channel reliably reaches no-code learners, aspiring makers, and founders learning to build without code without a one-off launch spike?
- What evidence would show Lack of Focus and Weak Recurring Model before you build more?
- Define which segment among no-code learners, aspiring makers, and founders learning to build without code pays first and why the problem is urgent now.
- Prove the workflow happens often enough to justify buying.
- Test one acquisition channel for no-code learners, aspiring makers, and founders learning to build without code before relying on launch traffic.
- Write down why a buyer would switch from free no-code tutorials, maker communities, and course platforms.
Relevant if
- You are building a web app for no-code learners, aspiring makers, and founders learning to build without code.
- The main value is specific: It helped learners understand no-code tools and build practical projects faster.
- You have interest, signups, usage, or founder confidence but have not proven paid repeat use.
- Buyers can already use free no-code tutorials, maker communities, and course platforms or avoid switching altogether.
Less relevant if
- You already have paying no-code learners, aspiring makers, and founders learning to build without code who repeatedly use the workflow and renew or expand usage.
- The product is an internal tool with a mandated user base and no external go-to-market risk.
Pre-build tests
- Run the workflow manually for a small group of no-code learners, aspiring makers, and founders learning to build without code.
- Ask one buyer to pay, renew, or sign a dated pilot before building the next version.
- Test one non-launch acquisition channel and count qualified conversations, not page views.
- Put the offer next to free no-code tutorials, maker communities, and course platforms and ask what would make the buyer switch now.
Transferable lessons
- Validate whether no-code learners will pay for the workflow, not only say it sounds useful.
- Treat Lack of Focus and Weak Recurring Model as the first assumption to test.
- Compare the product against free no-code tutorials, maker communities, and course platforms before adding more features.