
No-coding your product one iteration at a time.
About
Presenting a case study on how to start, build, and iteratively improve your product without writing a single line of code. The purpose is to demonstrate the feasibility and benefits of no-code tools, from idea inception to MVP, and beyond. This topic is crucial for empowering non-technical entrepreneurs and is particularly exciting for designers and product builders, as it allows them to bring their visions to life without relying on developers. The presentation will include practical, real-life examples from two designer-no coder-entrepreneurs.
Watch the full talk
Watch this WaysConf session, then continue with related talks or explore the current programme.
Talk in brief
In this WaysConf 2024 talk, Dare IT co-founders Natalie Pilling and Aleksandra Bis present practical strategies for building and scaling digital products using no-code tools and automation. Drawing from five years of developing their platform from a side project into an organization serving thousands of tech career switchers, the speakers outline ten core principles for iterative product development. They emphasize starting with concrete operational bottlenecks—such as replacing chaotic Google Sheets with automated Airtable databases—and adopting micro MVPs over complete system overhauls. Pilling and Bis share how leveraging tools like Webflow, Make, EasyCart, and Mailchimp allowed their small team to expand functionality incrementally, automate payments, and empower non-technical team members to ship features independently. They also discuss managing no-code technical debt, accepting production test risks, knowing when to discard outgrown platforms, and evaluating software tool trade-offs during an audience Q&A session.
Key takeaways
- 01
Solve Concrete Pain Points First
Focus initial no-code efforts on replacing manual bottlenecks rather than adopting tools for their own sake. Early automation of mentor matching in Airtable freed up capacity without expensive custom development.
Watch from 6:07 - 02
Prioritize Completion Over Perfection
Launching functional workarounds quickly delivers immediate value and validates demand faster than waiting for perfect custom implementations. Using EasyCart on top of Stripe simulated installment payments without complex custom coding.
Watch from 18:36 - 03
Expand Systems Iteratively Like a Web
Grow digital infrastructure by building connected capabilities around a proven core rather than attempting full ecosystem rollouts at once. Expanding from matching to recruitment, events, and payments created a robust operational engine over time.
Watch from 22:32 - 04
Empower Teams Through Shared Toolsets
Providing team members direct access to no-code platforms removes development bottlenecks and fosters rapid internal innovation. Non-technical staff can independently design, test, and ship features within months.
Watch from 27:16 - 05
Willingness to Discard Outgrown Platforms
Prototype systems with the understanding that early tools will eventually need to be replaced as user needs evolve. Transitioning from email-and-Notion setups to Circle and ultimately a unified Webflow platform supported long-term growth.
Watch from 30:28
Video chapters
- 1:59The Reality of Building Digital Products
Aleksandra Bis and Natalie Pilling reflect on design chaos, perfectionism, and the origin story of Dare IT.
- 5:59Starting with Problem-Driven Automation
The speakers explain why no-code adoption should always begin by solving clear operational bottlenecks.
- 12:45Selecting and Masterclassing Your Tech Stack
Pilling details how to choose core tools, leverage aggregators, and jumpstart development with ready templates.
- 18:36Embracing Imperfection and Workarounds
The founders share practical examples of using workaround tools to deliver features faster without custom code.
- 22:32Gradual Ecosystem Building and Team Empowerment
Bis outlines how Dare IT iteratively built a connected tool ecosystem while enabling non-technical team members.
- 33:09Managing Technical Debt and Live Failures
Pilling addresses the reality of scaling airtable databases, testing in production, and recovering from automated mistakes.
- 43:52Audience Q&A on Tool Selection and Platform Migration
The speakers answer audience questions regarding subscription cost management, SEO, and community platform trade-offs.
Read edited transcript highlights
These concise notes were edited from automatic captions and checked against the talk structure. They are not a verbatim transcript.
Overcoming Design Perfectionism with Micro MVPs
When building personal projects or new initiatives, designers frequently succumb to perfectionism, overthinking, and emotional attachment to early ideas. Instead of attempting to build a comprehensive custom platform right away, creators should pinpoint their single biggest operational bottleneck and solve it with the simplest possible feature. For Dare IT, this meant abandoning overwhelming Google Sheets containing hundreds of simultaneous users and migrating mentor-mentee matching into a clean, automated Airtable base in 2020. That small initial step unlocked massive operational capacity and established the foundation for future growth.
Watch from 5:59Accelerating Development with Ready-Made Templates
Becoming effective with no-code tools does not require mastering every advanced automation script or earning technical certifications before launching. Building product momentum relies on jumping directly into hands-on implementation and taking full advantage of pre-existing design components, workflow templates, and platform ecosystems. Utilizing Webflow site templates, Relume UI component libraries, and pre-configured automation recipes in Make or Airtable drastically reduces development time. This allowed the Dare IT team to focus on core user experience and value delivery rather than spending months reinventing basic technical infrastructure.
Watch from 15:44Pragmatic Workarounds for Payment Subscriptions
When attempting to introduce installment payments for course offerings, native Stripe implementations required custom backend coding while out-of-the-box alternatives carried prohibitive transaction fees. Rather than delaying launch, the team devised a creative workaround by deploying EasyCart on top of Stripe to manage recurring payment schedules as simulated installment plans. Although not a traditional custom solution, this setup met immediate user needs, took under a day to implement, and proved so reliable that it remained the primary payment workflow two years after launch, saving extensive engineering effort.
Watch from 19:41Democratizing Product Ownership Across the Team
No-code software development fundamentally transforms team dynamics by removing conventional engineering bottlenecks. In Dare IT’s early stages, a two-person team managed all updates, but as the organization expanded to five members, non-technical staff quickly acquired platform skills. Within months, team members were independently designing, configuring, and deploying new product features across front-end and back-end systems. This shared capability eliminated formal feature ticketing queues, fostered direct creative ownership, and dramatically accelerated the pace of product experimentation.
Watch from 26:55Navigating No-Code Complexity and Production Risk
As no-code architectures expand from isolated databases into centralized enterprise hubs, technical debt and operational complexity naturally increase. Centralizing cohort data into a single master Airtable base streamlined cross-functional workflows, but it also increased dependency risks and limited staging environments, meaning changes were effectively tested in production. While this led to occasional mishaps, such as inadvertently triggering a thousand unnecessary emails, accepting these risks and normalizing operational mistakes enabled the team to iterate significantly faster than traditional software environments allowed.
Watch from 33:09Evaluating Tool Costs and Platform Migration Trade-Offs
During the audience Q&A session, Pilling and Bis discussed their framework for selecting software tools and coping with price increases. Tool selection balances specific feature requirements with personal user preference and industry standard reliability. When platforms raise subscription prices, teams must evaluate the total value provided rather than defaulting to immediate migration. While certain tools like Mailchimp remain expensive, their operational efficiency justifies the ongoing cost, whereas other platforms can be safely replaced when lower-cost alternatives meet core criteria without compromising user experience.
Watch from 43:52



