Long-lived products rather than one-off builds. Payment systems, multi-tenant platforms, B2B commerce and native mobile. Mostly Rails, with Node and Swift where a project calls for it.
Four on a project is the size we aim for, six is the ceiling. Teams are assembled for the scope of the work, not carried between projects.
What we do
Not specifications into tickets. The first job is understanding what you actually need and why, which is almost always smaller than what was asked for.
We would rather ship the thing that works than the thing that was specified. If we think part of a build is waste, we will say so before we invoice for it.