Four engineers who build and ship production software
Four engineers, and all four work on your project
Lotus Tech Labs is four engineers in Ahmedabad, India. We build web and mobile products - and the AI features inside them - for founders and product teams in the US, UK, Europe and Australia. The work came before the company. The systems below were built by this team as freelance engineers, before Lotus had a name. That order matters: none of this is a capability we are describing, it is software running in production with real users on it right now. We take one project at a time and all four of us work on it. That is a deliberate constraint, not a stage we are growing out of. It is what makes it possible for you to talk to the person writing your code instead of to someone who will pass your question along.
Three systems, in production, carrying real load
Visual search across five million images
An events platform needed image-similarity search over a library of roughly five million photographs - upload one, find the matching ones. It returns results in under 200 milliseconds and currently serves around one million monthly active users.
Qdrant · vector search · sub-200ms
A ticketing platform that works where the signal does not
Organisers onboard, create events, sell passes and scan them at the gate. Gate scanning had to survive a venue’s bad connection, so the app queues locally and reconciles when it reconnects.
Postgres on Aurora Serverless · Valkey · AWS auto-scaling · Razorpay · Firebase push · SMS, WhatsApp and email · Flutter and React Native
Vendor profiles that write themselves
A marketplace for event vendors - artists, venues, photographers - had the problem every marketplace has: vendors will not write their own listings, and empty listings do not convert. A vendor now enters a prompt and the profile comes back filled in, with an about section, FAQs and images.
n8n · LLM-assisted content generation
You talk to engineers, and you use it before you accept it
Discovery call
We ask questions until we actually understand the thing. This is engineers asking, not a salesperson taking notes to relay.
A written PRD
You approve it before we write any code. If the scope is wrong, this is the cheap place to find out - and it is yours to keep either way.
Build, in agile iterations
Slack, Google Chat or email, on your tooling and your cadence, with at least one call a week. You see progress continuously rather than at a reveal.
UAT
You use what we built, on your own data, before you accept it. Nothing is "done" because we say it is.
Close - or carry on
Not every project has a fixed scope. Some clients keep us on an hourly retainer for a year with no defined requirements and we handle whatever comes up. Both work.
Where we are not a fit
We do not do staff augmentation - we take the problem, not a seat on your board. We do not build WordPress sites; we work in TypeScript on Node, and in Python where the work is machine learning. We do not publish a price list, because what a project costs depends on what it is and we would rather tell you honestly on a call. And we run one project at a time, so if we are booked we will say so.
If we are not the right team for your project, you will hear it on the first call rather than three weeks in.