Vibe Coder · Unit 18: Email, Payments and Commerce · Project
Milestone 18 of 23
A product that can charge
Email from your own domain and a tested checkout, in test mode.
One product, built one milestone at a time
Vibe Coder has one project. You pick an idea in Unit 1 and every unit adds a piece to it, until the last unit launches it. Every milestone ends with a push to your own GitHub repository. This is the milestone where the project becomes a business. Your product learns to send email from its own domain and to take a payment, and it only unlocks what was paid for when the payment provider says so.
- 1Your builder’s kitA one-line product idea, your role, and five working accounts.
- 2A fact-checked product briefOne page on your idea, tested against how the models really behave.
- 3Your product project in ClaudeA project with instructions and files, and your first real piece of work from it.
- 4A brand kit and research fileA name, images and market research for your product, with a second opinion.
- 5Your prompt libraryThe prompts you will reuse to build the product, each one tested.
- 6Your product specThe problem, the people, the first version and how you will measure it.
- 7A clickable prototypeA version people can click through, shown to three of them.
- 8A working first draftYour product generated from the brief, with sign-in and data, in your own GitHub repository.
- 9The first working versionYour app running on your computer, built with Claude Code.
- 10Your Claude Code setupProject instructions, a custom command and a skill made for your app.
- 11One AI featureA feature in your app that calls a model, with its key kept safe.
- 12A connected assistantClaude or ChatGPT connected to a tool you already use, with the right permissions.
- 13Sign-in and saved dataAccounts and a database behind your app.
- 14Your app, liveOnline at its own address, updating every time you save.
- 15Your product’s back officeThe automatic jobs behind your product, as tested workflows in GitHub.
- 16An agent that works for your productOne agent with narrow tools, limits, approval and a test set.
- 17A helper that answers from your documentsAnswers with sources, scored on your own questions.
- 18A product that can chargeEmail from your own domain and a tested checkout, in test mode.
- 19A model tuned for one jobA small experiment, measured against your best prompt.
- 20A brand image kitOn-brand images from one saved workflow, with your own LoRA.
- 21A launch videoThirty to sixty seconds, with voice, music and sound.
- 22A tested, locked-down appEvery flow checked, and each person able to see only their own data.
- 23Your launched productThe finished product, in front of people, with a page that shows your work.
You start with
A helper that answers from your documents
Answers with sources, scored on your own questions.
Milestone 17Your product gains
Email and a tested checkout
That makes 18 of 23 pieces in place.
Your role
The steps change with your role. Choose yours to see your version of this milestone.
Start with this prompt
Paste it into Claude or ChatGPT, or into Claude Code once you are building. Fill in the parts in square brackets with your own product.
I am adding email and payments to my product. Here is the product and who pays for it: [paste] Help me decide: what exactly I sell (one plan to start), the price, whether it is one-time or a subscription, and which provider fits where my customers are. Then list every email the product must send and mark each transactional or marketing. Work with me one step at a time. Ask me one question, wait for my answer, then go on. Do not write the finished thing for me: show me a draft, tell me what is weak about it, and let me decide. Finish with the events my server must listen for, and what each one should change in my database. Everything stays in test mode.
Build it step by step
5 steps, one from each lesson of the unit. Do each step after its lesson. A box you tick here is ticked in the lesson too.
Step 1 of 5 · from the lesson Transactional email with Resend
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepA product that can charge Send your product’s first real email
Set up Resend with your own domain. Send one transactional email from your product, triggered by a real action, such as a welcome on sign-up. Add a webhook workflow that records bounces.
Done when
Put the email templates in your repository as files, so that changes to wording are tracked.
Step 2 of 5 · from the lesson Taking payments with Stripe
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepA product that can charge Add a checkout in test mode
In Stripe test mode, create your product and price. Add a buy button to your app that opens Stripe Checkout for the signed-in user and returns to a success page. Pay with the test card.
Done when
Paid features must stay locked for now. The next lesson unlocks them properly.
Step 3 of 5 · from the lesson Webhooks: know who paid
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepA product that can charge Unlock paid features from the webhook
Add a Stripe webhook handler that verifies the signature, records the event id, and updates the user’s plan. Make your paid feature depend only on what your database says. Test success, failure and cancellation.
Done when
Write the events you handle, and what each does, into your repository’s README.
Step 4 of 5 · from the lesson Payments in India with Razorpay
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepA product that can charge Add a second way to pay, or decide not to
Decide whether your customers need Razorpay. If they do, add it in test mode: create an order on the server, open checkout, verify the signature, and update the user. If not, write down why and what would change your mind.
Done when
Whichever you chose, note it in your README under "Payments".
Step 5 of 5 · from the lesson Selling products with Shopify
Read the short notes and pictures.Do everything inside a blue frame.
ActivityBuild stepA product that can charge Decide how your product sells, and publish the unit
If your product sells goods, set up a Shopify development store with two products and show them on your site through the Storefront API, with a working checkout link and a new-order workflow. If it does not, write why, and move on. Then push this unit’s work to GitHub.
Done when
Your product can now send email and take money. Keep everything in test mode until the launch unit.
Publish it to GitHub
Your product repository
Commit the email templates, the webhook handlers and the workflows, and add a Payments section to the README. Keep everything in test mode. Commit and push.
A milestone is not finished until it is pushed. A public repository with a history is how other people, including employers, can see what you built. Never commit a key, a token or anyone’s private data.
When it is done
Every box above is ticked, the work is pushed to GitHub, and you can show the result to someone who has not seen it before. Then move on: milestone 19 is a model tuned for one job.