Spend one hour before you spend lakhs
The most expensive mistakes in websites and apps happen before development starts: wrong technology, vague scope, a lowest-price developer who disappears mid-project, a feature list padded with things nobody will use, a domain registered in someone else's name. A consultation exists to catch those mistakes while they are still free to fix. One hour of honest technical advice routinely saves clients tens of thousands of rupees and months of frustration — I have watched it happen for 11+ years.
Those years building web and app projects also mean 11+ years of seeing exactly how projects fail. In a consultation you get that pattern-recognition applied to your specific situation, in plain language. No jargon, no upselling, no pressure — the advice stands on its own, and you keep every document we produce whether or not we ever work together.
Who books consultations with me
Business owners starting their first website or app, who want to understand the landscape before talking to any developer or agency — what things should cost, what questions to ask, what traps to avoid.
Owners holding quotations they can't evaluate. Three quotes, three wildly different prices, three different technology names. I translate them into one comparable picture and flag what each is hiding or missing.
People with stuck or abandoned projects. The developer vanished, the site is half-built, passwords are scattered. You need a neutral expert to assess the damage and chart the cheapest way out.
Businesses whose website exists but produces nothing. Traffic without enquiries, or no traffic at all. You need a diagnosis before spending more on marketing.
Founders validating an idea. Before pitching investors or spending savings, you want a technical reality-check: what would this actually take to build, what should version one contain, what will it cost to run.
What we can cover, concretely
New project planning
You describe the business goal; I convert it into a realistic feature list, a technology recommendation with reasons, a phased timeline and an honest cost range. You leave knowing exactly what to ask any developer — and how to judge their answers. Many clients take this plan to other developers, and that is completely fine; an informed client is my favourite kind, whoever they hire.
Quotation and proposal review
Line by line through the quotes you have received: what is fairly priced, what is inflated, what essential item is suspiciously absent (backups, security, SEO basics, mobile testing, admin training, ownership terms). You will negotiate from knowledge instead of hope, and the questions I give you will reveal more about each vendor than their brochure ever will.
Rescue and audit for stuck projects
I examine the existing code, hosting, and access situation, then give you a written verdict: what percentage is salvageable, what completing it costs, what rebuilding costs, and — critically — the immediate security steps (password changes, domain transfer) that protect you today. Sometimes finishing is far cheaper than restarting; sometimes the code is genuinely beyond saving. You want that verdict from someone quoting the audit, not someone quoting the rebuild.
Website and performance audit
A structured review of an existing site: speed, mobile experience, SEO health, security basics, conversion blockers, content gaps. Delivered as a prioritised fix-list — quick wins first, structural work after — that any competent developer can execute, including your existing one.
Growth and SEO direction
If the website exists but business is not coming, we diagnose why: is it visibility (nobody finds you), credibility (they find you and leave), or conversion (they stay but never act)? Each has different fixes, and mixing them up wastes money. You leave with a priority list you can execute step by step within your budget — and a realistic timeline, because anyone promising page one of Google in a week is selling a story.
Technology and platform selection
WordPress or custom code? Shopify or WooCommerce? Native app or cross-platform? Shared hosting or VPS? These choices have long consequences and are usually made on a salesperson's preference rather than your actual needs. I explain the trade-offs in your context and give a recommendation with reasons you can verify.
Second-opinion support during ongoing projects
Several clients keep me as a neutral technical advisor while an agency builds their project — reviewing progress at milestones, testing quality, translating jargon, and keeping the vendor accountable. The cost of this oversight is a fraction of the cost of discovering problems after final payment.
How a consultation actually works
Before the call
You book a free estimate meeting directly from this website — pick your own date and time slot, and the meeting link arrives by email automatically. Fifteen minutes of preparation triples the value of the hour: write one sentence about what success looks like ("tile dealers in west UP should find me and enquire"), collect 3–5 reference websites you like, know your internal budget range, and list what you already have (domain, hosting, logo, content, photos).
During the call
Roughly an hour, online with screen sharing when useful. I ask questions first — about your customers, your competitors, how enquiries currently reach you — because the right recommendation depends on your business, not on technology fashion. Then we work through your specific agenda: the plan, the quotes, the stuck project, the diagnosis. You can record the call; many clients do.
After the call
You receive a requirement summary PDF capturing what we discussed and decided. If the next step is a project with me, this flows straight into a fixed itemised quotation. If the next step is with someone else, the summary works as your project brief. Either way, it is yours.
The questions I make sure get answered
Whoever you eventually hire, these ten protect you: Will the domain, hosting and website be registered in my name? Will I receive all passwords and source code on delivery? Can I get an itemised, feature-by-feature quotation? Is the payment structure tied to deliverables rather than dates? What counts as a "change" versus a "new feature" afterwards, and what does each cost? Are mobile responsiveness, SSL and basic SEO included? Will I be able to update content myself, with training? Can I see live projects and speak to a past client? What support is included after launch, for how long? And if we part ways, what exactly do I hand the next developer? A good professional answers all ten happily. Defensiveness at these questions is itself your answer.
Honest advice sometimes means "don't spend yet"
I regularly tell consultation clients things that shrink my own potential invoice: that a great mobile website should come before the app they wanted; that their existing site needs five fixes, not a rebuild; that their budget suits a phased plan rather than the full vision at once; that the agency quote in their hand is actually fair and they should take it. This is deliberate. Consultation only has value if the advice is independent of what I might sell you afterwards — and long-term, honesty is the best marketing I have ever done.
Common situations, straight answers
"My developer left the project incomplete. Can you help?" Yes. Secure your accounts first (I'll walk you through it on the call), then I audit what exists and give you costed options both ways.
"Can you review a quotation another agency gave me?" Yes — it is one of the most common requests, and one of the highest-value hours you can spend.
"Is the first consultation really free?" Yes, genuinely. The estimate meeting costs nothing and the summary PDF is yours. Deeper paid engagements — written roadmaps, full audits, rescue plans, ongoing advisory — exist if and when you want them, with prices agreed before, never sprung after.
"I'm not technical at all. Will I understand?" That is exactly who this service is for. If I cannot explain a recommendation in plain language, the recommendation isn't ready.
"Do you consult for projects you won't build?" Yes. Advice and construction are separate services; you can take either or both.
Book the hour that protects the lakhs
Whether you are planning your first website, comparing quotations, rescuing a stuck project, or trying to understand why your existing site produces nothing — come with your questions and leave with a plan. Book your free estimate meeting below; you choose the date and time, the link arrives automatically, and the plan we make is yours to keep, whoever builds it.
Three real consultation stories (details changed, lessons intact)
The quotation that shrank by forty percent
A coaching institute arrived with an agency quotation. Line-by-line review found a "custom CMS" priced like spacecraft, a mandatory "annual maintenance" worth more than the build, and no mention of who owned the domain. Armed with specific questions, the owner renegotiated: standard platform, itemised features, ownership in writing — same agency, same website, forty percent less, and a relationship reset on honest terms. Cost of the consultation hour versus the saving: not close.
The rescue that didn't need a rebuild
A trader's website had been "almost done" for eight months before the developer stopped replying. Panic quotes for rebuilding started at a lakh. The audit found the truth: seventy percent complete and competently built — the developer had vanished for personal reasons, not incompetence. We secured every account the same day, and a completion contract finished the site for a fraction of the rebuild quotes. The lesson repeats constantly: get the neutral verdict before paying for demolition.
The app idea that became a webpage first
A founder wanted a marketplace app — savings-threatening budget, twelve-month build. Consultation reframed it: the risky question wasn't "can this be built" (yes) but "will both sides show up" (unknown). Version zero became a focused website plus WhatsApp workflows, live in three weeks at one-twentieth the cost. It found real demand on one side and crickets on the other — priceless knowledge, learned cheaply. The app is now being built, shaped by a year of real behaviour instead of assumptions. Sometimes the best technical advice is a smaller first step.
Engagement formats and what you receive
The free estimate meeting — one hour, any agenda from this page, requirement summary PDF afterwards. Genuinely free, genuinely useful, zero obligation. Written technical roadmap — for bigger decisions: a document covering recommended approach, phased feature plan, technology choices with reasons, realistic cost ranges and vendor-selection questions. Yours to execute with anyone. Audit reports — website/hosting/SEO health or stuck-project assessment, delivered as a prioritised fix-list with effort estimates, ordered so quick wins come first. Ongoing advisory — a monthly hour (or per-milestone reviews) as your independent technical adviser while any vendor builds; translation, quality checks and accountability at a fraction of the cost of post-payment surprises. Every format has its price stated before it starts, and every deliverable is written to survive without me — no cliffhangers engineered to force the next booking.
A small glossary for your next vendor meeting
Scope: the written list of exactly what will be built — if it isn't written, it isn't agreed. Milestone: a deliverable checkpoint that payment should attach to. Staging: a private preview link where you watch work progress. Handover: the transfer of all passwords, code and accounts to you at completion — ask how it works before you start, not after a dispute. Retainer/AMC: ongoing monthly support — reasonable when scoped, a trap when mandatory and vague. Redirects (301): the forwarding rules that preserve your Google rankings during a redesign — their absence from a redesign quote is a red flag you can now spot. Ten minutes with these terms changes the power balance in any vendor conversation, which is rather the point of consultation in miniature.
Why I keep this service genuinely independent
An adviser who profits from the advice is a salesperson with better manners. So the boundaries are explicit: consultation deliverables are complete in themselves; recommendations name categories and criteria, and where I would personally be a candidate to build something, I say so out loud and you weigh it knowing the interest exists. Plenty of consultations end with me recommending another platform, another vendor, or no spend at all this quarter. Those clients tell other people — and that, over 11+ years, has been worth more than any project the honest advice ever cost me.
Preparing for your consultation: a 15-minute checklist
Write one sentence about success in business terms, not website terms — "wholesale buyers in NCR should find and enquire" beats "I need a modern site". Collect three to five reference links you like, each with one line about what you liked. Note your internal budget range — not to reveal, but so recommendations can be shaped to reality. List what exists: domain, hosting, logo, photos, written content, current passwords and who holds them. Bring numbers if any exist: monthly visitors, enquiries, ad spend. And bring the uncomfortable questions — the quote you suspect is inflated, the developer you suspect is stalling, the fear you'll be locked in. The uncomfortable questions are where consultations earn their keep, and nothing you share leaves the call.
What consultation is not
It is not a disguised sales pitch — the deliverables are complete without hiring me for anything else. It is not a magic shortcut — honest advice frequently includes the words "this takes months" or "that budget can't do that yet", said early so cheaper decisions can follow. It is not only for big projects — a twenty-thousand-rupee website deserves an informed buyer as much as a two-lakh application, and the free meeting fits both. And it is not a lecture — you talk first, at length; recommendations built before listening are the exact disease this service exists to cure.
One more story: the second opinion that kept a vendor
A retailer suspected their agency was overbilling and arrived ready for war. The milestone review found the opposite: fair pricing, competent work, terrible communication — the agency simply never explained anything, and silence had been read as deceit. One three-way call later, a reporting rhythm existed, the relationship survived, and the project finished well. Consultation isn't always about catching villains; sometimes it is about restoring enough clarity that good work can be recognised as good. Either way, you deserve to know which situation you are in — and that is precisely the hour on offer below.