01Questions
Frequently asked questions
The questions that come up most often, answered properly. Several of these argue against hiring us, which is the point: you should be able to tell from this page whether we are the right choice.
02Topic
Working together
How an enquiry turns into a project, and what you can expect from us.
How do I start, and what happens after I send an enquiry?
Send the contact form a description of what you sell, the platform you are on and what is going wrong. That is enough for us to tell you whether this is something we can help with.
The enquiry reaches the two of us directly. There is no sales team and no discovery call funnel. If it is a fit, the next step is a written scope before any code is written.
Who will actually be doing the work?
Nazir Abbas and Javed Iqbal, the two co-founders. Nazir leads development, Javed leads search. On larger builds we bring in designers and additional developers, but the people who scope the work are the people responsible for delivering it.
Do you work with businesses outside the United Kingdom?
The focus is UK retailers, and the search work in particular assumes a UK market. We have worked on projects in the United States and the UAE. If you are outside the UK, say so in your enquiry and we will tell you honestly whether we are the right choice.
What do you need from me to get started?
Access to the current site and its hosting, domain and DNS control, and whatever records exist of the current URLs, including Search Console and analytics exports.
We also need the commercial rules as they actually work, including the exceptions, and one person who can approve scope and sign off the URL map. Projects stall on unanswered commercial questions far more often than on engineering.
03Topic
Builds and platforms
Choosing a platform, and when a bespoke build is justified.
Should I use Shopify, WooCommerce or something bespoke?
It depends on how far your catalogue and checkout rules sit from the default model. A straightforward catalogue is usually best served by a well configured template platform, and we will tell you that rather than sell you a build you do not need.
Bespoke earns its cost when the catalogue does not fit the template model, when the checkout needs behaviour the platform resists, or when an integration with a stock or ERP system is the real work.
Do you build in Next.js and React?
Yes. Next.js with React and TypeScript is the default for a bespoke storefront, because server rendering means product pages arrive as HTML rather than waiting for JavaScript to run.
We also work in WordPress and WooCommerce, and with headless commerce engines where several channels share one catalogue. The stack is chosen per project rather than applied by habit.
Can you work on my existing site rather than rebuilding it?
Often, and it is frequently the better option. If the shop works but is slow, fragile or awkward to change, repair is usually cheaper and lower risk than a rebuild.
A rebuild is justified when the underlying model is wrong for how you now sell. No amount of repair fixes a catalogue structure that cannot express your products.
How long does a build take?
That depends entirely on the catalogue model and the integrations, and anyone who quotes a duration before seeing those is guessing. We give a timeline as part of the written scope, once we know what the shop has to do.
04Topic
Search and migrations
The questions that come up whenever a site changes address.
Will I lose my Google rankings if I rebuild or replatform?
You can, and it is the most common way an established shop loses revenue overnight. It is also largely avoidable.
Every URL that changes address needs a redirect to a genuine equivalent, agreed in writing before launch. Pages with no equivalent should return a proper not found or gone response rather than being redirected to the homepage, which is treated as a soft error and helps nobody.
Expect some movement for a few weeks after a migration. A sustained fall in indexed pages is a different matter and usually shows up in the logs before it shows up in a ranking report.
Do you do SEO as well as development, or do I need a separate agency?
Both are in the same small team, which is the point. Most ecommerce search problems are development decisions with a search consequence, and they get passed back and forth between a developer and an agency until nobody owns them.
A faceted navigation that generates a hundred thousand crawlable URLs is one example. So is a replatform that quietly drops product pages.
Should my filtered category pages be indexed?
Some of them. A filtered page deserves to be indexable when people genuinely search for that combination and the page answers it better than the unfiltered category.
Sort order, page size and most multi-facet combinations should not be. Without a cap on how many facets can combine, a site with a few hundred products can generate hundreds of thousands of crawlable URLs.
05Topic
Ownership, cost and support
The commercial questions worth asking any developer, including us.
Who owns the code, the domain and the hosting?
You do, and this matters more than it sounds. Your domain, DNS, hosting and analytics should all be registered in your business name, with us given access.
If a developer holds your domain in their own name, you cannot leave and you cannot recover the site if they disappear. Granting access is easy and reversible. Transferring ownership is neither.
What does an ecommerce website cost?
We do not publish prices, because a number without a catalogue model and an integration list is meaningless and usually wrong in both directions.
What we can say is where the cost actually goes: the catalogue model, the checkout rules and the integrations. The visual design is rarely the expensive part. If you have a budget in mind, say so in your enquiry and we will tell you plainly whether it is realistic.
What happens after launch?
Dependency and platform updates, uptime and error monitoring, tested backups, and a documented route for incidents. Core Web Vitals and crawl coverage get reviewed so a quiet technical regression does not become a trading problem.
Ask any developer when their backup was last actually restored, rather than whether backups exist. The answer is informative.
What if something breaks at the weekend?
There should be a named person, a monitoring alert that reaches them and a restore procedure that has been tested rather than assumed. The specifics depend on the support arrangement agreed for your project, and they are written down rather than implied.
Still not answered?
If your question is not here, it is probably specific to your catalogue or your platform. Describe it and we will answer directly.