Frequently Asked Questions
Cross-cutting questions about working with us. Service, location and industry pages carry their own questions.
Working together
We build websites, online stores and custom web applications, and run the SEO, digital marketing and AI automation work around them. Engagements are scoped from a business outcome — more qualified enquiries, a store that converts better, a process that stops consuming staff hours — rather than from a channel or technology preference.
With a conversation about what you need and what currently happens, then a written scope with specific deliverables, a timeline and an agreed measure of success. We do not give a firm quote before understanding the situation, because numbers produced that way change later.
Yes. A small site with proper service pages plus a complete Google Business Profile is often the highest-return work available to a small business, and it does not need a large budget. We would rather scope something that fits than sell something that does not.
Yes — the United States, United Kingdom, Canada, the UAE, Australia and New Zealand alongside Indian clients. Most project work runs remotely with scheduled review calls, which is how the majority of engagements run regardless of location.
Where a project genuinely benefits from in-person sessions in the Tricity region, that can be arranged by agreement. Most work does not require it, and remote working with proper documentation usually produces better records of what was decided.
Decisions, content and a named person who can approve things. Content readiness is the most common cause of delay on web projects — more than development capacity — so agreeing who owns it and by when is worth doing at the start.
Pricing and contracts
It depends mainly on the number of unique templates, whether content is written for you, and what integrations are needed — not on page count. When comparing quotes, ask each supplier how many templates are included and whether hosting, staging and post-launch fixes are inside or outside the price.
Both, depending on the work. Defined builds suit a fixed scope and price. Ongoing marketing, maintenance and open-ended development suit a retainer or hourly arrangement, because fixed-pricing uncertain work either pads the estimate or produces disputes.
Yes, and they should be planned rather than discovered. Domain, hosting and SSL as a minimum. For a CMS site, maintenance and updates. For e-commerce, platform subscription, payment gateway percentages and app subscriptions. For AI features, per-request running costs that scale with usage.
You do. Domain, hosting, code repository, analytics and advertising accounts should be registered in your name with access granted to us. We recommend agreeing this in writing with any supplier before work begins — recovering accounts held by a former supplier is difficult and sometimes impossible.
You keep everything. Code, content, accounts and documentation are yours throughout, not handed over at the end. We would rather be kept because the work is good than because leaving is difficult.
SEO and marketing
No, and nobody honestly can. Search results depend on factors outside any agency's control, including what competitors do and how algorithms change. What we commit to is defined work, accurate measurement and reporting that includes what did not work. Treat any ranking guarantee as a reason to look elsewhere.
Technical fixes can show within weeks. Content and authority gains usually take three to six months to become clear, and competitive terms longer. The timeline depends most on your starting point — a site with indexing problems can improve quickly once those are fixed.
They do different jobs. Ads buy visibility immediately and stop when you stop paying. SEO builds slowly and keeps working. If you need enquiries this quarter, start with ads. If you can invest for next year, SEO costs less per enquiry over time. Most businesses run both.
Only where we have genuinely distinct, useful information about that place. Pages that swap the city name and change nothing else are doorway pages and carry risk rather than benefit. This website itself runs an automated quality gate that refuses to index pages failing that test.
No to both. Purchased reviews breach platform policy and are increasingly detected and removed, sometimes along with the listing. Bulk link purchasing carries risk that is not worth taking on a site a business depends on.
What was done, what changed and what happens next — with impressions and clicks from Search Console, rankings for agreed target terms, and enquiries including calls and WhatsApp where tracking allows. A report that never mentions something that did not work is not a report of reality.
AI work
Almost certainly not. Training a model requires substantial data, expertise and budget. Nearly all practical business value today comes from applying existing models to your own documents and processes through their APIs.
It will, sometimes. Every workflow we design assumes that and includes review, confidence handling or escalation wherever correctness matters. Any supplier who tells you otherwise is overselling.
It depends on the provider, the plan and the configuration — business and API terms commonly differ from consumer product terms regarding whether inputs may be used for training. We configure retention deliberately and recommend reading the specific terms rather than assuming.
Usually per request or per token, so cost scales with usage. We model the projected monthly figure at expected volume during scoping rather than after the pilot, because pilots are inexpensive and production is not.
No. Nobody controls what these systems cite. What we can do is publish content that is precise, clearly attributed, well structured and genuinely original, which is what they appear to favour — and say plainly that the decision is theirs.
Technical and support
It depends on who maintains it and what it has to do. WordPress for content-led sites with in-house editors. Shopify for retail where launch speed matters. WooCommerce where control and commission matter more. Laravel or Node where business logic does not fit a general platform. Static HTML where content rarely changes.
Yes, starting with a short audit so the estimate is based on what is actually there. Sites built with heavy page builders or without version control take more care, and the audit is what makes an honest quote possible.
Yes — staged updates tested before going live, verified off-site backups, uptime and enquiry-delivery monitoring, security scanning and periodic performance review. It can also be handled by your team with documentation from us.
Yes. The process is a forensic copy first, then cleaning files and database, then identifying and closing the entry point, rotating credentials and requesting a search engine review where the site was flagged. Cleaning without closing the entry point leads to reinfection within days.
Most often oversized images, a heavy theme or page builder, too many scripts, or slow server response. Two or three specific changes usually account for most of the available improvement, which is why we measure first rather than installing a caching plugin and hoping.
Question not answered?
Ask it directly — we answer questions before there is a project, and we say when we are not the right fit.