The seven-day setup: one part a day

Many business systems are dropped in the first week, because setting them up turns into a project of its own. Marlene Konu put the pattern plainly in January 2026: "The fancier your system, the faster you'll abandon it," and "If your system only works when you're at 100%? It doesn't work."

Time is part of why. Etsy's 2024 Seller Census, quoted in its annual report, found that sellers spend on average 52% of their business time making and designing, and the rest on administration. That survey covers all Etsy sellers, not only those selling digital files, but the point holds: a setup that takes a whole weekend takes that time from making products.

The order below is the Start Here path from Lunith Commerce OS, with the parts specific to it taken out, so it works for a spreadsheet, a notebook or a set of databases. The rule behind it is to set up first what everything else reads from, and each day to add only what the next day needs.

Day 1: the rates everything else reads

For a seller, that is each storefront's fees: the percentage it takes, the processing charge, any flat charge per sale, the ad fee. Take them from each platform's own fee page and write down the date you checked. Remove the storefronts you do not sell on. A storefront with no fees filled in nets its whole gross, which is right only for one that charges nothing.

Day 2: what you make

One row per thing you made, not per listing: a product that sells on three storefronts is still one row. Note roughly how many hours it took and anything it cost to make. A guess is better than a blank, because the guess is what the hourly figure on day six is built from. If the system came with example rows, clear them once your own are in.

Day 3: where it is listed

One row per product per storefront, with the price on that storefront and a status: idea, drafting, ready, live, paused, retired. Keyword notes are notes; nothing you write here reads a search ranking.

Day 4: a first week of sales, or last month in one line

Either log the last week's orders one by one, or type last month's totals from each storefront's statement. From here the system has real sales in it, and its totals mean something.

Day 5: the last 30 days of spending

Subscriptions, ad spend, stock assets, contractors. Mark what bills every month. Tie ad spend to the storefront it was spent on, and a cost to a product where it belongs to one.

Day 6: read it

Net per storefront, after its own fees and after the ads you tied to it. Then revenue per hour per product, which puts the thing that took nine hours next to the thing that took four.

Day 7: a first weekly review

Four prompts, written down: what sold, what you shipped, one thing to fix, next week's one thing. Launch plans, content calendars and feedback logs can wait until there is a launch, a post or a piece of feedback to put in them. Nothing breaks if you never open them.

If you stall

Skip to day four with whatever you have. A week of real sales shows more than a finished catalogue with no sales, and the gaps are easier to see once sales are in.

This is the Start Here path in Lunith Commerce OS, with the parts specific to it taken out.