Body
**A bit of context**
I have been building mobile apps for a long time. I also ran an agency in Europe that shipped consumer apps. In the last two years I learned as much as in the eight years before. Consumer can work, but it is hard. There is a lot of competition. Many teams are funded. Good branding and design matter. Ads and store strategy matter. Vibecoding helps with speed, but it does not give you product sense or design skills. Most solo builders don’t have all of that.
**What this is about**
I started building internal mobile apps for small businesses. These apps are private. The icon has their logo. The data is theirs. The app runs one important job their team does every day. Owners can build it. Or a builder can build it for them. The value is simple: fewer mistakes, faster hand-offs, cleaner records, money collected sooner.
**What the apps do, in plain terms**
Field work: the worker arrives, taps “start,” takes photos, collects a signature, taps “done,” and the invoice is sent.
Studios and salons: bookings are kept in one place, reminders go out on time, no double booking.
Shops and wholesalers: scan items, update stock, get a clean export for accounting.
Forms and compliance: fill forms offline, require all fields, get a signed PDF saved in the right folder.
**Pricing and learning to watch**
Some platforms look cheap, then get expensive with seats, credits, or add-ons. Read what counts as usage. Check if you can export the project. Check who owns the data. Test the tool before paying. Plan time to learn it. One focused week now is cheaper than rebuilding later.
**What must be solid**
These are utility apps. One core feature must work every time.
If the core is booking, the app must not lose state.
If the core is notifications, they must arrive on time.
If the core is inventory, scans must be reliable.
If the core is forms, offline must work and signatures must stick.
Nice screens do not fix broken behavior.
**Ownership and scope**
Keep the brand of the business. Icon, splash, wording. Keep the data with the business. Keep roles simple. Decide if the app is only for staff or also for clients to see status or book. Fewer options means more use.
**A simple way to build and improve**
Make a small version that runs end to end. Put it on the phones of the people who do the job. Watch where they get stuck. Fix the biggest problem. Ship again. Repeat once or twice. When it feels smooth for them, brand it fully and roll it out.
**How to build**
I am technical, and for this kind of job I would not use Cursor. I would pick a mobile-focused vibecoding platform with three qualities: a good code model that handles real app logic (not only UI), built-in help for store tasks like signing, builds, TestFlight or internal testing, and App Store and Play submission, and clear pricing that stays reasonable without surprise per-seat or credit spikes. I use Vibecode App. It is free to start, the credit system is fair, and it is easy to ramp up. Whatever you choose, test navigation, state, auth, and push on real devices before you commit.
**How to charge**
Charge a monthly fee that includes support and small improvements. Add a setup fee if there are integrations or data migration. Be clear on what is included. No surprise bills.
**Reddit can help**
Spend time where your users talk. Read pain posts. Do not spam. Good places to start: smallbusiness, salons, truckers etc (there is a TON). Search for “no-show,” “double booking,” “inventory count,” “invoice delay.” Build the fix they describe.
**Last tip**
In many industries, just saying “we have a mobile app” still helps, even if the first version is simple. It opens doors. Then you earn trust by making one workflow work very well.
Top comments (4)