Can I vibe code Sizekick?

sizekick.io ↗·sizing-recommendations·$99/mo·tiered

KEEP — THE UI ISN'T THE MOAT

Sizekick combines 2D video/photo smartphone body scanning (computer vision) with exact garment measurement specs to predict fit. If you only need a questionnaire asking height, weight, and preferred fit, an AI coding agent can build that in a few days. However, building reliable client-side pose estimation, body-to-garment 3D mesh mapping, and handling biometric privacy regulation is a significant computer vision project that is inefficient to maintain in-house.

Share X LinkedIn

The verdict

KEEP

Replaces

$299/mo

Vibe code score

4/10

MVP build time

2-4 weeks

Full replacement

12-18 months due to browser-based computer vision pose estimation and 3D body fitting models.

Editorial opinion, produced with a published methodology from public information. Not a statement of fact about the vendor. How we score · Report an error · Pricing checked 2026-10-20

01

Why this verdict

Building a rule-based questionnaire size guide takes a weekend. Reconstructing 3D body measurements from 2D mobile camera feeds with GDPR-compliant biometric privacy controls requires specialized computer vision engineering.

Verdict

KEEP

Vibe code score

4/10

Moat strength

5/10

02

What it really costs

Sticker price versus what a real store ends up paying.

Entry$99/moTypical store$299/mo≈ estimated · 2026-10-20
Starter$99/moUp to 1,000 recommendations/mo with basic size chart matching
Growth$299/moUp to 5,000 recommendations/mo including camera-based AI body scanning
Enterprise$799/moHigh volume with custom garment pattern mapping and dedicated support

Charged based on store session volume or total sizing recommendations generated per month.

Where this number comes from
Captured
2026-10-20 (21 days ago)
Verified by
crawler

Assumptions: Charged based on store session volume or total sizing recommendations generated per month.

03

The one-shot build prompt

Paste it into your agent of choice. Nothing else needed.

The one-shot build promptbuild it on Lovable
Build a lightweight garment size recommendation microservice consisting of a React-based embeddable PDP widget, a Node.js/TypeScript REST API, and a PostgreSQL database.

1. Data Schemas: Implement tables for GarmentSpecs (id, SKU, brand_id, category, chest_cm, waist_cm, hip_cm, shoulder_cm, sleeve_cm, stretch_factor), SizeCharts (brand_id, size_name, chest_min, chest_max, waist_min, waist_max, hip_min, hip_max), and RecommendationLogs (session_id, sku, user_height, user_weight, body_shape, target_fit, recommended_size, confidence_score).

2. Recommendation Core Engine: Implement a sizing calculation module. Use standard anthropometric regression formulas (estimating chest, waist, and hip circumference from height, weight, age, and selected body shape) combined with user-provided direct measurements if available. Compare computed body bounds against the GarmentSpecs data adjusted by the garment stretch factor and user fit preference (tight, regular, loose).

3. Storefront PDP Widget: Build a client-side JavaScript bundle (<20KB) that injects a 'Find My Size' trigger adjacent to the native ecommerce size selector. Upon trigger, open a multi-step modal capturing user inputs. Provide instant size recommendations with detailed explanations (e.g., 'Size M will fit tightly across shoulders; Size L is recommended for a relaxed fit').

4. Return Feedback Calibration Engine: Implement a webhook handler for ecommerce return events. When an item is returned for fit reasons (e.g., 'too small'), adjust the dynamic offset variable for that specific SKU and size in the recommendation logic.

5. Edge & Failure Cases: Handle missing spec data gracefully by falling back to category-wide size averages. Manage metric (cm) vs imperial (in) conversions cleanly. Ensure no personally identifiable biometric data is logged.

6. Out of Scope: Real-time browser webcam video streaming, TensorFlow.js human body pose extraction, 3D body mesh generation, and biometric image data storage.

$ each button prefixes agent-specific run instructions · build your own product, never copy proprietary code, trademarks or designs

04

Scorecard

Deterministic scoring, same method for every product.

Vibe code score

4/10

Moat strength

5/10

Technical difficulty8/10
Operational burden7/10
Integration depth3/10
Data advantage7/10
Network effects3/10
Compliance load4/10

05

What you keep, what you lose

The honest trade of rebuilding it yourself.

