Qasim
Malik
I started Grownic because I kept meeting the same problem from two directions: teams with a rigid studio, and studios with a rigid idea of what they build.
My answer was to stop thinking in products and start thinking in particles. Small, well-made, interchangeable parts — tokens, pipelines, components, prompts, rules — that can be arranged into an editorial website on Monday and an autonomous agent on Thursday, without the quality changing between them.
Software should behave like nanoparticles — not like monuments.
A monument is impressive once. It is also fixed: to change it you demolish it. Most software is built this way, which is why every serious change feels like a rebuild and every rebuild loses something that was working.
Particles behave differently. Individually they are almost nothing - a token, a function, a rule, a single well-chosen word. Arranged, they become a product. Rearranged, they become a different product without anyone starting over. Flexibility stops being a promise in a proposal and becomes a property of the material.
That is the whole thesis of this studio. We invest obsessively in the small parts so that the large ones can move. It is also why our four practices share one team: the parts are common, only the shape changes.
Five rules I refuse to trade.
Smallest useful part
Every system we build is decomposed until each piece can be understood alone, replaced alone, and trusted alone. Big things fail slowly; small things fail visibly.
Shape follows the problem
We do not arrive with a template. The same team that builds an editorial site builds an agent — the particles are the same, the arrangement is not.
Detail is not decoration
A 40ms easing change, a corrected optical size, one fewer form field. None of it shows up in a scope document; all of it shows up in how the thing feels.
Refuse before you guess
Especially with AI. A system that says 'I don't know' keeps its authority. A system that invents once loses it permanently.
Leave it buildable
We hand over tokens, tests and documentation, not a dependency on us. Good work should outlive the relationship that produced it.
Ten years, one direction.
- 2016First line shipped for money
Freelance builds for local businesses - and the first hard lesson that taste is a deliverable, not a bonus.
- 2019From builder to systems thinker
Stopped shipping pages and started shipping design systems, pipelines, and the documentation that keeps them alive.
- 2022The nanoparticle idea
A realisation from repeated rebuilds: teams don't need bigger frameworks, they need smaller, recombinable parts.
- 2024Grownic is founded
One studio built as four - web, mobile, AI agents, AI automation - sharing a single vocabulary of craft.
- 2026Studio as a shape-shifter
A roster across eight countries, and a practice deliberately built to rearrange itself around whatever the work demands.
If you are reading this, you are probably deciding whether to trust a studio with something that matters to you. So let me be plain about what you would be buying.
You would not be buying capacity. Capacity is easy to find and easy to regret. You would be buying judgement — a team that will ask the uncomfortable question in week one so that nobody has to ask it in month six, and that will tell you when the thing you asked for is not the thing you need.
You would also be buying restraint. We build AI systems that admit uncertainty, interfaces that remove fields rather than add them, and automations that escalate to a human at exactly the right moment. Most of our best decisions are subtractions.
And you would be buying flexibility as a design decision, not a courtesy. Scope will change — it always does. Our work is built from parts small enough that change costs a conversation, not a quarter.
Bring us something difficult.
/ Qasim Malik, Founder & CEO, Grownic