Behind a beautiful frontend lies a tangle of complexity — no APIs, language barriers, and fragmented vendors. The actual job is managing all the ugly bits so users never see them.
Launching a product that looks simple on the surface often hides immense complexity underneath. Thieve.co is a prime example — a curated product discovery app built on top of AliExpress, the giant Chinese marketplace that does not offer APIs for integration. The actual job is to orchestrate a smooth release while handling all the messy dependencies behind the scenes, from vendor communication to marketing readiness.
The stakes are high. Products get shipped, but the marketing team might not be ready with distribution plans. Analytics might be missing, so you don’t know if the launch succeeded. These common-sense oversights happen all the time. You will learn how to avoid them.
Thieve.co: A case of building on a platform without APIs
Thieve.co started in Auckland, New Zealand, in 2017. It curates a list of products from AliExpress, the largest direct-to-consumer marketplace in China. AliExpress connects suppliers and consumers directly, eliminating middlemen and enabling extremely low prices.
The founder, Tim Scullin, put it plainly: “Although there are some awesome products on AliExpress, finding them can be a painful process. We created Thieve to solve that issue.”
Thieve.co is not a traditional e-commerce site — it does not hold inventory or manage logistics. Instead, it acts as a curated search engine and discovery platform. Products are selected by a global community of designers, fashion bloggers, and creatives, who submit their favorite finds. Moderators then vet these products by reviewing ratings, shipping costs, and reviews before making them available on the site.
Every product on Thieve.co links directly to AliExpress. Thieve.co earns revenue when users click through and purchase on AliExpress.
This setup created unique challenges:
- AliExpress does not provide APIs for product data or integration.
- Vendors in China are often not tech-savvy, and language barriers complicate communication.
- The product team had to build a seamless, beautiful frontend experience while managing these backend complexities invisibly.
Managing a product release under these conditions demands rigorous planning and cross-functional coordination.
Why Thieve.co’s market context matters
Thieve.co piggybacks on AliExpress’s success but operates in a crowded, competitive e-commerce space. The global e-commerce market was projected to reach USD 64 billion by 2020 and around USD 200 billion by 2026. Internet penetration continues to expand worldwide, fueling growth.
Despite the opportunity, the team knew that having a killer product release plan would be a winning factor to reach the right customer base and gain traction.
The product idea and validation
Thieve.co began as a side project at Launch Agent, a digital agency helping companies launch and grow ventures. It gained traction quickly, getting over 30,000 sessions in a few hours with positive feedback.
The team observed that while people loved AliExpress’s low prices, the experience was painful. Searching millions of products to find quality items was difficult.
Thieve.co’s core value proposition: ease the pain of finding awesome products on AliExpress.
The product’s crowdsourcing model was key:
- Over 100 designers, bloggers, and creatives submitted product recommendations regularly.
- Moderators verified product quality using ratings, reviews, and shipping costs.
- The curated list made discovery easy and trustworthy.
This model differentiated Thieve.co from AliExpress’s overwhelming product catalog.
The actual product challenge: managing complexity behind the scenes
Thieve.co’s frontend is simple and elegant. The backend is anything but.
AliExpress’s lack of APIs meant the team had to build custom scrapers and data pipelines.
Language barriers and vendor unreliability required manual intervention and constant quality checks.
The team handled:
- Data extraction and normalization from AliExpress product pages.
- Moderation workflows to ensure product quality.
- Mapping and categorization to enable relevant product recommendations.
- Integration of user feedback loops to refine product discovery.
This complexity affected the release plan and risk mitigation.
Product release checklist: what the Thieve.co team had to cover
The actual job of releasing a product like Thieve.co is not just shipping code. It is ensuring every part of the customer experience is ready and aligned.
Here is the checklist derived from the teaching:
Content readiness
- Clean, efficient layout and navigation.
- Consistent typography and branding across the site and app.
- Clear product categories to avoid user confusion.
- High-resolution images and videos for product previews.
- Accurate and detailed product specifications.
- Relevant and effective search query handling.
Design and UX
- Intuitive user flows from discovery to purchase.
- Responsive design for multiple devices.
- Fast loading times despite heavy product data.
- Seamless integration of the “Thieve Swipes” feature — a Tinder-like interface for product discovery.
Testing
- Functional testing of search, filters, and recommendations.
- Moderation and quality checks on curated products.
- Load testing to handle expected traffic surges.
- Cross-platform compatibility testing.
App optimization
- Performance tuning for both web and mobile.
- Analytics instrumentation to capture user behavior.
- Monitoring setup for errors and crashes.
Marketing and distribution readiness
- Content creation for social media channels (Facebook, Instagram, Pinterest, Reddit).
- Press releases and partnerships with influencers.
- Paid advertising plans on relevant platforms.
- Clear messaging aligned with product positioning.
Analytics and metrics
- Define product release success metrics (user sessions, click-through rate, conversion rate).
- Set up dashboards to monitor launch KPIs in real time.
- Plan for post-launch data analysis and iteration.
Risk mitigation
- Contingency plans for backend failures or data inconsistencies.
- Buffer time for marketing collateral approvals.
- Backup vendor communication channels.
- Clear escalation paths for critical issues.
The checklist reflects that a product release is a cross-functional coordination puzzle — engineering, design, marketing, and operations must all be in sync.
Building a product release plan: strategic components
The team used a Gantt chart to map out the entire year’s budget and roadmap from initial planning through launch, ensuring alignment and transparency.
Key components of the release plan included:
Strategic planning
- Define the product vision: "The best of AliExpress, created by creatives."
- Mission statement: "Thieve is a curated list of products you can buy directly from AliExpress."
- Identify product categories and target customer segments.
- Prioritize features that maximize user delight and ease of discovery.
Product positioning
- Emphasize curation and quality over quantity.
- Highlight crowdsourcing by designers and creatives.
- Differentiate from AliExpress by offering a superior UX and trusted recommendations.
Content creation and distribution
- Develop social media content tailored to each platform.
- Use Reddit as an efficient, less saturated marketing channel.
- Plan influencer collaborations and press coverage.
- Prepare advertising campaigns on e-commerce and social platforms.
Product adoption and retention
- Focus on user experience improvements to reduce friction at checkout.
- Optimize search relevance and product recommendations.
- Use engagement features like "Thieve Swipes" to increase time spent.
- Monitor user feedback and iterate rapidly.
Product release metrics
- Track sessions, click-throughs to AliExpress, conversion rates.
- Monitor product-level performance to identify top and underperforming items.
- Use analytics to guide subsequent releases and marketing efforts.
Risk mitigation plan
- Identify dependencies on AliExpress and prepare fallback options.
- Coordinate marketing and analytics teams to avoid launch-day blind spots.
- Prepare for language and vendor issues with dedicated moderation support.
- Schedule buffer time for unforeseen delays.
The customer challenges Thieve.co addressed
The team identified three core customer challenges:
-
Finding great products among millions on AliExpress. The sheer volume and low-quality listings overwhelm users.
-
Segmenting products correctly for different customer interests. For example, male vs female preferences, trending items by region.
-
Verifying product quality and shipping reliability. Avoiding bad experiences with unreliable vendors.
Thieve.co’s curated approach solved these pain points, making it easier for users to discover and trust products.
Differentiators that made Thieve.co stand out
- A premium curated segment of products from AliExpress.
- Unique UX features like "Thieve Swipes" for easy browsing.
- Personalized recommendations based on customer segmentation.
- Robust moderation processes ensuring product quality.
These differentiators were critical in a market crowded with e-commerce giants.
The actual launch: common pitfalls and lessons
The team emphasized that product launches often fail due to overlooked hygiene issues:
- Shipping the product before marketing is ready to distribute.
- Launching without analytics baked in, leaving you blind to user behavior.
- Poor presentation and communication during launch meetings.
- Lack of clarity on product positioning leading to confused messaging.
Most of these are avoidable with disciplined planning and cross-team alignment.
Managing complexity when your product depends on external platforms
Thieve.co’s reliance on AliExpress without APIs is a textbook example of indirect product ownership.
The product team had to:
- Build custom scrapers and data pipelines.
- Handle manual moderation and vendor communications.
- Abstract away the backend complexity so users see only a smooth experience.
This is a common pattern in India’s tech ecosystem, where many products depend on third-party platforms or legacy systems.
What the actual job is: orchestrating the entire release end to end
Talvinder’s teaching drills down to this: Your actual job is to anticipate every point of failure and make sure the product ships with marketing, analytics, design, and engineering all ready.
This means:
- Creating a detailed release checklist and plan.
- Aligning stakeholders with a clear roadmap and vision.
- Building buffers and risk plans for known unknowns.
- Communicating clearly during launch meetings — no reading from slides, just crisp, authoritative points.
Test yourself: Plan a product release for a complex product
You are the PM at a startup launching a curated e-commerce discovery app in Mumbai. Your product depends on a large external marketplace without APIs. The marketing team is ready in 3 weeks but engineering needs 5 weeks to stabilize the scraper and moderation pipeline. Analytics is partially set up. You have 6 weeks before a major industry event where the launch is expected.
The call: How do you plan the product release to meet the event deadline? What trade-offs do you make, and how do you communicate with marketing and engineering?
Your reasoning:
Where to go next
- If you want to master launch planning: Product Launch Playbook
- If you want to improve cross-team coordination: Stakeholder Management
- If you want to build analytics into your product: Analytics and Metrics Setup
- If you want to deepen your understanding of e-commerce products: E-commerce Product Management
- If you are preparing for PM interviews: PM Interviews