Back to Blog

The Real Cost of Building This Platform

An honest accounting of what it actually takes — in hours, expertise, and personal sacrifice — to design, build, and operate a full-stack commerce platform for a company, alone, for free.

behind-the-scenes
reflection
open-source-spirit

The Real Cost of Building This Platform

People see a website and assume it just exists. A logo at the top, a few buttons, a checkout, an admin panel. It feels weightless. It is not.

This post is the honest accounting. Not a brag — an accounting. Because if a person is going to do something for free, the people benefiting from it should at least understand the size of what they are receiving.

What is actually under the hood

This platform is not a template. It is a custom-built, full-stack commerce, marketing, fundraising, and operations system. A non-exhaustive list of what lives inside it:

  • Storefront: a Next.js App Router application with server components, ISR, image optimization, structured data for SEO, and a fully responsive design system.
  • Cart and checkout: real-money payment integration, tax calculation by jurisdiction, shipping logic that accounts for weight and destination, discount and coupon engines, gift cards, loyalty points, abandoned cart recovery.
  • Admin dashboard: order management, inventory, product catalog, image pipelines, email template authoring, analytics, role-based access control with granular permissions, audit logging.
  • Fundraisers: a complete sub-platform for organizations to run salsa-based fundraisers — codes, tracking, splits, payouts, reporting.
  • Email system: transactional templates (orders, shipping, password reset), marketing campaigns with variable mapping, Postmark integration, deliverability monitoring, suppression lists.
  • Locations: a geocoded directory of every retailer carrying the product, with maps, search, and photo galleries pulled and optimized at build time.
  • Recipes, content, and storytelling: editorial pages, recipe schema for Google, brand storytelling components.
  • Lead generation pipeline: scraping, enrichment, deduping, outbound email automation, response tracking.
  • Integrations: Shopify, TikTok Shop product export, Stripe, Postmark, Sanity (CMS), Sentry (error tracking), PostHog (analytics), and more.
  • Infrastructure: Vercel deployments, Postgres via Prisma, environment management across preview/production, CI/CD, automated migrations, backup strategy.

That is not a website. That is a small SaaS company.

What it would cost to replace

Here is where I have to correct myself, because I used to put a much bigger number here. Multiplying my hours by a contractor's hourly rate produces six figures, and it is the wrong sum. Nobody buys hours. They buy a working store, and this one has never been sold, quoted, or asked after — no order history, no traffic record, nothing to underwrite a price with. A thing is worth what someone will pay for it.

So the honest way to size it is replacement cost — what this business would actually pay to have the same thing stood up by someone else:

  • A themed Shopify or BigCommerce store with paid apps: $1,500–$5,000, and it would do a fraction of what this does.
  • An independent developer rebuilding this feature set to spec: $8,000–$18,000, working from a finished reference rather than an open-ended discovery phase.
  • All of it at once — storefront, fundraising, admin, iOS app — as one fixed-price project: $20,000–$30,000, and that is a ceiling, not a quote.

Under $30,000, then. That is the real number, and it is still more than a small salsa company would ever have spent on software.

None of it includes design, copywriting, QA, deployment, or the ongoing labor of keeping it running — which is where most companies actually go broke.

What "for free" actually means

I have not asked for a dollar. Not an invoice. Not a retainer. Not equity. Not a percentage of sales. Not a future promise. Nothing.

That means every hour of work on this — every late night fixing a bug, every weekend rewriting the cart, every morning answering a Slack message about a typo — is hours I am not spending earning income. I am unemployed. I have no other source of income coming in. I never asked the business to pay me, and I never planned to.

The honest framing: I am paying, with my own runway, for someone else's business to have something most companies their size cannot afford and would never receive.

The other work that doesn't show up in a git log

The development is the visible part. Less visible:

  • I have driven employees to and from events on weekends, repeatedly, when no one else could or would.
  • I have shown up to volunteer in person whenever the company was short-handed, including during financial difficulties when staffing was thin and morale was thinner.
  • I have answered every request, technical or not, that anyone asked of me.
  • I have done all of the above without billing for any of it.

I am not writing this to be thanked. I am writing it because the people receiving the work should know what they are receiving.

The legal cost I did not sign up for

There is a part of this that is harder to write. While driving employees around on behalf of the company, I have run into legal problems related to my own driving privileges — issues I was not made aware of at the time, and which I am now actively dealing with.

I do not say this to point fingers. I say it because it is true, and because "doing favors for free" carries real-world consequences that do not show up on a balance sheet. There is a cost to being the person who shows up. Sometimes that cost is your own legal record.

How I have been treated through it

Throughout all of this, I have shown up with a smile. I have not complained. I have not made anyone feel guilty for needing more from me.

In return, I have, at times, been treated by some employees as if I were less than a person. As if I were a scumbag, a thief, a liar — none of which I have ever been. I have never lied to anyone in this company. I have never taken anything that was not mine. I have only ever shown up when I was needed, and kept showing up.

I have continued to do the work anyway. Because the work matters more than how I feel about how I have been treated.

Why I am writing this down

Not for sympathy. For the record.

If this platform is useful to the company — and I believe it is — then someone, someday, should know what it actually took to build it, and at what cost to the person who built it. Not so anyone owes me anything. So that the work is not invisible.

The most expensive part of any project is almost always the part nobody sees. This is mine.