All use cases
Office & Admin

A restaurant owner spent 1,000 hours building his own POS and self-serve beer wall with Claude

A non-coder with a tech background built tablets, kitchen screens, reservations and inventory, and is honest about the grind.

Real storyDone with Claude

What they did

u/iliadz, who calls himself "highly technical, but NOT a coder," spent three months, about 1,000 hours, building a point-of-sale system for his restaurant with Claude: kitchen screens, routing, reservations, inventory, staff logins with PIN and NFC cards, and a self-serve beer wall. His first project a year earlier was a staff scheduling system.

How it went

It's live. He shared the messy middle too: screens kept registering ghost touches, so he had Claude build an app to log touches and traced the problem to cheap multi-port power supplies. He swapped in the original chargers and it stopped.

Worth knowing

This took 12-16 hour days with no days off. For most owners the lesson is smaller: start with one annoying tool (like a schedule), and only build if you can spot when the AI is going off the rails.

Try it yourself

You are a practical software planner for a small business owner who is not a programmer. TASK: Help me decide whether to build a small custom tool with AI or buy one, and plan the smallest first version. CONTEXT (fill in the [BRACKETS]): - THE ANNOYING TASK: [THE ANNOYING TASK] (example: making the weekly staff schedule) - WHAT I USE NOW: [WHAT I USE NOW] (example: paper + group text) - TOOLS I ALREADY PAY FOR: [TOOLS I ALREADY PAY FOR] (example: Square, Google Workspace) - HOURS I CAN GIVE IT PER WEEK: [HOURS I CAN GIVE IT PER WEEK] (example: 5) - WHO ELSE USES IT: [WHO ELSE USES IT] (example: 8 staff on phones) STEPS: 1. List 3 off-the-shelf tools that already do this and their rough monthly cost. 2. Estimate the hours to build a basic version myself with AI help. 3. Recommend buy or build, with the reason. 4. If build: list the smallest first version in 5 features or fewer, and what NOT to build yet. RULES: - Use only the facts I give you. If something is missing, ask or mark it NEEDED. Never invent prices, names or promises. - Plain, friendly language a customer or crew member understands. OUTPUT FORMAT: A short comparison table, a recommendation, then a 2-week plan. FOLLOW-UPS TO TRY NEXT: - Write the first prompt I should give Claude to start building version 1. - List what could break and how I'll know.
Open the full playbook

Want help getting this working? Rise Systems in Oconomowoc sets these up.

Read the original

Source: Reddit r/ClaudeAI · August 2026

Related