Support and backup for your FileMaker developer
Do you already have a FileMaker developer? Then you don't need to replace them — you need a backup.
Most FileMaker systems in Sweden are maintained by a single person. That works perfectly until the person falls ill, retires or takes another job. Then the business is left without the only person who knows how the system is built.
I step in as an extra pair of eyes and an extra pair of hands, without anyone having to be replaced.
I step in when
- The lead developer is ill, on holiday or on parental leave
- A larger project needs more capacity for a period
- You want an independent assessment of the system architecture
- You lack AI expertise in-house
- A developer is leaving, and the knowledge needs to be secured before the door closes
The last point is the most urgent when it happens, yet it is almost always discovered too late. If you know your developer is on the way out, a call is worthwhile while the person can still be asked.
I don't replace your developer
This is the most common concern. My assignments are clearly defined, and I never take over anyone else's client relationship unless you explicitly ask me to.
Nor should your developer feel scrutinised. I have sat in that chair myself since 1989 and know how it feels when someone from outside looks at your solution. In my experience, most developers are relieved to have someone to bounce ideas off.
Act before it becomes urgent
The best time to call me is before anything has happened. If I have already familiarised myself with the system, I can be there when you need me, instead of spending the first days working out what I am looking at. It also helps a great deal to be able to talk to the developer who built the solution.
Peter Watz, FileMaker developer since 1989. More than 200 solutions built, three of them in daily use for 26 years.
