The questions thatcome up most

The contract runs for an indefinite period, with a one-month notice period. We don't use twelve-month commitments or penalties for ending early.

That's a deliberate choice: the engagement should continue because it delivers results, not because you can't get out of it. If the numbers aren't moving the right way after a quarter, a conversation about ending things is more honest than keeping a client through a contract clause.

We start engagements on the first working day of the month or mid-month. The invoice is issued at the end of the month, for the period already delivered - not in advance.

Example: with a contract starting March 15, you get an invoice on March 31 for fifteen days, and on April 30 for a full month.

A monthly summary of the work: what got done, how the metrics agreed at the start have moved, and what that means for the next period.

The report tracks the same set of numbers for the whole engagement. We don't swap out a metric when it stops looking good - that's one of the four principles our work rests on.

We pair the report with a call at a convenient time, so there's a chance to ask questions. A document on its own is often dead weight if nobody talks it through.

Everything stays with you. The domain, hosting, code, and ad and analytics accounts are registered under your details, not ours.

We hand over full access and documentation. We don't build in dependency on the agency - if you decide to work with someone else, you're not starting from zero.

It depends on scope, not a price list off the shelf. For paid campaigns it comes down to media budget and service level, for builds it's project complexity, for SEO it's how competitive the industry is.

We give a quote after a conversation where we establish what needs to change. If it turns out a given service doesn't make sense for your margin and scale, we'll say so instead of preparing a proposal anyway.

Before that conversation we can give a rough range based on similar projects - without seeing your account and sales data, any more precise number would just be a guess.

Yes, and it happens regularly. Most often when the budget won't let a campaign gather the data it needs for optimization, when the margin can't absorb the cost of acquiring a customer, or when the problem sits in the product or service, not in marketing.

Launching a campaign in that situation just burns through a quarter of budget and ends with "advertising doesn't work." We'd rather have that conversation before signing than after.

Websites: WordPress, when content needs to be edited daily by several people, and Astro or headless setups, when speed and resilience to attacks are the priority.

Stores: Shoper and Shopify as subscription-based platforms, and WooCommerce, when the store is an extension of an existing WordPress site.

The choice follows how you sell and who will run the store day to day - not whatever happens to be trendy. We're partners with both Shoper and Shopify, so we have no stake in steering you toward one over the other.

Typically six to twelve weeks: two weeks for the workshop and architecture, three for template design, four for build-out and content, and the rest for testing and launch.

The biggest source of delay isn't coding - it's content and approvals on the client side. A project that arrives with finished copy and photos can close in well under half that time.

An online store usually runs eight to fourteen weeks, since it adds data migration and integrations for payments, shipping, and accounting.

Yes, and we design starting from mobile, not the other way around. The mobile version isn't a trimmed-down desktop version - it's usually the primary version, since that's where most of the traffic comes from.

We also check mobile-connection performance and Core Web Vitals scores before launch, not after. A site that takes four seconds to load on a phone loses part of its visitors before they see anything.

Launching a site takes two things: hosting, meaning space on a server, and a domain, meaning an address.

We can work with what you already have, or help with registration and selection. We're partners with SeoHost and cyber_Folks, so we have access to terms you won't find on the public price list.

Either way, the domain and hosting are registered under your details. You own them.

Yes. Once the work is done, you get access to the admin panel along with brief training on how to use it.

For WordPress sites and Shoper, Shopify, or WooCommerce stores, editing content doesn't require technical knowledge. For headless setups, the scope of self-service editing is decided during the project, since it depends on the content system chosen.

Yes. Most often that means integrations between systems: a store with an ERP, a store with accounting software, automatic document issuing, rolling out language versions, or setting up online payments.

We start by mapping the process, not by picking a tool. It usually turns out that some of the steps can simply be removed before we automate anything.

Those answer two different problems. Google Ads brings traffic from day one and loses it just as fast once you turn off the budget. SEO builds up over months, but it doesn't disappear the moment you stop paying for clicks.

With a short horizon and a need to sell right now, paid advertising wins. For building a position that lasts years, SEO does. Most often the sensible answer is both, in a mix that depends on how much time you have and what the competition looks like.

Paid advertising also tends to be the fastest way to check which search terms actually sell - before you invest in ranking for them.

The first changes in visibility usually show after two to three months, with a stable result after six. For a new domain or a very competitive industry, that timeline stretches out.

Technical fixes and cleaning up content you already have tend to work faster - that can show results within a few weeks. Building domain authority and ranking for competitive terms is a matter of quarters.

If someone promises the top spot in a month, it's worth asking for which term. Usually one nobody searches for.

Yes, if you write about what your customers actually search for, and publish regularly. A blog lets you rank for the questions people ask before buying, which the offer pages themselves won't cover.

No, if it would only exist "because you're supposed to have one" and get filled with mass-produced text. Google is increasingly good at spotting that kind of content and demoting it - and it factors into how the whole domain gets assessed.

A good test: does the article answer the question better than what's already in the search results. If not, it's not worth publishing.

Yes, and it doesn't have to mean switching providers. Some companies start with an audit or consulting - a second opinion on whether the current activity makes sense and whether the reporting shows what it should.

If the numbers show the current setup is working well, we'll say so directly. An audit is a closed, standalone project and doesn't commit you to anything further.

When visibility or traffic drops without an obvious cause, after a major site rebuild, and before launching a campaign - so paid traffic isn't sent to a site that can't handle it.

An audit also makes sense as a first step before publishing a new site. Fixes made before launch cost far less than the same changes made after.

Not only in a crisis. An audit makes sense after expanding a store, after changing the template or product range - to check whether the changes actually worked.

It also pays off at the start of an e-commerce business, whether the store was built in-house or by an outside contractor. Catching a flaw in the purchase flow in the first month is far cheaper than catching it after a year of selling.

Consulting covers the topics you choose and ends with a conversation. An audit is a full review and ends with a written report and a list of actions ranked by impact.

Consulting works well when you know what to ask. An audit works well when you know something's wrong but not what.

For owners of websites, stores, and apps, but also for designers and developers who want an outside view on the solution they're working on.

It works at any stage: before launching a first site, when expanding one, and for a site that has been live for years and has stopped bringing in inquiries.

We start with a conversation about goals and audiences, then the information architecture takes shape, which you approve before the first pixel of design work.

Next we design the key templates, not every page individually. We collect feedback in two rounds - an open-ended list of revisions can drag a project out for months without improving the result.

In the format agreed at the start - most often as an online preview for comments, plus source files once a stage closes.

We hand over source files always, including at the end of the engagement. It's the same principle as with accounts and code: the client owns what gets made.

Most often GetResponse, which we're a partner of - we help with account setup, sender domain authentication, and the first automation flows.

We also work with the tools built into Shoper and Shopify, and other platforms if you're already using them. Switching tools has a cost, and we only recommend it when the current one is genuinely holding things back.