By function: IT
IT operations automation
Joiners get access, leavers lose it, requests route themselves, and the automations the business runs on are documented and watched.
- First workflow live
- Joiner and leaver access, usually inside the first sprint
- Usually owned by
- The person who knows the most about computers
- Built on
- Google Workspace or Microsoft 365, Slack, Retool
- Judged on
- Leaver access removal and Request tracking
In short
IT operations automation provisions and revokes access from one record of who works here, routes internal requests to the right queue with the context attached, replaces spreadsheet processes with internal tools that have roles, and puts monitoring and documentation around the automations the business already depends on. SBD builds it in your accounts, with least-privilege access.
Who this is for
The people who usually own IT.
- The person who knows the most about computers
- IT managers in companies of 50 to 1,000
- Operations leads who inherited the automations
- Founders worried about who has access to what
Is this you?
If three of these sound like your week, this page is about your team.
- A former contractor still has the CRM
- Requests arrive five ways
- Nobody knows how many Zaps are live
- Everyone can edit the operations base
- API keys are in a shared document
What it costs today
Where IT loses the hours.
Leavers keep access
Offboarding is a memory. Months later a former contractor still has the CRM.
Requests arrive everywhere
Chat, email, a shoulder tap. Nothing is tracked, so nothing is prioritised and everything is urgent.
Shadow automations nobody owns
Dozens of Zaps and scripts built by people who have left. When one breaks, the business finds out from a customer.
Everyone edits the database
The operations base has one role: admin. A wrong click in a view takes an afternoon to undo.
For the person who runs IT
Access that follows the org chart.
Bring your list of tools and who has admin. We will show you what a joiner and a leaver should trigger, and how to find the automations nobody owns.
Show us your access list
By company size
IT at 10 people, and at 1,000.
- 1 to 10
Everyone is an admin and passwords live in a chat.
- 11 to 50
A few dozen Zaps built by people who have left, and no list of them.
- 51 to 200
Requests by shoulder tap, access by memory, and an operations base with one role.
- 201 to 1,000
An IT team, a ticketing tool, and still no single source for who should have what.
What we build
What we build for IT teams.
- 01
Access from one source
A joiner record grants the right accounts and groups. A leaver record revokes them, with a report of what was removed.
- 02
Requests that route themselves
A form or a chat command creates a tracked request, classifies it, assigns it, and reports status back where it was asked.
- 03
Internal tools with roles
Screens on a real database for the people who should not edit it raw, with approvals, audit logs and permissions by role.
- 04
The automation estate, documented and monitored
Every workflow listed with an owner, a runbook and an alert that fires when it stops. Secrets moved into a vault.
The workflows
The IT workflows, and what sets each one off.
- 01 Joiner and leaver access
When a people record changes
ThenAccounts and groups granted or revoked, with a report
- 02 Request routing
When a request arrives by form or chat
ThenLogged, classified, assigned, status reported back
- 03 Internal tool with roles
When the team needs a screen on data
ThenA Retool or Supabase app with permissions and an audit log
- 04 Automation inventory
When the audit runs
ThenEvery workflow listed with owner, runbook and alert
- 05 Secrets to a vault
When a key is found in code or chat
ThenMoved to the vault, rotated, reference updated
The numbers we move
How a IT build is judged.
Every build has a number written into the blueprint. These are the ones IT builds are measured by, and how we measure them.
| Metric | Before | After | How it is measured |
|---|---|---|---|
| Leaver access removal | Weeks, if remembered | Same day | Accounts active after leaving date |
| Request tracking | None | Every request logged and assigned | Share of requests with a ticket |
| Automations with an owner | Unknown | All of them | Workflows with a named owner and runbook |
| Secrets in code or chat | Common | None | Findings in the quarterly check |
Built on
The tools you already run, where we can.
-
Google Workspace -
Microsoft 365 -
Slack -
Retool -
Supabase -
Cloudflare -
Vercel -
n8n -
Zapier -
Make
Every tool we connect has its own page in the integrations directory.
Proof
Proof from builds like this.
- Customer story
Multi-user production dashboard
A multi-user dashboard with role-based access over production data, the pattern we use for every internal tool.
Read the story - Customer story
Retailer catalogue and order portal
Approved-user access control on an order portal, with inventory and status behind it.
Read the story
How it starts
An audit of the IT work your team still does by hand.
One to two weeks. We map the workflows, put an hours-a-week figure on each, and give you a costed blueprint in order of payback. The audit is credited in full to the build.
- Week 1 to 2Audit. We sit with the people who do the work and map it.
- Week 3Blueprint. Fixed scope, fixed price, the first build chosen by payback.
- Week 4 onBuild in two-week sprints, working software every second Friday.
- After go-liveSixty days of hypercare, then a care plan or run it yourself.
What this does not do
So the scope is clear before the call.
- Device management and networks. We work with your IT provider on those.
- Security certification. We build the controls; the audit is a separate engagement.
Terms, defined
IT terms, in plain English.
- Least privilege
- Each account has only the access its job needs.
- Runbook
- One page per system: what it does, what each alert means, what to do first.
- Automation estate
- Every workflow, script and integration the business depends on, listed with an owner.
Questions
What people ask about IT automation.
We have no IT team. Is this for us?
Especially. Most clients of 10 to 200 people have one person who knows the most about computers. This gives them a system instead of a list.
Can you take over automations someone else built?
Yes. The audit lists every live workflow with its owner and failure modes, and we harden or rebuild the ones that matter.
Who holds the admin access?
You. Every account is in your name and our access is a role you can remove in one click.
Reading
- Systems
How much should an AI agent be allowed to do?
An agent with an unscoped token dropped a production database and its backups in nine seconds. The permission model we use for every agent: read widely, write narrowly, spend with a cap, and escalate when unsure.
- Security
Your Lovable app is probably public
Over 170 Lovable-built apps had open databases in one disclosure. Most vibe-coded apps ship with row-level security off. How the leak works, the three named breaches of 2026, and the twenty-minute check to run before you tell anyone your app exists.
Related
- Function
HR and people
New starters have access on day one, leave is a message not a form, and the policy question is answered before it reaches HR.
- Function
Compliance and risk
Make the audit trail a by-product of doing the work, not a project you run afterwards.
- Function
Operations
The order moves through the business without anyone re-typing it, and everyone who needs to know, knows.
By function: Back office, Finance and accounting, Compliance and risk, Sales and RevOps, Customer support, Operations, Marketing, HR and people, Leadership
IT
Get the IT hours back.
Bring the one IT workflow your team still runs by hand. You leave the call with a yes or no on fit and the first thing we would build.
Book the call