Enterprise · Field data
DCOR
An offline-first field app with three roles, GPS attendance, a dynamic form engine and five languages.
Monthly plan
In the monthly bug fix plan you keep one engineer who knows your product, and you send small fixes and changes as they come up. I sort them by risk, fix them against a written scope and report back in writing. The price is quoted after a short discovery call, against a written scope.
It depends on how much change the product tends to need, so I quote after a short discovery call, against a written scope. I do not sell a fixed number of hours up front.
The scope sets what the plan covers, and I review it with you each month, so it can match how much your product really needs.
Tell me in the first message. I reply within 24 hours, and the scope can name how urgent problems are handled, though I do not promise response times.
Yes. I read it first, and I tell you plainly if something is too fragile to patch safely.
Read next
Enterprise · Field data
An offline-first field app with three roles, GPS attendance, a dynamic form engine and five languages.
Own product · Taxi dispatch SaaS
My own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
Consumer app
A consumer app shipped to both stores from one Flutter codebase on a .NET and Azure back end.
Next step
A discovery call within 48 hours, and a kickoff typically inside two weeks.