Writing
Small software, out loud
Most of what gets written about AI and code assumes you are an engineer. These posts assume you are not. They are about the gap between an assistant handing you working code and your team actually using it, and about the places that gap gets filled.
Slack
What Slack Workflow Builder can and cannot build
Workflow Builder automates a process. Most of what people ask for in Slack is a question answered, which is a different shape, and no number of steps gets you there.
Agents
Computer use drives software. It does not house it.
Claude can operate a desktop now. That makes more small tools get built, which makes the question of where those tools live sharper rather than softer.
Access
How to share an internal tool without making it public
Four ways to put a small internal app in front of your coworkers and nobody else, what each one costs, and which ones are not access control at all.
Approvals
What to tell IT when you want to deploy an app you built yourself
The five questions a security reviewer is actually asking, how to answer them about a tool you wrote, and how to get a decision that covers the next one too.
Artifacts
How to share a tool Claude built with your team
Artifacts, links, and the point where a chat window stops being a place to keep software your colleagues depend on.
Deploying
How to put an app online without a GitHub repo
Every deploy guide opens with "push your code to GitHub." Here is what actually accepts a folder, and what it costs you when it does.
Python
How to share a Python script with coworkers who do not have Python
Turning a script into something a colleague opens in a browser, with the steps that work today and the two places it will bite you.
The last mile
Your assistant wrote the tool. Now what?
An AI can write a working commission calculator in four minutes. Getting it onto a colleague’s screen is the part nobody warns you about.
Finance
The spreadsheet that runs your company
Finance teams have been writing software for thirty years. They just had to do it in the one tool where mistakes are hardest to see.
Landscape
Builders and runners: how to read the AI software market
Some products write your app. Others run it. The confusing part is that the assistant most people actually use does neither, and that is where tools get stranded.
Sales
Software for exactly one sales team
The tools a rep actually needs are too specific for any vendor to build. That constraint just stopped applying, and most of sales has not noticed yet.
Landscape
Where do you actually put it? The clouds, read from outside
An honest tour of the places you can run a small tool, judged on the only question a non-engineer cares about: how far is it from a folder to a link?
Got a tool stuck on your laptop?
That is the thing Sploot is built for. Private beta, soon.
One email when it's live. Nothing else, ever.