Question 1

How is pricing decided?

Accepted Answer

After we understand your requirement — pages, features, and ongoing needs. We send a custom quote. No fixed packages on the website because every business is different.

Question 2

What's included in a typical monthly plan?

Accepted Answer

Usually hosting, SSL, security updates, backups, and a set number of content changes. Exact scope is in your quote.

Question 3

How many revisions are included?

Accepted Answer

Design and content revisions during the build are included within the agreed scope. After launch, content changes are handled as part of your monthly plan — exact limits are in your quote.

Question 4

Do I own my domain and website?

Accepted Answer

Yes. Your domain is registered in your name. We manage it for you as part of the service.

Question 5

How fast are changes after launch?

Accepted Answer

Most text and image updates within 24–48 hours on business days.

Question 6

Can I cancel?

Accepted Answer

Yes, with notice as agreed in your contract. We'll help you export or transfer if needed.

Question 7

What if I need something bigger later?

Accepted Answer

New features or pages are scoped and quoted separately. Many clients grow with us over time.

Question 8

Who do you work with?

Accepted Answer

Businesses of any size worldwide — startups, SMBs, and enterprises. Clinics, coaching institutes, restaurants, SaaS teams, agencies, and local service providers who want a professional web presence without managing tech themselves.

Question 9

Can I contact you on WhatsApp?

Accepted Answer

Yes. WhatsApp is often the fastest way to reach us for quick questions or sending reference links. For formal quotes, the contact form works well too.

Question 10

What languages do you support?

Accepted Answer

We communicate in English and Hindi. Website content can be in the language your customers use — we'll discuss that during scoping.

Question 11

Do I need to understand the technical side?

Accepted Answer

No. You describe the goal in plain language — we handle design, build, hosting, integrations, and updates. We explain decisions when it matters, without jargon.

Question 12

Do you integrate Razorpay or other payment gateways?

Accepted Answer

Yes. We connect Razorpay, Stripe, Cashfree, PayU, PhonePe, and UPI flows — whichever fits your business. Setup and testing are included in the quoted scope.

Question 13

Can you build a chatbot from our PDFs or documents?

Accepted Answer

Yes. We can wire AI assistants that answer from your PDFs, FAQs, or website content — on your site or WhatsApp. Scope and pricing depend on how complex the answers and hand-offs need to be.

Question 14

Do you take over an existing website, or only build new ones?

Accepted Answer

Both. We rebuild slow or outdated sites on a modern stack, or start fresh when that is cleaner. A short WhatsApp chat tells us which path fits before you commit.

Question 15

Will a rebuild hurt my Google rankings?

Accepted Answer

We plan redirects, keep important URLs where we can, and make sure pages stay fast and crawlable. We check search basics before and after launch so visibility does not get a surprise drop.

Question 16

Can you hand the site off to my in-house team later?

Accepted Answer

Yes. We document what we built and can transfer hosting and access. Many owners keep us on for updates; others take ownership when they are ready.

Question 17

What does a typical web project look like?

Accepted Answer

Discovery on WhatsApp or a call, a clear written quote, then design and build in short loops with check-ins. Most business sites launch in days to a few weeks, then we host and maintain.

Question 18

Static vs a full web app — which do you recommend?

Accepted Answer

Static (with interactive bits where needed) for marketing, brochure, and SEO-critical pages. A fuller app when you need dashboards, accounts, or heavy logged-in workflows. We'll recommend the right fit in the first conversation.

Question 19

Can marketing update content themselves?

Accepted Answer

Yes when we wire a CMS or simple admin. Many owners also message us on WhatsApp and we handle updates as part of the plan — whichever fits your team.

Question 20

How do you avoid a long redesign cycle later?

Accepted Answer

We build with reusable components and clear design tokens so the next refresh is mostly content and theme changes — not a full rewrite.

Question 21

What CMS options do you support for static sites?

Accepted Answer

Popular headless options and simpler content models when you don't need a big editorial suite. We'll pick based on who edits content and how often.

Question 22

How do you keep dynamic pages fast with personalization?

Accepted Answer

We cache the shared shell where we can, render personalized bits on the server, and stream data so the page isn't blank while waiting. The goal is a usable first paint on real mobile networks.

Question 23

What's your approach to realtime updates?

Accepted Answer

Native WebSockets with reconnect for most live apps. Server-sent events when data is one-way. Managed realtime services when you want less infrastructure. We only add realtime when the product needs it.

Question 24

Do you handle auth and role-based access?

