# Is your AI-built app good enough to give to your employees?

> Before your team runs on a tool one person built with AI, four things have to hold: sign-in, who sees what, phones and mistakes. Tests you can run yourself.

Canonical: https://simondziak.com/writing/ai-built-app-ready-for-employees
Last updated: 2026-11-20

[Writing](https://simondziak.com/writing)

Published Nov 20, 2026 7 min read No Polish version yet

In short

It’s ready when four things hold: everyone signs in as themselves, each person sees only what they should, it works on the phones your people carry, and a mistake can be found and undone. You can run a test for each in an afternoon with two test accounts and your phone; a failed test is a clear no, and a pass is a good sign, not proof. If one fails, fix that one thing before your team relies on it, or, if what you built is really a CRM, look at a ready-made one first. At App369 a $450 Launch Check reviews sign-in and who sees what and ends with a fixed price for the fixes, one broken phone screen is an App Fix Ticket ($450 diagnosis, then $750 for a tested fix, $1,200 in all), a list of changes goes on the Monthly Dev Subscription from $1,495 a month, and a rebuild is quoted as a Web App MVP Sprint from $6,000.

I founded Workspace369 and App369 and benefit from both businesses.

A lot of company software is now built by one person with ChatGPT, Claude, Cursor, Lovable or Replit. In May 2026 Centiment surveyed 818 US workers for Zapier, all of whom had built or deployed a tool for work with AI coding tools in the past 12 months. Zapier published the results on July 6, 2026 as [34% of people shipping software using AI tools have no formal programming background](https://zapier.com/blog/building-business-software/). Among the builders with no formal programming background, 44% were building tools just for internal use, and 92% had run into a major challenge coding with AI, most often code errors or bugs (38%) and security and data privacy concerns (37%).

The jump from “it works for me” to “my team runs on it” is where those problems show up. On Hacker News, a developer [wrote on May 22, 2026](https://news.ycombinator.com/item?id=48242805) about being “hired to fix a vibe coded app for a company that one of their people whipped up over five months,” and finding “no security whatsoever.” One person built it, and the company then paid someone to fix it.

Here are the four things I’d want to be true before handing a tool like that to employees, and a test for each that you can run without reading code.

## 1\. Everyone signs in as themselves

A shared password means you can’t tell who did what, and you can’t remove one person without changing it for everyone.

**Test it:** make a second account for a test employee. Sign in as them in a private browser window and leave that window open. Back in your own window, remove that account the way you would when someone leaves. Now refresh the test employee’s window, then sign out and try to sign in again. If they can still see anything, if the old login still works, or if there’s no way to give each person their own account and take one away, it isn’t ready.

## 2\. Each person sees only what they should

Most teams need at least two levels: the owner sees everything, staff see their own work. Payroll, margins and other people’s clients often shouldn’t be on everyone’s screen.

**Test it:** as the owner, add a record only you should see. Sign in as the test employee and look for it, in lists, in search, and in any export button. Then open one of your own records, copy the address from the top of the browser, and paste it into the test employee’s window. If it opens, the app is hiding the link, not the data, and it isn’t ready. If it doesn’t open, that’s a good sign, not proof: a screen can refuse while the database behind it still answers anyone who asks it directly. You can’t see that from the screens; someone has to read the database rules.

## 3\. It works on the phones your people carry

A tool built at a desk often breaks on a phone: buttons off the screen, forms that won’t scroll, text too small to read when you’re on your feet.

**Test it:** do your team’s three most common tasks on your own phone, with the phone’s text size turned up. Then do one of them where your signal is worst, such as a stairwell or a parking garage. If a button is off the screen, a form won’t scroll, or something you saved is gone when you reopen it, it isn’t ready. If anyone needs a laptop to do their job in it, they’ll stop using it.

## 4\. A mistake can be found and undone

With one user, you know who changed what. With ten, you won’t. Someone will delete the wrong customer, or two people will edit the same record at once.

**Test it:** change a test record, then look on that record for a history that shows who changed it and when. Delete a test record, then try to get it back. Open the same record in two windows, change it differently in each, and save both. Last, find yesterday’s copy of your data: ask the tool you built it with where backups are kept, then open that page and check the date of the newest one. If there’s no history, the deleted record is gone for good, the first save disappears without a warning, or you can’t find a copy from the last day, it isn’t ready for records you can’t afford to lose.

## What to do if a test fails

You don’t have to throw it away. These are the kind of fixes that go into an app that already works. Start where it’s cheapest: tell the tool you built it with exactly which test failed, then run the test again. If it still fails, or the fix breaks something else, stop and have the code read.

App369 is my app development business in Miami. I also build and run Workspace369, and I’ve shipped 21 projects since 2020 across iOS, Android, macOS and the web. The paths below are separate, not steps to add up. Pick the one that matches what failed.

**If test 1 or 2 failed (sign-in, or who sees what):** the first step is a [**$450 Launch Check**](https://app369.com/fixed-price/ai-app-rescue/?utm_source=simondziak&utm_medium=essay&utm_campaign=ai-built-app-ready-for-employees), ready in **3 business days** from read-only access to your code. No production keys or passwords. I go through sign-in and roles, your database rules, keys in the browser, payments and deploys, and rank what I find. It doesn’t cover phone screens, change history or backups. It covers React, Next.js or Vite front ends on Supabase or Firebase, with Stripe. If yours is built on something else, check fit by email before you pay; the link is on that page. The report ends with a fixed price for a Rescue Sprint: up to 5 critical or high issues fixed in 7 business days, for $1,950, or $1,500 after the $450 credit. You can also take the report and fix it yourself. The fixes ship as pull requests you deploy; a pull request is a change to your code that you review and put live yourself.

**If one phone screen or one flow is broken:** that is one known bug, and the [App Fix Ticket](https://app369.com/fixed-price/flutter-firebase-bug-fix/?utm_source=simondziak&utm_medium=essay&utm_campaign=ai-built-app-ready-for-employees) is a $450 diagnosis, then $750 for a tested fix: $1,200 in all. Check fit by email before you pay.

**If you have a list (several phone screens, a change history, backups):** the [Monthly Dev Subscription](https://app369.com/fixed-price/monthly-dev-subscription/?utm_source=simondziak&utm_medium=essay&utm_campaign=ai-built-app-ready-for-employees) works through requests one at a time. Starter is $1,495 a month for one app and covers bug fixes, small features, and UI and copy changes. Studio is $3,995 a month and adds new features and screens. Which plan your list needs depends on your app, so check fit by email before you pay. You can pause or cancel anytime.

**If the Launch Check shows a rebuild would cost less:** the report says so, and it’s quoted as a [Web App MVP Sprint](https://app369.com/fixed-price/web-app-mvp/?utm_source=simondziak&utm_medium=essay&utm_campaign=ai-built-app-ready-for-employees). That starts with a written scoping in 3 business days that ends in a fixed quote. The scoping is credited in full against the build, and after a Launch Check you don’t pay a second $450 for it. Builds start from $6,000. Native mobile apps are quoted separately.

**If what you built is really a CRM or a client tracker:** a ready-made one such as HubSpot or Pipedrive may cost less than fixing yours. On its pricing page, check which plan includes separate logins, permissions and the phone app. [Workspace369](https://workspace369.com/pricing/?utm_source=simondziak&utm_medium=essay&utm_campaign=ai-built-app-ready-for-employees), the product I build, is a ready-made one too: roles and permissions start on the Voyager plan at $74 a month with 2 seats, extra seats are $10 a month each, it’s on the App Store and the web, and it keeps an activity history across records (depth varies by plan). It fits a business that sells, signs, invoices and gets paid. If your tool tracks something else, you don’t need my product.

I do all the work myself. The work happens in writing; no call needed.

_Prices and plan details as shown on app369.com and workspace369.com on November 20, 2026._

## Frequently asked questions

### Is my AI-built app good enough to give to my employees?

Check four things first: everyone signs in with their own account, each person sees only what they should, it works on a phone, and a mistake can be traced and undone. If any fails, fix it before the team relies on it. At App369, a $450 Launch Check reviews the first two (sign-in and who sees what) in 3 business days.

### Can my team share one login?

They can, but then you can’t tell who changed what, and removing one person means changing the password for everyone. Give each person their own login before the tool holds anything important.

### How do I test permissions without reading the code?

Make a test employee account. As the owner, create a record only you should see, then look for it from the test account, including by pasting its address into the test account’s browser. If it opens, the data isn’t protected. If it doesn’t open, that’s a good sign, not proof: the database rules still have to be read, which is part of App369’s $450 Launch Check.

### What does it cost to get an AI-built internal tool checked?

At App369, a Launch Check is $450 in 3 business days and covers sign-in and roles, database rules, keys in the browser, payments and deploys. Fixing up to 5 critical or high issues is $1,950, or $1,500 after the $450 credit. Prices as shown on app369.com on November 20, 2026.

### Should I rebuild it instead?

Not by default. If people already use it and the tests show specific gaps, fix the gaps. At App369, the $450 Launch Check report says so if a rebuild would cost less. A rebuild is quoted as a Web App MVP Sprint, which starts with a written scoping that ends in a fixed quote, with builds from $6,000. After a Launch Check you don’t pay a second $450 for that scoping.

## Where to go next

- [Built a CRM or business app with AI? Finish it from $450](https://app369.com/service/finish-ai-built-business-app/?utm_source=simondziak&utm_medium=essay&utm_campaign=ai-built-app-ready-for-employees)
- [AI-built app rescue: the $450 Launch Check](https://app369.com/fixed-price/ai-app-rescue/?utm_source=simondziak&utm_medium=essay&utm_campaign=ai-built-app-ready-for-employees)
- [Keep building with AI, or hire a developer to finish it?](https://app369.com/blog/hire-developer-finish-vibe-coded-app-2026/?utm_source=simondziak&utm_medium=essay&utm_campaign=ai-built-app-ready-for-employees)
- [Rebuilding it: the Web App MVP, from $6,000](https://app369.com/fixed-price/web-app-mvp/?utm_source=simondziak&utm_medium=essay&utm_campaign=ai-built-app-ready-for-employees)

[All writing](https://simondziak.com/writing)

## Related

- [Home](https://simondziak.com/)
- [llms.txt](https://simondziak.com/llms.txt)
