No Code

7 posts

stripe3 min readCurated summary

Solo founding is at an all-time high: Top performers have these traits in common

Solo founders now represent 63% of new Stripe Atlas C corps, but performance is increasingly polarized: median revenue is falling while top performers grow rapidly. Stripe’s analysis of thousands of solo-founded startups found that the strongest companies tend to be AI-native, global from launch, B2B-focused, and effective at retaining customers. Multifounder startups generally pull ahead over time, though exceptional bootstrapped solo founders can nearly match them. ## AI-Native Products - Top-decile solo founders were about twice as likely to build products whose core functionality depends on AI models. - By year two, AI-native startups generated nearly twice the revenue of other solo-founded companies. - Their advantage was broad-based, spanning approximately the 50th through 95th revenue percentiles—not merely the result of a few extreme outliers. - AI lowers the technical barrier, allowing founders to focus on solving problems quickly, shipping products, and finding distribution. ## Global Sales from Launch - Top-performing solo founders sold to an average of 10 countries in their first month, compared with three for median founders. - By month 24, they reached about 40 non-US countries, versus six for median founders. - International customers generated 51% of top-decile revenue, compared with only 2% for median companies. - Early access to large markets such as the US helped accelerate growth. ## B2B Business Models - Top solo founders were nearly 30% more likely to build B2B companies. - By month 24, the median solo B2B startup generated more than four times the revenue of the median B2C startup. - Among top performers, B2B companies earned nearly twice as much as comparable B2C companies. - This advantage persisted among bootstrapped startups, suggesting it was not primarily caused by easier access to funding. ## Early Customer Retention - Nearly 30% of customers at top-decile startups returned the following month, compared with 8% at middle-decile companies. - Top performers began recovering churned customers around three months earlier. - By the start of year two, their first-month customers were spending 47% more than at acquisition—roughly twice the increase seen among middle-decile startups. - In B2B, top solo founders retained initial customers at six times the rate of median founders. - Recurring billing was more common among top performers, by 26 percentage points in B2B and 20 points in B2C. ## Solo Founders Compared with Teams - Solo startups initially generated more revenue than multifounder startups, but multifounder companies led by month 24. - Top-decile multifounder startups produced 53% more revenue than top-decile solo startups, even after accounting for funding. - Among the very best bootstrapped companies, the gap narrowed to just 5%. - Exceptional solo founders compensate for limited headcount through speed, resourcefulness, hiring, advisors, and founder networks. Solo founders appear most likely to succeed when they use AI to move quickly, target business customers, sell internationally from the beginning, and validate demand through strong retention. Teams still offer a long-term advantage, but highly capable, well-connected solo founders can approach team-level performance without outside funding.

Read original(opens in new tab)
figma2 min readCurated summary

Issue No.14: Software Is Culture | Figma Blog

Software increasingly shapes how people communicate, play, create, eat, and connect. Figma’s January 2026 newsletter argues that as AI evolves from tool to teammate, software will become more responsive to human needs—and its cultural influence will grow. The issue explores this idea through design, language, gaming, food, and physical fabrication. ## Design Is Culture - Familiar interactions such as pinch-to-zoom, infinite scroll, and tap-to-like were once novel inventions. - These interface patterns have had a major influence on how an entire generation thinks and feels. - The newsletter highlights 10 iconic interactions to examine their broader cultural impact. ## Language Is Culture - Social media and recommendation algorithms help new slang spread rapidly, including expressions such as “6-7,” “aura,” and “rizz.” - Linguist Adam Aleksic explains that algorithms influence not only how people speak, but also how they think and relate to one another. - “Algospeak” has become a measure of virality and a distinctive feature of online communication. ## Gaming Is Culture - Video games have grown from simple experiences like Pong into a $184 billion industry built around expansive worlds, characters, game modes, and side quests. - Despite this complexity, players often navigate games through a small set of controller inputs. - Epic Games UX designer Aashrey Sharma examines how these simple controls enable rich interactions and what they suggest about the future of interfaces. ## Food Is Culture - British Columbia’s small farms are under pressure from factory farming and rising costs, with farmers reportedly leaving the industry at an alarming rate. - Entrepreneur Aaron Veale used Figma Make to build a marketplace connecting local growers with restaurants. - By prompting the AI tool, he produced a working minimum viable product in less than three weeks, demonstrating how AI can help individuals address urgent community problems. ## Fabrication Is Culture - Designer Kelsey Fairhurst combines digital design with hands-on manufacturing to create “softline brutalist” stainless-steel flatware. - Her Forks Plus project grew through years of research and work between a Brooklyn studio and a Cleveland fabrication shop. - The story presents software and design tools as companions to physical making rather than replacements for it. The newsletter’s central recommendation is implicit: treat software as a cultural force, not merely a productivity tool. Designers and builders should consider how the interfaces and AI systems they create will shape behavior, language, creativity, and everyday life.

