S.01
The context architecture
What you sell, who supplies it, how you sound and when to escalate, turned into files Claude reads at the start of every session.
For Shopify operators
The Clarion sets up Claude as the operating system of your Shopify store, and builds the automations it runs on.
Claude Code and Cowork, connected to your store, your inbox and your books in accounts you own, then context-engineered around your products, your policies and your tone.
01 / The problem
Claude is impressive for a week. Then the re-explaining starts.
If you run a store, the list is familiar: the same handful of customer questions arriving over and over, most of them asking where an order is; an apps bill that climbs exactly when the store is busiest; a month-end spreadsheet nobody quite trusts; whole days that go on patching holes instead of running the business.
Claude can take real weight out of that, and every owner who tries it hits the same wall. Its built-in memory is a set of notes it writes for itself, a rough sketch of what you sell. Your returns policy, your supplier terms and the way you sound never make it in, so the drafts read like a stranger wrote them and the same details get re-explained chat after chat.
That wall is not a lack of discipline. Claude simply has nowhere to keep what you tell it. The fix is a folder of plain files it reads at the start of every session, so it already knows your products, your margins and your tone, and follows your rules.
01 / Monday
You ask for one reply.
Draft a reply to this customer. She wants to return a table lamp.
Happy to. First, tell me about your shop: what you sell, your policies, how you like to sound.
the next ten minutes
We sell homeware on Shopify. Returns within 30 days if unused, customer pays return postage unless the item is faulty, refunds in 3 to 5 working days. Tone is warm and brief, first names...
02 / Tuesday
A new chat. Half a memory.
new chat
Draft a reply to this customer. He's asking where his order is.
Happy to. You sell homeware, if I remember right. What are your delivery times, and how do I look up his order in the store?
the gist survives, the details start again03 / The fix
Your business, written down once.
your-business/
CLAUDE.md
business-context.md
working-preferences.md
decision-log.md
plain files, yours to open and change
wired to be read at the start of every session
context loaded
04 / Every morning after
Starts where the last one finished.
your-business/
CLAUDE.md
business-context.md
working-preferences.md
decision-log.md
Draft a reply to this customer. Lamp arrived damaged, she wants a refund.
Drafted, in your tone, against your returns policy. The lamp arrived damaged, so the return is postage-free and the refund lands in 3 to 5 working days. It's in your drafts. Ready for your approval.
05 / After the chat
What it learns today, it knows tomorrow.
your-business/
CLAUDE.md
business-context.md
working-preferences.md
decision-log.md
+ damaged items: offer a replacement first
the files move with the business
One update from today worth keeping. I've drafted it for the decision log:
+ damaged items: offer a replacement first
Approve
Approved
02 / The method
Context engineering, before any automation.
Most AI setups fail for the same reason: the system does not know the business. It files the electrician's invoice under the wrong supplier and answers a refund question with someone else's returns policy. Every Clarion engagement makes the same three moves, in the same order, because each one is what makes the next one work.
Context. The work starts with the context architecture, written before a single workflow goes live: your suppliers and how they bill, your FAQs and policies, your tone, your escalation rules, the exceptions you would never think to mention until they go wrong. That architecture powers every prompt, every classification and every draft.
Connections. Context tells Claude how your business works. Connectors let it act: your email, calendar, files and the tools the business already runs on, reached from inside Claude. Connectors are only as good as the context behind them, so the context comes first; the connecting itself starts in the first session.
Automations. Once Claude knows the business and can reach its tools, the repetitive work is built into n8n automations: scoped and priced before any work starts, built in accounts you own, with an approval gate on every action that matters.
We call the discipline context engineering. In plain English: Claude that knows your business and does not forget it. It sits under every Clarion setup and build, and it is why the work sounds like you.
The context work is also the part you can start yourself: the free Context Kit, sent by email, is where every paid setup starts.
03 / Claude Business Setup
Claude, set up around how your business actually works.
A Clarion setup is the method above applied to your store: Claude Code and Cowork installed, connected and context-engineered around how it actually runs, day to day. Out of the box, Claude is a brilliant stranger to your store. Set up properly, it works like someone who has been in the store for years.
S.02
The connectors
A connector is a switch Anthropic or the tool's maker has already built, switched on inside your own Claude account. No code is written for it and nothing is hosted by The Clarion: the connection lives in an account you own and can revoke.
A connector on its own hands your tools to that brilliant stranger. Wired after the context work, it gives the same reach to a system that knows the business, which is why the context comes first.
The ones we wire most often for a store: Shopify, through its official connector, built by Shopify; Gmail, Google Calendar and Google Drive, built by Google; Xero, Slack, Notion and Stripe, each through its maker's official connector; and Microsoft 365, built by Anthropic, for businesses on that side. All nine sit in Anthropic's connector directory, vetted before they are listed, and they ship with Claude itself: nothing extra to buy, switched on inside the paid Claude plan a Clarion setup runs on.
Some are deliberately limited, and it helps to know where. Xero is read-only: a window into the P&L, the cash position and who owes what, never a hand that posts entries. Microsoft 365 now writes as well as reads, but only after your Microsoft administrator consents to the new permissions and switches them on; Teams stays read-only. And Gmail drafts rather than sends: every email Claude writes sits in your drafts until you send it. The systems further down this page go deeper than these connectors: they run on API-level integrations built in your own accounts, which is how a dashboard can read Xero on a schedule rather than only when you ask in chat.
S.03
What the Working Setup hands over
deliverables, not promises
- Claude Code and Cowork installed and configured, with connectors wired to your Shopify store and your Google Workspace or Microsoft 365
- A context architecture built for the store: a workspace constitution, canonical context files covering products and policies, suppliers, tone and escalation rules, a decision log, a memory layer and scheduled maintenance so none of it rots
- Two or three Claude workflows running in the store's actual operations, not demo data
- An operating cadence document and a recorded handover call
- 30 days of asynchronous questions afterwards
Setup Session
€250
60 minutes, screen-share. Claude installed and connected, your first context file built, and a cadence plan for the rest. The right start if you want the method proven before you buy the Working Setup.
Working Setup
€850
The full deliverable list above. A scoping call, a working session over screen-share, then we finish the setup offline and deliver it working. This is the flagship.
Advisory hour
€200 per hour
Already set up, or just want an hour? Anything Claude Code or Cowork: your setup, a stuck workflow, a second opinion, a decision you want an experienced pair of hands on.
04 / The free kit
The starter kit, free.
The Clarion Context Kit is the skeleton our paid setups are built on, and the same files our own store runs on: a workspace constitution template, canonical context file templates, a decision log and the maintenance schedule that keeps Claude current instead of slowly going stale.
It is free because a folder of templates should not cost money. The work is in filling it with your store, and the kit shows you exactly how, whether you do that yourself or book us to do it with you.
05 / The systems
Four systems that already run our own store.
Each one is a fixed-scope install at a published price, built in accounts you own. The two lighter systems come first; the two deeper ones follow. Every install starts with a short, free call, and slots are limited to two a month: the next open slots are in September, and the Content System installs from October.
01 Slots from September
The Profit Dashboard
€400 install optional care plan €200 per month
One answer for what the store actually earned. n8n pulls your Shopify sales and costs, your Google and Meta spend and your Xero actuals on a schedule, and Claude renders them as one overall live profit view, refunds and payment fees netted off. The numbers hold because the dashboard reads the same bank-fed Xero actuals your accounts are built on, not a copy keyed in by hand.
Before the install you complete a short profit-definition worksheet: which costs sit where, how refunds are treated. The dashboard then answers your definition of profit rather than a generic one, and one install call puts it live. It reads your accounts and writes to none of them.
Book the install call
02 Slots from September
The Invoice Filing System
€600 install optional care plan €200 per month
Every invoice and receipt, filed without you. Once a week Claude scans the store's email inbox, finds the invoices and receipts, and downloads each one to your Google Drive, filed by supplier, date and amount into entity, month and supplier folders. Paper receipts are photographed into the same folder and filed the same way. No renaming, no sorting: an organised archive you own, kept current while you get on with the store. Documents land in your Drive and nowhere else, and nothing posts to your books.
Book the install call
03 Slots from September
The Inbox System
€1,900 install optional care plan €200 per month
A morning triage of the store inbox, built in your own n8n and your Google Workspace or Microsoft 365. Automated noise is filed before you sit down, the real customers are surfaced, and each one has a reply written in the store's voice, waiting in your drafts. Where-is-my-order questions are answered from live Shopify order data, sensitive emails are flagged for you rather than answered, and long-running conversations keep their history in per-thread context files. Nothing sends without you.
Book the install call
04 Installs from October
The Content System
€1,900 install optional care plan €200 per month
The store's search opportunities, gathered and ranked on a schedule: keywords, competitor gaps, pages that are fading. The system works out where the next article earns most, then drafts it in the store's voice through your own Claude account: article, title, meta description, FAQs, internal links. Drafts push to the store's blog unpublished; you read, edit and publish, and nothing goes live untouched.
It is sold on the voice work, the search strategy and the approval loop, not on word count.
Book the install callThe care plan
€200 per month per system
Monitoring, error fixes and small tweaks, capped at ninety minutes of delivery time a month. It is attached by default at booking because the services a system connects to will change underneath it, and it is why the system still works in month nine. Decline it if you like, and cancel any time; without it, fixes are booked as Advisory hours.
Bespoke
Anything else: the Automation Audit
€500 fixed · one week
Not every workflow fits a named system. The audit maps where your hours actually go and comes back with a priced roadmap: the automations worth building, a fixed price for each (bespoke builds from €1,500, in your own n8n account), and the ones to skip because the payback is not there. The deliverable is the scope itself, and there is no obligation to build any of it with us. Start with a note about what is eating the week.
The first store these systems ran was our own.
4
systems on this page running live in our own store
60
minutes in the Setup Session, your first context file included
30
days for an install to go live in your store, or everything you have paid comes back
0
emails sent, articles published or files attached without your approval
06 / Who you work with
Someone whose job is to keep up with this field.
I am Daniel, an e-commerce operator. The work is context engineering, n8n automation and agentic AI: systems that hold a business's knowledge, do its repetitive work and stay inside their approval gates. I build and run them daily in my own Shopify store; the systems on this page are the ones it runs on, not demos.
This field moves weekly. Part of what you pay for is that I keep up: what changed, and whether a working store should care. And you deal directly with the person doing the work.
07 / The process
How the work runs.
STEP 01
Start
The €250 Setup Session, booked and paid in one step. Sixty minutes later Claude is installed, connected and carrying the store's first context file. Systems start with a short, free install call from their cards; anything bespoke starts with the audit.
STEP 02
Build
The context architecture is written first, then the system is built in accounts you own. Installs are scheduled into published windows and are live in your store within 30 days of install start, or everything you have paid comes back.
STEP 03
Approve
You review everything the system produces and approve each draft, article and attachment. The approval gate stays after handover; it is part of the design.
STEP 04
Support
Every Working Setup includes 30 days of asynchronous questions. Every system carries a €200 per month care plan for monitoring, error fixes and small tweaks, declinable and cancellable any time. New work is always quoted separately at a fixed price, so support never creeps.
The guarantee
You own everything.
The Claude account, the n8n account, the API keys and the custom app in your store are all yours. Any Google Cloud project behind the systems sits inside your own Workspace. We build and operate as an invited user, and if you ever decide to leave, you keep the workflows, the context files and the credentials. We remove our access and that is that.
And the working guarantee: no email is sent, no article is published and no file is attached without your approval. That is how the systems are built. There is no setting to find.
One more, for the installs: if a system is not live in your store within 30 days of install start, everything you have paid is returned in full.
08 / Questions
The practical questions.
What does each system need?
The Profit Dashboard needs Xero: the numbers are only as true as the bank feed behind them. The Invoice Filing System needs Google Drive and a Google Workspace or Microsoft 365 mailbox for the weekly scan. The Inbox System needs Google Workspace or Microsoft 365. The Content System needs a Shopify custom app, a two-minute consent in your own admin. If your stack does not fit, say so on the contact form and we will tell you plainly whether it is worth forcing.
What does it cost to run?
Beyond the install: your n8n account at roughly €24 a month, your Claude plan, and the API usage the systems generate. Every vendor bills you directly. Nothing passes through us and nothing is marked up.
Who owns what?
You own everything: the Claude account, the n8n account, the API keys, the custom app in your store, and every context file and workflow we build. We work as an invited user in your accounts.
What happens if we stop working together?
You keep it all. Cancel the care plan whenever you like; we remove our access and the systems keep running where they always ran, in your accounts.
Will it do things without me?
No. The systems are built draft-first: replies wait in your drafts, articles push unpublished, the dashboard reads and never writes. The approval gate is the design, and it never comes off.
What about Sidekick?
Use it; it is useful and it is included with your store. Sidekick works inside Shopify, on what Shopify can see. These systems join the store to the things around it, the inbox, the ad accounts and the books, and they answer to you. The two are not in competition.
We are not on Shopify. Is that a no?
No. This page speaks to Shopify because that is where our own store runs and where the systems are proven, but the Automation Audit takes a good problem from any owner-run business, and everything after it follows from what the audit finds.
09 / Start
Start with a session, not a sales call.
€250 books a 60-minute working session: Claude installed and connected, your first context file built, and a plan for the rest. You pick the slot and pay at booking.
10 / Contact
Not sure which of these fits, or want to talk it through first?
Send a note about what you are trying to fix.