Should a vertical platform begin with a directory, public content feed, or relationship feed?

Choose the primary model from the user's first job: find a suitable provider, consume useful content, or maintain trusted relationships. A review directory, public feed, and relationship feed are not alternative home-page layouts and have no fixed order of complexity. Wavesteam compares core objects, cold start, distribution, trust, governance, and commercial loop. A hybrid can follow, but the first release needs one dominant loop or all three sides lack supply.

Model	Core object and entry	Success	Cold-start priority	Main governance risk
Directory/review marketplace	Merchant or service via search and filters	Find, inquire, book, or fulfil	Verified supply, structured data, geographic density	Fake merchant, review manipulation, price and fulfilment dispute
Public content feed	Author and content via recommendation/follow	Learn, save, interact, convert	Reliable quality content, tags, distribution	Copies, illegal material, undisclosed promotion, ranking bias
Relationship/circle feed	People and relationship via friends/groups	Repeated interaction and trust	Import genuine relationships, invitation, visibility expectations	Harassment, relationship abuse, privacy, pile-on
Hybrid	Merchant, content, and relationships	Content informs choice and transaction or trust persists	Prove one loop first	Permission, recommendation, review, and attribution multiply

When comparing platform capabilities, constraints, and switching costs, also compare Should a referral distribution program start with SaaS or custom development? and How different are the app and mini-program versions of the same product?; the linked guidance adds context that should be considered in the same decision.

A directory needs identity and qualifications, category or location, availability, price, and fulfilment state; reviews should link to real experience and support merchant response and appeal. A content feed can begin with following, recency, tags, and human operation rather than complex ML, while recording exposure, click, negative feedback, and quality. A relationship feed need not start with real-time chat: visibility-limited posts and relationship rules can be tested before messaging.

Use real tasks to select. An explicit search for a nearby bookable service favors directory and filters. A decision needing education and examples favors content. A member or peer community whose value comes from continuing interaction favors relationship and visibility. Wavesteam validates with interviews, search and support evidence, and comparable clickable tasks rather than inferring from the industry name.

For each candidate, observe whether users find the result, time, required trust evidence, and next action. Then test supply: who creates and verifies listings, who produces content repeatedly, and why people connect. Recommendation cannot fix empty or untrusted supply, and a relationship graph without interaction motivation is an empty shell.

Platform duties differ. A marketplace may trigger verification and consumer duties under China's E-Commerce Law. Personalized ranking can require assessment under the Algorithmic Recommendation Provisions. Posts, comments, and relationships need reporting, appeal, review, evidence, and account governance under relevant content rules such as the content ecosystem provisions. Wavesteam implements confirmed merchant, content, recommendation, visibility, and appeal controls; the operator and advisers determine the actual legal position.

Add another model only from evidence. A service directory can add cases that improve choice. A content community can add following after users repeatedly seek the same authors. Measure content-to-listing paths, searches needing experiential material, and qualified retention from relationships rather than copying a competitor tab.

Wavesteam delivers the primary loop, objects and states, cold-start supply plan, distribution rules, governance workspace, and evidence measures. Track valid supply and fulfilment, qualified content use and conversion, or relationship interaction and retention alongside complaints, false actions, and human cost. Duration follows media, review, traffic, and actual scope rather than a generic calendar number.