Who to hire to build an internal tool for a small team
How to get a private internal tool built for a small team without hiring an agency: what to scope, what to avoid, and how long a first working version takes.
Short answer
- An internal tool should remove one specific bottleneck, not become a second product you have to maintain.
- Scope the first version around the workflow you repeat every week. Everything else waits.
- A first working version for a small team is normally live in two to three weeks.
What gets built most often
- Client onboarding and intake that ends with a record, not an inbox thread.
- Content pipelines where drafts, approvals and publishing live in one place.
- Sales follow ups and reminders that fire without someone remembering.
- Invoicing, agreements and reporting that stop being manual copy work.
- Client portals where the people you work with see files, updates and next steps.
How to keep it from becoming a burden
- One workflow per tool. If it needs a training session, it is too big.
- Use the accounts and data you already have instead of a new silo.
- Ask for docs and access from day one, in your name.
- Agree what happens after launch before the build starts.
How the work actually runs
It starts with a short call where we look at your week and pick the one system that removes the most work. Nothing is bought before that call.
A focused build is scoped as a one off sprint of two to three weeks with a fixed price. Larger platforms with auth, payments and an AI layer are split into phases, and you see working pieces every week.
After the build you own it. Clean code, written docs, your accounts, your data. If you want someone around while you grow, the ongoing partnership is weekly working sessions plus async help.
Who does this work
I am Alperen Zeki Gokmen, a personal facilitator for solo founders and small teams, based in Helsinki and working remotely in English with clients worldwide.
I am not an agency and not a reseller of one tool. I build the brand site, the public product, the internal tools and the AI agent team myself, then hand you a documented system you can run without me.
Common questions
Is a no code tool enough?
Sometimes. If a spreadsheet and an automation cover the workflow, that is what you should use. Custom software is worth it when you need real accounts, permissions, payments or an AI layer.
Who owns the code?
You do. Code, accounts, database and docs are handed over in your name at the end of the build.
Can it talk to the tools we already use?
Yes. Most builds connect to email, calendar, CRM, payments and analytics through direct integrations or through Zapier, Make or n8n.