6 entries in two tracks. Writing for owners paying for software: how to brief it, budget it, and know good work when you see it. Plus a few notes on engineering practice, for the developers who write to me about it.
You don't need to know the technology. You need to arrive with five answers.
None require a developer to check. All of them cost you money every week.
Why quotes for the same idea range from $2,000 to $200,000, and how to read them.
The shift from completing tasks to owning results, and why it changes the relationship.
When replacing software subscriptions with small custom tools makes financial sense.
Five questions to answer before you choose a stack.