E-commerce Platforms for Tiny Teams: What Works When You’re Under 20 People

If your company is under 20 people, the right e-commerce platform is the one that needs the least human attention per order. Not the one with the best feature matrix. Under 20 heads, nobody has "store admin" as a full-time job — it's a slice of someone's week, wedged between shipping product and answering customers. Pick a platform that assumes you have a merchandising team and you'll spend your Fridays fixing theme regressions instead of selling.

This is a different question from which platform has the most features. Here we're asking something narrower: what survives contact with a team where one person is marketing, support, and ops at the same time?

The real constraint isn't budget — it's who owns the store

Ask a 12-person company what their storefront costs and they'll say "$105 a month." That's wrong by roughly an order of magnitude.

The actual cost is: platform subscription + payment processing + apps + the fraction of a salaried person's time it consumes. That last one dominates. A person at $70K fully loaded costs about $34/hour. If your store eats six hours a week — theme tweaks, app updates, inventory reconciliation, a checkout bug on mobile — that's roughly $880/month in labor against a $105 subscription. The subscription is 11% of the real number.

So the useful question when comparing e-commerce platforms isn't "what does it cost," it's "how many hours a week does it demand, and from whom?" Everything below is organized around that.

What a tiny-team platform actually has to do

Under 20 people, a storefront has to clear four bars. Miss any one and it starts generating work instead of revenue.

• Run unattended for a week. If nobody logs in for seven days, orders should still flow, taxes should still calculate, and inventory should still decrement. No manual steps.
• Fail loudly, not silently. A failed payment webhook that nobody notices for four days is worse than an outage. You need alerts that reach a human phone.
• Survive one person leaving. If the only person who knows the theme code quits, can the rest of you still change a product price and ship a promo?
• Cost nothing when you're idle. Seasonal or launch-driven businesses shouldn't pay peak-tier fees in February.

None of those are features. They're operational properties. Feature lists get written for buying committees; tiny teams are actually buying an ops profile.

Three shapes that work under 20 people

There are really only three viable architectures at this size. Everything else is a variation on one of them.

Shape 1: The all-in-one storefront

You get hosting, checkout, inventory, POS, and an app ecosystem in one subscription. One vendor, one bill, one support line. This is the default for physical-product brands doing real volume, and it's the default for a reason — the alternative is stitching together five vendors with one part-time person maintaining the seams.

The tiny-team read on Shopify: the $39 Basic plan gives you two staff accounts, which is genuinely enough for a five-person company but a real constraint at fifteen. Grow at $105 gets you five seats; Advanced at $399 gets fifteen. Watch that staff-seat ladder, because it's the thing that quietly forces upgrades at small companies — not sales volume. Also check the transaction-fee structure: if you're not using Shopify Payments, you're paying a platform fee on top of your processor's cut. If that bothers you, there are Shopify alternatives with no transaction fees worth pricing out before you commit.

Ops load: moderate. Roughly 3-6 hours/week once launched, most of it merchandising rather than maintenance. Who owns it: one marketing or ops generalist, part-time.

Shape 2: The bolt-on cart

You already have a website — WordPress, Webflow, Squarespace, a static site your developer built. You don't want to migrate it. You want to add selling to it. A bolt-on cart embeds a store into the site you already have, which means no migration risk, no SEO reset, and no relearning your CMS.

This shape is badly underrated at the sub-20 size. If your content is your marketing engine and your catalog is under a few hundred SKUs, ripping out a working site to rebuild it on a storefront platform is a month of work that produces no new revenue. Embedding a cart is a two-day project. The trade-off: deep customization is more limited, and you're managing two systems (site + store) rather than one.

Ops load: low. 1-3 hours/week. Who owns it: whoever already owns the website. No new role.

Shape 3: Checkout-only for digital products

If you sell software, courses, templates, or memberships — anything that doesn't ship in a box — you probably don't need a storefront at all. You need a checkout, a delivery mechanism, and someone to handle global sales tax so you're not registering for VAT in nine jurisdictions.

Merchant-of-record platforms are the single biggest ops saving available to a tiny digital business. They become the legal seller, which means they handle EU VAT, US sales tax nexus, and the filings that come with both. For a five-person software company, that's the difference between an accountant relationship and a quarterly panic. You pay for it in transaction percentage — typically around 5% plus a fixed fee, versus roughly 3% for raw payment processing — so the math flips against you somewhere north of $500K/year, at which point you can afford proper tax help anyway.

Ops load: very low. Under an hour a week. Who owns it: the founder, usually, and that's fine.

The cost math nobody shows you

Here's the same $30K/month store modeled three ways, with labor priced in at $34/hour.

Two things fall out of this. First, the platform subscription is never the deciding line item — apps and hours are. Second, the "expensive" 5% merchant-of-record option is competitive with the "cheap" one once labor is priced in, because it deletes an entire category of work. If you want the full tier-by-tier breakdown, we went deep on what you get at every e-commerce price point.

App sprawl is the tiny-team killer

The all-in-one shape has one specific failure mode at small scale: apps.

Every app is a $15-49/month subscription, a theme injection, a support relationship, and a potential breakage point on the next platform update. A store with fourteen apps installed has fourteen things that can break during Black Friday. And the team that installed them is four people who each added a couple during their onboarding week — nobody remembers which ones are load-bearing.

Rules that hold up under 20 people:

• Cap it. One app per genuine business function, hard limit around six to eight total. Want a ninth? One comes out.
• Write down why. A one-line note per app in your team wiki: what it does, who installed it, what breaks if it's removed. Ten minutes now, an afternoon saved later.
• Audit quarterly. Uninstall anything nobody has opened in 90 days. Most stores are paying for two or three of these.
• Prefer native. If the platform ships an 80%-good version of what the app does, take the native one. Fewer seams to maintain.

