Field notes: product, compliance, bilingualism — written while building.
Neither one first. The real question is which of your two pains costs more every month. How to calculate it, and the decision rule.
Quebec's Law 25 for early-stage software companies: what's in force, what the penalties really are, and the requirements most teams miss.
Adding French after launch costs three to six weeks of rework. What bilingualism demands of your data model, your interface and your documents.
Build & operate trades budget for equity. When it's smart, when it's a trap, and the clauses to negotiate before signing.
Projects don't derail on technology. They derail because nobody wrote down what wasn't in v1. How to scope in four weeks.
An enterprise buyer sends you 120 questions about your security. What they're really checking, how to answer without lying, and the six documents to have ready before anyone asks.
A false forecast is worse than no forecast. The problem is almost never the tool: it's the absence of an objective exit criterion at each stage.
It's often the largest share of an ERP project's effort and almost never appears properly on the quote. Why, and how to approach it.
The same product can cost five times more or less. The seven factors behind the gap, and the ones you can act on.
The full rewrite is almost always the wrong call, and almost always the first instinct. Four tests to decide, and the middle path.
The phrase reassures and guarantees almost nothing. What matters legally, what matters commercially, and the questions to put to your host.
Mobile money, entry-level devices, unstable networks, multiple currencies. What a Canadian-designed product has to change to work in West Africa.
