+91 766-599-1888 • hello@praveenpatel.com • WhatsApp
How I work

A Process With No Surprises In It

Most bad software projects fail the same way: unclear scope, invisible progress, and a bill that grows. These seven steps exist to remove all three.

Get a free quote +91 766-599-1888
Steps
7 stages
Quotes
Fixed, in writing
Updates
Live staging link
The process

Seven steps from first call to launch

Each stage has a defined output, so you always know what you are approving and what happens next.

01

Discovery call

A straight conversation about what the business does, what is not working and what success looks like. No slide deck. If I am not the right fit for the project, I will say so here rather than three weeks in.

45-60 minutes
02

Written scope and fixed quote

You get a document listing exactly what will be built, what is excluded, the timeline in milestones and a fixed price. Nothing starts until you have read it and agreed. The scope is yours to keep either way.

2-4 days
03

Design you can click

Wireframes first for structure, then visual design. For websites you approve a working page in the browser rather than a flat image, so what you sign off is genuinely what gets built.

1-2 weeks
04

Build in visible milestones

Development runs in two-week milestones on a staging URL you can open any time. You see progress as it happens instead of receiving a status report about work you cannot verify.

2-16 weeks
05

Testing and your review

Cross-browser and mobile testing, speed and security checks, and a review round where your team uses the system properly and lists what needs changing before launch.

3-7 days
06

Launch and handover

Deployment, analytics and Search Console setup, a walkthrough recording for your team, documentation, and full credentials handed over. You own everything, including the source code.

1-2 days
07

Support after launch

A warranty period covering any bugs at no charge, then an optional maintenance plan for updates, backups, monitoring and new features. No lock-in either way.

Ongoing
Commitments

What you can hold me to

You work with the developer

Not a salesperson, not an account manager, not a team you never meet. The person who scopes your project is the person who writes the code and the person who answers when something breaks at nine at night.

Custom built, not assembled

No purchased themes dressed up as bespoke work, no page builder stacked on a page builder. Clean code written for your requirement, which is why these sites load fast and stay maintainable.

You own everything

Source code, database, domain, hosting account and every credential. Registered in your name, handed over at project close. No licence traps and no hostage situations if you decide to move on.

SEO built in, not bolted on

Semantic structure, schema markup, fast loading and clean URLs from the first line of code. Ranking is much harder to retrofit onto a site that was not built for it.

Fixed price, written scope

You know the number and the deliverables before work begins. Additions are quoted separately and visibly, so the final invoice never contains a surprise.

Long-term support

Ten years in, I still maintain systems I built early on. The value of software is in year three, not launch week, and that is how I build it.

What I need from you

Projects run late for predictable reasons

In ten years, the overwhelming majority of delayed projects were delayed on the client side, and almost always for the same three reasons: content that was not ready, feedback that came in fragments over several weeks, and a decision-maker who was not in the room until late.

None of that is a criticism — running a business is a full-time job and a website is not your priority. But it is worth knowing up front, because a project where content is ready and one person can approve decisions typically finishes in half the calendar time of one where it is not.

  • One person who can give final approval
  • Content and images ready, or agreement that I write and source them
  • Feedback consolidated into one round rather than trickled daily
  • Access to whoever actually does the work the software will support
  • Existing data exported if we are migrating from another system

What happens if something goes wrong

Bugs found during the warranty period are fixed at no charge, and there is no argument about whether something counts as a bug — if it does not do what the scope says it does, it gets fixed.

If a project genuinely turns out to be the wrong idea partway through, I would rather stop it than bill you for finishing something you will not use. That has happened twice in ten years, and both clients came back later with a better-scoped project.

If you decide to move to another developer at any point, you take the code, the database and every credential. No handover fee and no obstruction.

FAQ

Questions about working together

How much does a website or software project cost?
Every project is priced individually, because two websites with the same page count can involve very different amounts of work. Rather than publish a price list that would be wrong for most enquiries, I give you a fixed written quote after a short scoping call — usually within two to four days. The quote covers exactly what will be built and what is excluded, it does not change mid-project, and there is no obligation to go ahead. Ask and you will get a real number for your specific project.
How long will my project take?
Websites take two to five weeks, ecommerce four to ten weeks, and custom software six to sixteen weeks depending on scope. Large ERP implementations are staged over several months so value arrives early rather than everything landing at the end. Timelines are agreed in writing with milestone dates.
Do you work with clients outside Udaipur?
Yes, routinely. Around half of all projects have been for clients elsewhere in India — Jaipur, Delhi, Mumbai, Bengaluru, Ahmedabad, Pune — and overseas in the UK, UAE, USA and Australia. Work runs on video calls, shared documents and WhatsApp, and in-person visits are arranged where a project genuinely benefits from them.
Will I own the source code?
Yes, completely. Source code, database, domain and hosting are registered in your name and handed over at project close, along with documentation. There are no per-user licence fees and nothing that prevents you from taking the project to another developer later.
What if I need changes after the project is delivered?
Every project includes a warranty period during which any bug is fixed at no charge. Beyond that, changes can be requested ad hoc at an agreed rate, or covered by a monthly maintenance plan that includes a block of hours, updates, backups and priority support.
Do you provide hosting and domain?
Yes. Managed hosting with SSL, daily backups and monitoring, plus domain registration in your name. If you prefer your own AWS, DigitalOcean or existing hosting account, I will configure and manage it there instead — the account stays yours either way.
Can you fix or take over a project another developer abandoned?
Yes, and it is a regular part of the work. It starts with a paid code audit that documents what exists, what is broken and what is insecure, followed by a written stabilisation plan. You keep the audit regardless of whether you continue with me.
How do payments work?
Typically in milestones: an advance to begin, staged payments as milestones are delivered and approved, and the balance before launch. Larger projects are split across more milestones. Payment by bank transfer or UPI, with a GST invoice for every payment.

Let us talk about your project

Tell me what you are trying to build or fix. You will get an honest opinion, a written scope and a fixed price — with no obligation to go ahead.

Get a free quote +91 766-599-1888

Reply within one working day   Fixed written quote   You own the code