Programs
We map almost every conversation onto one of four engagement types. Picking the right one in the first week saves three weeks of friction later. The fifth type — "you bring requirements, we bring developers" — we don't do; the reasons are at the bottom of this page.
Every engagement begins with a free 30-minute call. If we're not the right studio, we'll point you at someone who is — usually with a name and a warm intro.
/01
New product, from spec to production
A complete custom platform: data model, API, persistence, auth, deployment, frontend. Most often a SaaS or an internal tool.
/02
Legacy app, made workable again
Your existing app works, mostly, but new features are taking longer than they should and people on your team are afraid to touch certain files. We rebuild from inside out.
/03
Performance and architecture
A focused engagement: a slow API, a database that has outgrown its primary key strategy, a queue that's started backing up. We measure first, then change one thing at a time.
/04
Retainer for software in flight
Monthly retainer for ongoing engineering: bug fixes, small features, security patches, on-call. Four tiers, transparent hour budgets, no roll-over expiry beyond 90 days.
Pure body-shop or staff-augmentation engagements — "we have the spec, we just need a developer for three months". We tried it for two years. The work was less interesting, the outcomes were worse, and the writing-down-decisions habit (which is most of what makes our work different) doesn't happen when we're inside someone else's process. If that's what you need, we keep a list of three studios in Andalusia we'd trust and we'll send you names.