When Kabir and Ananya started their four-person web studio in Pune, they did what every new agency does. They bought things. A rack-mounted server for client staging sites, a pricey camera kit for product shoots, a second set of monitors “for when we hire,” and a year of hosting for every client up front. Eighteen months later, most of that kit was gathering dust while their bank balance looked thin. This is the story of how they moved to on-demand infrastructure for a small web agency, and what they learned along the way. The team is fictional, but if you run a studio, you will probably recognise every scene.
Chapter one: the server in the corner
The staging server was Kabir’s pride. It hummed in the corner of the office and hosted preview builds for every client project. The trouble was that most weeks it ran two or three sites at most. During quiet months, it ran none. It still needed power, cooling, updates and the occasional Saturday rescue when a disk complained.
Ananya did a back-of-the-envelope calculation one evening. The server was busy for perhaps a fifth of the time it was switched on. “We are paying for a whole house,” she said, “and living in one room.”
They switched to spinning up cloud staging environments only when a project needed one, and shutting them down after client sign-off. The monthly bill started tracking actual work instead of sitting flat. When a big launch came in, they scaled up for a week. When things went quiet, the cost shrank on its own.
Chapter two: the camera nobody touched
The camera kit had been bought for one ecommerce client who needed product photos. Since then it had come out twice. Meanwhile, the lenses were already a generation behind.
The fix here was even simpler. For the next shoot, they rented a body and two lenses from a local photography store for the weekend. They got newer gear, paid only for the days they used it, and returned it without worrying about storage. Then they did something they had not planned: they listed their own old camera kit with the same store’s rental pool, so on weekends they were not shooting, it earned a little back instead of sitting in a drawer.
Chapter three: the client visit in Jaipur
The turning point came with a hotel client in Jaipur. The brief was a full website redesign plus fresh photography of the property and the old city around it. Ananya flew in for three days with the rented camera kit. The question was how to get around: between the hotel, the photo locations and a couple of meetings, she needed flexible transport without the hassle of daily taxis.
A colleague pointed her to MotoShare, where residents and rental shops in Indian cities offer their two-wheelers and cars for short hires. She searched by city and dates, picked a scooter light enough for the old-city lanes, confirmed it online and paid when she collected it near the hotel. For three days of work, it was exactly the right amount of vehicle.
On the flight home she kept thinking about it. The scooter’s owner had a vehicle that would otherwise have stood still that week. She had a short-term need. A listing in the middle connected the two. That was the same logic they had been applying to their own studio, just on a different street.
Chapter four: rethinking what the agency owns
Back in Pune, the two founders sat down with a whiteboard and drew two columns: things they use every day, and things they use occasionally. The first column was short: laptops, a good chair each, the project management board, the code repository. The second column was long.
- Staging and testing environments moved to on-demand cloud instances.
- Photography and video gear became weekend rentals.
- Premium stock media switched from a big annual bundle to per-project licences.
- Meeting rooms for client workshops came from a co-working space by the hour.
- Specialist freelancers, such as an accessibility auditor, were brought in per project rather than hired full time.
The aim was not to own nothing. It was to own the things that work all day and rent the things that work some days.
Chapter five: the side effect nobody expected
With less money tied up in kit, they could say yes to smaller clients without worrying about covering fixed costs. They also had more time. No more Saturday server rescues, no more stock-licence renewals they had forgotten about.
There was a planning lesson too. Because each project now carried its own costs, they started scoping infrastructure, media and travel at the very start. Their guide to planning a company website well ahead of development now includes a line for “what will we rent for this project?” alongside sitemap and content inventory.
What other studios can take from this
If your agency is small and growing, a few habits from Kabir and Ananya’s story are worth borrowing.
- Measure busy time, not ownership. Ask how many hours a week each expensive asset actually works for you.
- Scale with the project. Let staging, storage and media costs rise and fall with real client work.
- Rent the occasional, own the constant. Daily tools deserve investment. Monthly ones rarely do.
- Put idle kit to work. If you do own something you use rarely, see whether it can earn by serving others.
- Budget per project. Include rented items in each quote so they never become hidden overhead.
Where the studio is now
The server is gone, sold to a hobbyist. The office corner holds a plant. The hotel site in Jaipur launched with photography the client loved, and the studio’s second year has been noticeably calmer on cash. When a new team member asks what they should buy for a project, the first answer is always a question: “Do we need to own it, or just use it for a while?”
For a small web team, that one question tends to protect both the budget and the focus. And if you are building or refreshing your own studio’s site to tell clients how you work, our notes on service pages that convert visitors into enquiries may help you explain the value clearly.
