PROJECT · THE JUICY PATTERNS ADMIN
Who signed up, who paid, and what needs me today: all in one place. Every part of the system already exists in dozens of products. Only the fit to my business is specific.
One admin for everything I sell: live workshops and digital courses. Buyers only meet a small part of it: a sign-up page, a payment page and the course itself. Everything else happens behind the scenes, on my side.
In mid September I wanted one place for everything around my workshops and courses: who paid, for what, and where each person stands. I went at it as if I were inventing something new. Eight agents worked on it and produced a spec of nearly 17,000 words, five rounds of mockups and a work plan of about five months.
The mistake The first release was built and shipped in a single day. The next morning I stopped it. A system that handles real money had changed completely overnight, and I could no longer tell what I was looking at.
That same day I started over with four fields: name, price, number of seats and description. This time, one small module at a time, not everything at once. By the evening the first module was running on staging. Six days later it was live on the site.
The five-month plan stayed in the drawer. What's live today is much smaller, and it took a week to build.
Because the parts are standard and the fit is specific. Every system has a payment page, a sign-up list and an income report. But my receipts come out of Morning, which I use anyway. Every line waiting for me has a WhatsApp button with the link already in it. The last seat in a workshop goes to whoever paid first. And the last day for a full refund follows the terms accepted at purchase.
There was nothing to discover, only parts to put together. So I put them together exactly the way my business needs them.
Every part of the system went through the same four steps, in the same order. The first release had a plan and a canvas too. What was different: it replaced the whole admin at once, with no period of the new one running next to the old. The team recommended that period, and I skipped it. Since then, every module has gone through the four steps on its own.
Before each module, the product manager agent wrote a plan and the other agents added what they saw from their side.
Example
The admin's plan also had the software architect, the finance agent, the security agent and the customer success agent on it. Out of it came six questions only I could answer, such as how I sign in and what happens when someone asks for their details to be deleted.
Every screen was drawn on a design canvas in two or three versions side by side, and I picked.
Example
The home screen came in three versions: the list first, the number first, or the weeks ahead. I picked the weeks ahead. And when testing found a screen nobody had drawn, the page for someone who got a refund, it wasn't built straight away. It went back to the canvas in three versions and was built only after I picked.
Everything built went to staging first, with demo payments and no real money.
Example
The day before launch we walked the whole way through in a browser: building and buying a course, adding a workshop participant and paying, marking a refund request, undoing it, and deleting someone's details. Ten findings came out. Nine were fixed and checked again the same day, and the page for someone who got a refund went to the canvas.
Nothing went live without my word.
Example
On September 29 I gave the go and the system went up. I typed the payment keys in myself, outside any screen. The last step is still ahead: a first real payment, a small one, to check the checkout.
This is the team that built the system that's live. Eight agents sat on the first plan, and most of them came back for this one.
At every step, I picked, corrected and approved.
Wrote the plan, folded in what the other agents said, and ruled when they disagreed.
Had each module hand over one small list that Home, Participants and Income read from, so a new module joins without changing what exists.
Drew the canvas rounds, every screen in several versions, on laptop and phone.
Built what sits under the screens: the data, the Morning payment connection and the refund rules.
Built the screens themselves, as picked on the canvas.
Wrote the edge cases for a whole canvas round and found defects before every release.
Drafted the purchase terms and corrected the cancellation fee rule in the plan.
Set that only my account signs in and that keys never appear on a screen, and added protections before launch.
Set money to show by month, before VAT, with a refund counted in the month it happened.
Mapped what buyers will actually send me, like "where's my link", and Home was built from that.
Planned and wrote the workshop emails.
Read every Hebrew line before it reached me.
Two Claude Code sessions worked in parallel, one on workshops and one on courses, with one simple rule: only one of them ships at a time.
Every name and number on these screens is made up.
Only what needs me today: someone who paid but has no seat yet, or a payment that matches nobody. Each line has one button that fixes it, and below that sit the next dates. A single line at the top of the page shows recent sales and this month's income.
Each date has a name, a price, a number of seats and a description. I can add a participant and send a personal payment link on WhatsApp, and there's an open sign-up page too. A seat is held only for someone who has paid.
A course is built from lessons with video, text and files, published one lesson at a time. Buyers get in with a personal link.
One page per person, with every purchase on it and the state of each one in plain words. Refund requests are marked there, along with the last day a full refund is owed.
Payments and refunds by month, before VAT, each row linked to its Morning receipt. Read only: the books stay in Morning.
One page for the name, phone, WhatsApp and address, plus a line showing each connected service is working. The keys to those services never appear on any screen.
