Website, CRM & marketing package for online shops

The whole front end of the business: a storefront built for search and AI answer engines, hosting and domain, branding and product graphics, a CRM configured around purchase behaviour rather than generic sales stages, the automations that carry an order from basket to dispatch to review to reorder, an AI chatbot for delivery and returns questions, email and SMS marketing, and Google and Meta accounts set up with a clean product feed behind them. It is scoped per shop, so anything already working we leave alone.

Price on application, and that is not evasion. A shop with forty products and one delivery option is a different build to one with four thousand variants, trade pricing and a warehouse system to connect. Some brands need a replatform, some just need the store they have wired into a CRM and an email programme. We scope it, price it, and you see the number before anything starts. Publishing a headline figure we would not honour helps nobody.

It depends on your category and how much of the stack you need. What we can point to is Fast Track Leasing: around five enquiries a day from search, with £0 spent on ads to get them, off the back of 400+ pages answering what customers search for. That is a different market to retail and we would not promise you the same numbers. Product and category content compounds over months. If you have stock to move sooner, shopping ads run alongside while it builds.

Usually yes, because they hold different things. Your store platform holds transactions: what was bought, when, for how much. A CRM holds the relationship around them — the pre-sale question that never became an order, the customer who returned twice, the trade account due a call, the buyer who bought once eighteen months ago. It also holds the people who never reached checkout at all. We feed order data into the CRM rather than replacing the platform you already sell on.

A short sequence that triggers when someone reaches checkout and leaves. Timing matters far more than discounting: the first message goes out within the hour and normally does nothing more than show the basket and answer the thing that stopped them, which is usually delivery cost or the returns policy. A discount, if it appears at all, comes later, because training people to abandon on purpose is expensive. It needs correct consent and correct tracking to work, and we set both up rather than bolting on an app and hoping.

Yes, and that is the point of doing it properly. Shopping and catalogue ads run from a product feed, not from your pages. When titles, identifiers, prices or stock levels drift away from the site, items get disapproved and you end up paying for clicks on things you cannot ship. We build the feed from the same source as the storefront, so a price change or a sold-out variant flows through, and disapprovals surface as an alert rather than as a quiet drop in revenue you notice a fortnight later.

Usually. Most storefront, payment, courier and inventory systems expose an API or a webhook, and where they do we wire straight in. Some older warehouse and EPOS systems are genuinely closed. Where that is the case we say so up front and build around it, normally by making the CRM the front end and pushing a clean handover into the other system. That assessment happens during scoping, not after you have paid.

We do, end to end. The reason this is one package rather than five suppliers is that the handovers are where these projects fail: the developer blames the marketer, the email agency blames the developer, and you are project-managing all of them between stock takes. HDC covers development, marketing, CRM, integration and process design in one team, so there is one number to ring when something needs changing.