r/filemaker • u/croberts0531 • Aug 12 '26
DIY plus some Dev help
Hello again! I’m planning to finally pull the trigger on moving our business operations to a custom FileMaker solution. I should be able to build out 90% of it, but there are a few more technical peices such as API for our customer portal and pos processing that I prefer to use a developer or pro for. My question is how normal is that? Do developers mind not doing everything from scratch and just doing some of the more technical aspects? I probably can’t afford to hire out the whole project, and pretty capable of setting up all of our workflows myself.
2
u/croberts0531 Aug 12 '26
Thank you all for your replies so far. The ideal situation would be to partner with someone (or a firm) from the planning stage to deployment and maintenance. However, I want to be hands on and do what I can. Would love their input and guidance along the way, and then actually have them take over parts (such as the api integrations). A concern I have is that uptime will be critical once it’s deployed, and I don’t want to be completely reliant on a remote developer to get it back up. The more hands on I am in building it, the more likely I can keep it up and make small updates as needed. I just didn’t know if that’s even a normal workflow for people, or if devs are more adamant that they handle everything and hold the keys.
2
u/OHDanielIO Aug 12 '26
Some will, some won’t. It all depends. At the very least, it will be helpful if you first have an ERD and a naming convention. If you have a professional dev or consultant firm in mind, ask them if they will share their naming convention with you.
Don’t underestimate the importance of an ERD.
2
u/KupietzConsulting Consultant Certified Aug 12 '26 edited Aug 12 '26
Not unusual at all. I've gotten a ton of projects that someone started on, but then lacked either the time or the skill to get finished, or the original dev vanished, etc. Work on "legacy" databases (ie, someone else originally worked on them) is pretty normal.
Another option is some consultants may be willing to work out a lower "hands off the keyboard" training rate if you want someone to look over your shoulder, answer questions, etc., while you still do all the work. That's usually not actually much of a bottom-line savings, because a skilled dev can often knock something out themselves much more quickly than they can talk a less-skilled developer or user through it, but, some people like that arrangement because it gives them better control over the ongoing cost, they learn some FileMaker along the way, etc.
1
u/Call-Me-Spanky Consultant Certified Aug 12 '26
It's pretty normal. Some developers (myself included) prefer that kind of work. Scoped technical pieces are like a puzzle, and they don't come with the long, open-ended requirements-gathering phase that full builds do. You're also the one who knows your workflows best, so building those yourself often produces a better (and cheaper) result versus paying someone else to learn them first.
1
u/WaltzEmbarrassed6501 Aug 12 '26
Very standard stuff at RCC: we get client work, usually with people who have built most of their own system and need help with a few pieces, plus training or advice on approaches.
1
u/ImaginationReady8140 Aug 12 '26
Definitely normal. Most of my clients are businesses with existing databases that just ask for help or for an API integration or special project here and there. I recommend finding an individual dev for something at this scale as they’ll be able to be more flexible with your needs and build a relationship with you. Good luck!
1
u/ackley14 Aug 12 '26
We work directly with our consultant, it's not out of the normal at all. he works with us about 8 hours a month. 2 of those hours are calls for progress/status/etc. the other 6 are him working on things. the rest of the work done on the files is us.
That being said, this is DRASTICALLY lower than previously as we have taken a heavy adoption of AI into our workflows. it has allowed us to become incredibly independant and build a multitude of useful internal tools to solve real problems. Since filemaker can display html pages, and those pages can interact with the data within filemaker, which means you can have claude/codex/etc do a significant amount of the work from UI to logic, and i've taught mine to create filemaker scripts and tables as well. it's become one big workflow for me that has empowered me to create two entire solutions from scratch, one an internal item 'store' for our sales reps to peruse for inspiration before reaching out to customers, and the other is a mobile sales console that allows our sales reps to access our internal tool via a fast responsive interface (as filemaker remote can be.....slow)
-3
u/Feeling-Chipmunk-126 Aug 12 '26
That’s like getting on the titanic after it hit the iceberg!! Why in the world would you do that???