Stable’s Post

Here's Cardinal (YC W23)'s startup stack (I highly recommend all!) ** Due to this tweet's success... Product: * Knowledge & Comms: Notion & Slack * Product: Cardinal (YC W23) * Product Analytics: PostHog Engineering: * Security & Compliance: Drata * Payments: Stripe * Task Management: Linear * Admin Dashboard: Retool * Cloud: Fly.io + Amazon Web Services (AWS) * Workflow Orchestration: Temporal Technologies * LLM Observability: Traceloop * Pen Test: Oneleet (YC S22) * DNS & WAF: Cloudflare * Code: GitHub Design & GTM: * Customer Support: Intercom & Slack * Website Builder: Framer * Design: Figma * CRM: HubSpot * Email Marketing: Loops * Scheduling: Calendly * Note-taking: Grain * Screen recording: Screen Studio * Docs: Mintlify Operations & Other: * Payroll and benefits: Justworks & Take Command * Mail: Stable * Taxes: Fondo * Bookkeeping: Puzzle 🧩🚀 * Email/Calendar: Google Workspace * Insurance: Vouch Insurance * Bank & CC: Brex Did this #startupstack in case it helps someone as I got asked a lot. Yes, it's a bit Y Combinator skewed, take it or leave it.

🚀 **2/3 of developerd features have no or negative business value** 📈 Did you know that not all features built into software actually contribute to business success? 🤔 Let's dive into some fascinating findings from Ronny Kohavi , a seasoned expert who's run experiments at tech giants like Amazon, Microsoft, and Airbnb. 🌐 Ron's analysis at Microsoft revealed a thought-provoking breakdown of the features they developed and their impact on business outcomes. Here's what he discovered: 📊 🟢 Approximately 1/3 of the features were not only positive but also statistically significant. These are the game-changers, folks! 🔝 They directly contributed to business growth and success. 🟡 Another 1/3 of features were flatlined, showing no significant difference in business outcomes. While they didn't harm the business, they didn't move the needle either. ⚖️ 🔴 The remaining 1/3 of features were, surprisingly, negative, and they also showed statistical significance. 😬 These features had an adverse impact on business outcomes. What can we learn from this insightful analysis? 🤓 It's clear that not every feature we build will drive business value. To maximize success, we should consider leaving non-differentiating features to commerce accelerators and shift our focus towards experimentation! 🧪 Remember, in the ever-evolving tech landscape, experimentation is the key to innovation. 🛠️ Let's stay agile, learn from our data, and build software that truly makes a difference. 💡 #commerce #accelerators #softwareprojects

