[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-pricing-tiers-design-en":3,"blog-adjacent-pricing-tiers-design-en":29,"blog-related-pricing-tiers-design-en":62},{"id":4,"slug":5,"title":6,"excerpt":7,"content":8,"cover":9,"tone":10,"author":11,"publishedAt":12,"updatedAt":12,"readingMinutes":13,"featured":14,"tags":15,"category":19,"seoSettings":28},60,"pricing-tiers-design","Designing Pricing Tiers","Tiers are not random feature buckets. They should let a client recognise which one they belong to.","\u003Cp>For SaaS and productised services, pricing is often decided on instinct: list the features, split them into three tiers. Clients finish reading without knowing which tier fits them, or why the expensive one costs more.\u003C\u002Fp>\n\u003Ch2>The shape of three tiers\u003C\u002Fh2>\n\u003Cp>An entry tier solves one clear problem at a low price, without being crippled, so the core flow works end to end.\u003C\u002Fp>\n\u003Cp>A standard tier targets the most common client size, includes collaboration and data capabilities, and is the one you actually sell.\u003C\u002Fp>\n\u003Cp>A high tier serves clients with special needs: private deployment, audit, custom integration, priced to reflect service cost.\u003C\u002Fp>\n\u003Ch2>Two design principles\u003C\u002Fh2>\n\u003Cp>Group by value, not by feature count. Clients pay to remove a headcount, not to gain ten buttons.\u003C\u002Fp>\n\u003Cp>Leave an upgrade path. When a client grows, there should be a natural reason to move up rather than re-evaluate the market.\u003C\u002Fp>\n\u003Cp>Pricing is part of the product. Clear pricing halves the conversation in sales.\u003C\u002Fp>","","blue","佳益方圆团队","2026-06-17T11:10:00+08:00",1,false,[16,17,18],"Pricing","Commercial","Product",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},2,0,"product-thinking","Product Thinking","Requirement analysis, user experience and product design methods, plus the thinking from business problems to product solutions.","lightbulb","article",50,{},{"previous":30,"next":45},{"id":31,"slug":32,"title":33,"excerpt":34,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":36,"updatedAt":36,"readingMinutes":13,"featured":14,"tags":37,"category":41},40,"testing-on-a-budget","What to Test When the Budget Is Tight","Without a dedicated QA team you still need a strategy. Spend the limited effort where failures cost the most.","cyan","2026-06-19T11:10:00+08:00",[38,39,40],"Testing","Quality","Engineering",{"id":13,"parentId":21,"slug":42,"name":40,"description":43,"icon":44,"cover":9,"tone":10,"kind":26,"sortOrder":4,"count":21},"engineering","Hands-on engineering practices in architecture, performance optimization, AI integration and cross-platform delivery from our R and D team.","cpu",{"id":46,"slug":47,"title":48,"excerpt":49,"content":9,"cover":9,"tone":50,"author":11,"publishedAt":51,"updatedAt":51,"readingMinutes":13,"featured":14,"tags":52,"category":56},80,"database-pool-outage","Incident Review: Running Out of Database Connections","The system went down at nine on a Monday morning because one connection was never closed.","slate","2026-06-15T11:10:00+08:00",[53,54,55],"Retrospective","Incident","Database",{"id":57,"parentId":21,"slug":58,"name":59,"description":60,"icon":61,"cover":9,"tone":10,"kind":26,"sortOrder":31,"count":21},3,"project-retrospective","Project Retrospectives","Real project records from zero to one, covering problems, solutions, lessons learned and final outcomes.","clipboard-check",[63,73,83],{"id":27,"slug":64,"title":65,"excerpt":66,"content":9,"cover":9,"tone":67,"author":11,"publishedAt":68,"updatedAt":68,"readingMinutes":13,"featured":14,"tags":69,"category":72},"grading-requirement-confidence","Grading the Confidence Behind Requirements","Treating requirements as facts is the most common cause of delay. Requirements differ in how reliable they are.","indigo","2026-10-15T09:00:00+08:00",[70,18,71],"Requirements","Risk",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},{"id":20,"slug":74,"title":75,"excerpt":76,"content":9,"cover":9,"tone":67,"author":11,"publishedAt":77,"updatedAt":78,"readingMinutes":13,"featured":14,"tags":79,"category":82},"vertical-product-rules","The Watershed for Vertical Products: Writing Industry Defaults into the System","Vertical is not a new industry label on a generic product. The real barrier is understanding and carrying the default rules that practitioners take for granted.","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[80,81],"Industry Products","Product Design",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},{"id":84,"slug":85,"title":86,"excerpt":87,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":88,"updatedAt":88,"readingMinutes":13,"featured":14,"tags":89,"category":91},51,"mvp-boundary","Drawing the Boundary of an MVP","Minimum viable is not the fewest features; it is one complete business loop running end to end.","2026-10-03T10:13:00+08:00",[90,18,70],"MVP",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21}]