Skip to content
All case studies
2021 — 2026Founder · Developer · Operator

CompraSocial.me

300,000 orders, run by a very small team and a lot of automation.

Delivered at LumaUp sp. z o.o.
Screenshot of the CompraSocial.me homepage
The live product, captured from the public site.
300,000+
orders processed
90%
operations automated
5 yrs
in production

Context

A high-traffic social commerce platform built on WordPress with custom Vue.js integrations, which processed over 300,000 orders — with roughly 90% of daily operations handled by scripts rather than people. Live since 2018, selling across 11 social platforms in 4 languages.

The product

What it sells
Social media growth services — followers, likes and views — across Instagram, TikTok, Threads, Facebook, YouTube, Twitch, Spotify, Telegram, Clubhouse and Pinterest.
Who buys it
Creators and small businesses building social proof, primarily in Italy, with the storefront localised into Italian, Polish, French and Spanish.
Retention mechanics
A points programme ("Cristalli") for registered users plus a 10% bonus on multi-item baskets — both built to raise repeat-purchase rate rather than first-order conversion.
Service promise
Delivery within hours and staffed support 7 days a week — which is only affordable because the fulfilment pipeline underneath is automated.

The problem

The platform grew faster than a small team could manually service. Order handling, verification, delivery tracking and customer messaging were all human tasks, and each one scaled linearly with volume — the classic point where a growing business quietly stops being profitable.

Architecture

Architecture — simplified
SEO · organic no variable cost WordPress storefront · content · SEO Vue.js islandsAPI · PHPMySQL · MongoDBOperations automation ~90% automatedIntakeorder capturedValidaterules + checksDispatchfulfilmentReconcilestatus syncHuman decisionrefunds · disputesexceptions onlyVolume grows, workload does not 300,000+

The interesting part is not the storefront, it is the operations loop underneath it: the automation layer watches the order pipeline and only escalates the exceptions, which is what let order volume grow without headcount growing alongside it.

Technical specification

Platform
WordPress with a bespoke theme for content and SEO, with the interactive surfaces — checkout, dashboards, order flows — replaced by custom Vue.js components against a dedicated API.
Catalogue
11 social platforms, each with its own service types, quantity tiers and fulfilment routing.
Localisation
Four languages (Italian, Polish, French, Spanish) across storefront, checkout and transactional messaging.
Data layer
MySQL for the transactional store alongside MongoDB for high-volume order and status records.
Automation coverage
~90% of daily operations — intake, validation, fulfilment dispatch and status reconciliation — run unattended, with alerting on exceptions rather than supervision of the happy path.
Human-in-the-loop
Refunds and disputes always escalate to a person; automation handles volume, people handle judgement.
Acquisition
SEO treated as an engineering concern, since organic search was the channel without a variable cost per order.
Longevity
In production since 2018 and still trading — over 300,000 orders across its lifetime.

How I built it

  1. Built the commercial surface on WordPress for speed and SEO, then replaced the interactive parts — checkout, dashboards, order flows — with custom Vue.js components talking to a dedicated API.

  2. Mapped every recurring manual operation, ranked them by hours-per-week, and automated them in that order.

  3. Wrote integration scripts covering order intake, validation, fulfilment dispatch and status reconciliation, with alerting on the exceptions instead of supervision of the happy path.

  4. Kept a human decision point on anything involving refunds or disputes — automation handled volume, people handled judgement.

  5. Ran SEO and content as a first-class engineering concern, since organic traffic was the acquisition channel that did not have a variable cost.

Outcome

  • Over 300,000 orders processed across the platform's lifetime.
  • Around 90% of daily operational work automated, dropping the operational overhead dramatically.
  • The business stayed runnable by a small team for five years, because volume growth stopped translating into workload growth.

Have a workflow, a platform, or an invoice that needs work?

Tell me the shape of the problem. If I am not the right person I will say so quickly.

Get in touch