About
A small studio,
built around the work.
Webloom Labs is a founder-led software studio. We design and build commerce platforms, custom software, and the systems that keep them running — and we stay involved after launch.
Why we exist
Most software
problems are
business problems
A lot of projects go wrong before any code is written. The tool gets chosen first, the business gets fitted around it, and everyone spends the next two years working against the software instead of with it.
We start the other way round — with how the business actually operates, including the exceptions nobody wrote down. That usually changes what gets built, and occasionally it means telling someone they do not need us at all.
We are deliberately small. It means we take on fewer projects than a larger agency would, and it means the person you speak to is the person doing the work.
What we believe
Five things we
actually hold to
Not a values page. These are the specific commitments that decide how we quote, what we take on, and what we say no to.
Direct Communication
You work directly with the people building your product.
Engineering First
Technology choices are made around the problem — not because a particular tool is fashionable.
Built for the Long Term
We care about maintainability, performance, and what happens after launch.
Honest Advice
If a simpler solution is better, we will tell you.
Small Team, Senior Attention
We stay close to the work instead of passing projects through layers of account management.
Founders
The two people you
will actually be dealing with
Shakil Ilham
Technical Founder
BSc (Hons) Artificial Intelligence — reading
Leads the engineering. Industry experience as a full stack developer and as an AI and ML engineer, which is the combination most of our work draws on — product built end to end, with the machine learning parts treated as engineering rather than a demo.
Ashfak Nawshad
Sales Co-Founder
BSc (Hons) Artificial Intelligence — reading
Runs the commercial side — the first conversation, scoping, and making sure what gets quoted is what actually gets built. The technical background means scoping happens with someone who understands the build, not a layer of account management on top of it.
How we work with clients
No layers between
you and the work
A small studio only works if the working relationship is direct. This is what that means in practice.
One team, start to finish
The people you talk to are the people writing the code. Nothing gets relayed through an account manager.
Scoped before quoted
We work out what the project actually involves before putting a number on it, because the alternative is a number that changes.
Shipped in stages
Something usable at the end of each stage, so a change of direction costs you one stage rather than the whole plan.
Yours to keep
Your code, your data, your infrastructure, documented well enough that another team could pick it up.
Process
Five stages,
the same every time
You work directly with the people building your product at each one. See what we build.
Understand
We learn about the business, users, goals, constraints, and existing systems.
Plan
We define scope, technical direction, architecture, and delivery plan.
Design
We turn requirements into clear user flows and interfaces.
Build
We develop, integrate, test, and iterate.
Launch & Improve
We deploy, monitor, optimize, and continue improving the product.
The work we want
What we are
looking for
We are better at some projects than others, and being specific about that saves everyone a conversation.
Projects with a real constraint
Work where the requirements do not fit the obvious tool. That is where building something is worth more than configuring something.
Businesses that will still be here
We would rather maintain a system for years than ship it and disappear. Long relationships suit how we work.
Commerce and the systems around it
Storefronts, the operations behind them, and the integrations that keep stock, orders, and accounting agreeing with each other.
Teams who want to be involved
Clients who will tell us how the business actually runs. The best builds come out of that conversation, not out of a brief.
Technology
A short list,
on purpose
These are the tools we work with often enough to support them properly years from now. Some of what we build with them we publish.
Frontend
- Next.js
- React
- TypeScript
Commerce
- Medusa.js
- Stripe
- Headless CMS
Backend
- Node.js
- PostgreSQL
- Supabase
Infrastructure
- Docker
- Coolify
- Cloudflare
AI
- OpenAI
- LLM APIs
- n8n
Work with us
Have something
you want built?
Small enough to care about the details. Experienced enough to build the difficult parts. Tell us about the problem and we'll come back with a technical direction, scope, and timeline.
You work directly with the people building your product.