Read original(opens in new tab)
stripe4 min readCurated summary

Stripe Atlas startups in 2025: Year in review

In 2025, early-stage startups launched faster, reached revenue sooner, and sold internationally from the beginning. Stripe Atlas data shows that these gains occurred despite a smaller share of startups raising funding, suggesting improved infrastructure and execution—not just venture capital—are driving growth. Founders are also increasingly building AI companies, particularly AI-agent businesses, although the post ends before fully explaining that shift. ## A More Global Startup Ecosystem - Atlas incorporations represented 169 countries in 2025, up from 158 in 2024. - European incorporations grew 48%, especially in the UK, France, and Germany, as founders sought access to US capital markets. - While 56% of Atlas startups are US-based, founding teams are increasingly distributed: - 24% of teams with multiple founders span more than one country. - This is a 79% increase since 2017. - Common pairings include Canada–US, UK–US, and India–US. - Distributed teams form both through prior in-person relationships and entirely online professional connections. ## International Sales from Launch - The typical startup sold to customers in two countries during its first six months in 2025, compared with one country in previous years. - Startups at the 90th percentile reached 15 countries, up from 12 in 2024. - Examples include: - Rork, which reached 69 countries in its first month and generated $100,000 in five days. - Zeabur, which served developers in 46 countries. - Payment infrastructure, compliance tools, cloud services, translation APIs, and globally distributed founders have reduced the barriers to international expansion. - Selling globally is increasingly a default launch strategy rather than a post-product-market-fit phase. ## Revenue Arrives Faster - The share of Atlas startups gaining a first paying customer within 30 days rose from 8% in 2020 to 20% in 2025. - Among startups that began accepting payments within three months, median time to first payment fell from 38 to 34 days. - Atlas’s 2025 payment changes allowed founders to accept payments immediately after incorporation, avoiding lengthy EIN delays for non-US founders. - Median first-six-month revenue increased 39% year over year, indicating that faster monetization reflects stronger product shipping and customer acquisition as well as better infrastructure. ## More Startups Reach Significant Revenue - The number of startups reaching $100,000 in their first six months rose 56% from 2024. - These companies reached that milestone in 108 days, compared with 121 days previously. - The average startup acquired 242 customers in its first six months, more than 50% above the prior year. - Growth was strongest among top performers: - 10th-percentile startups generated 18% more revenue than comparable 2024 companies. - 90th-percentile startups generated 52% more. - The overall market improved, but the gap between breakout companies and average performers widened. ## AI Becomes a Dominant Startup Focus - The share of Atlas founders identifying their companies as AI startups grew from 15% in 2023 to 33% in 2024 and 42% in 2025. - AI adoption also expanded among LLCs, rising from 5% in 2023 to 22% in 2025. - This growth occurred alongside weaker early fundraising: - Only 2.2% of Atlas startups at least six months old raised funding within three months of incorporation, down from 3.1% in 2024. - Pre-seed deal volume was largely unchanged even as Delaware C-corp formations increased. - The supplied article indicates that founders are shifting attention toward AI agents rather than AI infrastructure or copilots, but the provided text ends before detailing that trend. ## Practical Conclusion Modern payments, cloud infrastructure, compliance tools, and developer platforms are enabling founders to launch, monetize, and expand globally within weeks. Early startups increasingly need to assume international reach from day one while focusing on rapid customer validation and efficient execution, particularly as funding becomes less automatic.

Read original(opens in new tab)
stripe2 min readCurated summary

New features to help SaaS platforms manage risk and stay compliant

