based in Lagos · — WAT
Vol. 04, Iss. 02
↓
For ambitious small and medium businesses who treat their software the way good restaurants treat their kitchens — with care, with patience, and with a point of view.
& discipline
Iteluvia, n.
Latin root —
"to weave again"
est. MMXXII
Small by choice
Three to seven engagements a year. We take fewer clients so each one gets our full attention.
Senior only
Every line of code, every pixel of design — produced by someone with a decade or more in the work.
Outcome over output
We measure success in revenue moved, hours returned, and friction removed. Not in deliverables shipped.
Three disciplines,
one studio.
We move between design, engineering, and advisory work — sometimes within the same week. The boundary between them has never made much sense to us.
Recent
commissions.
How we
work, slowly.
Every engagement, regardless of scope, follows the same five movements. We don't skip steps. We don't take shortcuts. The pace is the point.
Listen.
We start with conversations, not briefs. Stakeholder interviews, audits of what exists, hard questions about what should and shouldn't.
Define.
A point of view, written down. Strategy, scope, success criteria. The document we'll point to when something is unclear.
Design.
Iterative, in the open. Weekly working sessions, real prototypes, the design language emerging by the third or fourth round.
Build.
Code that ships every week. Production from day one, no staging-environment theatre.
Tend.
Three months of post-launch support included. Many engagements continue as quiet retainers — software is gardened, not built.
Have an ideaworth takingseriously?
We're selective about who we work with — not because we're precious, but because the work demands it. If what you're building matters, we should talk.