Jon Chui

I'm excited to share that I'm co-founding HealthSpark with my college classmate Stephen Grinich, and we were recently backed by Y Combinator! HealthSpark is empowering physical therapists to launch, run, and grow their own AI-native independent practice by automating their administrative tasks including insurance, scheduling, calls, texts, and charting. If you know any physical therapists, we'd love to get in contact! https://lnkd.in/gRFRknXz

65

15 Comments

As a tech entrepreneur, I'm always looking for ways to streamline the development process. Recently, I discovered a game-changer: using Claude 3.5 Sonnet's artifacts to rapidly prototype and build MVPs. 🔧 Use Case: Building a Task Management App Here's how I leveraged Claude to create a basic task management app in record time: 1. UI Design: Used Claude to generate React components for the main dashboard, task list, and input form. 2. Backend Logic: Created Python scripts for data handling and API endpoints. 3. Database Schema: Designed a simple SQL schema for storing tasks and user data. 4. API Documentation: Generated a comprehensive API doc in Markdown format. The best part? Claude provided all these as reusable artifacts, allowing me to iterate quickly and focus on core functionality. 💪 Benefits: - Rapid prototyping - Consistent code structure - Easy collaboration with team members - Significant time and resource savings Have you tried using AI to accelerate your MVP development? DM me for a free detailed guide using Claude for MVP development. Follow Leon Zheng to join the unique journey of AI! #TechInnovation #MVPDevelopment #AIinTech #ClaudeAI #ProductDevelopment

1

3 Comments

Would it be possible to have some help updating this section of our website on Framer? Simple edits: 1) Update to say Terms and Conditions, 2) put a heart between "with" and "in" and 3) Put Space Needle within the word Seattle. 4) If possible, make "Built with <3 in Seattle a really cool mini interactive graphic. 5) Ensure that the spacing is adjusted so that it looks right. I'm new to Framer and am having some trouble.

5

1 Comment

PoC or MVP? That is the question. Choosing between a PoC (Proof of Concept) and an MVP (Minimum Viable Product) is not as straightforward as it may seem. Recently, I spoke with a founder grappling with this dilemma. While some may argue for jumping straight into MVP, I believe there’s a distinct time and place for both approaches, depending on the context and goals. As a developer, I see the differences between PoC and MVP development from a slightly different perspective. A PoC is all about proving a concept's technical feasibility. It’s a stripped-down version with minimal features, meant to validate whether the idea can work. The development process here is often quicker and doesn’t prioritize scalability or long-term use. Think of it as a quick test run—just enough to see if the foundation is stable. On the other hand, MVP development is a different ball game. It’s a product with core functionalities, ready to be introduced to the market and tested by real users. Here, user experience, scalability, and code quality matter because this is what your audience will interact with. Unlike PoCs, MVPs need to hold up under real-world conditions. At Pecode, we help founders make this decision based on their unique needs—whether that’s validating an idea with a PoC or launching a market-ready MVP. What stage of development is your startup in, and how are you deciding between PoC and MVP? #StartupDevelopment #PoCvsMVP #ProductDevelopment #TechInnovation #MVPDevelopment #ProofOfConcept #NoCodeSolutions #SoftwareDevelopment #StartupLife #ProductLaunch #Entrepreneurship #LeanStartup #TechStartups #Innovation

29

5 Comments

Who knew building a scalable backend could be this easy? Enter Supabase (Open source) Supabase is quietly changing the way we think about backend infrastructure. Think about it—instant backend, built-in auth, real-time data, Storage buckets like S3 all without having to write endless custom code. For product managers, this means faster iterations and fewer headaches coordinating between frontend and backend teams. For developers? It’s a mixed bag. On one hand, it simplifies the process. On the other hand, it raises the bar on what’s expected. You’re no longer just the coder—now it’s about how fast you can deliver solutions. It's time to think bigger.

6

1 Comment

There's a subtle but seismic shift when organizations cross the threshold from product to platform management. 1. Your Success Metrics Change PRODUCT: Success = Your Users' Success PLATFORM: Success = Your Partners' Success + Their Users' Success 2. Ecosystem Dynamics Emerge - You're no longer just shipping features - Third-party developers start building on top of your solution - Your roadmap includes API endpoints, not just user interfaces - You spend more time on documentation than marketing copy 3. Value Creation Shifts Before: You created 100% of the value Now: You might only create 20%, but you enable 500% more total value 4. The Critical Insight It requires comfort with less control. The best ideas often come from outside your team - and that's exactly what you want. Key Indicators You're Becoming a Platform: ✓ Partners ask about your API before your UI ✓ Competitors become collaborators ✓ Your team debates governance more than features ✓ Users create unexpected use cases you never designed for The most interesting part? This transition often happens organically before teams even realize it. The question isn't whether to make the shift, but whether to embrace it. Have you noticed this transition in your organization? What were the first signs? #ProductManagement #PlatformStrategy #TechLeadership #DigitalTransformation

10

