Skip to content
01

A studio builtaround one idea:decide it properly.

Bhavesh Works exists because too much software is designed by people who will never build it, and built by people who were never told why. I do both, from the first sketch to the final deployment.

Founded
2022
Based
Anand, Gujarat
Team
One developer, no hand-offs
Engagements
Project or retained

Craft

Craftsmanship in software is not ornament. It is the difference between a system that can be changed on a Tuesday afternoon and one that requires a meeting, a migration plan and somebody’s weekend.

Bhavesh Works is the freelance studio of Bhavesh Bhoi, a full-stack developer in Anand, Gujarat. One person scopes the work, designs it and builds it, so nothing is lost between a brief and a deployment.

It is deliberately small. Every engagement gets senior attention because there is no second tier to hand it to, and I take on fewer projects than I could so that the ones I take are finished properly. Where a project needs more hands, the studio is Bhavesh plus trusted collaborators, and the proposal says so.

Studio facts

The studio,stated plainly.

Studio
Bhavesh Works — an independent software studio
Run by
Bhavesh Bhoi, full-stack developer
Team
One person, plus trusted collaborators where a project needs them
Founded
2022
Based in
Anand, Gujarat, India
Works with
Vadodara, Ahmedabad, Gujarat, India, United Kingdom (remote), United Arab Emirates (remote), Australia (remote), Switzerland (remote), Singapore (remote)
Core services
Custom CRM & ERP Development; Web Application Development; Performance & Technical SEO
Also available
Website design & development; UI/UX design; Graphic design; Social media design
Typical timelines
CRM & ERP: 10 – 20 weeks; Web Apps: 8 – 16 weeks; Performance & SEO: 3 – 6 weeks
Engagement models
Fixed-scope project, or retained
Languages
English, Hindi, Gujarati
Working hours
09:00 – 19:00 IST
Contact
works@bhavvesh.in · +91 70966 72257

Where I work

Based in Gujarat.Working across India.

The studio runs from Anand, Gujarat — close enough to Vadodara and Ahmedabad for a site visit or an in-person kickoff to be an easy call, not a production. Everywhere else, a project runs the same way it does locally: calls on your schedule, shared documents, and something deployable every week, whether the client is down the road or across the country.

City

Anand

Home base. Where the studio actually works from.

City

Vadodara

The nearest major business hub, about an hour away — in person when it helps.

City

Ahmedabad

Gujarat's largest commercial centre — the same, on-site when useful.

State

Gujarat

Client visits and on-site work anywhere in the state, scheduled around the build.

Country

India

Everywhere else runs the way it does locally — calls, shared documents, weekly deployable progress.

Remote, beyond India

I also take projects from businesses outside India and deliver them remotely — there is no office abroad. Each country has its own page with the real working-hours overlap and what changes when personal data is handled from India:

Method

How a project runs,start to handover.

Four stages, each with a milestone you can check. Whatever the service, the end is the same: you own the code, the accounts and the documentation, and you do not need me to keep moving.

01First two weeks or so

Discovery

I map the problem before the product: who touches it, what breaks today, what the numbers say. You leave with a written scope you could hand to any competent developer, whether or not that developer is me.

You getA written scope and a price range.

02Most of the project

Build, with weekly demos

Deployable increments, every week, on a real URL, with a short demo. No status decks describing progress you cannot click. Direction corrects while correcting is still cheap.

You getA working build you can use, every week.

03Agreed in the proposal

Launch

A staged release with data migration where needed, monitoring in place and a plan to roll back. You sign off before anything switches over.

You getYour sign-off before go-live.

04A phase of its own

Handover

Documentation, a walkthrough with your team, and access and credentials transferred. On final payment the repository, infrastructure accounts and design files are yours — you do not need me to keep moving.

You getYou own the code, the accounts and the documentation.

Difference

What usually happens,and what happens here.

A discovery call that is really a sales call.

A discovery phase that ends in a written scope you own either way.

An estimate given before the problem is understood.

A range first, a number after architecture — and I hold it.

Designs handed to engineers who have to invent the missing states.

Empty, error, loading and permission states designed before the happy path.

A junior on the keyboard, a senior on the call.

The person you speak to is the person writing the code.

Handover as an email with a repository link.

Handover as a phase, with documentation, a walkthrough and a support window.

Tooling

Boring technology,chosen on purpose.

I am not paid by any vendor and I do not chase releases. These are the tools I can support for years and hand to your team without a translation layer.

Application

Next.js · TypeScript · React

Data

PostgreSQL · Prisma

Interface

Tailwind CSS · Figma

Delivery

Vercel · GitHub

Measurement

Lighthouse · Search Console · Web Vitals

Structured data

JSON-LD · schema.org

Questions

Questions people askabout the studio.

Bhavesh Works is an independent software studio in Anand, Gujarat, India, founded in 2022 by Bhavesh Bhoi. It builds custom CRM and ERP systems, web applications, and performance and technical SEO work, and offers design alongside.

It is one person: Bhavesh Bhoi, who scopes the work, writes the code and is the person you talk to. Where a project needs more hands, the studio is Bhavesh plus trusted collaborators, and the proposal says so.

The studio runs from Anand, Gujarat. It works with clients across Vadodara, Ahmedabad, Gujarat and the rest of India — in person where it helps, and remotely through calls, shared documents and something deployable every week everywhere else.

Yes, remotely. The Regions pages show the real working-hours overlap and what changes when personal data is handled from India, for each country the studio serves.

No. The studio is based in Anand, Gujarat, India, and delivers work for UK businesses remotely — including teams in London, Manchester, Edinburgh and Glasgow. There is no UK office, and the studio does not claim one. In January the UK working day overlaps the studio's by about four and a half hours, and in summer by about five and a half.

Three main services: custom CRM and ERP development, web application development, and performance and technical SEO work. Website design, UI/UX design, graphic design and social media design are also available alongside them.

A web application typically takes 8 to 16 weeks and a CRM or ERP build 10 to 20. Performance and technical SEO work typically takes 3 to 6 weeks. Each service page lists its own range.

Work is scoped as a fixed project or on a retainer. A range comes first and a firm number after the architecture is settled, and that number is held. For a quick sense of budget before writing a full brief, you can message on WhatsApp. Bhavesh Works is not the cheapest option — it charges for senior attention on the whole build.

You do. On final payment the repository, infrastructure, credentials and documentation transfer in full, and design work is delivered as editable source files rather than exports alone.

They were built by me while I was at Aina Tech Services LLP, and the site attributes them that way. They are shown as evidence of my work, not as Bhavesh Works client projects.

Yes. The Work page shows the live CRM systems with the public evidence for each, and bhavvesh.in holds Bhavesh Bhoi's personal projects and experiments, which are kept separate from the studio's client work.

Email works@bhavvesh.in, message or call +91 70966 72257 (WhatsApp is supported), or use the contact form. Working hours are 09:00 to 19:00 IST.

Work together

If that sounds likehow you want to build.

Tell me the problem rather than the feature list. The first conversation is about whether I am the right developer for it — and I will say so if I am not.