Build an app with Claude without code: six steps and three prompts for sellers

For store owners and freelancers who want a small tool for their own business and do not write code.

By the end you will have built your first artifact, know how to change it and share it, and have three prompts for tools a COD seller can use this week.

The steps come from Anthropic's tutorial on using artifacts to create apps without writing code.

What an artifact is

An artifact is a page or tool Claude builds from your description. It opens beside the conversation and is saved in the Artifacts section of the sidebar, so you can reopen it on the web, desktop or mobile app.

Step 1: describe the problem

Start in any conversation. Tell Claude the tool you need, who will use it and the problem it solves. Claude may ask follow-up questions. If it does not, ask it to.

Anthropic's example: "I want one place to see which launch tasks are behind, because right now they're spread across three spreadsheets."

Step 2: ask Claude to build it

When the idea is clear, say:

Build this as an artifact.

Step 3: change it by talking

For whole-page changes, ask in the conversation, for example: "Group the priorities by owner instead of by day." For a single spot, click Comment, select the spot, write your request and keep "Send to Claude" checked. Before a big change, choose Duplicate from the artifact's title menu so you can compare or go back.

Step 4: add abilities

• Saved entries: tell Claude what the tool should remember. Entries stay even after Claude changes the tool.
• Downloads: ask for a button that downloads the data as a spreadsheet.
• Connected tools: artifacts can read from and write to tools such as Asana, Google Calendar or Slack.
• Claude inside the tool: ask Claude to add itself so people can use it from the page.

Step 5: share it

Click Share and invite people by email, or share with your organisation by link. Invitees start with comment access. Raise their access if they need to add entries.

Step 6: know the limits

• Saving entries and connected tools need a paid plan.
• Each artifact has a storage limit listed in the Help Center.
• People you invite need a Claude account, and their usage counts against their own plan.
• Exporting to HTML keeps the layout but turns off saving, Claude and connected tools.

Three apps for a COD store

1. Order follow-up board. Prompt:

I run a cash on delivery store in Morocco. Build an artifact where I can add each order with customer first name, product, price in MAD and a status: new, confirmed, shipped, delivered, refused. Show the count per status at the top and let me filter by status. Add a button that downloads the list as a spreadsheet.

1. Price tester. Prompt:

Build an artifact for choosing a selling price. Inputs: product cost, shipping cost, packaging, ad cost per order and expected refusal rate in percent. Show profit per delivered order and per 100 orders at three prices that I can edit. Highlight the price with the best profit in green.

1. WhatsApp reply templates. Prompt:

Build an artifact with a list of reply templates for my customers: delivery question, price question, order confirmation, delayed parcel and refused parcel. Each template has a Copy button. Let me edit a template and save my changes.

Saving edits in the third app needs a paid plan, as noted above. If you are on the free plan, ask Claude to keep the templates fixed.

After you build one

• Test it with real numbers from last week.
• Ask Claude: "What could go wrong with this tool? List three problems and fix them."
• Duplicate it before you change anything big.

My honest take

The first version is rarely perfect, and that is fine. The value is speed: you can have a working tool in one conversation and fix it in the next, which used to take a developer and a quote.