Building new products is (supposed to be) fun 🎉, but it's hard to know where to start 🤨 ➡️ Here's the framework I use to line up features on the path to an MVP #product #software

12

Launch Week is finally here! We're kicking off the week with a highly requested feature: Custom Middleware for Encore.ts, our open source backend framework for TypeScript. While Encore.ts comes with most common middleware built-in (auth, logging, tracing, etc.) the ability to easily define custom middleware is useful whenever you need to define your own reusable functionality across multiple endpoints. Learn all about the launch and follow along throughout the week at: https://lnkd.in/dw2ZhU85

19

1 Comment

🚨 The silent killer in software isn't what you think I've spent 10 years as a designer working with startups. Now I'm building a B2B software company. And I keep seeing the same pattern: Most founders obsess over: • Feature lists • Tech stack • Speed • Marketing But they're missing the biggest shift in how people choose software. It's design. Here's why this matters: 1. Users have changed. They don't compare your product to competitors. They compare it to every app on their phone. Slack didn't win because it had better features. It won because it felt natural, simple, joyful. 2. "But software is about functionality!" Wrong. (I've heard this 100x from engineering founders) Your product has 7 seconds to make users *feel* something. That's why Notion beats Confluence That's why Linear beats Jira That's why Figma beats Adobe First impressions = everything 3. Here's what great design buys you: • Faster user adoption • Word of mouth growth • Higher usage rates • Better retention Design isn't a cost. It's leverage that compounds. 4. The secret? Great design isn't about being pretty. It's about: • Reducing cognitive load • Creating obvious workflows • Making complex things simple • Building trust through polish 5. Most software looks like it was built by engineers for engineers. That worked in 2010. It fails in 2024. Why? Because users have tasted what good design feels like. And they won't go back. 6. The playbook is simple: • Hire designers before you think you need them • Make design your moat • Let your UI be your best marketing While others add more buttons, you're building momentum through design-led growth. This is exactly how we're building Rallybase. Beautiful by default. Powerful when you need it.

34

3 Comments

Over the last week, pre.dev has matched 50 Entrepreneurs/Businesses with Dev Agencies, reducing their costs by >20% compared to searching for an agency on their own. How did we do that? By providing them a complete set of schematics, documentation, and a boilerplate codebase based on their unique idea - in minutes (before they even talk to a dev agency). We also allow them to dynamically filter functionality that may not be necessary for a first product lunch, reducing their development overhead. So if you or anyone you know is looking to save money on software development, check out https://pre.dev today!

43

4 Comments

Running llama 3 by meta does not require you to have sophisticated system setup. I have set it up on my personal laptop which happens to have a GPU with it. I have used llama.cpp to run the int4 and int8 quantized model of llama 3. Running a language model for your personal use does not require you to have cloud access such as azure. I have demonstrated one use case of deploying personal language model. During my research purposes It so happened that chatgpt was very hard to access either cause it was down or the site simply would be buggy during which I used the llama model deployed by https://lnkd.in/gWfkaKZA where I think such systems can be deployed by organizations for internal research purposes. Below is the link to the steps I followed in deploying and comparing the int4 and int8 quantized model. https://lnkd.in/gzShCPCD

21

5 Comments

This is my first time writing an article. It's about how to build an MVP without prior knowledge of mobile development, the mistakes I fell into and how to avoid them, the results, and the journey of learning. I will post part two soon for a deeper dive.

37

2 Comments

Ever wonder what keeps tech founders up at night? I'm sharing key challenges faced while co-founding an accessibility-focused company. Spoiler: It's not just about coding. 1. Building accessible products is difficult. Using an accessible product is great. Building it, however, is a whole different story. There's no rulebook or guide. But that doesn't mean it's impossible. My hack: focus on user-centered design, and don't just listen to your customers. Bring them along for the ride. Build with them. 2. Getting funding for what may seem like a niche market comes with its own challenges. 'Social impact' is a term people like to throw around. It makes people feel good if they see it or if they are part of it. But when it comes to getting funding, one of the key questions that often comes up is: "Is there a lot of demand? Will people pay for it?" Now, don't get me wrong, every entrepreneur is faced with this question when they step out to raise funding. But here is the difference with building in the accessibility space. You need to prove that your product has universal benefits. 3. Education. Education. Education. As an entrepreneur, you quickly learn that you need to build to solve your customers' pain points. But here's the problem. The people who are often times the decision makers, end up being people who haven't faced the problem. Or they do not understand how crucial the problem may be. So how do you bridge that gap? You educate. You advocate. You raise awareness. Without the proper education, the value of your product will be negligible. Overwhelmed yet? Don't worry. There are solutions to these problems. That is the beauty of entrepreneurship. There is no magic bullet for a problem or a challenge. But you will always find a solution. What challenges have you faced in your journey? Drop them in the comments.

13

Large codebases are scary! 😱 When you're starting out contributing to a mammoth codebase like SigNoz with over 300000 lines of code, you have no idea where to even start looking. We took an open issue from Signoz's repository and asked Potpie AI's low level design agent to help us get started. The results were mindblowing 🤯. For a repository with THOUSANDS of files, Potpie was able to : * Pinpoint which exact file needed to be updated * Tell which part of the code needed updating * Suggest next steps like testing 🥧 agents >> Try us out at https://potpie.ai We are open source! Pranay Prateek Ankit Nayan Shivanshu Raj Shrivastava

51

5 Comments

How to put a product (or service) on the market that is profitable? I didn’t find yet the precise secret sauce, but I move forward with the recipe. Here is some learnings. 👇 I spent time building software products. Some of the projects were great success ($15K invested for $2M ARR), others were epic fails ($3M invested for $100K ARR) and others never see the daylight. To put a product on the market, there is one preliminary constant: the product must bring value to the user. When I’m talking about value, it is real value to solve a real problem; not a nice to have feature. You should be the painkiller on the market, not the vitamin. 👉 Now, you have a market, you are solving a problem. There is still the question of the price. I’m a huge fan of Jonathan Stark value-pricing approach (if you don’t know, it worths the reading) and the good old Solera formula 4:1/8:1 introduced by Tony Aquila. The idea behind value-pricing is to identify the value generated for the end user and capture a part of the value. According to Tony’s formula, you charge $1, your user should get between $4 and $8 of value. We can quibble on the ratios depending on industry, products, etc and this can evolve over time depending on the competition. But there is an important point. 👉 You have an idea about the market price. Better, you can evaluate if it worths the investment. You have a market price and a problem. Are you able to solve this problem at that range of price? If not, this is not a worth problem to solve 😅. The last pressing question is about how to solve the problem. There are infinite possibilities to address a problem (hopefully by software 😆) and it is very difficult to get proper feedback from the (potential) user. 👉 Buyers are liars. Many founders engage in discussions with potential customers to get feedback on their ideas. However, the issue is that users (particularly friends) are unlikely to criticize your concept. Instead, they might offer vague compliments like "this is cool!" or "I'm very interested!" which are often not real indicators of interest. The only way to obtain a true signal in these discussions is to attempt to make a sale. 👉 Skip the market research and go straight to the sales call. A positive aspect is that you're pre-validating the distribution channel. If you struggle to find anyone to talk to now, it's unlikely you'll reach them later. This process allows you to make mistakes and gain experience before engaging in real high-value sales calls. You're also testing the latent need hypothesis directly with the market while keeping expenses low. Is this a recipe for success? For sure not but at least it is possible to work around avoidable mistakes. 😊 And you? 🤔 Do you have some process to exchange about putting a product on the market? I’m curious to hear in the comments. 👇

13

4 Comments

I finally had time to write the second post about early-stage product design mistakes that startups make. This post is about the mistakes we made at Ackcio, wherein we incorporated every single client request without considering broader market requirements. Please take a look and let me know your thoughts. If you found this post helpful, please share it and spread the love. If you like to stay informed about future posts, please subscribe!

54

1 Comment

As business owner or non-tech founder, it is difficult to evaluate the performance of your software engineering team. There are technical metrics. Yet, the most important are the business metrics 📈 👇 Plenty of papers discussed about the engineering velocity. There are different approaches. Yet, the most accepted metrics today are the DORA metrics. There are 4 DORA metrics: 1️⃣  Change lead time: the time it takes between the first line of code produced by the developer to be successfully deployed to production. 2️⃣  Deployment frequency: how often application changes are deployed to production. 3️⃣  Change failure rate: the percentage of deployments that cause failures in production, requiring hotfixes or rollbacks. 4️⃣  Mean time to recovery (a.k.a. failed deployment recovery time): the time it takes to recover from a failed deployment to production. Thanks to those 4 metrics, you have a clear view. You know better your Software Delivery Throughput and your Software Delivery Stability. Measuring those metrics is quite easy with modern tooling and CI/CD pipeline but how do you know if it is good or bad? 🤔 The DORA group is publishing yearly their report. The report includes the statistics from more than 39,000 professionals. The performance levels of engineering organizations are the picture linked to this post. ⚠️ As for all statistics, you should consider your context and the industry you are part of. SaaS for social media is a bit different than Medical Devices where regulations slowdown the delivery cycle to production. Now, it is up to you. 💪 We used to say: "Meten is weten" in Belgium 🇧🇪 ("Measuring is knowing"). It is the first step to improve the throughput and the stability. Even if you may need an experienced professional to fix things up. 😉 👇 Did you take the test with your own engineering team? Do you collect such information through your tools? Are you Elite, High, Medium or Low performer? Or a bit of each? 🙂 👇

7

2 Comments

According to the International Consumer Protection and Enforcement Network (ICPEN), 76% of global sites and apps employ at least one dark pattern, with 67% utilizing multiple deceptive strategies. I understand that, at a company level, the pressure to deliver quick results can sometimes lead to the unintentional introduction of dark patterns in product design. While these tactics might achieve short-term goals, they often make technology stressful and challenging for users. This goes against the very purpose of technology, which is to simplify and enhance the user experience. https://lnkd.in/gWQAGN-9

2