u/ming_builds

I'm comparing how the same custom-software scope is priced across countries. I searched first and found this earlier r/webdev pricing discussion for a smaller tablet/CSV app:

https://www.reddit.com/r/webdev/comments/1nj46aa/roughly_how_much_would_such_a_custom_software/

The answers varied a lot, so I want to make the scope more specific.

Assume a production-ready, browser-based internal system for a service company with 5–20 users:

• customer and job records
• assign jobs to staff
• job status and activity history
• file uploads
• due-date reminders
• simple dashboard and CSV export
• admin and staff roles
• responsive on phone and desktop
• deployment, basic documentation, and 30 days of bug fixes

Not included:

• native mobile apps
• payment processing
• accounting, payroll, or POS
• legacy-data migration
• third-party integrations

If this were a real client brief, could you share:

1. Your country or market
2. The one-time price or range you would quote
3. Your realistic delivery time
4. Ongoing maintenance/support pricing
5. The requirement most likely to increase the price

I run CodeStack Studio, a digital product studio in Malaysia. I'm not hiring, selling, or messaging respondents from this post. I'm trying to understand whether a lower-cost offer can be delivered responsibly, or whether it usually just shifts cost into support, QA, and maintenance.

Rough ranges are completely fine.

I run a small software studio, and before deciding whether this problem needs more software at all, I want to understand one real incident from people who work in food service.

Think of the most recent wrong, missing, duplicated, or badly delayed order you saw:

• What kind of operation and country was it in?
• How did the order arrive: paper, verbal handoff, POS printer/KDS, phone or messaging, or a delivery tablet?
• Where did it break, and who noticed first?
• What happened next: remake, refund, delay, complaint, extra staff time, or no meaningful cost?
• What workaround or system was already in place, and why did it fail that time?

I’m not asking whether you would buy an imagined app, and there is no product link or request to DM me. I’m mapping real handoffs first so I can see whether a process change — not necessarily a new system — is justified. If enough people share incidents, I’ll return with an anonymized summary of the recurring breakpoints.

I currently make an iPhone app for one narrow workflow: after a job is done, it records whether the customer paid in full, paid partially, still owes money, or needs a follow-up.

I’m considering an Android version, but I don’t want to build it from a pile of polite “yes, sounds useful” votes. I want to understand whether Android users doing real client work already have this problem.

If that describes you, I’d appreciate four details:

1. What kind of work do you do?
2. How do you track payments now — memory, WhatsApp, paper, spreadsheet, accounting software, or something else?
3. Which part actually causes trouble: remaining balance, partial-payment history, promised payment date, or forgetting whether you already followed up?
4. If a small Android beta focused only on that workflow existed, would you test it with real jobs for a week? What would it have to do for you to keep it?

I’m not collecting emails or sharing a download link in this post. I’ll use the answers to decide whether Android deserves a prototype and which type of worker it should serve first. Critical answers are more useful than encouragement.

I built WhoPaid for freelancers, contractors, home-service workers, cleaners, tutors, repair workers, and anyone doing small client jobs where payment tracking gets messy.

The problem I wanted to solve is narrow: the work is done, but the payment status lives across WhatsApp, notes, bank history, memory, and “I’ll send it later” messages.

WhoPaid is not full accounting or invoicing software. It is a lightweight job/payment tracker for answering:

• who paid?
• who still owes?
• was this only partially paid?
• who needs a follow-up reminder?

Current features:

• add jobs by client, job title, category, amount, date, and notes
• mark each job as paid, unpaid, or partial
• record received amount and remaining balance
• track partial payment history when customers pay in parts
• set reminders for unpaid and partially paid jobs
• see unpaid balances, daily income, monthly reports, payment breakdowns, and top unpaid clients
• use local records before signing in
• optional Sign in with Apple backup/sync
• multiple currencies and languages

It is free to download and use for the core job/payment tracking flow, with Pro for higher limits and fuller reporting.

App Store: https://apps.apple.com/my/app/whopaid-job-pay-tracker/id6764868229

I’d appreciate feedback from anyone who tracks small jobs or client payments: does this feel useful because it is focused, or would you expect more invoicing/accounting features?

I’m looking for early feedback on WhoPaid, a simple iOS app for freelancers and small-job workers who need to track whether a job is paid, unpaid, partial, or needs follow-up.

The problem I kept seeing was not “I need full accounting software.”

It was smaller and messier:

• a client says “I’ll pay later”
• a deposit is paid but the balance is still pending
• payment proof is buried in WhatsApp or notes
• you forget whether you followed up already
• your weekly income becomes mental math

WhoPaid is meant to stay narrow: jobs, clients, amounts, payment status, and follow-up state.

App Store: https://apps.apple.com/my/app/whopaid-job-pay-tracker/id6764868229

I’d especially like feedback on:

• whether the paid / unpaid / partial flow makes sense
• whether the app feels too simple or just enough
• what would make you trust it for real freelance/small-job tracking

WhoPaid is a small iOS app I made for a very specific freelance problem: remembering which jobs are actually paid, unpaid, or partly paid.

I kept finding payment details scattered across chats, notes, and memory. For small jobs, a full accounting app felt like too much, but doing it mentally was unreliable.

The app is intentionally simple:

• add job/client
• amount
• paid or unpaid
• partial payment notes
• follow-up notes

The part I care about most is making the unpaid list obvious enough that I do not forget to follow up.

I’m looking for honest feedback on whether this is too narrow, or if the narrowness is what makes it useful.

https://code-stack-studio.com/jobbuddy

I’m looking for feedback from people who do freelance work, small job work, or any client work where payment follow-up gets messy.

WhoPaid is a small iOS app for tracking:

• job/client
• amount
• paid vs unpaid
• partial payment notes
• follow-up notes

The problem I’m trying to solve is not full bookkeeping. It is the smaller everyday mess where a client says “I’ll pay later”, the payment note is buried in chat, and you forget what is actually paid vs just promised.

I’m specifically looking for feedback on:

1. whether the app feels fast enough for logging small jobs
2. whether the unpaid/paid flow is clear
3. whether it needs more fields, or if adding more would make it feel too heavy

Product link: https://code-stack-studio.com/jobbuddy

If you test it, the most useful feedback would be what feels confusing in the first 2 minutes.

Not revenue in a fancy accounting sense.

I mean the messy freelance version where you're mentally adding things like:

"that client paid half" "that one said tomorrow" "that small job is done but not paid" "that invoice is sent but maybe not seen" "that one paid but I forgot to record it"

Then you look at your bank account and it doesn't match what you thought you made.

I hate that guessing feeling.

It makes freelancing feel more unstable than it actually is because your brain is constantly doing rough math in the background.

How do you track this without turning it into a full accounting system?

I don't mean obvious scammers.

I mean the normal clients who seem nice, approve the work, say everything looks good, then casually go "I'll send payment later" like it's no big deal.

That phrase stresses me out more than it should.

Because now I'm stuck between:

• not wanting to sound pushy
• not wanting to forget
• not wanting to keep checking chat history
• not wanting to work for free

It's such a small sentence but it creates this weird mental tab that stays open until the money actually arrives.

Do you follow up on a fixed schedule, wait a few days, or just avoid clients who do this?

Not big invoices or formal projects.

I mean the messy stuff

• quick one-off jobs
• someone says "I’ll pay later"
• partial payments
• follow-ups you think you’ll remember
• random notes in chats

I realized the hard part isn’t knowing what to track. It’s staying consistent when the job feels too small to open a full system.

How do you handle this Spreadsheet notes accounting tool or just memory