The corollary matters when you're choosing: count how many apps you'd need to reach parity. A platform that needs six apps to match another's native feature set isn't cheaper — it's $200/month and six upgrade risks more expensive.

Who does what, by headcount

The org chart changes what's viable more than revenue does.

Three to five people. Nobody owns the store; the founder does it between other jobs. Optimize ruthlessly for zero maintenance. Bolt-on cart or checkout-only. Do not take on a platform that expects theme work.

Six to twelve people. One person — usually marketing or ops — has the store as maybe 20% of their role. This is where an all-in-one platform starts making sense, because that person can absorb the merchandising load. Set up alerting now rather than later, and make sure a second person has admin access before you need them to.

Thirteen to twenty people. You likely have a dedicated e-commerce or growth hire, plus a developer you can pull in. This is the first point where custom themes, headless setups, and open-source e-commerce platforms for developer-led stores become defensible rather than aspirational. It's also where staff-seat limits start driving your plan tier.

The transition that hurts is 5 → 12. That's where teams outgrow the bolt-on cart, migrate to an all-in-one mid-growth, and discover that migration is a six-week project nobody scheduled. If you can see it coming, run the move during a slow quarter — our e-commerce platform migration playbook covers sequencing it without losing order history.

When to move up a tier — and when not to

Move up when you hit one of these:

• You've run out of staff seats and people are sharing logins. That's a security problem, not an inconvenience.
• You're selling on three or more channels and reconciling inventory by hand. At that point you need real multi-channel inventory sync, and the manual work already costs more than the upgrade.
• Transaction-fee savings at the higher tier exceed the price difference. Run this number — it flips earlier than most people expect.
• You're adding wholesale, which has genuinely different requirements. See e-commerce platforms for B2B wholesale with net terms.

Don't move up for a feature you'll use once a quarter, because a competitor is on the higher tier, or because a report looks nicer. And don't replatform entirely to escape a $60/month difference — the migration will cost you twenty times that in hours.

A 30-day rollout with no dedicated ops person

Week 1 — decide and document. Pick a shape based on product type and headcount. Write down your five must-haves before you open a single pricing page; it stops feature-page drift.

Week 2 — build the minimum store. Products, payments, tax, shipping. No theme customization, no apps. Ship the default theme. Make it pretty after it's making money.

Week 3 — wire the alerts. Failed payments, out-of-stock, webhook failures, and a daily order-count summary into your team chat. This is the step everyone skips and every tiny team eventually regrets.

Week 4 — write the runbook and go live. One page: how to add a product, how to issue a refund, how to fix the three most likely breakages, and who to call. Two people read it. Then launch.

Total: about 25-30 hours of one person's time. If a platform can't be stood up in that window by a non-specialist, it's the wrong platform for a company your size. For the wider stack around the storefront — support, email, analytics — see our take on e-commerce tooling for tiny teams, and browse the full set of e-commerce platform comparisons when you're ready to shortlist.

Frequently Asked Questions

What's the cheapest e-commerce platform for a team under 20 people?

Cheapest by subscription is a free or $5-tier bolt-on cart, or a checkout-only merchant-of-record platform with no monthly fee at all. But cheapest by total cost is whichever one demands the fewest hours from your team. At $34/hour loaded labor, a platform that saves two hours a week is worth about $290/month — more than most of the subscription differences you're agonizing over.

Do we need a developer to run an online store at this size?

For a bolt-on cart or a checkout-only setup, no. For an all-in-one storefront on a default theme, also no — though you'll want access to one for occasional work. You genuinely need a developer on staff only if you're doing custom themes, headless builds, or self-managed open-source platforms, which is rarely worth it below about 15 people.

How many staff accounts do we actually need?

Count everyone who touches orders, refunds, or products — usually more than you'd guess, because customer support needs order access too. Under 20 people that's typically three to six seats. Check the seat ladder before you pick a plan, because staff limits force upgrades at small companies more often than sales volume does.

Is Shopify overkill for a five-person company?

Not automatically, but it's often more platform than a five-person shop needs if you're selling under 50 SKUs from an existing website. The honest test: if you'd use the POS, the multi-channel selling, and at least three apps, it earns its keep. If you'd use the checkout and nothing else, an embedded cart does the same job for less money and less maintenance.

Should we self-host to save money?

Rarely, under 20 people. Self-hosting trades a predictable subscription for unpredictable hours — security patches, uptime, PCI scope, and someone who has to care about all three at 2am. The Shopify vs WooCommerce comparison for DTC brands breaks down where that trade actually pays off, and it's later than most founders assume.

How do we handle sales tax without an accountant on staff?

Either use a merchant-of-record platform that becomes the legal seller and files on your behalf, or bolt an automated tax-calculation service onto your storefront. For teams under 20 selling internationally, merchant-of-record is almost always the right answer — the percentage you pay is cheaper than the compliance work you avoid.

What breaks first as a tiny team grows?

Inventory accuracy, then staff seats, then support response time. Inventory goes first because manual reconciliation across channels scales terribly. If you're already selling on more than one channel, fix that before you touch anything else — and get your customer support tooling sorted before the volume arrives, not after.

The short version

Under 20 people, choose your storefront by ops load, not feature count. Physical products with real volume: all-in-one. An existing site you don't want to rebuild: bolt-on cart. Digital products: checkout-only with merchant-of-record tax handling. Cap your apps, wire your alerts, write the one-page runbook, and revisit the decision when staff seats — not revenue — start pinching.