Job sheets your techs can finish
with no signal
I build custom offline-first mobile apps for contractors and field-service teams, with a web dashboard for the office. Your forms, your approval steps, your reports.
10+ years building iPhone and Android apps, 100+ mobile products shipped. Built by the engineer who writes the code.
Try it: tick a box with no signal, then bring the signal back.
I have built this before
We needed two mobile products simultaneously: a field inspection tool for engineers in remote locations with offline-first requirements, and an executive dashboard for our board to track directives. Mikalai architected and shipped both — on time, no critical bugs post-launch. The field app handles daily active users across multiple regions; the board dashboard is part of our standard governance process.
When a mobile product cannot fail, you call someone like Mikalai.
That client is under NDA, so there is no logo here, and that is true of a lot of my best work. One real quote is worth more than a wall of logos I can't show you.
I'm happy to sign your NDA before you tell me anything about your operation.
Three questions to answer before you spend anything
- When a tech is somewhere with no signal, how does the job sheet get finished and signed?
- How many hands does it pass through between the tech's phone and billing?
- Does the office see where a tech is, or what was actually done on site?
If you have a clean answer to all three, you probably don't need me. If one of them is awkward to answer, send me a few lines.
An app for the field,
a dashboard for the office.
These are the typical pieces. Your scope decides what is in and what is out.
On site, on the phone
- Job sheets and checklists built around your own forms
- Photos and notes attached to the job
- Customer signature captured on the phone
- Everything saves on the phone first and sends when signal returns
In the office, in a browser
- Completed work shows up as it is sent
- Approve a job, or send it back with a note
- Reports and exports shaped the way billing, an inspector or an insurer needs them
- Boiler inspectionWaiting for approval
- Panel upgradeApproved
Built in Flutter, which means one codebase for iPhone and Android. The office gets its copy as soon as the phone has signal.
When custom makes sense,
and when it doesn't.
Custom is worth it when
- Your form or approval steps don't fit standard field-service software
- The work happens where signal doesn't reach: crawl spaces, mechanical rooms, remote sites
- The paperwork is for an inspector, an insurer or a regulator and has to look a specific way
An existing tool is the better call when
- Standard software already covers how your crew works
- The gap is a setting you haven't found yet
In that case I'll tell you, and you save the build.
How it works
- 01
You send a few lines on how a job runs today.
No form to fill in. A paragraph is enough.
- 02
I answer in writing.
Whether custom makes sense, what I would build, and what I would leave out.
- 03
We agree the scope, then the price and a date.
I estimate against a specific scope. If the picture isn't clear yet, we can start by the hour while we work it out.
- 04
You hold working builds on a real phone.
A first version typically takes 2–4 weeks once scope and designs are settled. Production-grade scope takes 4–6.
One person to deal with
You deal with me, the engineer who writes the code. If a project needs a designer or a QA tester, I brief them, so your time doesn't grow with the size of the team.
- I sign your NDA before you share anything
- Everything is written down, so nothing depends on anyone's memory
Questions people ask
- How much does it cost?
- It depends on scope, so I don't quote blind. I estimate against a specific scope and give you a fixed price and a date before I start. If the picture isn't clear yet, we can start by the hour while we work it out.
- We already use field-service software. Does this replace it?
- Not necessarily. I build the pieces your current software doesn't cover: your own inspection form, your approval steps, a specific report. If the app needs to exchange data with something you already run, we check that while scoping.
- What happens when there is no signal?
- The app saves everything on the phone and sends it when signal returns. The tech can finish the job sheet and get the customer's signature whether or not there is a connection.
- What happens after launch?
- You can keep me on a monthly retainer for fixes and updates, or hand the code to your own developer.
- Where are you based?
- In Europe. I overlap with US East Coast mornings, and because everything is written down, time zones rarely get in the way.
- Can you sign an NDA?
- Yes. I'd rather sign it before you share anything about how your business runs.
Next step
Send a few lines on how a job runs today
I'll reply with whether custom makes sense or an existing tool will do.