Istiaq Nirab full stack + ai
← Case studies
01 PHP 2024

SoundCloudPlace

Social growth marketplace

A storefront and admin for buying social growth packages — likes, views, streams and followers across six platforms — built for client Omar Faruque.

6
platforms sold
40+
packages configured
0
code changes to add a platform
storefront — homepage & services
storefront — homepage & services
Overview

SoundCloudPlace sells growth packages — likes, views, streams, followers — across Facebook, YouTube, Spotify, Soundcloud, Instagram and TikTok. Rather than hardcoding six product pages, the whole storefront is driven by a small set of admin-managed tables: platforms contain groups, groups contain packages and the order form fields those packages need. Adding a seventh platform is a content operation, not a deploy.

Role

  • Full stack engineer

Timeline

  • 1 month

Team

  • Solo

Client

  • Omar Faruque

Stack

  • Laravel
  • MySQL
  • Vue
  • Bootstrap
  • PayPal
The problem
  • Every platform sells a different shape of thing — a video URL, a profile link, a track link — so the order form itself had to be configurable per package, not fixed in code.
  • Prices and package contents change often; a completed order still needs to show exactly what the customer bought and paid for, even after the live package is edited or removed later.
  • The client needed to run this alone from an admin panel — creating platforms, groups, packages and FAQs — without ever touching code.
Approach
  1. Content as data, not templates

    Platforms, groups and packages are plain Eloquent models the admin edits directly. The storefront and the order form render entirely from that data, so a new platform or package is a form submission, not a pull request.

  2. Order forms defined per group

    Each group owns a set of form fields (text, url, email, select…) that render dynamically on the order page and validate against what that specific package actually needs — a YouTube view package asks for a video URL, a Spotify package for a track link.

  3. Orders keep a receipt, not a reference

    Placing an order snapshots the package's title, price and features into a package_snap row before creating the transaction. Later edits to the live package can't retroactively change what a customer was already sold.

platform page — Facebook packages
platform page — Facebook packages
order form — dynamic per-package fields
order form — dynamic per-package fields
admin dashboard — groups management
admin dashboard — groups management
Outcome

The client runs the full catalog — platforms, groups, packages, pricing and FAQs — from the admin dashboard without engineering involvement. Orders flow through PayPal checkout with status tracking (processing, on-hold, completed) and email notifications on status change, giving the client a simple support workflow for every transaction.

ContactGMT+6

Have something that needs building, fixing, or finishing? Write one paragraph — that's usually enough.

open to new work
Local time--:--:--
Based inDhaka, BD
Experience6+ years