Clear answers for better decisions.

A phone intro call usually takes about 20 to 30 minutes. If the conversation includes a code review or a deeper technical discussion, it may take closer to 1 hour depending on what you want to cover.

For an intro call, a short description of your project or situation is enough. If you want us to review code, tickets or technical notes, you can share those beforehand so we can prepare more effectively.

We do not send a quote unsolicited, but we are happy to prepare one if you want to continue. First we want to understand the context well and make sure the scope is clear.

We only move forward when there is a good match. If we think we are not the right partner, we say that honestly and without obligation.

Yes. The initial conversation is free and without obligation. We want to understand your needs properly before any collaboration starts.

We usually reply within one business day and aim to arrange an intro call within 1 to 2 working days. In busier periods it may take a little longer, but we do our best to help quickly.

New websites, redesigns, online stores, technical clean-up, SEO foundations and ongoing care. Smaller improvements can also be scoped when they solve a clear business problem.

Yes. We can audit, redesign, migrate, optimise or take over an existing website. We first review the current setup and clarify what is worth keeping.

No. We can work from existing material, help define the content structure and identify what is missing. Full copywriting, translation and content production are scoped separately.

Content direction and structure are included. Full copywriting can be coordinated separately when needed.

Yes. Language structure, URLs, navigation, metadata and content management are planned from the start so every version remains consistent and maintainable.

The page templates can be included. The legal wording must be supplied or reviewed by a qualified adviser.

Accessibility is considered in structure, interaction, colour, semantics and keyboard behaviour from the beginning.

Every project is quoted after a short initial conversation. You receive a fixed proposal with the scope, deliverables, schedule and exclusions before work begins.

Timing depends on scope, content readiness, feedback and integrations. The agreed schedule and the responsibilities on both sides are included in the proposal.

A focused landing page can often be delivered in four to six weeks. Larger websites depend on content readiness, feedback and integrations.

Yes. The plan can change when the website, request volume or operational importance changes.

You receive a clear explanation and separate scope before additional project work begins.

Yes, when self-editing is part of the scope. We choose the editing setup around the content you actually need to manage and provide a clear handover.

For marketing websites, we usually work with Nuxt or Astro. For e-commerce, Shopify or PrestaShop may be a good fit. The final choice depends on content, integrations, editing needs and long-term maintenance.

The decision follows catalogue complexity, team workflow, integrations, budget and the level of technical control required.

Yes. Migration is scoped after reviewing product data, variants, media, URLs and the source platform.

Core payment and shipping configuration is included. Complex carrier, tax or market rules are scoped separately.

No. We can coordinate content requirements, but photography and full copywriting are separate services.

An audit or focused research phase is usually the best start because it separates assumptions from evidence.

Timing depends on the starting point, competition, crawl patterns and the work required. Early technical changes may be visible sooner than content growth.

Yes, implementation can be included or scoped after the audit when priorities and dependencies are clear.

Yes. The platform, access and technical condition are reviewed before implementation begins.

Not always. Recurring work is useful when content, competition or commercial priorities continue to change.

Measurement follows the objective and can include visibility, qualified landing-page traffic, engagement, leads and technical health.

You can choose a clean handover or ongoing care. Support can include maintenance, monitoring, technical updates and a prioritised improvement backlog.

You do. Domains, hosting and third-party accounts should remain in your name. Ownership of the code, credentials and documentation is made explicit in the proposal and handover.

Maintenance, content replacement and contained improvements can fit a plan. Structural work is scoped separately.

Response depends on the selected plan, current priority and the information required to begin safely.

Often yes, after an initial technical review confirms that the stack and condition are supportable.

Yes. Stores have payment, catalogue and checkout dependencies that require a separate review and scope.

Yes. Languages, markets, currencies and editorial ownership are defined before implementation.

Yes, when the stack is viable. The goal is to integrate with the team, not force a preferred framework.

Yes, when the communication model, attribution and client relationship are agreed in advance.

Yes. Direct client communication can be included when roles and decision ownership are clear.

Capacity, priorities, response expectations and unused time are defined before the retainer begins.

Availability depends on current commitments and the clarity of access, scope and schedule.

Frontend-facing integrations can be included. Broader backend systems require an agreed specialist or separate scope.