01
Specificity over genericness.
A site for selling sneakers should not be the same site as one for distributing research. Different problems, different shapes. The best work refuses to flatten into a template.
// About
A small studio, working at a deliberate pace.
01 — Studio
Tuki Stack started in 2022 with a simple proposition: that good web work does not have to be either a templated rush or a year-long agency engagement. There is a middle path, and most of the time it is the one that produces things worth keeping.
We are small by choice. Five people working on two or three projects at any time. That is the size that lets us care about each engagement without spreading thin, and that lets clients have a real working relationship with the team building their software.
We are not a body shop. We are not a design agency that wrote a website once. We are engineers and designers who treat web work as a serious craft, working with teams who feel the same way about whatever it is they are making.
02 — Principles
What we hold to.
02
Performance is a kindness.
Speed is how software respects its users. A fast page works on bad networks, old laptops, and impatient afternoons. Every audit starts here.
03
Decisions over deliverables.
Pixel-perfect mockups are easy to produce. Choosing the right shape for the problem is the hard part. We focus on the hard part, and the deliverable follows.
04
Build for the team that inherits it.
Most code is read more than it is written. We name carefully, document what is not obvious, and leave the codebase in a state where the next engineer can read it without us in the room.
05
Small teams ship better software.
The communication overhead of a large team usually costs more than the work it produces. We stay small on purpose, and bring people in for what they are excellent at, not what they are passable at.
06
The web is enough.
Modern browsers do more than most teams realize. We work with the platform, not around it. Fewer dependencies, fewer abstractions, more code that still runs in five years.
03 — How we work
A rhythm that respects everyone's time.
A
Weekly working sessions, not status meetings.
One scheduled hour each week with your team. We come with progress to show, decisions to make, and questions that need answers. The rest of the week is asynchronous and unblocked.
B
A working document, not a deck.
Every project has a single living document with scope, decisions, open questions, and links to whatever is being built. Anyone on either team can read it and know where things stand.
C
Working software, not mockups.
By the second week, you are reviewing interfaces that run in a browser. Mockups are a tool for thinking, not for sign-off. Real software gives you the feedback you can actually use.
D
Direct access to the people building it.
No account managers between you and the engineers. A shared Slack channel, response time measured in hours during working windows. The team you meet in week one is the team that ships it.
04 — Team
The five of us.
01
Adaeze Okeke
Founder · Technical lead
LAGOS, NG
02
Diego Castellanos
Senior engineer · Backend
BOGOTÁ, CO
03
Petra Sjöström
Designer & engineer
MALMÖ, SE
04
Théo Andrieu
Engineer · Infrastructure
LYON, FR
05
Ife Adebayo
Operations · Project lead
ABUJA, NG
05 — Next