Crave it. Tap it. Eat.
a home feed that puts the food first and the interface second.
onboarding-v3.mov
design-pass.mov
build-log.mov
week-one-retention.mov
client-standup.mov
delivery-app.mov
HELLOmy name is
weblume
HELLOmy name is
labs
^ ω ^
¯\_(ツ)_/¯
{ ^-^ }
(¬_¬)
weblume labs
we build apps people actually open
projects start at ₹70,000 · booked 3 weeks out
showreel-2026.mov
shipped for teams in
fixed
price, agreed before we start
friday
a build in your hands, weekly
day one
your repo, your figma, your accounts
gst
invoiced in inr, no lock-in
selected work
things we actually shipped
three of the products we designed and built end to end. hover to pull one out of the pile.tap one to open it.
case study
a food delivery app, end to end
ordering, discovery and payments — designed and shipped for indian users, on indian rails.
Kitchens near you
offers and nearby restaurants, ranked by what actually arrives hot.
Pay with UPI in one tap
upi, cards and cash on delivery — the three that matter here.
what we do
three things, done properly
design, build, and the long unglamorous bit after launch. we do all three or we do not take the project.
we need this in the store before our raiseon it!
an mvp you can actually install
you come to us with an idea and a deadline. six weeks later there is a real build on a real device — not a prototype, not a deck. testflight in week four.
week-04-testflight.mov
make it feel expensivesay less
design that survives real users
every screen gets drawn, prototyped and pressure-tested before a line of code exists. motion, empty states, error states — the parts template apps forget.
design-pass-03.mov
can you stay on after launch?that's the plan
we stay after launch day
launch is the start of the job. we watch crash-free rates, ship every other week, and sit in your standup until the thing runs itself.
release-cadence.mov
release cadence
we ship on a rhythm, not in bursts
every square is a day, every shade is a release — the gaps are weekends and the two weeks a year we close.
373releases across 176 shipping days
hover a square
how it works
from first message to live app
no discovery-phase invoices, no account managers. here is the whole engagement, start to finish.
- 01a conversationday 0
- 02scope and fixed priceday 1–2
- 03design you can clickweek 1–2
- 04build, in the openweek 3–6
- 05launch and stayweek 6+
01day 0
a conversation
you message us on whatsapp with whatever you have — a doc, a sketch, or just the problem out loud. you talk to the people who will build it, not a salesperson.
a call, same week02day 1–2
scope and fixed price
we turn the conversation into a written scope: screens, platforms, what is in and what is explicitly out. then one fixed price for the whole thing.
a quote you can sign, free03week 1–2
design you can click
every screen drawn and wired into a prototype you can open on your own phone. we change it here, where changing it is cheap.
an interactive prototype04week 3–6
build, in the open
a build in your hands every friday, in your own repo from the first commit. you watch it become real instead of waiting for a reveal.
testflight by week four05week 6+
launch and stay
we handle store submission, review responses and the first weeks of crash reports. then we either hand over cleanly or stay on retainer.
live, and supportedtimezonesoverlapping hours with the gulf, europe and us east
contractsmsa + nda before anything starts, your paper or ours
ownershipyour repo, your figma, your store accounts from day one
invoicinginr with a gst invoice — milestone-based, never upfront in full
takes two minutes · you get a scope and a price, free
the handover
you get the actual thing
not a slide deck of screenshots. a signed build, in your store account, with the source in your repo and a designer who still answers messages.
- your apple + google accounts, not ours
- source, designs and assets handed over on day one
- a walkthrough call before we close the project
case study
how we design an onboarding
six screens from a travel app we designed. every one of them is a decision about where someone drops off.
the point of the redesignevery screen earns its place or it goes
01welcome
a face, not a product tour
no logo splash and no three-slide explainer. the first frame is someone you could actually meet, in a place you might actually go — because the pitch is the people, and every second spent explaining is a second spent leaving.
02your dates
ask the easy question first
dates come before the account. it's the one thing a stranger will answer cold, it takes two taps, and it makes every screen after it personal instead of generic.
03the promise
one sentence, held for a beat
a single full-bleed frame that says what the app is for. most onboardings bury the promise on slide four. we put it where attention actually is, and give it the whole screen.
04the people
proof before the ask
real travellers whose dates overlap yours, with the match reason spelled out. showing the payoff before requesting anything is the whole reason the next screen converts.
05location
permission with the reward on screen
the location prompt fires here, with matches already pinned on the map behind it. asking while the reward is visible converts far better than asking cold at launch.
06the plan
end on a name and a date
the flow finishes on a plan that already exists — a person, a city, a day. the last frame of onboarding should be the reason to open the app tomorrow, not a confirmation receipt.
the stack
build your stack
tap what you want it built with. we'll carry your picks into the conversation so the first message already has something in it.
tap a brick to stack it
your buildnothing picked yet — tap a brick
and it plugs into what you already run
payments, auth, analytics, support. we wire the services you have instead of asking you to move.
how we build
we build with claude
claude, anthropic’s ai model, is part of how we work. it helps us move faster on the grunt work — every line is still designed, read and shipped by a person on our team, and the code is yours either way.
claudeby anthropic
- drafting code
- writing tests
- reviewing changes
- untangling bugs
the idea
most agencies sell you hours. we would rather sell you a thing that exists.
the gap between a good idea and a shipped app is almost never the code. it is taste, sequencing, and someone who refuses to hand over something broken.
so we kept the team small and the standard annoying. every build ships like it is our own product.
we work with founders in bengaluru, dubai, london and wherever else the internet reaches.
if you have something you want built properly, say hi.
sudip,
founder, weblume labs
founder, weblume labs
on price
one fixed price, written down before a line is built. if we scoped it wrong, absorbing that is our problem — it does not come back to you as a change order.
on access
you talk to the people building it. no account manager sits between you and the work, and nobody bills you for a discovery phase before the work starts.
on the code
your repo from the first commit. you own the thing while it is being written, not after the final invoice clears — and there is no handover day to dread.
on cadence
a build in your hands every friday, wherever you are. you watch it become real week by week instead of waiting months for a reveal.
on scope
we will talk you out of features. the fastest way to ship is to build less, and we would rather say so in the first call than invoice you for it in the sixth week.
on the standard
nothing leaves here that we would not ship as our own product. the team is small and the standard is annoying, and that is the entire trade.
pricing
fixed price, no surprises
three ways to work with us. every quote is locked before we start.
launch
get the first version out.
best for validating an idea
₹70,000
fixed price · 3–5 weeks
includes
- android app, built for the phones people here actually carry
- phone number + otp login — no password to forget
- upi and cards live through razorpay, tested end to end
- play store submission handled for you
- 30 days of fixes after launch
most picked
scale
the whole product, properly.
best for a real launch
₹1,00,000
fixed price · 6–8 weeks
includes
- android + ios from one codebase
- upi, cards and netbanking, plus payouts if you need them
- an admin panel, so you change content without paying us
- hindi and one regional language wired in from the start
- both stores submitted · 90 days of support
partner
a squad that stays.
best for ongoing roadmaps
₹85,000
per month · pause or stop anytime
includes
- a designer and an engineer, reserved for you
- a release every two weeks
- in your whatsapp, not behind a ticket queue
- gst invoice every month, no lock-in
< founder discount >
building your first thing, bootstrapping, or shipping something for your community? show us what you are making and we will take 15% off your first project.
* open to pre-revenue and solo founders.
faq
questions people actually ask
scope, money, timelines, and who owns what.
we design and build mobile and web apps end to end. you bring the idea and the domain knowledge, we bring design, engineering and the discipline to get it into a store. most clients come to us for a first version and stay for the roadmap.
₹70,000 for a single-platform launch build, and ₹1,00,000 for a full cross-platform product with payments and an admin panel. retainers run ₹85,000 a month. everything is fixed-price before we start — no hourly surprises, and you get a gst invoice.
a launch build takes four to six weeks, and you get a testflight or internal-track link around week four so you are holding the thing well before it is finished. scale builds run eight to twelve weeks with a build in your hands every fortnight.
yes — most of our work is. we run on overlapping hours with the gulf, europe and the us east coast, and handle store accounts in whichever region you are publishing to. billing is in inr with a gst invoice.
you do, completely, from day one. everything lives in your repo and your figma from the first commit. there is no license, no lock-in and no hosting you have to buy from us.
a conversation. bring whatever you have — a doc, a sketch, a competitor you like, or just the problem out loud. we turn that into a scope and a fixed price within two working days, free.
that is a good chunk of what we do. we audit the existing build, tell you honestly whether it is worth rescuing or rewriting, and give you a price for either path before you commit to anything.
whatsapp, mostly. it is where our clients already are and it keeps decisions moving. you get a direct line to the people building your app, not an account manager.
say hi
still reading? just message us
no form, no discovery call to book. it goes straight to the people who would build it.