Product engineering
Web products built to be operated: sensible data models, readable code and a deployment path anybody on the team can follow.
CloudBhumiWork with usIndia · Product engineering
Engineers who stay
We support a growing set of companies in India with product engineering, maintenance and infrastructure.
Overview
Product engineering in India
We build and run products for companies across India: the first version, the versions after it, and the unglamorous maintenance that decides whether software is still useful in year three.
We do not take handoff projects and disappear. The team that ships a release is the team that fixes it at month nine, which changes how carefully the first version gets written.
In short
- Product engineering and ongoing maintenance
- Cloud infrastructure and deployments
- Long term ownership, not handoffs
Offered in India, remotely.
What it covers
The work, named
Ongoing maintenance
Dependency updates, small fixes and the steady care that keeps a working product working.
Cloud infrastructure and deployments
Hosting, environments and releases set up once, properly, so shipping stops being an event.
Rebuilds and migrations
Moving off something that no longer fits, in slices, without a big bang cutover weekend.
Long term ownership
A named team that stays with the product, so context does not reset every quarter.
How it starts
No theatre
Four steps, in this order, every time. You will know where you stand at each one.
- 01
Understand the business, not just the brief
We ask what the software is meant to change. Features that do not serve that get cut early, which is cheaper for you.
- 02
Scope in slices
A defined first slice with a date, then the next. You see working software before you have spent the budget.
- 03
Ship and operate
The release goes out with monitoring and a rollback, and we stay on it afterwards.
- 04
Keep it alive
Maintenance continues as a standing arrangement rather than a rescue call two years later.
Who it suits
A good fit if
- Indian businesses replacing spreadsheets, paper or software that has stopped fitting
- Institutions and operators who want the same team for the build and the years after it
- Companies who need engineering and infrastructure from one place rather than stitching vendors together
Questions
Before you ask
What companies want to know before they hand over any part of their technology.
What kind of products do you build?
Web products that people use to do their job: platforms, internal tools and operational systems. Patashale, AtithiVishram and Arjaka are our own examples of that kind of software.
Do you take on maintenance for an existing product?
Yes, and a good share of our work is exactly that. We read the codebase first and tell you honestly what is worth keeping.
Do you hand the code over at the end?
The code is yours throughout. What we avoid is the handoff model where a vendor ships once and vanishes: we would rather keep operating what we built.
How large is the team?
A deliberately small core of three, with a network of more than twenty vetted designers, engineers and marketers we bring in as a project needs them.
Where in India do you work?
Our office is in Pune, Maharashtra, and we work remotely with companies across the country. Our institutional and hospitality clients today are in Karnataka.
Other ways we work
US · Remote
Dedicated tech support for US companies
We partner with United States based companies as an extended engineering team, providing reliable support across their software stack.
Read moreGlobal
Managed technology for growing teams
We help companies plan, build and manage their technology so their teams can focus on running the business.
Read moreTell us what is breaking
Describe your stack and where it hurts. We reply within a business day with an honest read on how we would take it on.
Start the conversation