# Turn a spreadsheet you run by hand into a small web app

> A staged plan and prompts for turning the spreadsheet your team edits by hand into a web app with logins, forms and an import of your existing rows.

- URL: https://paperchasewebb.ai/bots/marketplace/items/turn-a-spreadsheet-into-a-web-app/
- Type: Agent use case pack
- Category: Vibe coding
- By: PaperChaseWebb
- Works with: Claude Code, Cursor (named in the listing); Plain .md
- Price: $19 USD
- Difficulty: Intermediate
- Setup time: 20 min
- Time to result: One to two weekends
- Format: Markdown (.md) file, turn-a-spreadsheet-into-a-web-app.md
- Version: 1.0, updated 2026-10-15
- License: Personal and commercial use. The apps you build are yours.

## What you end up with

The sheet that everyone is afraid to sort becomes an app with forms, validation and a history of who changed what.

## What you get

- One .md playbook, plus a project rules file for your agent
- A planning worksheet: columns to fields, people to roles, edits to actions
- Six stage prompts: data model, screens, validation, logins, import, deploy
- Seed and import script prompt that checks every row before loading it
- Pre-launch checklist that follows the same six areas as App Launch Check

## Who it is for

Operators and small business owners whose inventory, booking, client or job tracking lives in a spreadsheet that has outgrown itself.

## Tools needed

- Cursor or Claude Code: builds the app in stages
- Supabase or SQLite: the database that replaces the sheet
- Cloudflare Pages or Vercel: hosting
- You need: A spreadsheet with consistent columns
- You need: Comfort running commands in a terminal

Cost to run: Free tiers of Supabase or SQLite plus Cloudflare Pages or Vercel cover most small internal apps.

## How it works

1. **Map the sheet.** Use the worksheet to turn each column into a field with a type and each person into a role with permissions. Expected: A one-page data model you can explain to a coworker.
2. **Data model first.** Have the agent create the schema and nothing else. Review it against the worksheet. Expected: Tables and fields that match the sheet, with nothing invented.
3. **Screens and forms.** Build list, detail and edit screens for the main table only. Expected: You can add and edit a record in the browser.
4. **Validation and logins.** Add the rules the sheet never enforced, then logins with the roles from step 1. Expected: Bad input is rejected and each role sees only what it should.
5. **Import your rows.** Export the sheet to CSV and run the import with a dry run first. Expected: A report of rows that passed and rows that need fixing.
6. **Check and deploy.** Run the pre-launch checklist, then deploy. Expected: A live URL and a list of what is left to fix.

## Sample prompt: Stage 1: data model only (Cursor or Claude Code)

```
We are replacing a spreadsheet with a web app. Today, only design the data model. Do not create screens or install UI libraries.
Columns and types: [paste the worksheet table].
Roles: [role and what it can do, one per line].
Produce: the schema for [Supabase or SQLite], one sentence per field explaining why it has that type, and a list of any column you think should be split or merged.
Do not invent fields that are not in my list. Ask if something is unclear.
```

Locking the schema before any screen is built avoids the most expensive rewrite in this kind of project.

## Free preview of turn-a-spreadsheet-into-a-web-app.md

````markdown
# Turn a spreadsheet you run by hand into a small web app

PaperChase agent use case pack (playbook), version 1.0. For Cursor or Claude Code, with Supabase or SQLite, hosted on Cloudflare Pages or Vercel. Time: one to two weekends.

## Is this the right move?

Answer these before writing any code. If you tick two or more of the first group and none of the second, a no-code tool may suit you better.

No-code is probably better if:
- [ ] Fewer than 5 people use the sheet
- [ ] Nobody needs different permissions
- [ ] You never need to connect it to other systems
- [ ] You do not want to maintain code

Build it if:
- [ ] Different people should see or edit different rows or columns
- [ ] Mistakes in the sheet have cost money or time
- [ ] Per-seat pricing of no-code tools would cost more than your time
- [ ] You want to own the data and the code

## The six stages

1. Data model only
2. List, detail and edit screens for one table
3. Validation rules the sheet never enforced
4. Logins and roles
5. Import your existing rows, dry run first
6. Pre-launch check and deploy

Each stage ends with a commit and a check you can do in the browser. Do not start a stage until the last one passes.

## Contents

1. Planning worksheet
2. Project rules file for your agent
3. Stage prompts 1 to 6
4. Import checklist
5. Pre-launch checklist
6. After launch
````

## Worth knowing

- If the sheet holds personal data, logins and row level access must be done before the import, not after.
- Keep the old sheet read-only for a few weeks rather than deleting it.
- Spreadsheets with merged cells or free-text dates need cleanup before import. The pack covers common cases.

## Questions

**Why not just use Airtable or a no-code tool?** Often you should. The worksheet includes a short test for when a no-code tool is the better choice. This pack is for when you want to own the code and avoid per-seat pricing.

**Can I use Bolt or Lovable instead?** Yes for the screens. The staged prompts still apply. Database rules and the import step are easier with a code editor.

## How to buy

$19 one time at https://paperchasewebb.ai/bots/marketplace/items/turn-a-spreadsheet-into-a-web-app/. Stripe checkout, then an instant download page; the download link is also in your emailed receipt.

Seller: PaperChaseWebb Inc., mgmt@paperchasewebb.com