About SO WHAT STRATEGY
An IT company that asks the second question.
SO WHAT STRATEGY is an IT company working across software engineering, cloud infrastructure, data systems, product design and technology consulting. We help organisations decide what technology to build and then build it carefully.
01Strategic philosophy
Strategy is a sequence of honest trade-offs.
We do not believe in technology for its own sake. A new platform, framework or AI feature is only worth adopting if it changes an outcome someone cares about.
Our philosophy is to make the trade-offs visible — cost against speed, flexibility against simplicity, build against buy — so the people responsible can choose with full information.
02Approach to technology and business challenges
Start from the problem. Arrive at the system.
Business challenges rarely arrive labelled as technical ones. A slow month-end close, a frustrated support team or an unreliable report can each have causes in process, data, software or infrastructure. We investigate before prescribing, and we prefer improving what exists over replacing it when that is the better answer.
03Working principles
How we behave on every engagement.
- Clarity before code
- Scope, assumptions and success criteria are written down and agreed before building starts.
- Evidence over opinion
- Decisions are based on measurements, prototypes and user feedback wherever possible.
- Small, frequent delivery
- Working increments reduce risk and keep priorities grounded in reality.
- Plain language
- We explain technical matters in terms that non-specialists can evaluate.
04Collaboration
One team, shared visibility.
We work as an extension of the client's team, with shared task tracking, regular reviews and direct access to the people doing the work.
Depending on the situation we can lead delivery end to end, work alongside internal engineers, or provide independent architectural review.
05Quality and delivery practices
Quality is a practice, not a phase.
- Peer code review on every change
- Automated tests and continuous integration
- Infrastructure defined and versioned as code
- Security checks on dependencies and configuration
- Monitoring and alerting from the first release
- Documentation maintained alongside the code
06The name
“So what?”
The phrase is the question a good editor asks of every paragraph and a good strategist asks of every plan. It cuts through jargon and demands a consequence.
We apply it to technology: a feature, migration or architecture is only finished when we can say clearly what it changes. The name is a reminder to ourselves as much as a promise to clients.