RepairAmigo
Repair shop software for cell phone, computer and console
Productivity·Operations & Logistics
What is RepairAmigo?
RepairAmigo is software to run your whole cell phone, computer and console repair shop from one screen, built inside a busy repair shop: 50,000+ real-life repair tickets in 14 years and counting. Check in a device in seconds: returning customers are found by phone number. Labor, parts and tax are calculated the moment you pick the problem, so every quote is the same whoever is at the counter. Parts are deducted from live inventory as you repair. Add cash management, staff roles, warranty returns linked to the original repair, reports and optional text updates through your own Twilio account. It runs on your computer, on your own network, and your data stays there. English, Spanish, Portuguese or Hindi. Download free; Paid is one-time, currently US $99. No subscription.
Ready to launch?
Submit your product and get discovered by builders and creators worldwide.
Launch Now
FounderPlaybooks.
What other founders did to grow.
2722 dispatches from hundreds of founders, pulled from the week's best podcasts.
My advice for the app builders out there is like until you really have a clear user need around an additional tier — when is the opportunity to bring it — because by introducing it too early it introduces all sorts of complexity into the business and it ends up being more work than it's actually worth.
Don't Add a Second Tier Until You Have a Clear User Need Driving It
Multi-tier pricing adds product, engineering, support, and paywall complexity. Brandon's rule: don't add a tier until you have direct user evidence of a specific unmet need that tier would address. Premature tiering fragments the message and creates decision paralysis at the paywall without lifting revenue.
He was like 'yeah pretty much everybody else works on the website.' I was like 'oh so the app must just be some sort of add-on here.' And he was like 'no no, 95% of our sales are through the app.'
20-person team, 1.5 devs on mobile, 95% of revenue from mobile
Charlie recounts a 20-person dev team where one and a half engineers worked on the app while the rest built the website — yet 95% of sales came through the app. Teams habitually allocate dev resources by what's easy to hire (web), not where revenue actually happens (mobile). For subscription apps, hard-prioritizing mobile is usually the obvious unlock no one takes.
There's a play for whatever you're stuck on.
Read all 2722 playbooks