Four kinds of app.
One way of building them.
Customer app
Book, pay, track the truck, see past work, refer a neighbor. The app a repeat customer opens instead of calling.
Field app
Today’s jobs, checklists, before-and-after photos, signatures, and it keeps working when the basement has no signal.
Client portal
Approvals, files, invoices, and progress in one place. For agencies, contractors, and anyone tired of emailing PDFs.
Ops tool
The spreadsheet that runs your business, turned into a tool with permissions, history, and a dashboard you check from the truck.
Eleven weeks to both stores
A new build every Friday
One codebase for both platforms, backend in your own accounts, payments live in test mode by week six. You install a fresh beta every week and break it.
Six screens. No manual.
Open, book, pay, done. If a customer needs a tutorial, we cut screens until they don't. This is the booking flow we ship most often.
APPLE · GOOGLE · PHONE
NEXT VISIT · PAY · BOOK
LIVE CREW AVAILABILITY
APPLE PAY · GOOGLE PAY · CARD
ADDED TO THEIR CALENDAR
“YOUR TECH IS 12 MIN AWAY”
Under the hood
The boring parts, written down so your next developer never has to guess. Everything lives in accounts with your name on them, not ours.
1.0 is where it starts
Store changes, handled
Apple and Google update their rules and SDKs every year. We update before the deadline, so your app never gets a warning letter.
We hear the crash first
Crash reports and outages page us, not you. Most fixes ship before a customer thinks to mention it.
One feature a month
A thirty-minute call to pick it, a build to test it, a release to ship it. Twelve real improvements a year.
Leave with everything
Cancel any time. The code, the accounts, the data, and the store listings were in your name from day one.
The scoping call
Ninety minutes with you and whoever answers the phone. We leave with the screen list, what to cut, and a fixed price for the rest.
Clickable prototype
Before a line of code, you hold the whole app on your own phone and tap through every screen. Change anything. It's cheap here and expensive later.
Both stores, same day
We handle the listings, screenshots, review notes, and the rejections that come back. Then flat monthly care keeps it live, updated, and growing.
Questions
- How is an app priced and paid for?
- The build is quoted to scope, then paid in three phases: 50% up front, 25% before the revision round, and the balance at launch. You know the full number before the first phase is paid.
- How long until the first version?
- Typically four to eight weeks to a first release, depending on how much version one has to do. Scoping is where that number is decided, which is why we separate must-ship features from later ones before quoting.
- Who owns the code and the accounts?
- You do. The codebase, the repositories and the store accounts are yours, so you are never locked into us to keep your own app running.
- What happens after launch?
- A maintenance retainer is set up at launch, because apps do not sit still: phones update, operating systems change, and something eventually breaks. The retainer covers keeping it working and shipping new versions.
- Can I start smaller than a full app?
- Yes. A clickable prototype is the cheapest way to find out whether the idea holds up, and it becomes the scope for version one if it does.