Capabilities
Organised by what you are trying to accomplish
Not a service catalogue. These overlap on purpose, because real problems do not respect the boundaries between them.
Most engagements start in one of these and grow into others. A client arrives wanting a website and leaves with the internal system that made the website worth having; or arrives wanting an app and discovers the problem was never an app.
That is the point of entering through the problem rather than the deliverable.
Related thinking
How we reason about this work.
Where we put the server, and why it was not the cheapest option
The cheap answer was Europe, and for most visitors it would have been invisible. We hosted in Johannesburg anyway, for the two things a CDN never caches.
When you have no case studies
Every new firm faces the same gap, and most of them fill it with something that is not quite true. There is a better answer, and it starts with leaving a section out.
The two readers
The person who signs and the person who evaluates want opposite things from the same page. Writing for one loses the other, usually silently.
Not sure which of these it is?
That is the most common way people arrive, and the path we designed for first.