When software becomes part of how an organization runs every day, maintaining it stops being purely technical. People notice things. A button takes too many clicks. Someone has an idea that could save time, but it surfaces in a meeting and is gone by the next week.
That was the situation facing Family of Kidz, a growing provider of pediatric therapy and special-education services. Their custom Claris platform had become central to daily operations, but feedback was coming from everywhere: email, meetings, hallway conversations. Bugs, questions, ideas, and feature requests all competed for attention, with no dependable way to see what had been submitted or what happened next. We wanted to fix that without adding another piece of software to manage.
Building support into the system itself
Instead of bolting on a separate ticketing platform, we built the support process into their existing Claris FileMaker environment. That decision matters. A user who hits an issue or has an idea does not have to leave the system, open another application, or figure out who should get an email. The request starts where the work already happens.
From there, submissions move through a defined workflow: reviewed, categorized, prioritized, and tracked through completion. The team sees what has been raised and where it stands, and requests no longer depend on somebody remembering a conversation from two weeks ago.
Why we kept it in Claris FileMaker
There are capable standalone ticketing systems, but for Family of Kidz another disconnected application would solve one problem while creating another. Because the support workflow lives in the same platform as the rest of their operation, it can be shaped around how their team already works. We built the core workflow quickly, tested it with the people who will actually use it, and refined it without treating support as a separate implementation. The result feels less like an added tool than a natural extension of the platform.
What changes once feedback has somewhere to go
The system is in final testing ahead of rollout, so the real measure will come from everyday use. But the goal is straightforward: every request should have a home. Users should know that what they submit has not vanished into an inbox. The team should be able to tell an urgent issue from a good idea meant for later, and see the workload clearly enough to prioritize it responsibly.
That sounds simple, but it changes the relationship between a business and the software it depends on. Instead of waiting for problems to get loud enough to demand attention, the organization gains a repeatable way to capture feedback and improve over time. Good custom software should not stay frozen at launch. It should keep evolving with the people and processes it supports.
The Scarpetta Group is a Claris Platinum Partner. If your organization has outgrown email threads, informal requests, and scattered feature lists, we would be glad to talk about what a more integrated approach could look like.
