Application Maintenance
A new field, a report change, a screen tweak, without a new project
Changes too small for a separate order come out of a monthly pool of hours. Before we start, you get an estimate in hours and a date.
How it works
From request to change in production
Example: a new field on goods receiving.
- 1RequestYou tell us what you want changed and why. We ask for details if anything's missing.
- 2Estimate in hoursYou get the number of hours from the pool and a date. We start once you approve.
- 3Change and testThe change is built on a copy of the app. You can check it before release.
- 4ReleaseThe change goes to production and the hours show up in the monthly report.
When it makes sense
Signs small changes wait too long
The wish list keeps growing
Users ask for small improvements, but none is big enough to order a project.
Every change needs a new contract
Adding one field means signing an order and waiting for a quote.
Workarounds instead of changes
The team puts data in notes or a side spreadsheet because the field is missing.
The report misses what matters
The data is in the system, but the report doesn't pull it, so someone adds it up by hand.
What's covered
Changes we make from the pool of hours
Anything that doesn't need a project of its own.
Fields and forms
New fields, picklists, data validation.
Reports
New columns, filters, Excel export.
Screens
Layout, field order, shortcuts for frequent tasks.
Permissions
New roles and changes to who sees what.
Notifications
Emails and messages when a status changes.
Small integrations
A new field in the ERP exchange or an extra export.
Results
How we check the results
Every month we show the changes made, hours used and what's waiting in the queue.
- 1Changes released this month
- 2Hours used from the pool
- 3Time from request to release
- 4Changes in the queue
Unused hours roll over to the next month.
FAQ
Common questions
How do I know how many hours a change will take?
You get an estimate in hours before any work starts. We begin once you approve it.
What if a change turns out to be big?
We say so at the estimate and suggest a separate project or splitting it into smaller parts.
What about unused hours?
They roll over to the next month, as in every maintenance package.
Who decides the order of changes?
You do. We suggest what gives the most for the fewest hours.
Let's talk
Describe the change
Tell us what's missing in the app and who it gets in the way of. We reply within one business day.
Application Maintenance
Other parts of this service
Fixes and bug repairs
You report it, we fix it, it’s back up. Priority depends on how badly the problem blocks your work.
I want to know more Monitoring and response
We watch availability, errors and certificates. You hear about most problems from us – with the fix already in hand, not from your users.
I want to know more Hosting and infrastructure
Servers, domains, backups, updates. We can take over the whole setup or work on your infrastructure.
I want to know more Any technology
We also take over systems we didn’t build – after a short audit of the code and access. Old technologies don’t scare us.
I want to know more