Catalogue
Product structure, categories and the information buyers need.
What are you working on?
A sentence is enough — we will work out the rest together.
A shop built around your products and the people buying them. We plan the catalogue, design the shopping experience and build the store, with payment and business connections scoped together.
The core of this engagement. We agree the exact scope in your project plan.
Product structure, categories and the information buyers need.
Product pages, navigation, basket and checkout design.
The storefront and the platform setup behind it.
Agreed payment, shipping and system connections, checked before launch.
Every engagement runs through the same moves, and you always know which one we are on.
We start where the money is decided and work outwards from it.
Products, variants, stock and images modelled so that adding the next hundred is not a project.
Payment methods, shipping rules and a quiet launch before the real one.
Work this has already carried. All of it is live, and all of it is still ours to keep running.
Nothing here was chosen because it is fashionable. Each one is on the list for something it does that the alternative does not.
Vue and Nuxt by default, React and Next.js where your own team already lives. Server-rendered either way — a page that needs JavaScript to show its first sentence is a page a search engine reads last.
07 toolsThe content model is designed before the CMS is chosen, so your editors get fields that match how they actually think rather than a page builder to fight.
05 toolsEvery deploy is reversible and every error reaches us before it reaches you. That is the whole of what a retainer buys, and it runs whether or not anything is being built that month.
05 toolsUsing something we have not listed? Say so on the call — half of what we know arrived because a client was already on it.
There is no handover document, because there is no handover. That is where most of the cost usually hides.
The numbers are agreed before the build and checked on every deploy, not measured once on launch day.
Hosting, certificates and dependency patches are ours. You are never chasing a developer who has left.
Still deciding? Half an hour on a call is usually enough to know either way.
“Every layout has its own page now — you can send it to a buyer and know at once which flat you are talking about.”
The questions that arrive by email anyway. If yours is not here, ask it on the call.
Whichever suits the catalogue and the way you work. We recommend one after the first call rather than before it.
Yes, and it is usually what separates a shop from a spreadsheet. We agree which system holds the true stock figure.
Swish, Klarna and card are the normal set in Sweden. Others are added when your buyers ask for them.
Yes. Products, customers and order history come across, and the old links keep working.
Start with a 30-minute call. The scope, the fee and the dates go into a project plan before any work begins.
Tell us what you are building. If it is a fit you will have an offer — and if not, we’ll tell you upfront.