Stripe introduces three features aimed at helping platforms balance rapid onboarding with fraud prevention and compliance. The updates let platforms reserve user funds, customize risk and compliance controls, and tailor onboarding data collection by region. Together, they provide more control while reducing financial exposure and engineering effort. ## Reserves for Risk Protection with Radar for Platforms - Platforms can place temporary reserves on user funds through the Stripe Dashboard or programmatically. - Reserves can use: - Fixed amounts - Rolling reserves - Custom Radar rules can identify high-risk businesses and automatically reserve funds to protect against disputes or insolvency. - Platforms can also hold funds from unusual transactions—such as orders with long delivery windows—and release them after the return period ends. - Radar’s risk signals are trained on more than $1.4 trillion in payment volume. ## Specialized Controls for Trusted Platforms - Stripe Verified for platforms gives trusted platforms additional control over Stripe’s risk and compliance systems. - Platforms can extend deadlines for eligible risk and compliance tasks directly from the Dashboard. - Stripe may provide benefits tailored to specific industries or business models. - For example, property-management platforms may receive higher ACH limits to support rent collection during peak periods. ## Flexible, No-Code Onboarding Workflows - Stripe’s updated embedded onboarding component lets platforms choose which information to collect from users. - Platforms can configure workflows for regional requirements, such as: - Proof of liveness in Singapore - Document uploads in Canada - Automatically updated components reduce engineering work by about 90%, from roughly 40 weeks to fewer than four. ## Future Expansion - Stripe plans to add risk signals covering broader financial exposure beyond fraud. - Verified access will expand to more trusted platforms. - Additional controls for customizing onboarding and verification requirements are also planned. Platforms can use these tools to build more targeted risk strategies, protect funds, support legitimate users, and launch in new markets with less compliance-related engineering effort.

Read original(opens in new tab)
coupangOriginal article

Coupang SCM Workflow: Developing (opens in new tab)

Coupang has developed an internal SCM Workflow platform to streamline the complex data and operational needs of its Supply Chain Management team. By implementing low-code and no-code functionalities, the platform enables developers, data scientists, and business analysts to build data pipelines and launch services without the traditional bottlenecks of manual development. ### Addressing Inefficiencies in SCM Data Management * The SCM team manages a massive network of suppliers and fulfillment centers (FCs) where demand forecasting and inventory distribution require constant data feedback. * Traditionally, non-technical stakeholders like business analysts (BAs) relied heavily on developers to build or modify data pipelines, leading to high communication costs and slower response times to changing business requirements. * The new platform aims to simplify the complexity found in traditional tools like Jenkins, Airflow, and Jupyter Notebooks, providing a unified interface for data creation and visualization. ### Democratizing Access with the No-code Data Builder * The "Data Builder" allows users to perform data queries, extraction, and system integration through a visual interface rather than writing backend code. * It provides seamless access to a wide array of data sources used across Coupang, including Redshift, Hive, Presto, Aurora, MySQL, Elasticsearch, and S3. * Users can construct workflows by creating "nodes" for specific tasks—such as extracting inventory data from Hive or calculating transfer quantities—and linking them together to automate complex decisions like inter-center product transfers. ### Expanding Capabilities through Low-code Service Building * The platform functions as a "Service Builder," allowing users to expand domains and launch simple services without building entirely new infrastructure from scratch. * This approach enables developers to focus on high-level algorithm development while allowing data scientists to apply and test new models directly within the production environment. * By reducing the need for code changes to reflect new requirements, the platform significantly increases the agility of the SCM pipeline. Organizations managing complex, data-driven ecosystems can significantly reduce operational friction by adopting low-code/no-code platforms. Empowering non-technical stakeholders to handle data processing and service integration not only accelerates innovation but also allows engineering resources to be redirected toward core architectural challenges.

figma3 min readCurated summary

In the file at Config 2021 | Figma Blog

