Your 7-day trial

A new workspace starts on a seven-day free trial on Collection, with every feature switched on. No card, nobody to talk to first. Here is exactly how access works, which plan to choose when the week is up, and a plan for the week itself.

What's included

Everything. The trial runs on Collection, the plan with every tool in it, so you see what each plan includes before you choose: the ranking engine with its order-value target, attribution, nudges, webhooks, imports, taking payments into your own Stripe account, the public API, the assistant (with 1,000 credits for the week) and messaging are all live from the moment you name your workspace. The only limits are the ones that apply to every account — the event ingest rate cap and the 20 MB import ceiling.

Three things keep you on track without anyone having to call: a setup checklist on the dashboard that ticks itself off as Stitchwork sees each step happen (the tag, your catalogue, a year of orders, your team, the reply-to address), a strip across the top of every page saying how many days are left, and a handful of short emails to the workspace owner — never more than one a day.

Choosing a plan

When you are ready — on day two or day seven — the workspace owner chooses a plan in Settings → Workspace → Your plan. Two are published, priced by the size of the business:

The optimisation tools are order-value ranking, the attribution report, and nudges measured against a held-back control group. Website browsing on each client record is on every plan, and so are the tools themselves; what they read — browsing, and where each sale came from — is collected from the day the tag goes on. On every plan: £15 / month for each MCP seat (one per person or agent granted an AI connection — see AI agents), more assistant credits at a penny each that never expire (see credits), and yearly billing at ten months' price. The quote payment fee is on top of Stripe's own card fees and is handed back if you refund the payment — see Stitchwork's fee. Texts and WhatsApp go through your own Twilio account at Twilio's price; we add nothing.

People, AI connections and showrooms are counted for you as they change. On a monthly plan, ones added mid-month are billed from the next renewal; on a yearly plan they are charged for the rest of the year straight away. Independent covers one showroom — adding a second asks you to move to Collection. An owner can change plan at any time from the same card: a bigger plan is charged for the rest of the period now, a smaller one is credited against the next invoice.

Every new shop starts with the launch package, £1,250 once: we load your catalogue, put the tag on your website, bring in your order history, and connect Twilio and WhatsApp. On a monthly plan it is on your first invoice; on a yearly plan it is included. You can also book it from the same page before your trial ends, and it is then not charged again when you subscribe.

Payment is by card through Stripe. Invoices, card changes and cancellation are on Stripe's billing portal, one click from the same card in Settings. Everything you set up in the trial carries straight on — there is nothing to migrate.

How access is enforced

Your workspace carries a single access state, and only a deliberate change to your account moves it — no billing event and no background process writes it. A trial workspace is kept open by any one of three things: the trial date, a live self-serve subscription, or a live AWS Marketplace entitlement.

Access is evaluated on every request. There is no scheduled job, so an expired trial locks the workspace the next time somebody loads a page — not overnight, and not a day late.

What a locked workspace looks like

Getting unlocked or extended

Subscribe — the owner can do it from the locked page itself, and the workspace opens the moment the payment goes through. Or ask us: if the week ran out while a CSV export was stuck in someone else's queue, that is not a reason to lose the work you have already done — trials get extended, and a workspace can be switched back on at any point. It takes effect immediately: no re-import, no re-install, no waiting for a billing cycle. Everything is where you left it and your team can carry on mid-quote.

A week that works

You do not need all seven days, but this is the order that avoids dead ends — each day makes the next one produce visible results.

1. Day 1 — Catalogue in

   Sign up, name the workspace, import products. Get web_url and category populated even if nothing else is. Add a channel for each physical location.

   Done when Products shows your real SKUs with prices and categories.

2. Day 2 — History in

   Import a year or two of orders. This is the single highest-leverage thing in the week: it fills the bestseller signal, seeds the customer list, and makes every ranking output immediately credible instead of empty.

   Done when Rankings shows a non-zero bestseller input count and the unmatched-SKU list is short.

3. Day 3 — Tag live

   Generate keys, install the script tag, wire view_product and add_to_cart into your own site code. Confirm the consent mode matches your legal position.

   Done when Rankings shows product views accumulating and a customer timeline has web rows on it.

4. Day 4 — Tune and show

   Open Rankings, look at the top 50 with their per-signal contributions, and move the sliders until the order matches what a good salesperson would say. Then drop <sw-recs> somewhere real, or re-rank one category page.

   Done when A visitor on your site sees an order you would defend.

5. Day 5 — Sell something

   Invite one salesperson, scope them to a channel, and have them build a real quote for a real customer. Send it. Watch it arrive on the customer's phone.

   Done when A quote has reached sent and the customer has opened it.

6. Day 6 — Close the loop

   Print QR codes for the store, add the join endpoint to your site, and — if you take card payments on quotes — connect Stripe. Subscribe a webhook to whatever system needs to know about orders.

   Done when A store visit appears on a customer timeline next to their browsing.

7. Day 7 — Decide

   You now have real data, a real quote and a real personalised surface. Choose the plan in Settings, talk to us about terms for a larger group, or don't — nothing you built goes anywhere.

Things you can safely put off

Trials get derailed by optional work. None of these block anything else, so leave them until you have decided to stay:

• Stripe Connect. Quotes work fine without it — the customer accepts, and you invoice however you already do.
• The "buy now" URL template. Only needed if you want the public quote page to hand off to your own checkout.
• Per-channel staff rosters. The owner and workspace admins can already reach everything.
• Attribution settings. The 90-day window, 7-day half-life and time-decay default are sensible; touches are captured either way, and the report lets you switch models without saving anything.
• Category balance and price-target ranking. Both are off by default and both are refinements, not fixes.

Clearing out test data

You will make a mess in week one — that is what a trial is for. Deletes are real, not cosmetic, so the mess actually goes:

All four are owner-only. See Roles and permissions.