The free tools.
You do not need an account with every platform in this guide. Start with the task, choose one suitable tool and keep the result somewhere you can return to. Your first session starts in Claude in your browser, with the supplied facts. You do not need a code editor.
Tools and plan details below were checked on 21 November 2026. Follow the linked official comparison before buying: allowances, feature access and billing can change.
Understand the different jobs.
An AI assistant helps you discuss, draft and review. A design tool helps you arrange and refine what people see. An AI builder can generate a working draft. A coding agent can change project files and help run checks. Hosting makes the project available online. A database stores organised information, such as products and orders. Authentication establishes who is signed in. These jobs overlap in some products, but buying one subscription does not automatically pay for all of them.
Use this as a map, not a shopping list. In the first-session lessons, you work in Claude. In the taste lessons, choose references and a way to sketch. Databases and hosting become useful when the project needs them.
Research and design.
What MCP actually means.
MCP, short for Model Context Protocol, is a shared way for an AI application to connect to tools and information. Think of it as a connection with named abilities, such as reading a design file. It is not a design model or a promise that the assistant can do everything in the connected app.
For a Figma workflow, the assistant needs a compatible connection, permission to the file and access to the required tool. A connection does not remove account restrictions. The current Figma documentation gives Starter access limited monthly read calls, with higher limits for eligible paid seats. Some write tools are exempt from those read limits; AI-generating actions may use separate credits. Check the exact action instead of calling the entire workflow “free.” Figma access and credits (opens in a new tab)
An API is an interface software uses to request an operation or information. An integration connects services into a useful workflow. Later, your store might save an order in a database and request a receipt email through an API. MCP could help your assistant inspect or configure parts of that work; it does not replace the application's own behaviour. You do not need to configure any of these connections in this stage.
Generating and building.
A generated draft is a starting point. Check the facts, layout, actions and data behaviour before calling it a product. A button that shows a success message without saving anything is not a working purchase system.
Hosting and services you will meet later.
These are examples, not a requirement to combine every service. Later build lessons will choose a coherent route, show its setup and explain alternatives at the relevant decision. The first product page needs none of these accounts.
Make a spending decision.
Write the job, your expected usage, the limit you are reaching, the plan's actual billing period, any extra usage charges and how you can export or recover your work. Set a budget before enabling paid usage. “I need a custom domain for a client launch” is a concrete reason. “Everyone uses the paid plan” is not.
To begin, open Claude and the first lesson. Other tools can wait until a lesson needs them. Buying a tool does not complete an exercise.
Start your Vendow practice website in Claude.
Write a brief and useful copy, create one design artifact, check it on desktop and phone, then save your work. Your first lesson is free, and a paid plan is optional.