Your website spent three weeks with this customer. Your showroom has never met them.
Stitchwork carries what happens on your site into the conversation on your floor, and carries it back out again. Your associate opens the quote already knowing what this person considered, ruled out, and came back to twice. One customer, one record, both sides of the door.
For showroom retail where the order runs to four figures and the decision takes weeks · 1–15 locations
Your customer decided to spend £4,000 weeks ago. They still haven't decided where.
Something lands in their feed. A product they didn't know they wanted. They watch the video twice and screenshot it.
They search the model. They read every spec. They sit on the configurator for nineteen minutes and leave without buying.
They drive ninety minutes to see one in person. An associate spends the first ten minutes asking what they've been looking at, then an hour on the rest. They leave saying "I need to think."
Back on the configurator. A different finish, a different size. They add it to basket. They close the tab.
They walk in somewhere new and start the conversation over from the beginning, with someone who doesn't know any of this.
The same conversation, five times over — and no thread between them.
That was one customer, one decision, five touchpoints — and nobody in your business knows it was the same person.
Your channels don't share a memory. Your customer assumes they do.
Your website knows more about that person than anyone who works for you. Every page, every configuration, every return visit. And it cannot tell a single member of your staff any of it. Meanwhile your associate — the one who can actually close a £4,000 decision — spends the first ten minutes of every conversation rebuilding by hand what the website already had.
The same wall runs the other way, and it shows up in the numbers. The floor stops sending customers to the site, because when the sale closes online the store's figure goes down. Marketing can't prove a campaign drove footfall, because the till doesn't know who walked in. Everyone is optimising their half.
The old playbook assumed channels were separate businesses. Your customer never agreed to that. They've been moving between web and store for a decade. Your data still isn't.
This is the gap Stitchwork closes. Not by replacing anything — by giving every surface one record of the same customer, so the next conversation starts where the last one ended instead of at the beginning. The honest ledger of who contributed comes free, underneath. But the customer never sees the ledger. They just feel known.
One customer, known on both sides of the door.
The same engine that ranks your catalogue for a visitor online is the one your associate is looking at when that visitor walks in. Two surfaces, one record underneath.
An associate who already knows the conversation.
Your team opens the quote builder, picks the customer standing in front of them, and sees what that person has been considering — with recommendations shaped by the same engine that runs the site. Build the quote line by line, send it, watch them open it on their phone.
- Their browsing, cart adds and searches, inline
- Configurable lines — sizes, finishes, discounts, tax in or out
- Sent as a link and an email; opens on their phone
- Take the deposit in the room, or hand off to your own checkout
A site that learns who's looking.
One script tag. Stitchwork watches what visitors browse, add and search, and ranks your catalogue against a live score you tune yourself — bestseller, popular, carted, newness, featured, on offer — with a personal overlay for each customer.
- Recommendations panel you drop in anywhere
- Category grids re-ordered per visitor
- Interest signals your marketing stack can read, to switch a banner or a CTA
- Anonymous browsing that joins their record the moment they identify
One customer record. One thread that doesn't break.
Every view, every add, every store visit, every quote, every order — attached to the same person, whether they identify by email, by a handoff from your own checkout, or in a couple of seconds in the room. Delete the quote, delete the customer, close the store: the thread survives all three, because the alternative is a customer you have to meet twice.
Tell it the number you want to sell towards. Then watch it learn.
Your catalogue carries a score built from signals you weight yourself. One of those signals is a target average order value — so the number your business actually runs on becomes a dial, not a hope.
Set the target and the products sitting near it rise across every surface at once: the panel on your website, your category grids, and the list in your associate's hand when someone walks in. It's a curve, not a cutoff — a £1,900 piece against an £1,800 target scores near the top, a £200 one near the bottom, and you decide how wide that curve runs.
- Balance the categories so your best-selling shelf can't quietly take the whole panel — or name the two that should split it evenly and let the rest queue up behind.
- Feature a piece and it lifts anyway, even for a fully personalised visitor. A merchandising decision should beat the algorithm, so it does.
- Nothing is a black box. The Rankings page breaks each product's score down signal by signal, tells you how much data is actually feeding each one, and lists every SKU on an order that doesn't match your catalogue — so when something ranks oddly you can see why instead of guessing.
It won't break your website.
You have a scar from a third-party script. Everyone who runs a storefront does. So here is exactly what ours does and doesn't do, before you have to ask your developer.
One script, and it can't throw into your page.
It runs your own navigation code before it runs any of ours, guards every browser call that can fail, and swallows its own network errors rather than surfacing them. The recommendations component removes itself rather than render a broken state where a shopper could read it. There is a test that loads the whole tag into a deliberately hostile browser to keep it that way, and it runs on every commit.
Your consent banner, not a second one.
It detects Cookiebot, Shopify Customer Privacy and IAB TCF v2.2 — OneTrust, Usercentrics, Didomi, Iubenda and the rest — and follows whatever it finds. Global Privacy Control overrides all of it, including a platform that says yes. Your customer sees one banner, and it's the one you already chose.
We never store your customer's IP address.
Only a salted hash of it, so a visit can be recognised without the address ever being written down. The cookies are first-party, on your domain, and none of them are readable across origins — the tag sends what it needs in the body of the request.
Your data is isolated at the database, not just in the query.
Every table is scoped to your workspace and enforced by Postgres row-level security, so a query that forgot its filter still can't return another retailer's customers. And it works the other way too: if your account ever lapses, your customers keep paying quotes and your site keeps tracking. A billing state never interrupts a sale.
Four things you probably can't answer today.
Who walked in already knowing us?
You'll see which customers browsed you online before they came through the door, what they were looking at, and how long they took to decide. It stops being a hunch your best associate has.
Where did the conversation close?
A session opened in one showroom can close on a phone at midnight, three weeks later. The thread holds — and the associate who opened it is named on the record when it does.
What's this customer's whole story?
Browsing, campaign arrivals, store visits, every quote and every order — one stream, newest first, with their searches in their own words. Not a tally. The actual sequence, because six visits in four minutes and six over five weeks are different people.
Why did they come back?
Because the second conversation started where the first one ended. Your associate already knows what they considered, what they ruled out, and what they were quoted.
The ones your dashboard doesn't answer.
What the associate sees the moment the customer walks in.
The whole thing is written down. Including the parts we'd otherwise explain on a call.
The script tag. The ranking weights and how to tune them. How an anonymous browser becomes a named customer. Every endpoint in the v1 API, the webhook payloads, the failure modes that actually happen. Written for the person who has to make it work on a Tuesday afternoon — not for the person signing the contract. Send it to whoever would have to install it and see what they say.
Read the documentationNo form, no email gate. Seventeen pages of plain HTML you can read on the train.
We'll show you the parts that work and tell you which ones aren't built yet. You get the same answer on the call that you got on this page — we'd rather lose the deal than the second meeting.
Your best associate can hold maybe forty relationships in their head.
Stitchwork holds every customer you have, on every channel, and hands the right one back at the moment they walk in. Give us thirty minutes and one real customer journey from your own catalogue. We'll walk it back across your website, your floor and your marketing, and show you exactly where the thread breaks today. You'll leave with the map whether or not you ever use us.
By hand, not by checkout. There's no plan catalogue and no public price, because there's nothing here you'd buy without talking to someone first.
Seven days free with every feature switched on. No card, no reduced tier, no feature gates. Long enough to get your catalogue in and watch one associate use it.
Terms agreed per client — flat, per seat, or both — in your currency, on your interval. Set once, written down, and not moved without a conversation.