A sample sketch and quote · maintenance: A driving school: an app left by a freelancer who stopped answering, taken over and looked after
First a takeover at a fixed price: access, a backup, a fix and a new version in the stores. Then a monthly plan with hours of work and a response time, which you can change or end.
ExampleThe firm, its competitors, their numbers and this quote are illustrative and point to no existing business. The method, the rate and the market prices beside the quote, each with its source and date, are real.
- For
- A driving school in Pomerania: 11 instructors, about 600 students a year, an app for booking lessons
- Kind of work
- Taking over the app, then a monthly care plan
- Takeover and plan
- 5 days of work over 2 weeks, then the Care plan
Five sentences from the client and one question from us
That is enough to start. We ask the sixth question: how will you know it worked?
From the client
I run a driving school in Pomerania: 11 instructors and about 600 students a year.
Students book lessons in an app a freelancer built for us two years ago.
He has not answered for six months, and since the last phone update the app sometimes will not open.
We do not know where the code is, or who has access to the server and the store accounts.
We want someone to take over the app, fix what does not work and answer when something breaks.
How will you know it worked?
Students book without calling the office, and when something stops working I know whom to write to and when I will hear back.
What we read in it
- Access first. Without the store accounts, the server and the code, nothing can be changed safely.
- A day without the app has a price: lessons that are lost and calls to the office. We count it below, because the choice of plan depends on it.
- The takeover is one-off work at a fixed price. Care is a monthly plan you can change or end.
- The goal can be checked: the time from a report to an answer, and the days a month the app did not work.
Next to three driving schools: the longest wait for a first lesson
We checked three schools in the same town the way a new student does: signing up, a lesson slot, a reminder, payment and progress. At each one we asked for a first lesson and timed the confirmation of the slot.
- Client's school
- 11 instructors, about 600 students a year, Pomerania
- Competitor A
- a chain of driving schools with its own app in several towns
- Competitor B
- a school with sign-up through a form and payment on its website
- Competitor C
- a small school that signs students up by phone
What a student can do without a phone call
| Without a call | Client's school | Competitor A | Competitor B | Competitor C |
|---|---|---|---|---|
| Sign up for a course | partly | yes | partly | no |
| Pick an instructor and a lesson slot | partly | yes | no | no |
| Get a reminder of a lesson | no | yes | partly | no |
| Pay for the course | no | yes | yes | no |
| Check progress and hours left before the exam | partly | yes | no | no |
| Google rating | 4.3212 reviews | 4.6540 reviews | 4.7133 reviews | 4.498 reviews |
| Time to the confirmation of a first lesson | 26 h | at once | 3 h | 15 h |
- Client's school: sign-up, slots and progress are in the app, which since the last phone system updates sometimes does not open.
- Competitor B, sign-up: a form; the office sets the first lesson by phone.
- Competitor B, reminder: a text the day before, with no way to move the lesson.
One request per school, from a phone with an up-to-date system. We count the confirmation of the slot in the app, by text or by phone.
Data as a table
| Firm | Result |
|---|---|
| Competitor A | at once |
| Competitor B | 3 h |
| Competitor C | 15 h |
| Client's school | 26 h |
What follows
- The client's school confirmed the first lesson after 26 h: the app did not open on our phone, and the office called back the next day. At competitor A the slot was confirmed at once.
- Its Google rating is the lowest in the group: 4.3 (212 reviews). When the app works, the school gives students the same as A: sign-up, slots and progress.
- That is why we start with the takeover and the fixes. It brings back what was already built, without writing the app again.
- A and B have payment on the website and reminders. We do not add them during the takeover. After it, we quote them separately or in the plan's hours.
The takeover at a fixed price
One-off work before we change anything. After it the app runs on the latest phones, and all access is on the school's accounts.
| Item | Days |
|---|---|
| Recovering access: server, domain, store accounts, code | 1 |
| A data backup and a test restore | 1 |
| Updating libraries and fixing the bug after the phone update | 1 |
| A new version in the App Store and Google Play | 1 |
| Monitoring and an alert on outage | 0.5 |
| A description of the app: how it works, where things are, how to run it | 0.5 |
| Total | 5 |
| Price | €2,400 |
| Range | €2,160–3,360 |
- The takeover takes 2 weeks, because recovering store accounts depends on Apple and Google.
- A day of both founders: €480 net, which is €30 for one person's hour.
- Amounts are net, plus 23% Polish VAT.
- Our amounts are converted from złoty at the NBP average rate of 28 October 2026 (table 210/A/NBP/2026, EUR 1 = PLN 4.409) and rounded up. Figures from publications and from the example firm's own market stay in their own currency.
Risks of the takeover
| Risk | What we do | Effect on price |
|---|---|---|
| Store account access cannot be recovered | We recover it through Apple and Google support, with the firm's documents. We start on day one, because it can take a while. | +1 day |
| The code is not in a repository or does not build | We rebuild it from the server and describe the missing parts before fixing anything. | +1 day |
The bottom of the range assumes the code is in a repository and builds: then we save half a day.
What a day without the app costs
A care plan is chosen by the cost of downtime. Work it out for your firm in the last column: four numbers are enough.
| Item | The example school | Yours |
|---|---|---|
| Lessons booked in the app in a day | 25 | to fill in |
| The share of them lost when the app is down | 40% | to fill in |
| The margin on one lesson | €32 | to fill in |
| Office hours on calls and booking by hand | 4 h | to fill in |
| The cost of an office hour | €12 | to fill in |
| A day without the app | €368 | to fill in |
The Care plan costs €240 a month, less than one day without the app in this example (€368).
A plan does not guarantee there will be no outages. It gives a response time, hours of work and monitoring that alerts us when the app stops responding.
Three care plans
The plans differ in hours of work a month and response time. An hour costs the same in every plan.
Watch
For an app that rarely changes and whose downtime costs little.
€120 / mo.
- hours of work a month
- 4
- response time
- 2 business days
- price of an hour
- €30
Care
Our pickFor an app clients use every day.
€240 / mo.
- hours of work a month
- 8
- response time
- 1 business day
- price of an hour
- €30
Develop
For an app that grows: something new every month.
€480 / mo.
- hours of work a month
- 16
- response time
- 4 hours in business hours
- price of an hour
- €30
- An hour in every plan costs €30, the same as in a build: a day of both founders is €480 for 16 hours.
- You pay for the server, domain, store accounts and outside services to the providers on your own accounts, at cost.
- Amounts are net, plus 23% Polish VAT.
- Our amounts are converted from złoty at the NBP average rate of 28 October 2026 (table 210/A/NBP/2026, EUR 1 = PLN 4.409) and rounded up. Figures from publications and from the example firm's own market stay in their own currency.
In every plan
- Uptime monitoring and an alert on outage.
- Security updates of libraries and the server.
- A daily data backup and a test restore once a quarter.
- A new version in the stores when Apple or Google require it.
- Work from this list counts towards the plan's hours.
What we recommend and why
For the example school we recommend Care: students book every day, so an answer within a business day matters. Watch is enough for an app that rarely changes. Develop makes sense when a new feature arrives every month.
The care plans against the market
Published 2026 prices for monthly care. The cheapest are for WordPress websites and show the floor of the market. Looking after an app takes more work.
- published ranges
- our three plans
Trejka · care for a WordPress website
EkspertWP · care for a WordPress website
Zleca.pl · basic upkeep of a web app
JCD · care with 5 hours of work
Technetium · an SLA with a response time
Rocking Tech · app support, United Kingdom (GBP)
Kolonell · software maintenance, Europe (EUR)
BizBees Studio · Watch
BizBees Studio · Care
BizBees Studio · Develop
Foreign currencies converted at NBP rates of 28.10.2026 (table 210/A/NBP/2026): GBP 1 = PLN 5.2645, EUR 1 = PLN 4.409.
Data as a table
| Source | Range |
|---|---|
| Trejka · care for a WordPress website · 29.10.2026 | PLN 149–799 |
| EkspertWP · care for a WordPress website · 2026 | PLN 200–800 |
| Zleca.pl · basic upkeep of a web app · 29.10.2026 | PLN 500–2,000 |
| JCD · care with 5 hours of work · 29.10.2026 | PLN 1,000 |
| Technetium · an SLA with a response time · 29.10.2026 | PLN 1,000–2,500 |
| Rocking Tech · app support, United Kingdom (GBP) · 30.03.2026 | £450–1,250 |
| Kolonell · software maintenance, Europe (EUR) · 22.10.2026 | €800–1,200 |
| Source | an hour |
|---|---|
| Trejka · care for a WordPress website | PLN 166.33 |
| EkspertWP · care for a WordPress website | PLN 250 |
| JCD · care with 5 hours of work | PLN 200 |
| Rocking Tech · app support, United Kingdom (GBP) | £75 |
| Kolonell · software maintenance, Europe (EUR) | €100 |
| BizBees Studio · every plan | €30 |
We give the price of an hour only for plans that state their hours. The cheapest plans have no hours or bill them separately.
The 15–20% rule beside our plans
The industry rule says maintenance costs 15–20% of the build's price a year. The firms that give it sell maintenance, and we found no independent study. Below we apply it to the Recommended scopes on this list.
| Sketch | Recommended scope | The rule, a month | What we propose |
|---|---|---|---|
| The enquiry automation | €2,400 | €30–41 | no plan, fixes by the hour |
| The AI order agent | €4,320 | €55–73 | Watch, €120 |
| The rental app | €5,280 | €66–89 | Watch, €120 |
For smaller builds the rule gives €30–41 a month, less than the smallest plan (Watch, €120). Watch costs more because it includes hours of work. If you use less than half the hours for three months, we propose a lower plan or billing by the hour.
Sources of the rule; both firms sell maintenance: Netguru · 1.06.2026, Kolonell · 22.10.2026
Terms and what we need from you
Terms
The takeover has a fixed price for an agreed scope. If some access cannot be recovered, we say so before going further.
Access, code, data and documentation are on the school's accounts.
Care plan: 3 months first, then month to month with 30 days' notice.
draft term · to be confirmed
Unused hours move to the next month once.
draft term · to be confirmed
If you use less than half the hours for three months, we propose a lower plan.
draft term · to be confirmed
Response means confirming the report and a plan for the fix, on business days from 9 to 17. The fix gets its own date.
draft term · to be confirmed
Work beyond the plan's hours at the same rate, and only after you agree.
draft term · to be confirmed
When we stop working together, within a week we hand over everything the next team needs.
draft term · to be confirmed
What we need from you
- The firm's documents needed to recover the store and server accounts.
- A contact at the hosting firm and the domain registrar, if you have one.
- A list of what does not work today, from instructors and students.
This page is not an offer under the Polish Civil Code (art. 71). We give your price in the sketch, one business day after five sentences.
Your sketch looks the same, only with your five sentences
One business day, no meeting and no contract. Write how your process works today and how you will know it worked.