The Role
You own everything IT and everything we do online. The business is fully online, so if it runs on a computer, a browser or a server, it is yours: it works, it is secure, it is backed up, it is documented, and it keeps getting better.
This is an ownership role, not a ticket-taking role. You spot problems before anyone reports them, you find your own answers, and you bring solutions to us rather than questions.
What You Will Do
1. Keep the systems running
- Watch system health and fix issues before they hit the business.
- Manage accounts, access rights and security.
- Handle settings, updates and configuration across all tools.
- Run backups, test restores, and keep a recovery plan that actually works.
2. Support the team
- Be the first point of contact when someone is stuck.
- Acknowledge fast, fix it or put a workaround in place, then record the cause and the permanent fix.
- Explain things in plain language to non-technical colleagues.
3. Deal with everyone outside the company
- Be our single point of contact for vendors, suppliers, software providers, hosting and domain companies, developers and agencies.
- Chase support tickets until they are closed, and hold suppliers to what they promised.
- Review contracts, renewals and pricing, and negotiate better terms.
- Work with our internal teams and, where needed, directly with clients on technical issues.
4. Build automations
- Remove manual work by connecting our tools through APIs, Make, Zapier, scripts or AI.
- Build internal tooling, reports and dashboards that give management a clear view.
- Research what is available online and pick the simplest solution that solves the problem.
5. Document everything
- High-level design: how our systems fit together.
- Low-level design: how each system is set up.
- SOPs, user guides, an asset list and an access overview.
- Written so that anyone could pick it up if you were away.
6. Run new IT projects
- Take charge of any new IT-related project from start to finish: scope, planning, delivery and handover.
- Manage any outside developers or agencies involved, and report progress to management.
- Make sure every new system is documented and added to the routines before the project is called done.
7. Improve the stack
- Audit tools for correct use, missing features and cost.
- Cut or justify subscription spend.
- Propose new systems with a clear business case: what problem it solves and what it is worth. Convenience or novelty is not a reason.
What You Will Own
| System | What it is for |
|---|
| Chatterfy (CRM) | Leads and customer chats in the inbox. |
| Google Workspace | Company email, Drive and documents. |
| Websites, landing pages & domains | Brand sites to build and maintain; domains on TransIP.nl. |
| Telegram | Everything run on Telegram: multiple accounts, channels and groups, bots, paid subscriptions and payment providers (InviteMember), message forwarding and any new Telegram tooling. |
| AI tools & other SaaS | Content, research, automation and new tools as the stack grows. |
How You Will Work
Running the systems comes first. Incidents and support requests beat everything else on any given day. Everything else is planned work.
This is a full-time role. You have a lot of freedom in how you structure your day, but you must be reachable on an ad hoc basis. If something breaks, we need you to pick it up quickly, including outside normal hours.
You will work from a simple set of routines, tracked on a checklist so nothing quietly slips:
| Cadence | What gets done |
|---|
| Daily | Critical systems checked, support requests answered, incidents logged and resolved or escalated. |
| Weekly | Incidents closed out, updates reviewed, short report shared with management. |
| Monthly | Systems audited on use and cost, backups restore-tested, improvements proposed. |
| Quarterly | Full stack reviewed, systems consolidated or retired, recovery readiness tested. |
What You Need
- Real, proven experience in an IT operations or systems role. This is not a first job.
- Strong automation skills: Make, Zapier, APIs, scripting or AI tooling. You should be able to show what you have built.
- Hands-on with SaaS platforms, settings, integrations and user management.
- Excellent at researching solutions online and teaching yourself new software fast.
- Able to write clear documentation and clear English.
- Confident dealing with suppliers and outside parties.
- Able to lead IT projects on your own, not just maintain what already exists.
- Available full-time and reachable at short notice when something breaks.
- Calm under pressure, cost-aware, and able to work on your own without being chased.
Success Looks Like
- Business-critical systems stay up. Downtime is rare and fixed fast.
- Backups are always available and proven by testing.
- Documentation is complete and current, so nothing depends on one person's memory.
- Checklists are done on time and management gets a clear weekly view.
- Manual work drops every quarter because of automation.
- Subscription costs are lower or clearly justified.
- Suppliers deliver what they promised, because someone is holding them to it.
- New systems are only added when the business gain is clear.
- IT projects land on time, fully documented, without Gijs having to run them.