Config 2021’s breakout sessions emphasized practical systems for building products and teams. Coda’s Helena Jaramillo described how to create a strong product vision without existing user data, while Stripe’s design team shared principles for meeting immediate needs without sacrificing long-term scalability. Both approaches rely on context, shared perspectives, strong foundations, and thoughtful communication. ## Building a Vision from Zero to One - At Coda, Helena Jaramillo worked on a publishing platform designed to help users share best practices and discover documents. - Because the product was new, the team lacked existing user behavior, research participants, and historical data. - Helena built context by studying competitors and adjacent products, annotating screenshots in Figma, and identifying useful or unsuitable patterns. ## Developing a Strong Product Perspective - The team explored what publishing on Coda should feel like: a blog post, a no-code app, or a website. - They used Helena’s publishing experience and internal discussion to form a shared point of view. - Two priorities emerged: - Make publishing interactive documents easy. - Help publishers feel proud of and recognized for their work. - These principles shaped features such as simple publishing flows, photos, subtitles, and bylines. - When user insights are unavailable, a team can rely on collective intuition and expertise—but only by aligning around a clear perspective. ## Communicating the Broader Story - Helena created a “tl;dr page” in Figma to align cross-functional partners. - Rather than documenting every feature, the page used a short flow and several mockups to show the product narrative. - The goal was to make the intended experience understandable without requiring deep project context. ## Designing for Immediate Needs and Long-Term Scale Stripe’s Connie Yang, Tayler Aitken, and their team focus on simplifying complex processes for businesses and end users. Their approach combines urgency with long-term planning. - **Think in long time scales:** Stripe uses a “city planner mentality,” considering how systems connect, handle growth, and respond to future needs—potentially as far ahead as 2030. - **Lay strong foundations:** Teams should invest in fast, accessible products and scalable systems instead of short-term fixes. - Stripe’s design-system color tables, for example, include contrast and accessibility ratings, embedding quality requirements directly into the infrastructure. - **Prioritize rigor and quality:** Because Stripe handles payments and payouts, user trust is essential. The team accepts additional complexity when it produces a more reliable, polished experience. The practical recommendation is to combine strong early judgment with durable systems: build enough context to form a clear vision, communicate that vision simply, and make foundational decisions that continue serving users as the product grows.

Read original(opens in new tab)
figma3 min readCurated summary

How Notion pulled itself back from the brink of failure | Figma Blog

Notion nearly failed in 2015 because its original product and technology stack did not match what users wanted. Founders Ivan Zhao and Simon Last moved to Kyoto, rebuilt the product from scratch, and used an intensive, collaborative design process to create Notion 1.0. The relaunch succeeded because it combined powerful customization with a simple, approachable user experience. ## Rebuilding Notion from the Brink - Notion’s first version was a programming-oriented tool intended to help nontechnical users build software. - The founders realized they had focused on their own vision rather than customer needs. - With funding running low, they dismissed their team, sublet their office, and relocated to Kyoto to reduce expenses and concentrate on rebuilding. - Zhao spent as many as 18 hours a day designing and iterating on the new product. - The mission remained the same: enable people to create tools tailored to their own problems without writing code. ## Collaborative Design Under Pressure - Zhao and Last worked closely across design and engineering, switching roles as needed. - Figma’s multiplayer capabilities allowed them to work in the same files simultaneously, brainstorm quickly, and explore product problems together. - This collaboration helped them move faster during their year-long rebuild. - Notion 1.0 launched in March 2018 and quickly reached the top of Product Hunt. - The product later reached one million users with only seed funding and earned praise for its user experience. ## Simplicity Despite Powerful Features - Notion’s new-user home screen was intentionally minimal, using a small set of simple icons. - Its visual style drew inspiration from classic interfaces, including Susan Kare’s iconography and the look of Windows 95. - Zhao argues that design is central because users value how a daily tool feels, just as they care about the physical qualities of a hammer or knife. - The product’s challenge was to make extensive functionality feel approachable rather than overwhelming. ## Create Many Variations, Then Choose One - Zhao repeatedly duplicated user flows and changed small details such as icons, wording, and layout. - Notion’s broader philosophy is to explore many permutations before selecting the strongest solution. - Team members are encouraged to produce rough drafts, including unconventional or bad ideas, instead of committing too early. - Designers, copywriters, engineers, and illustrators all use this iterative approach. - Teammates then critique and stress-test the alternatives, narrowing them down to the best option. - Zhao credits this process with helping create Notion’s distinctive brand. ## Design as a Thinking Tool - Notion treats design as part of the thinking process, not merely as a final production stage. - The team develops ideas visually in Figma from the beginning, using it as a flexible scratchpad. - This design-centered approach extends across the small company, involving more than just dedicated designers. Notion’s recovery demonstrates how a failing product can be transformed by listening more closely to users, rebuilding around their needs, and creating space for rapid, collaborative experimentation. Teams facing similar pressure can benefit from exploring many options early, testing them together, and protecting simplicity even when the underlying product is powerful.

Read original(opens in new tab)