Accepted Answer

Yes — login, sessions, and roles for admins, staff, or customers. Multi-tenant setups and audit-friendly defaults when your product needs them.

Question 25

Can the app work offline or as a PWA?

Accepted Answer

When it matters, we can add PWA install, caching, and basic offline buffering. It's scoped into the quote only if you need it — not bolted on by default.

Question 26

Shopify, headless, or fully custom — how do you choose?

Accepted Answer

It depends on catalogue size, customization needs, and who runs day-to-day ops. We lay out a simple recommendation in the first week — Shopify when ops speed wins, headless or custom when you need tighter UX or data ownership.

Question 27

Do you handle shipping and order ops integrations?

Accepted Answer

Yes. We connect regional and global shipping tools — Shiprocket, Delhivery, BlueDart, Shopify shipping, FedEx integrations, and similar — or bridge to your existing spreadsheet/ops flow when that's enough to start.

Question 28

Can marketing launch campaign pages without a developer?

Accepted Answer

When we wire a CMS or simple admin, yes — banners, landing pages, and seasonal offers without waiting on a sprint. Many owners also message us on WhatsApp for updates as part of the plan.

Question 29

Which CMS do you recommend?

Accepted Answer

It depends on who edits content and how complex your models are. Sanity or similar for editorial speed, Payload/Strapi when you want more control or self-hosting, and simpler models when a big suite is overkill. We give a clear recommendation in week one.

Question 30

Can we self-host the CMS?

Accepted Answer

Yes for stacks that support it — for example Payload or Strapi on your cloud. Hosted SaaS options work too when you want less ops. We'll match the choice to your team and budget.

Question 31

How do you handle migration from a legacy CMS?

Accepted Answer

Content audit, schema mapping, redirects, and a careful cutover with a rollback plan. We test migration before go-live so you're not rewriting every page by hand.

Question 32

Is live preview actually live?

Accepted Answer

We wire draft preview against the real front-end layout — not a fake staging copy that drifts. Editors see what customers will see before publishing.

Question 33

When is bespoke software the right call?

Accepted Answer

When SaaS templates force the wrong process, when tool sprawl costs more than a focused build, or when the workflow itself is your advantage. We lay out a simple buy-vs-build recommendation early — before you commit.

Question 34

Do you replace a legacy CRM or internal tool?

Accepted Answer

Yes. We map the domain, plan data migration, often run old and new in parallel, then cut over with a rollback plan so the business doesn't pause.

Question 35

Can we own the codebase?

Accepted Answer

Yes. Code, hosting access, and documentation are yours. We manage day to day when you want us to — but ownership stays with you.

Question 36

What about ongoing support after launch?

Accepted Answer

You can keep us on a retainer for updates and care, or take a full handoff with runbooks and training. Many clients start with us nearby, then decide.

Question 37

Will an AI agent replace my team?

Accepted Answer

No — we design agents to take repetitive work off your plate (FAQs, triage, drafts, routine updates) while your team handles edge cases and approvals. You stay in control of what the agent can do.

Question 38

How do you keep agents from making things up or leaking data?

Accepted Answer

We ground answers in your approved docs and tools, limit what the agent can access, require human handoff when confidence is low, and keep sensitive actions behind confirmations. Scope is written down before we go live.

Question 39

What's a realistic timeline for a first production agent?

Accepted Answer

A focused single-workflow agent (for example WhatsApp FAQ with handoff, or a triage bot) often reaches a pilot in a few weeks after scope is clear. Multi-step or multi-agent systems take longer — we quote after a short discovery chat.

Question 40

Can the agent take real actions, or only draft replies?

Accepted Answer

Both are possible. Many projects start with grounded answers and drafts, then we add scoped actions — update a CRM, create a ticket, send a confirmation — with approval gates where you want them.

Question 41

Will a personal AI assistant replace my EA or office manager?

Accepted Answer

No. We design it to take the repetitive long-tail — triage, first drafts, scheduling ping-pong — while your team handles judgement calls and relationships. It augments; it does not replace.

Question 42

How do you handle privacy for inbox and calendar access?

Accepted Answer

Access is scoped to what the assistant needs, sensitive actions stay behind confirmations, and we avoid keeping more data than the workflow requires. We can discuss region, retention, and NDA before anything connects.

Question 43

What if the assistant drafts something wrong?

Accepted Answer

Risky actions use confirmation gates by default. We pilot against your real threads, tune from mistakes, and keep a simple log so you can see what happened and roll back the rule set.

