Why I started Tinker Works
Most small organizations already run on a stack of tools they pay for every month, a calendar, an invoicing app, some kind of intake form, a shared drive where the records are supposed to live. What they usually need is not another platform to learn on top of all that. They need the tools they already have to do the job they were bought for, and to work together instead of sitting in separate corners. That is what I started Tinker Works to do, build a solution on the tools you already use so the technology fits how the business works instead of the other way around.
The thing I kept noticing
Spend time around small organizations and the same situation shows up. On paper the place runs on proper systems, an EHR or a CRM, a shared drive, a binder of policies. In practice it runs on people remembering where things are and messaging each other to find them, asking whether a form got signed, which version of a file is current, who has the answer this time.
The reason is almost never the people. It is that somewhere along the way they started changing how they work to fit their software, instead of setting up the software to fit how they work. They learn the workarounds, they keep a mental map of what lives where, and they cover the gaps the tools were meant to handle themselves.
Why behavioral health
A lot of my work focuses on behavioral health and recovery programs, where this gets harder than almost anywhere. The rules are some of the strictest around, and the record keeping has to be right every time. On top of that there is constant pressure on small organizations to adopt new technology, and a field with that much regulation has a hard time keeping up. Working out which tools fit which rules becomes a job on its own, and it falls to people who already have a full one. I know the rules behind the paperwork, including 42 CFR Part 2, and I build on the tools you already use, so that working out is something I can do for a provider instead of it being one more thing on their list.
Doing it yourself
More organizations are trying to solve this on their own now, especially with AI tools making it feel within reach to build something custom. That can work for a while. The trouble usually shows up later. A solution built in a hurry can have a security hole nobody notices until it matters, or it holds up at the current size of the organization but not the next one, or so much time goes into building and rebuilding the internal tool that it costs more time than it ever saved.
I build platforms with these same AI tools, so I know how much they make possible and also where they tend to go wrong. The value is not really the building. It is knowing which problems are worth solving that way and which ones are not.
How I work
When I start with an organization I spend the first while talking to the people who do the work, since they know where the day actually goes. From there I look for the tasks that repeat, the ones that could run on their own, and I go through the tools already in place to see whether they are set up the way they could be. A lot of platforms have features buried in them that would solve half the problem if they were turned on and configured properly.
Then I start with the one task costing the most time, get it working, and hand it over. You own what I build outright, documentation included, no subscription and no lock in. If it helps to have me around as the organization grows there is a simple support plan, but the system is yours either way.
That is the idea behind Tinker Works. It saves you time managing documentation so you can focus on your mission rather than managing documents. From spending time with your computer to spending time on what matters most to your business. If you or someone you know is buried in that kind of work, quotes are always free at tinkerworks.services.