A $96,280 bill. Do you see yourself, your project, or your team in the picture below? (image clipped from Jeff's video) I just watched a great, insightful video by YouTuber Jeff Delaney about the recent costs and consequences for real developers (cara.app) using tools like Vercel, Netlify, Heroku, etc. Check it out here: https://lnkd.in/ehNvhr5x Here's my advice and words of warning. While I appreciate what these tools offer—quick setup and deployment capabilities—they can become a cost trap as your product scales, especially for new developers and startups. Remember: These tools are excellent for getting started, but to scale properly and avoid hefty bills, you'll eventually need to pivot. If you're struggling with the cost of running your applications in production, let's chat. We have a track record of reducing infrastructure costs on AWS by over half. Have you used these tools before? What was your experience? Should these tools be held more responsible for the infinite scaling they provide to developers? Let me know your thoughts below!

My review of shipfast ⚡ Why you need to pay attention. Good things 👍 + Landing page sections are clean and easy to use. + Great docs for setting up everything (google auth, database, stripe, email, etc). + NextJS allows Static Site Generation at build so my blog is blazing fast. Great for SEO. Not so good 👎 - Uses NextAuth. This is very rigid in how it needs user data to be structured. When using the DynamoDB Adapter, it forces me to structure users and sessions into a way I'm not used to. - No way of doing environments. You can use local development but I still like the idea of having the option for a deployed environment that isn't production. - No request body validation. Have to do this myself. - All documentation expects deployment to Vercel. We've all seen that post about the $97,000 Vercel bill 😬 Why you should care: Even with these limitations I've been able to build an MVP in 2 days. If you try to build this from scratch then you'll spend weeks just getting everything set up. By which time I'll be getting users, earning revenue and building the next set of features, always being one step ahead of you. It also means I could test multiple ideas in a month and see which one takes off best. What are your thoughts on these startup templates? #startup #saas #software

Question to tech/SaaS folks: This is in terms of getting investment — Is it better to make an MVP that looks good and "kind of works" or to build something scalable that works, but will need work and can work moving forward? I'm asking in terms of dev and cost (and retention if people first see the "just put it out" MVP). Is spending 3 months making a "fake product" worth then having to start it from scratch?

About three months ago we released SaaS Boilerplate as open-source - since then, we got more than 1.1k github stars, over 600 people in our Discord community and we observe Development Teams use it on daily basis. BUT… We also got feedback, that the stack is a bit heavy, that you need to know a lot of technologies to get started… Yeah, not all teams can dive into hardcore enterprise-level stack from the get go. We also spotted we need something lightweight for some projects at Apptension… Immidiately after the release of SaaS Boilerplate, my brilliant cofounder Michał Kleszcz started building a lightweight version of SaaS BP based on some most modern tools like Next.js, GraphQL and Apollo and more. Now, I am happy to announce that we just released ALPack - obviously, as open-source. So, if you consider starting a new project and looking for a lightweight yet powerful stack that has some of the most important features for building Apps from day 0 - check it out 👉 https://lnkd.in/dnQ5fzuH #nextjs #react #graphql #startups

Do you know that scaling your application doesn't have to be costly or complex? Nobox offers scalable backend services that grow effortlessly with your business needs, ensuring optimal performance at every stage✅️ #TechInnovation #BackendAsAService #CloudComputing #BusinessGrowth #StartupSupport #AviationServices #DataManagement #SocialNetworking - #EfficientTech #BusinessEfficiency

Hey LinkedIn champions! Today, let's embark on a tech adventure into the fascinating realms of building scalable software through the magic of microservices and containerization. 🏗️💻 𝗪𝗵𝘆 𝗦𝗰𝗮𝗹𝗲 𝗠𝗮𝘁𝘁𝗲𝗿𝘀? 📈 Scaling your software is like turning up the volume on your favorite tune; it amplifies impact! Microservices and containerization are the secret ingredients to make your digital symphony heard loud and clear. 🔊 𝗠𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀: 𝗧𝗵𝗲 𝗦𝘂𝗽𝗲𝗿𝗵𝗲𝗿𝗼𝗲𝘀 𝗼𝗳 𝗦𝗰𝗮𝗹𝗮𝗯𝗶𝗹𝗶𝘁𝘆! 🦸 Imagine your software as a superhero squad, each with its unique power (microservice) working together to save the day! Microservices break down the monolith, making your app nimble, scalable, and oh-so-powerful. ⚡ 𝗖𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿𝗶𝘇𝗮𝘁𝗶𝗼𝗻: 𝗕𝗲𝗰𝗮𝘂𝘀𝗲 𝗘𝘃𝗲𝗿𝘆 𝗛𝗲𝗿𝗼 𝗡𝗲𝗲𝗱𝘀 𝗮 𝗦𝘂𝗶𝘁! Containers are like superhero suits, providing each microservice with its own invincible armor. They keep everything tidy, portable, and ready for action across any digital battlefield. 🌐 𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀 𝗚𝗮𝗹𝗼𝗿𝗲! 🚀 ⚙️ S͟c͟a͟l͟a͟b͟i͟l͟i͟t͟y͟: Microservices allow you to scale specific features, not the entire application. No more bottlenecks! 🔧 F͟l͟e͟x͟i͟b͟i͟l͟i͟t͟y͟: Containers make deploying and updating a breeze. It's like giving your software a makeover without breaking a sweat. 🌍 C͟o͟n͟s͟i͟s͟t͟e͟n͟c͟y͟: Containers ensure your software behaves the same way everywhere, from your local machine to the cloud. No more "it works on my machine" mysteries! Share Your Scaling Stories! 💬 Have you ventured into the world of microservices and containerization? What challenges have you faced, and what victories have you celebrated? Let's swap tales and conquer the scaling universe together in the comments! 🌐💬 #ScalableSoftware #Microservices #Containerization #Wamisoftware

It’s tempting to go after everyone—from hobbyists to Fortune 500s—when you’re a new company. But the better choice is usually to do more of what works. Since the rise of Heroku, the default for dev platforms has been to start by marketing to developer hobbyists and then, over time, develop a user base that will lead to acquiring larger customers. We’ve had the opposite experience at Aptible. We started by serving a niche market: growing healthcare tech startups that needed to update their security and compliance protocols to suit HIPAA regulations. We found that we were well-positioned to provide the infrastructure they needed as they scaled. Soon, our customers’ businesses were growing. They asked for our help managing their infrastructure as they scaled, and we had a choice to make: we could go the Heroku route, expanding our market share using the product we’d already developed; or we could focus on improving our existing product to retain our current clients. We chose the latter. And as our product developed, we found that we’d built the perfect platform to serve tech clients who were already scaling. By focusing on retention, we built out our own niche. Staying narrow means we’ve been able to focus on very specific customer needs, like increased container sizes. Our customers love that they can scale up their container sizes all the way to the limits of AWS, while other providers, for various technological reasons, have smaller size limits. Our unique ability to give scaling companies the infrastructure they need—infrastructure that can handle complex requirements and works for development teams of dozens of engineers—turned into our market. Going broad sounds fun if you’re serving a niche industry. But our experience at Aptible tells me that staying in your lane can make all the difference. We are now in a position to call ourselves the best (and only!) platform for scaling companies because we focused on customer retention…in other words, we stuck with what works.

Aptible started with a niche: healthcare tech startups scaling under HIPAA. By prioritizing customer retention and refining our platform, we've become the go-to for scaling companies. Staying in our lane made all the difference. 🛣️⬇️ #ScalingWithAptible