Question 44

Can it send email and book meetings on its own?

Accepted Answer

Yes when you choose to. Most owners start with draft-only or confirm-before-send, then widen autonomy once the pilot feels solid. The rules are written into the scope — not left to chance.

Question 45

How do enterprise agents stay accurate on company policy?

Accepted Answer

We ground answers in your approved wiki, PDFs, and SOPs, require citations when useful, and escalate when confidence is low. Stale docs get flagged in the pilot so you know what to update.

Question 46

Can you limit what the agent can see by team or role?

Accepted Answer

Yes. We scope retrieval and tools by team or role when you need that, and keep a clear written policy for what must always go to a human.

Question 47

Will this replace our IT or ops helpdesk?

Accepted Answer

No. We design for the long tail of repetitive questions and ticket helpers, with your team on edge cases and approvals. It reduces busywork; it does not replace ownership.

Question 48

What systems can the agent connect to?

Accepted Answer

Common stacks include docs/wiki, ticketing, CRM, and internal databases with APIs. We confirm each connection during discovery and only wire what you approve.

Question 49

Which channels can a chat and voice agent cover?

Accepted Answer

Typically website chat, WhatsApp, and voice when scoped. We can discuss SMS or email during discovery. Multi-channel setups share context and tuning where it helps QA.

Question 50

How do you keep voice agents from feeling slow or robotic?

Accepted Answer

We set latency budgets, test scripts on real devices, and pilot before launch. If voice isn't ready to feel good, we start with chat/WhatsApp and add voice when quality clears the bar.

Question 51

How do you match our brand voice?

Accepted Answer

We tune from your existing copy, support transcripts, and tone rules, then grade sample replies before go-live. You approve the voice — the bot doesn't invent one.

Question 52

How does human handoff work when the bot is stuck?

Accepted Answer

We define escalation rules up front. When the agent is unsure or the request is sensitive, your team gets the full thread and reason — not a dead-end loop.

Question 53

How long can a workflow agent keep running?

Accepted Answer

Hours to days (and longer when scoped) using durable background jobs that resume after restarts. We design for waits, approvals, and retries — not a single chat turn.

Question 54

Do workflow agents always need human approval?

Accepted Answer

Risky actions — CRM writes, emails, refunds, ticket closes — use approval gates by default. You can widen autonomy after a solid pilot; the rules are written into the scope.

Question 55

What happens if a step fails halfway through?

Accepted Answer

We use idempotent steps and retries where safe, surface failed/waiting status clearly, and keep a log so ops can resume or intervene without guessing.

Question 56

Can these agents write to our CRM or send email?

Accepted Answer

Yes when you approve those tools. Access is scoped, actions are typed, and sensitive steps can require confirmation before they run.

Question 57

When is a multi-agent system the right choice?

Accepted Answer

When the work has clear specialisation boundaries — plan, research, act, review — or longer paths where one mega-prompt keeps failing. For short FAQ-style flows, a single well-scoped agent is usually better.

Question 58

How do you keep shared memory from leaking data?

Accepted Answer

Memory is scoped to the run and the roles that need it, with limits written into the design. We avoid dumping entire corpora into every agent step.

Question 59

Do you always include a reviewer agent?

Accepted Answer

For customer-facing or high-risk output, yes — agent review and/or human confirmation. Internal drafts can start lighter; we widen gates only when the pilot earns it.

Question 60

Is multi-agent slower or more expensive than one agent?

Accepted Answer

Often slightly more cost and latency per run — traded for better quality and clearer ownership of steps. We only recommend multi-agent when that trade-off is worth it.

Question 61

Hybrid vs vector-only retrieval — which do you use?

Accepted Answer

Hybrid by default — keyword plus vector search with reranking. Vector-only often fails on names, codes, and IDs; hybrid holds up better on factual recall.

Question 62

How fast do answers update when we edit a document?

Accepted Answer

We wire re-index hooks so updates land as soon as the pipeline runs — usually minutes after an edit for connected sources. Exact timing depends on how your docs are hosted.

Question 63

Can you keep knowledge scoped per team or client?

Accepted Answer

Yes. Retrieval can be limited by team, client, or collection so one corpus doesn't leak into another — with a simple audit trail of what was searched.

Question 64

What if the agent isn't sure of the answer?

Accepted Answer

Low-confidence or ungrounded questions escalate to a human with the full context. We don't invent policy when the docs don't support it.

Questions, answered.

Didn't find your answer?