Before we helped a single business grow online, we ran a Shopify store.
Not as a hobby. Not as a portfolio piece. As an actual direct-to-consumer brand selling physical products, taking real orders, handling real returns, answering real customer questions, posting on social, writing blog content, trying to get found on Google, watching the analytics. We did all of it ourselves. Then we fixed all of it ourselves.
The store is called Lumovex. It still runs, on the same stack we now build for clients as AI Ready websites. The point of this post is what we learnt from it that an AI consultant will never learn, and why we think dogfooding is the only honest entry point to selling web growth.
You cannot grow what you have not run
Six months in, we had a client ask us to "sort out customer support" for a Shopify brand much like ours.
The instinct, if you are a consultant, is to start with a workshop. Discovery. Map the customer journey. Define the support categories. Workshop the response taxonomy. Build a chatbot. Ship it. Move on.
The instinct, if you have actually been the person at 11pm answering "where is my order" messages, is different. You know the request is not "automate support". The request is "stop me from ever again typing the same shipping update twice, and stop visitors leaving the site because nobody answered." Those are different problems.
Most "support bots" fail because they are designed by people who have never been on the receiving end of the problem. They build a chatbot that parrots the FAQ page back to customers. The customers were already not reading the FAQ page. The bot does not help.
The thing that helps is recognising that most inbound messages are about three things: order status, returns, and "is this right for me". Build an assistant that handles those perfectly, captures the customer's details, and hands everything else to a human cleanly. That is not a chatbot. That is a conversion layer with hard guardrails.
We only know that because we sat through the inbox first.
What our own store taught us about priorities
The first thing we built for ourselves was the wrong thing.
We built a competitor price monitor. It scraped competitor pricing weekly and sent us a report. It worked. We were proud of it. We used it twice and then stopped reading the reports.
Why? Because competitor pricing was not actually our biggest pain. The pain was that nobody could find us. We were posting on social maybe twice a week, writing zero blog content, and ranking for nothing. The best product page in the world earns nothing if no one ever reaches it.
So we fixed being found. Daily content across three platforms. Then a proper search and content engine: blog posts written to answer what customers actually search, the site tuned so Google and AI search could understand it. Three months later, twenty-eight posts published, ranking for thirty-plus terms, traffic compounding. Then we tightened the site itself so more of that traffic turned into orders.
The lesson is not "we are clever". The lesson is "you cannot prioritise correctly until you have skin in the game". A consultant doing discovery would have asked us "what hurts most" and we would have said "competitor pricing" because it was the most technically interesting problem. We were wrong. We only learnt we were wrong because we shipped the wrong thing first and watched ourselves not use it.
This is now one of the most valuable parts of any new engagement. Our free AI Growth Audit asks the question we wish someone had forced on us: where are you actually losing customers - in being found, or in converting the ones who find you? The honest answer is almost never the interesting one.
A consultant doing discovery would have asked "what hurts most." You will answer with the most technically interesting problem. You will be wrong.
What it taught us about pricing
When we started doing this for clients, we had no idea what to charge.
The honest first instinct was to bill hours. We did some quick maths on how long a build took, multiplied by a rate, and started there.
Three problems showed up immediately.
Hourly billing rewards slow. If we got faster, and we got much faster the more we built, we would earn less. That is the wrong incentive for a business that wants to stay sharp.
Hourly billing makes scope arguments inevitable. "Why did this take 60 hours and not 40?" Nobody enjoys that conversation. Including us.
Hourly pricing penalises customers who chose us for being fast. A partner who gets you live in two weeks looks "more expensive" than one who drags it out over eight, even though the first is wildly better value.
The fix was simple, honest pricing for an outcome. A one-off price for the website, the foundation everything builds on. Then simple monthly plans for the layers that grow you: the assistant, the voice agent, the Growth Partner. From £999 for the site, from £199 a month for an assistant, from £499 a month to have us growing the whole thing. Same scope, same number, however long it takes us. If we get faster, good. If we get slower, we eat it. That puts us on the same side of the table as the client every time.
We could not have worked that out from a spreadsheet. We had to feel the friction of the wrong model on real engagements before we knew what to fix.
Why this matters for you
If you are about to engage anyone for an AI or web build, ask them one question that almost no agency will pass.
"What did you build and grow for yourself before you started doing it for clients?"
If the answer is "we built a SaaS product that pivoted six times" or "we ran a consulting practice for seven years" or "we have a strong AI methodology", you are talking to a strategy firm dressed up in a hoody.
If the answer is "we ran a real business, hit the same problem you have - the same empty pipeline, the same invisible website - and fixed it with the same stack we are about to build you", you are talking to operators.
We are not the only operators. Pick one. Just make sure you do.