Most businesses need a fast website, not an app. Some genuinely need the app.
Offline job sites, photo capture, push notifications, barcode scanning, GPS check-ins: when the work happens away from a desk and a browser is not good enough, an app is the right call. When it is not, we say so.
Mobile Applications
One codebase for iOS and Android with React Native or Expo.
Offline-first for job sites with no signal, syncing when it returns.
Camera, GPS, signatures and barcode scanning where the work needs them.
Push notifications through the same notification service as your email and SMS.
App Store and Play Store setup in your own developer accounts.
Crash reporting and analytics so you know what is used and what breaks.
Platforms we use here
AWS
Postgres
GitHub
Offline first
built for the job site with no signal, not the office with fiber
What you get
iOS and Android apps
Store listings in your accounts
Backend API
Release pipeline
From $18,000
Includes the backend. Store fees and device testing at cost.
Every price sits on the pricing page. Real numbers, no gate.
Discovery week
Five days inside your business before we write a line of code or put a number on a proposal. We shadow the actual work, not the org chart, because what owners say is broken and what is actually broken rarely match.
Day 1
The map
Read-only access to every system, and a list of who logs into what. By the end of the day the current process is drawn on one page, including the parts that live in someone’s head.
Day 2
Shadow the work
A morning beside the person who really runs it. We watch the spreadsheet, the phone, the retyping, and count the hand-offs where a job goes quiet.
Day 3
The paper trail
The last twenty quotes and invoices, a day of real calls and emails, the support inbox. The paperwork shows what happens; the interviews show what people think happens.
Day 4
Try the shelf first
An afternoon configuring the off-the-shelf tool that gets closest. If it does 80% of the job, that goes in the plan instead of a build, even though the build is the bigger invoice.
Day 5
The one-page plan
What to do first, what can wait, a fixed price per phase and a date for the first working slice. We read it together in thirty minutes.
What we look at
Every system you run, and who has the login
The spreadsheet everyone actually works from
Your last twenty quotes and your last twenty invoices
A day of real calls, emails and texts
Every hand-off where somebody retypes something
What an existing tool could do instead of a build
What you get
A one-page plan with a number on it
The sequence: what we build first, and why that piece
A fixed price per phase, with a place to stop between phases
The date the first working slice goes live
What we would configure instead of build
What you own at the end of it, and where it lives
The plan is yours to keep, whether we build it or someone else does.
Small, well-defined jobs do not need a week. A single API, a data migration or a one-screen internal tool gets the first call and a written quote, and we skip the shadowing.
Almost every plan changes after this week.