Theme edited in place
Cornerstone edited through the theme editor or forked years ago, so every theme update is a manual merge nobody wants to do.
[ E-commerce ]
BigCommerce stores built on the platform, not around it.
BigCommerce gives you a lot out of the box: hosting, a CDN, a solid checkout and real APIs. Most of the trouble I see comes from fighting that instead of using it — hard-forked themes that cannot take updates, a pile of Script Manager snippets, and integrations held together by CSV exports.
Free store review · Fixed scope · Theme changes in Git, not the live editor
[ What holds BigCommerce stores back ]
The platform is rarely the limit. The way the theme, scripts and integrations were bolted on usually is.
Cornerstone edited through the theme editor or forked years ago, so every theme update is a manual merge nobody wants to do.
Tracking pixels, chat widgets and old app scripts loading on every page, including checkout, long after anyone remembers why.
ERP, PIM or warehouse sync running on scheduled CSV imports that fail silently and overwrite good data.
Heavy Handlebars templates, unoptimized images and render-blocking scripts on the pages where shoppers decide.
Moving from Magento, WooCommerce or Shopify without a redirect map, losing product URLs that took years to rank.
Wholesale pricing and quote requests handled by spreadsheets and email because B2B Edition was never set up properly.
[ How it works ]
Theme code, Script Manager, installed apps, integrations and Core Web Vitals. You get a written report on what to keep, what to remove and what each change is worth.
Theme work in Git using the Stencil CLI and pushed to an unpublished theme, or a headless build on a preview deployment. The live storefront is never the test environment.
Applied in a low-traffic window, then speed, checkout and integrations re-checked against the baseline, with the previous theme kept ready to reapply.
[ What actually changes ]
I work across BigCommerce Essentials and Enterprise, on classic Stencil storefronts and headless builds. Where the native feature does the job, I use it rather than adding another app.
[ Example engagement ]
A store with 22 Script Manager entries, several from apps uninstalled long ago, all loading site-wide. Unused scripts removed, the rest scoped to the pages that need them.
Illustrative example of a typical engagement. Figures vary with the state of your systems and are not a guarantee of a specific outcome.
[ Free · 48 hours ]
Send me your store URL. You get a written review of theme code, scripts, apps and page speed, with the fixes ranked by likely impact.
[ Pricing ]
Tell me the number you have to work with. I'll tell you honestly what's achievable within it — and if it isn't enough, I'll say so before we start rather than halfway through.
Hourly rate $20/hoursmall jobs and ongoing work · fixed price for defined projects
Scope agreed in writing, price agreed in writing, before any work starts. No hourly creep and no invoice you haven't already approved.
For ongoing work — maintenance, monitoring, updates and small changes. Month to month, cancel whenever, no minimum term.
For a single bug, a short task or ongoing tweaks, where writing a full scope would cost more than simply doing the work. Billed in real time, reported in writing.
Budget too tight for the whole thing? I'll often suggest doing the highest-value part first and the rest later, rather than doing all of it badly.
[ Questions ]
$20 an hour for small fixes, extension conflicts and hourly work, billed for time actually spent. Anything with a defined outcome — an upgrade, a migration, a speed project — gets a fixed price agreed in writing before I start, so the number does not move halfway through.
Only if you have a real reason: content-heavy pages, a custom front end, or several storefronts that need to share components. For most stores a well-built Stencil theme is faster to ship and cheaper to run. Catalyst makes headless easier, but it still means hosting and maintaining a Next.js app.
Yes — from Magento, WooCommerce, Shopify or OpenCart. Products, variants, customers, order history and content are moved, and every old URL gets a 301 redirect. I rehearse the migration on a trial store before the real cutover.
Yes. I keep changes in Git and isolate them from the base theme as much as Stencil allows, so pulling in Cornerstone updates is a merge, not a rebuild.
Yes, through the Management API and webhooks, with the sync direction and conflict rules agreed up front. Rate limits vary by plan, so the integration is built to queue and retry rather than fail.
If wholesale customers need their own pricing, company accounts with several buyers, quotes or purchase orders, usually yes. If you only need a discount for a handful of trade accounts, customer groups and price lists may be enough.
Hosting and the CDN are rarely the problem. Third-party scripts, oversized images and heavy theme templates are. I measure first and show you where the time goes.
Both are good hosted platforms. BigCommerce tends to suit larger catalogs, B2B and multi-storefront setups; Shopify has the bigger app ecosystem. I build on both, so I have no reason to push you either way.
[ Related services ]
[ Let's talk ]
Describe what you need in a few lines and you'll get a straight answer on scope, cost and timeline — same working day, from the person who'd actually build it.