KickSide/Use cases/Internal tools & ops

Make the tool you built permanent

You made something with Claude or Cursor that actually works. KickSide is where it goes to keep working, with real data, for the rest of the team, next year.

northwind.local/ledger/review
Ledger review queue: uncategorised card and bank transactions with the categoriser's proposals, confidence and reasoning
What gets built

The things ops teams ask for and never get

The script works. It just has nowhere to live except your laptop.

Approval inbox

One place, one queue, nothing slips out unseen

Anything an agent drafts or decides waits here for a person. This is the difference between an automation you can defend to your boss and one you quietly turn off.

Scheduled automations

Set once, runs whether or not you are at your desk

The Monday report. The renewal reminder. The weekly check on who has not been contacted. It tells you when it fails instead of failing silently.

Connections to what you already run

One set of credentials, on your machine

Read from your existing systems and write back to them, from one place, with one set of credentials that lives on your machine rather than in six different scripts.

The thing you built last Tuesday

Bring your own agent

Point Claude or Cursor at your copy and what it builds lands next to everything else, with the same data underneath and the same rules in force.

northwind.local/inbox
An AI-drafted reply to a qualified lead waiting in the inbox for a person to approve
Nothing leaves without a yes. A workflow drafted this reply; it waits in the inbox until a person approves, edits or rejects it.
northwind.local/inbox
A SOW pricing exception waiting in the inbox: workstream hours and rates, $356,300 against a $340,000 budget, and the approver form
An approval with context. A pricing exception waits with the hours, rates and budget a reviewer needs, and the fields they fill in.
The approval inbox

Nothing leaves the building without a person saying yes

Every agent, automation and module writes into the same queue. You read it once a day, approve what is right, and edit what is close. This is the screen that makes the rest of it safe to switch on.

Inbox Waiting · 4 from automations · nothing sent yet
Outbound draft · Northwind LogisticsRe: the contract you sentWritten in your voice. Brand check passed. Nothing goes out until you approve it.
ApproveEdit2m
Lead reply · inbound@Drafted reply to Harbor & ValeScored 82 against your buyer description. They named a budget in the form.
ApproveEdit14m
Renewal reminder · Ferrovia SystemsRenews in 30 days, nobody has calledScheduled automation. Suggests a call rather than an email, because the last two emails went unanswered.
ApproveSnooze1h
Deal-health monitor · 5 deals flaggedTwo proposals nobody followed upRan at 06:00. Took no action of its own. Open the list or dismiss it.
OpenDismiss6h
The approval inbox. Names and companies are illustrative. Every row here was produced by software and is waiting on a human.
What changes

Four things that are true the day it stops being a script

01

It survives you

It runs on a machine that is not your laptop, with credentials that are not in your home directory. You can go on holiday. Someone else can look at why it broke.

02

Other people can use it

Unlimited users on every plan, including the free one. The people who need the output stop asking you for it.

03

It leaves a record

What ran, when, for whom, against which record. When someone asks why a customer got that email, there is an answer that is not your memory.

04

The next one is easier

The second automation reads the same contacts and writes to the same inbox as the first. You are adding to one system rather than starting another.

Who uses it

The person who is currently the integration

RevOps, business systems, an operations lead with a scripting habit, or a founder doing all of it. Usually the one person in the company who knows how the tools actually connect, and who is tired of being the connection.

Start on Community, on your own machine, free. When a second person needs to use what you built, or you need a separate copy to test on, that is the moment Cloud starts to make sense. Not before.

What it will not do

  • Clean up your data. If the underlying records are a mess, automation makes the mess arrive faster. That is a services engagement and Spiral Scout does those.
  • Write itself. Something in the box will get you started, but the useful version is the one you or your AI tool shapes around how your company actually works.
  • Replace the systems you have. It connects to them. Most teams keep everything they already run.
What it connects to

Read from them, write back to them

Connections are configured once and live on your copy, with one set of credentials instead of six scattered across scripts. Disconnect any of them and what you built stays.

HS

HubSpot

Contacts, companies and deals. Read, and written back.

GM

Gmail

Threads and drafts, with a person approving before anything sends.

GC

Google Calendar

Meetings and scheduling, for anything that has to happen before a call.

SL

Slack

Post alerts where your team already is, instead of another inbox.

JI

Jira

Issues, sprints and status, for reports nobody wants to assemble by hand.

GH

GitHub

Repos, issues and pull requests.

WH

Webhooks

Anything that can post JSON, in either direction. The escape hatch.

AI

Claude and Cursor

Over MCP. Your own agent builds inside your copy, against real data.

northwind.local/setup
MCP connection details during setup: the server URL, a masked token and the client config to paste
Claude and Cursor, over MCP

Your AI tool connects during setup

The setup step issues a token and prints the client config to paste into Claude or another MCP client. The token is shown once and can be revoked in Settings.

Where to start

Install it, connect one thing, move one script.

Pick the smallest automation you already rely on and move that one first. It is the fastest way to find out whether this is going to work for you, and it costs nothing to try.

curl -fsSL https://get.wippy.ai | sh
wippy install kickside
Community edition, free.