Notes you can use
Short pieces on framing the task, choosing a system, and accepting the work. Each note answers one question.
When a mobile app is too early, even if you want one very much
An icon on the home screen does not make a scenario mobile. First check how the phone differs from a good account.
How to accept a project from a developer: the code, the access, the check
Acceptance is not a feeling that it sort of works. It is a short list you can walk through without the author.
A website, a client account, and a service: do not build all three at once
A storefront, a repeated action, and internal records are different products. They can be linked. They do not have to be mixed in the first release.
What goes into an MVP, and what is better left out on purpose
The first version should run from the start to the end. You may want the rest. You do not have to build it now.
A CRM from scratch, or a ready-made system: how to choose without buying what you do not need
Your own CRM is not a sign of maturity. It is an answer to rules that a packaged system keeps breaking.
How to write a brief that keeps development from spreading
A developer does not need a novel. They need to see what should change in the work, and where the first version ends.