48V Products ecommerce rebuild
How 48vproducts.com moved off its old WordPress store into the monorepo storefront with Medusa checkout—sales held steady or grew.
Case studyCase studies
Short answer
PunkSolid publishes three case studies today: eight anonymized healthcare WordPress rebuilds at 1,000–6,000 pages each, the named 48vproducts.com ecommerce move off WordPress, and our own twelve-site ai-network in this repo. Speed and revenue details follow the facts we are allowed to share; drafts stay noindex until reviewed.
Each case study covers the starting platform, the size of the site, the tracking and forms that had to keep working, what we built in its place, and the measured results we are allowed to share. We write them for operators who need evidence—not generic “digital transformation” language—before they trust a migration or custom build.
Published stories
- What changed when we rebuilt 9 sites (draft) — aggregate PageSpeed,
Core Web Vitals timing, page counts, and tracking-stack parity across the eight healthcare rebuilds plus
48vproducts.com. Method notes for citations; numbers match
facts.tsin the repo. - Healthcare sites rebuilt off WordPress (reviewed) — eight provider sites, each with 1,000–6,000 pages, moved from WordPress and Elementor into code built in Cursor. Call tracking, analytics, consent, testing, and HIPAA forms carried over; mobile PageSpeed scores moved from about 65–75 to 92–98 on the projects we can quote. Traffic and leads held steady or grew.
- 48V Products ecommerce rebuild (draft) — 48vproducts.com
left its old WordPress store for the shared
apps/web+apps/cmsstorefront in this monorepo. Checkout and catalog run there today; sales held steady or grew. Before/after PageSpeed and SKU counts stay draft until owner input O5. - PunkSolid network build (draft) — how we shipped twelve static sites and
roughly 160 Markdown pages with topic ownership, mirror canonicals, and
pnpm validate/ preflight gates—built and maintained in Cursor.
Most of our clients’ analytics remain confidential, so case studies omit client names, URLs, and traffic figures unless the client agrees to be named. Speed results on healthcare work are PageSpeed Insights performance scores (the 0–100 lab score Lighthouse reports)—not a substitute for Core Web Vitals pass/fail in Search Console, which we report separately where we have permission.
Every project ends the same way: the client gets full access to the finished code and can maintain it in Cursor, hand it to another developer, or keep working with us—see code ownership and methodology for how those handoffs work.
Pages in this section
Healthcare sites rebuilt off WordPress
Eight healthcare provider sites of 1,000–6,000 pages each, rebuilt in Cursor with their tracking stack. Mobile PageSpeed went from 65–75 to 92–98.
Case studyBuilding the PunkSolid twelve-site network
How PunkSolid shipped the ai-network package—twelve Astro sites, mirror parity, topic ownership, and a content quality gate—built in Cursor.
Case studyFAQ
Why are most clients anonymized?
Healthcare providers asked us not to publish names, URLs, or traffic figures. Only **48vproducts.com** may be named in marketing copy; other industries stay described by size, stack, and outcomes we can verify.
Which case study covers ecommerce?
[48V Products ecommerce rebuild](/case-studies/48vproducts-ecommerce-rebuild/) documents the move from its old WordPress store into the monorepo storefront, the cutover redirects, and post-cutover PageSpeed lab scores. Sales held steady or grew.
Where is the proof for your own marketing sites?
[PunkSolid network build](/case-studies/punksolid-network-build/) explains the twelve Astro sites, mirrors, validators, and tests in `apps/ai-network`—facts you can confirm from the repository.
Plan your build or migration
Send the site, the stack, and the deadline. We reply with questions, risks, and a proposed first step.