Contact
Write if you want to know more about the work, or about something you are making.
Globus is a Shopify studio in Copenhagen. We take on new stores, apps, migrations, and stores that have stalled. Tell us briefly what you sell and where it stalls — we reply with the kind of job, not an hourly figure on work we have not seen. The budget fields (10–20, 20–50, 50–100, and 100+ thousand DKK) are ranges, not a quote.
What we need before we answer
Tell us what you sell and where it stalls. A store that is slow on the product page is a different job from a store that still lives on WooCommerce, and different again from an internal tool the team is missing in Shopify admin. The more concrete the first note is, the less time we spend guessing. Name, email, project type, budget, and timeline are enough for us to reply. The subject and the message are where you say what should be different when the work is done.
Say which platform the store is on today, whether the catalog already lives in a PIM or a spreadsheet, and whether orders have to continue into a warehouse, an ERP, or just Shopify. Also say if you sell in one market or several, and if checkout has rules that are not standard: gift cards, B2B prices, subscriptions, shipping that depends on postal code. Those details decide whether the next step is a theme, an app, or a move. They do not decide a price in the first email, and we do not invent percentages for how much faster the store will get.
We reply from Copenhagen, usually within one working day, at hello@globus-dev.com or on whatever you send in the form. The first reply is a clarification, not a finished proposal full of phases you did not ask for. If the job is small, we say so. If it needs someone on your side to settle the catalog, shipping, and who approves the page, we say that too. You should not book a long engagement to learn that the product page can be fixed in the theme.
When we agree on the direction, we write down what will be built, the milestones, and what is not included. You see that scope before we write code. During the build there is one place status lives, and one person on your side who can approve the homepage and the product page. After launch you can come back with the next concrete job. That can be a single fix or a longer run. It is scoped the same way.
Globus is a Shopify studio. We do not take on random websites beside that, and we will not promise that a new app fixes a problem that sits in the content or in the shipping rules. The phone is +45 51 98 23 45 if you would rather start there. The company number is CVR 41972386. The office is in Copenhagen, and we work with brands in Denmark and abroad.
If you already have a quote from someone else, you can send it, but also write what it does not cover. A quote that only says setup has often left out the life of the theme after launch, the apps the store cannot run without, and the integration the warehouse needs on day one. We do not read it in order to undercut it line by line. We read it to see whether the job is described. If the catalog is missing, that is not a developer question yet. If the shipping rules are missing, we can still build the theme, but we cannot go live until someone chooses them.
You do not need a requirements document. A page with what you sell, a few example products, and one sentence about what is wrong is a better start than twenty pages describing a store you have not settled. We ask what is missing in the first reply. If the project has to wait because three people all think they approve the homepage, we say that before the calendar fills with meetings that do not move anything.
Say what has already been tried. A theme you have edited, an app you turned off, a move that stalled at the redirects. That saves the first week. You do not have to attach a whole catalog to get a reply. A few products and the name of the system the warehouse uses are enough for us to say whether the next step is a conversation or a decision you need to make internally first.