Insights
Not thought leadership. Answers to the questions that come up while you are choosing what to build and who to build it with.
An app demonstrated on office wifi tells you nothing. The real test is a three-year-old phone at the edge of a signal, and that has to be designed for, not patched in.
Read the articleYou do not need to know how it will be built. You need to describe the work accurately, and that is a skill you already have.
Read the articleStudent records are among the most sensitive data an institution holds, and India now has a law about it. Most of what is required is unglamorous and inexpensive.
Read the articleThe usual advice assumes a connection you may not have. The right answer depends less on the technology than on what happens to your operation during an outage.
Read the articleScanning a room of files produces a room of unsearchable images. The value is in what happens after the scan, and that is the part most projects skip.
Read the articleA twenty-module proposal is easy to sign and hard to deploy. Four of them carry almost all the value, and the rest can wait until the first four are actually being used.
Read the articleAn annual maintenance contract is where most of the long-term cost of software sits, and where the least attention is usually paid.
Read the articleThe useful cases are narrower and more boring than the marketing suggests. They are also real, and they are mostly about paperwork rather than diagnosis.
Read the articleAlmost every vendor says it. Very few contracts define it, and the gap between the sentence and the clause is where organisations get stuck.
Read the articleIf you are weighing a decision and want a straight opinion on it, that conversation costs nothing and does not commit you to anything.
