Insights
Writing about the parts that actually go wrong
Not thought leadership. These are the questions we get asked in first meetings, answered properly — including the ones where the honest answer costs us work.
6 articles
- Buying software4 min read
Seven questions to ask before hiring a development company
Including the two that most suppliers hope you will not ask.
Read - Engineering5 min read
Offline-first is a requirement, not a feature
If your software stops working when the connection drops, you have not built for the conditions it will actually run in.
Read - How we work4 min read
Specifications are not bureaucracy
The step most projects skip is the one that decides whether scope is a document or an argument.
Read - Strategy5 min read
Build or buy: a straight answer for small businesses
Custom software is not automatically better. Here is how we decide, including the cases where we tell clients not to build.
Read - Retail5 min read
Why imported POS software gets Sri Lankan tax wrong
VAT and SSCL interact in a way most international point-of-sale packages do not model, and the workaround usually lands on your cashiers.
Read - Buying software4 min read
What a software quote should actually contain
If a quote is one number and a delivery date, you are not being given enough information to make a decision. Here is what to ask for instead.
Read
Next step
Got a question we have not answered?
Ask it. If it is a good question we will probably write it up, and you get the answer either way.