Matt Kenchington’s Post

Software development is expensive, but I've seen many founders missing on this secret sauce to 2x their Dev team's production. (Obviously, without making them work longer) Many founders choose their developers to work in silos. - Building out features... - without knowing what they are for... - Having no idea about how the customers gonna use it. - Most importantly, how much you plan to scale that feature... Developers can deliver more efficiently if they know your future plans of extending a feature in the short term, or not. Because this helps them understand what level of effort in software design that specific features require. For example: If the feature they are developing is not intended to expand, atleast in the near future. They can worry less about structuring that well, and can deliver it fast, or on the flip side they can make it easily extendable from the ground up. You may wonder why don't all the features can go with that same precision? 👉 The answer is the the timeline and the ROI it's gonna provide. Once you let them understand the ROI of a specific feature, they can choose to deliver it fast or either more scalable. If you find this piece of content helpful, Help others via a Repost ♻️. #software #productdevelopment #saas #founders

SaaS founders demo their products to me every day. Quotes I hear almost EVERY time are... 'Huh that's weird, usually this loads immediately' 'We're working on getting this to be a bit faster' 'While we wait, I'll just explain what we're aiming to do' I get it... I know what it takes to build lightning fast tech with a great user experience. But how much are you prioritising product experience for users? It's critical to do the work. Because those frustrating moments are when you lose a customer to a competitor with a better product. There's a technical rule at play. It's called the Doherty threshold. Productivity soars when a computer and it's users interact at a fast responsive pace. It means neither has to wait on each other. The optimal speed is <400ms which is a rate at which a computer response feels instant. When things slow down it doesn't only affect productivity, it also becomes frustrating for the user. If this persists, their relationship with a product is associated with frustration and boredom. It stops users actually wanting to use the software. So, if you're planning that back end rebuild and a new tech stack, can you really put it off that much longer without losing more customers?

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.

I may be one of the only developers that encourages my clients NOT to buy my product! Why? Because I've seen countless examples of adopters investing time, resource, and money into solutions no one else in the business believes in. I've seen SAAS providers (in all industries) promise the world only for the finance manager to cancel the subscription 6 months later. The bottom line 👉 if you don't have an executive / board sign-off, or a #BusinessContinuity policy, or a validated and tested plan in place, technology isn't going to solve that. But with a BIA (#BusinessImpactAnalysis), you can utilise technology if you're confident it can be used during a disruption. You can streamline and make your plans agile by visualising the plan on a beautiful interface. It CAN be the evolution in how you conduct your resilience. But it must come at the right time.

Spent the last few weeks catching up with family and friends. Some of them building SaaS products, and some scaling them. One thing that stood out, particularly when the founders are doing this for the second time, is that they are doing a two step dance in building their product.   Let me elaborate on that, they are building their MVP quick and dirty without being overly concerned about engineering quality of product or feature completeness or scalability. What they are focused on is good design and simplicity in the critical user journeys contributing to the value props. They are doing this with LCNC tools, lot of other single feature SaaS products and lots of software duct-tape with some healthy sprinkling of server-less. Once they have found the PMF they are working towards getting the real product developed with current product as a living spec with a combination of in-house dev team led by a CTO and consulting services vendors. Three of them gave the same playbook.   My interest piqued, did some more research and indeed, that is definitely the advise being given by quite a few seasoned SaaS-preneurs and investors. That to me seemed very smart even if a bit wasteful. Been thinking of the ways to have the cake and eat it it too, while retaining the agility to pivot to a new cake 😀! What is your approach? Do you do a two-step dance or are you in the camp that believes good things take time and effort, and do a slow-build with few customers? #saas #ai #softwaredevelopment #engineering #2024vision #saasos

How developers feel jumping from one product release cycle to the next 🤣 It can get tiring, especially for younger developers. I got worn out about two years into my career. It felt like I was always going from one cycle to the next, never stopping for breaks. Allow me to share some advice: If you feel yourself burning out, take some time off. It takes stamina built up over time and discipline to know when you’re good to go and when you’re not. Do you ever get tired of product release cycles? #engineering #product #saas #tech #techcommunity #innovation

Here is the time-tested blueprint for contemporary SaaS development. Twelve Essential Principles for developing a scalable, modern cloud-based SaaS product. 1. Codebase: One codebase tracked in revision control, multiple deployments. 2. Dependencies: Explicitly declare and isolate dependencies. 3. Config: Store configuration in the environment. 4. Backing Services: Treat backing services as attached resources. 5. Build, Release, Run: Strictly separate build and run stages. 6. Processes: Execute the app as one or more stateless processes. 7. Port Binding: Export services via port binding. 8. Concurrency: Scale out via the process model. 9. Disposability: Maximize robustness with fast startup and graceful shutdown. 10. Dev/Prod Parity: Keep development, staging, and production as similar as possible. 11. Logs: Treat logs as event streams. 12. Admin Processes: Run admin/management tasks as one-off processes. By adhering to these principles, Engineering teams can create products that are not only easier to develop and maintain but also more resilient and adaptable to changing business needs. #SoftwareArchitecture #12FactorApp #SaaSDevelopment #CloudComputing #BestPractices — ♻️ Amplify your network! Share and repost if you found this valuable. 💡 Stay updated on software architecture insights at follow.paramg.com. ✍️ Connect with me on blog.paramg.com for more in-depth articles.

The MVP development landscape is clouded with several myths and misconceptions, much like many popular concepts within software development. At the Techtiz blog, our Myth Buster Series aims to debunk these prevalent myths surrounding tech concepts, simplifying them for those non-tech folks. Feel free to add myths that you've come across in the comments section below. Read our latest blog here: https://lnkd.in/deHzfEdr

Explore our latest article to uncover how the right tech stack can supercharge your Minimum Viable Product journey. Gain insights on optimizing performance, reducing development time, and aligning your tech stack with your product vision. #MVP #TechStack #ProductDevelopment

🌟 Day 24 of 100 SaaS in 100 Days 🌟 Hi, I'm Himanshu, and today we're talking about Kissflow. Even if you don't know much about coding. Kissflow is helping companies big and small make their own apps and automate their work easily. Kissflow is here to solve big problems for IT Leaders, Developers, Process Owners, and Business Users: 🔍 For IT Leaders and Developers: 1️⃣ "How can we let our teams make apps quickly without losing quality?" 2️⃣ "What tools let us automate complex business tasks easily?" 3️⃣ "Can we add our current systems to new apps without problems?" 4️⃣ "How can we make it easier for our teams to be innovative in making apps?" 🔍 For Process Owners and Business Users: 1️⃣ "How can we make our work smoother and more efficient with custom apps?" 2️⃣ "What options do we have to change our work processes as our business changes?" 3️⃣ "Can we get up-to-date info on our work to make smart decisions?" 4️⃣ "How do we make sure our tech upgrades help us meet our business goals?" Kissflow does this by: ✅ Offering easy-to-use platforms for making apps and automating work ✅ Making it simple to connect with current business systems ✅ Providing immediate data and reports for smart choices ✅ Offering flexible solutions that grow with your business Why Kissflow? Because it's where "easy" meets "breezy". Imagine being able to wave a magic wand and poof! Join me tomorrow as we keep exploring how SaaS is changing industries and the way we work. P.S. Here is a picture of one of my favourite metal bands.