The TWIMCO notebook
Field notes.
Useful observations from inside the work.
For people building a better way.
385 notes

Your AI assistant will find the folder everyone forgot was shared.
For years, an old salary spreadsheet shared with the whole company was safe in practice, because nobody could find it. An assistant that searches everything a person can open finds it in seconds. Spend an afternoon asking the questions an over-curious colleague would.
Read the note ↗︎
Two customers booked the same Saturday. Here's what actually broke.
Saturday, 9:55 a.m. A family with a toddler and a photographer is at the studio door, and so is a fashion crew with a rail of clothes. Both have confirmations. Walking back through how it happened shows that nobody did anything wrong, which is exactly the problem.
Read the note ↗︎
Ask how AI touched your code, then write the answer into the contract.
Almost every developer you might hire now works with AI tools, and almost no proposal says so. Here are the questions to ask on your next call, what a reassuring answer sounds like, and what belongs in writing afterwards.
Read the note ↗︎
Anthropic's human-review rule isn't new. Now it's spelled out.
If your Claude-powered screener tells someone they don't qualify, a qualified person was always supposed to see that first. Anthropic's October 8 rewrite makes the rule much harder to miss.
Read the note ↗︎
Automate the invoice reminder. Keep the phone call.
Nobody enjoys chasing a client for money, so it slides until the end of the month. Reminders are a great job for software, as long as the software knows when to stop: the invoice is disputed, the customer already promised a date, or the payment arrived this morning.
Read the note ↗︎
Sort your app's notifications before your users do it for you.
Somebody on your team added each notification for a good reason. Together they've taught your users to swipe without reading, or to switch them off. Sorting them into four piles takes an afternoon and usually ends with fewer, better interruptions.
Read the note ↗︎
Your wholesale customers want to reorder, not browse.
Most wholesale buyers already know what they want. It's roughly what they ordered last month, sent over from a PDF price list by email. Build the portal for that before anything else.
Read the note ↗︎
Putting the PDF online isn't putting the service online.
A fillable PDF on the county website feels like progress. For the person applying, it's still a paper form, just harder to fill in on a phone. Here's what changes when the form becomes a service.
Read the note ↗︎
A letter to the owner of the system everyone wants to rewrite.
You've heard it in three meetings now: the old system has to go, so let's rebuild it properly. Before you sign off on that, here's what we'd want you to know, as plainly as we can put it.
Read the note ↗︎
Before the second warehouse opens, decide which orders it gets.
A second warehouse sounds like faster shipping. In the first week it mostly produces questions: who gets this order, what happens when half of it is in each building, and which stock count the store should believe.
Read the note ↗︎
Your team already uses AI. Write the policy for that team.
If the policy says no AI and people are pasting customer emails into a chatbot on their phones, the policy isn't working. These are the questions worth answering before you write one more rule.
Read the note ↗︎
The admin screen is where your software earns its keep.
Customers see the polished part. Your team spends the whole day in the back office, which is usually where a product quietly falls apart. So let's take a typical admin screen apart, one piece at a time.
Read the note ↗︎
You may not need an app. Here's how to tell.
"We need an app" is sometimes exactly right and sometimes a way of saying we want to be taken seriously. Four common beliefs are worth checking before you pay to build and maintain two of them.
Read the note ↗︎
Your approval chain will stall on someone's vacation. Plan for it now.
Picture the last week of the quarter. A purchase is stuck, the approver is somewhere sunny, and three people keep refreshing their inboxes. Almost all of it can be fixed before it ever happens.
Read the note ↗︎
The AI reads the invoice fine. Plan for the one it doesn't.
It's Monday, a few hundred invoices are waiting, and the demo read every sample perfectly. The part worth designing is the page it reads slightly wrong, the one that looks complete and nobody questions.
Read the note ↗︎
Before you buy AI search, read what people couldn't find.
Somewhere in your analytics is a list of things people typed into your search box and got nothing back. It's the most honest research you own, and it often explains more than a new search engine would.
Read the note ↗︎
ChatGPT builds the calculator now. Build the one it can't.
Ask ChatGPT for a bill splitter today and it draws one in the chat. So which tools on your site still earn the visit? The ones that need something only you know.
Read the note ↗︎
Freeze config the night before you cut over.
On the evening before cutover, someone flips a flag "just for the test" and a cron job deploys an old config. By morning, what you cut over isn't what you reviewed. A freeze needs a list you can check, not a channel message asking people to be careful.
Read the note ↗︎
Name auth, capture, and settle before checkout ships.
Order placed, says the screen. Somewhere else the card hold may or may not exist and the stock may or may not be reserved. When those feel like one moment and are really several, you end up shipping what you never captured.
Read the note ↗︎
Spec the conflict before the field app ships.
A technician saves a status with no signal. Someone else edits the same record on another device. Both are honest, and when they reconnect one will win, the fields will mix, or the record will freeze. If you don't choose, the software will.
Read the note ↗︎A familiar problem? Let’s look closer.
Tell us where you want to go. We’ll find the first thing worth changing.
Tell us about it ↗︎