weidhaus

Articles

Explore real-life examples of our proven IT optimization success through our case studies and articles.

What automation looks like at fifteen people

Automation has an image problem at small companies. It sounds like something for enterprises with a platform team and a budget — not for fifteen people who are busy doing the actual work. In reality, small teams have the most to gain, because every hour lost to a manual handoff is a bigger share of the day. And the automation that helps is almost never the impressive kind. Start with the boring 20% The best first automations are the small, repetitive handoffs nobody enjoys and everybody forg

1 minutes
Published on

Your shared drive is a map of who owns what

Open almost any company’s Google Drive and you can read its whole history in the mess. Folders named after people who left. Three versions of the same document, none of them trusted. Files owned by a personal account instead of the company. “Ask Sarah, she has it” as a filing system. It looks like a tidiness problem. It’s really an ownership problem. Why “who owns this?” is the expensive question When files are owned by individuals instead of the organisation, every departure becomes a small

1 minutes
Published on

Least privilege, without the friction

Least privilege is one of those ideas everyone nods along to and almost nobody implements. Give people exactly the access they need, nothing more. Simple on a slide. Painful on a Tuesday, when someone is blocked and the fastest fix is to grant them everything “just for now.” Why it usually fails It isn’t that people disagree with the principle. It fails because the friction lands on the wrong day. Locking things down creates small blockers now; the risk of over-granting shows up later, invisi

1 minutes
Published on

Before you buy another tool, connect the ones you have

The instinct is understandable. Something feels slow or manual, a vendor promises to fix exactly that, and buying the tool feels like progress. Sometimes it is. More often, you have just added a tenth island to an archipelago that already doesn’t connect. The hidden cost of one more tool Every new tool comes with a tax that isn’t on the invoice: another login to manage, another place data lives, another thing to secure and offboard, another source of truth competing with the others. Buy enoug

1 minutes
Published on

The account you forgot to close

Every company has a plan for the first day. Almost none have a real plan for the last one. Onboarding is loud. A new person shows up, they need access, and everyone can see whether it worked. Offboarding is quiet. Someone leaves, the laptop comes back, and the accounts mostly just… stay. That quiet is exactly where risk accumulates. What actually happens when someone leaves In most environments I audit, offboarding is a mental checklist owned by one busy person. Suspend the mailbox, maybe. R

1 minutes
Published on

What I automate with Zapier first

Not every problem needs custom software. A lot of the leverage in a business hides in small, repetitive handoffs — and Zapier is usually the fastest way to remove them. Where I start * Onboarding & offboarding — provision and deprovision accounts and access from one trigger * Lead and form routing — get every enquiry into the right place instantly * Cross-tool sync — keep Google, Slack, Jira and your CRM agreeing with each other * Notifications that matter — the right alert to the right p

1 minutes
Published on

One source of truth across HR, Google and Entra

Most access problems aren't malicious — they're drift. A person changes teams, an account lingers, a spreadsheet goes stale. The fix is to make one system authoritative and let everything follow it. The problem Before: identity lived in three places. HR had one version of a person, Google another, Entra a third — and Atlassian did its own thing. Every mismatch was a small risk and a recurring support ticket. The design * One authoritative record per person (HR / Entra) * Automated sync t

0 minutes
Published on

Zero-touch onboarding, end to end

One of the most satisfying systems to build is onboarding that simply runs. Here's how I wired a client's new-hire flow so a person is added once and everything else takes care of itself. The trigger It starts in the source of truth — an HR record. When a new hire is created, a Zapier workflow picks it up and kicks off the sequence. No one files a ticket; the record is the ticket. What provisions automatically * Identity and mailbox in Google Workspace via the Admin SDK * Group membershi

1 minutes
Published on

Identity is the real integration layer

Most teams reach for automation and integrations the moment something feels slow. But the tools are rarely the real problem. The real problem is that no single system decides who a person is, what they can access, and when that access ends. That is the integration layer — and identity is its foundation. Why identity comes first Every meaningful automation eventually asks the same question: who is this person, and what are they allowed to do? If the answer lives in three different places — an

1 minutes
Published on