What you can actually replace

  • ✓Interactive PDP size guide overlay modal
  • ✓Form-based user size recommendation (height, weight, age, fit preference)
  • ✓Storefront analytics dashboard for sizing widget interaction rates
  • ✓CSV ingestion interface for brand garment measurement charts
  • ✓Dynamic fit advice callouts (e.g., 'Runs small, order one size up')

What you lose

  • ×Smartphone camera video/photo 2D AI body scanning models
  • ×GDPR-compliant biometric data pipeline that auto-deletes raw user images
  • ×Cross-brand body measurement and actual garment return outcome models
  • ×Automated garment spec parsing from pattern design files and CAD tech packs
  • ×Integrated 3D body visualization models for end-users

06

Why people still pay — the real moats

Moats

  • — Proprietary computer vision models trained on 3D body scans and sizing outcomes
  • — GDPR biometric compliance framework for handling customer imagery
  • — Database connecting actual garment specs across brands to real human body dimensions

Hard parts

  • — Running WebGL/TensorFlow.js pose estimation in mobile WebViews without rendering lag or crashes
  • — Extracting reliable anthropometric body measurements regardless of camera tilt, room lighting, or loose clothing
  • — Maintaining GDPR compliance and biometric consent frameworks when acquiring user imagery
  • — Normalizing messy, unstructured apparel technical specification sheets across thousands of SKUs
  • — Onboarding brands that lack structured or accurate physical garment measurement data
  • — Navigating legal risks related to biometric photo ingestion under EU and US state privacy laws (e.g., BIPA)
  • — Ongoing tuning of sizing algorithms against store-specific post-purchase return reason data
  • — Handling customer support overhead when user self-measurement errors cause bad sizing advice

Network effects you cannot generate

  • — Cross-merchant user biometric profile portability allows buyers scanned on one brand to get instant fit advice on another.

Build this instead

Rule-Based PDP Fit Advisor

A light widget asking customer height, weight, and preferred fit, comparing those against a structured Shopify garment measurement matrix.

Build this instead

Garment-to-Garment Spec Matcher

A PDP tool allowing buyers to enter exact measurements of a brand/shirt they already own to find the matching size in the target SKU.

Build this instead

Return-Driven Sizing Callout

An automated system that reads historical Shopify return reason data and dynamically displays 'Runs Small' warnings based on real customer feedback.

07

Prior art — do not start from zero

Existing projects and paid alternatives worth pricing first.

08

Open source alternatives to Sizekick

Self-hostable projects that cover most of the same ground. Free licence, your infrastructure, your on-call.

09

Have you actually replaced it?

One click, no account. It moves the ranking.

Community verdict

share on X ↗
Successful
0
Failed
0
Success rate
no data yet
Spend killed
$0/mo

10

Compare

Same category, different trade-offs.

11

FAQ

+Can I really replace Sizekick with an AI-generated app?

NO — COMPUTER VISION BODY SCANNING IS NOT AN LLM WRAPPER. Building a rule-based questionnaire size guide takes a weekend. Reconstructing 3D body measurements from 2D mobile camera feeds with GDPR-compliant biometric privacy controls requires specialized computer vision engineering. An MVP takes roughly 2-4 weeks; matching the product properly is closer to 12-18 months due to browser-based computer vision pose estimation and 3D body fitting models..

+How long does it take to rebuild Sizekick?

A usable internal version: 2-4 weeks. A version you would sell or bet a business on: 12-18 months due to browser-based computer vision pose estimation and 3D body fitting models., mostly spent on running webgl/tensorflow.js pose estimation in mobile webviews without rendering lag or crashes.

+What do you actually lose by leaving Sizekick?

Smartphone camera video/photo 2D AI body scanning models GDPR-compliant biometric data pipeline that auto-deletes raw user images Cross-brand body measurement and actual garment return outcome models

+Is it legal to build a Sizekick alternative?

Building a competing product with your own code is normal competition. Copying their code, trademarks, brand assets or scraping their platform is not. Use the prompt to build your own implementation of common features.

Written by EcomReStack research agent — 18 years in the Magento ecosystem. Last reviewed 2026-10-20.

Sources consulted

Scores are computed, not typed. Read the methodology.

One e-commerce SaaS teardown every week.

Honest verdicts, build prompts and overlooked vertical SaaS opportunities. No tracking pixels, no drip sequence, unsubscribe in one click.

free forever · no third-party tracking · the prompts stay public