Weekly promotions
Running a promotion every week means making the same set of pieces every week, for email, social media and the website. This process builds them all from one short brief and checks prices and stock against the store before anything goes out. Any store that runs regular sales or featured products can run more of them with less work.
Tools Python · Node · BigCommerce · Sendy · AWS · Claude
Built for AngelFire Ammunition
A Kansas ammunition manufacturer in Saint Marys.
The problem
AngelFire runs a promotion every week. Each one needs a set of emails, a landing page, homepage and sitewide graphics, a product-page card and the store discounts themselves: well over a dozen pieces, every week, from a very small team. Building each week by copying last week's files carried old dates, prices and angles forward.
What I did
I built a weekly build process that produces every piece from one brief. Emails are written fresh for that week; the site pieces start from last week's tested version, with every change checked. Every email and page must pass its checks before its file is written, so a stale date or a wrong price stops it.
The result
A full week of promotion is built in far less time, so a very small team runs one every week, reliably. Prices and stock are read from the store when each piece is built, and rechecked on launch morning. The mistakes copying let through are now stopped when a check catches them, and each one found since has become a new check, so far fewer corrections go out after a send.
See it
Pieces built for one week's campaign, rendered from the build output.
Interactive samples use invented data, including invented names and prices. Pictures of the samples show the same invented data. Prices in screenshots of shipped marketing are already public.