When $1,800/month breaks your sticky note system

Most small product businesses hit a version of this wall. You're 18 months in, making maybe $1,800 a month selling candles (or soap, or prints, or whatever you make), and the informal system that got you here stops working. Orders arrive in Instagram DMs. You write them on sticky notes. You restock supplies when you notice you're out. It worked fine when you were doing a few orders a week for friends.

Then last month you missed two custom orders because the notes got buried, and you ran out of wax mid-batch on a third. The customer who didn't get her candles by the promised date didn't yell. She just stopped following you. That's how you lose the word-of-mouth momentum that got you to $1,800 in the first place.

The problem isn't the sticky notes. It's that you've outgrown a memory-based system without building anything to replace it. And the gap between 'winging it' and 'implementing enterprise software' feels huge when you're still doing this part-time out of your kitchen.

A 2x2 quadrant with axes for business scale (vertical) and system complexity (horizontal). Shows where different approaches fit: memory-based for early stage, lightweight systems for the middle ground, and full platforms for high scale.

The two things that actually need tracking (and the one that doesn't)

When small operators think about 'getting organized,' they imagine building systems for everything: customer database, marketing calendar, financial projections, inventory levels, order queue, supply chain, fulfillment tracking. That's six systems, and implementing all of them at once is exactly how this starts feeling like a second job.

Start with two. Just two.

First: which orders are you supposed to fulfill, by when, and have you done it yet? That's your order log. Second: when do you need to reorder each critical supply before you run out mid-batch? That's your reorder trigger. Everything else can stay informal for now.

The thing you do NOT need yet is a full e-commerce platform with payment processing, abandoned cart recovery, and email sequences. You already have a working acquisition channel (Instagram, word of mouth). You already know how to take payment (Venmo, whatever). The breakdown is happening between 'customer said yes' and 'customer got the thing on time.' Fix that specific gap. Don't rebuild the whole business.

System	Build Now?	Why
Order log	Yes	This is where orders are getting lost
Reorder triggers	Yes	Running out mid-batch kills delivery promises
Customer database	Not yet	Your head works fine at this volume
Marketing calendar	Not yet	Acquisition isn't the bottleneck
Full e-commerce	Not yet	You have a working sales channel already

Building an order log that matches your scale

An order log is a list of promises with deadlines. It needs six columns: customer name, what they ordered, when they need it by, whether they've paid, whether you've made it, whether you've delivered it. A spreadsheet works. A notebook page with those six headers works if you rewrite it weekly and don't lose the notebook.

The format matters less than the capture rule. Right now orders arrive in DMs and some make it into your head and some don't. The fix is a bright-line commitment: when you get a DM order, what happens next? Screenshot and add to the log within an hour? Only confirm the order once it's logged? Pick one. The operators who actually stop losing orders are the ones who define the mandatory next action and then do it every single time, even when they're tired, even when it feels unnecessary because 'I'll obviously remember this one.'

You won't. Two weeks from now when you're batching production, you will not remember the details of a DM you got at 9 PM on a Tuesday. The log remembers for you. That's the whole job.

The format matters less than the capture rule. Define the mandatory next action and then do it every single time.

Inventory reorder triggers

Running out of wax mid-batch is not an inventory management problem, it's a trigger problem. You know you need wax. You know roughly how fast you go through it. The issue is you don't have a defined moment when you stop making candles and go order more.

Set a physical trigger for each supply that matters. When your wax hits 10 pounds, reorder. When you have 4 ounces or less of a fragrance oil, reorder. Write the trigger levels on the storage shelf if that helps. The number itself is less important than having a number at all.

This is not sophisticated. You're not forecasting demand or optimizing order quantities. You're creating a rule that prevents the specific failure you're experiencing: realizing you're out of something only when you need it right now. A dumb rule you follow beats a smart system you forget to check.

1. Pick a trigger level for each critical supply. Wax at 10 lbs, fragrance at 4 oz, wicks at 50 count.
2. Write the number on the shelf. Physical reminder beats digital reminder you'll ignore.
3. When you hit the trigger, reorder immediately. Don't wait until you need it right now.
4. Adjust the number after a month. Too many emergency reorders means the trigger is too low.

Why 'just use Shopify' misses the point

The default advice for a small product business doing $1,800/month is always 'get on Shopify' or 'use Square' or whatever the current platform is. And those are good tools. But they solve a different problem.

Shopify gives you a storefront, a cart, payment processing, inventory sync, shipping labels. If you want to sell to strangers at scale and automate fulfillment, that's useful. But this candle maker isn't trying to sell to strangers. She has a working model: people find her on Instagram, DM her, she makes the thing, they pay, she delivers. The breakdown is in the informal tracking, not the sales channel.

Adding a full e-commerce platform when you don't need online checkout or automated inventory is like buying a commercial kitchen when the issue is you keep forgetting to preheat the oven. It's not wrong, exactly. It's just not the constraint. And now you have a monthly software bill and a system to maintain that doesn't fix the actual thing breaking. This is the same pattern we see with operators who think their CRM is broken when the real issue is process, not software.

The 15-minute daily rhythm that makes it stick

Here's what kills most lightweight systems: you build them, you use them for three days, you get busy, you skip a day, and suddenly you're back to sticky notes because the system 'didn't work.'

The system didn't fail. You stopped feeding it.

Block 15 minutes every day at the same time. Morning works for most people, but pick whenever you'll actually do it. Open the order log. Update anything that changed yesterday. Check what's due in the next three days. Look at your reorder triggers. Close the log.

That's it. Fifteen minutes. If the system needs more than that, you over-built it and should simplify. The goal is not a perfect system. The goal is a system you'll actually use tomorrow, and the day after that, and the day after that, until checking it is as automatic as checking your phone.

Run it for two weeks before you add anything. Most people discover they need less than they thought, not more. The urge to add fields and tabs and integrations is strong. Resist it. A simple system you maintain beats a sophisticated one you abandon.