Process

How a project unfolds

First we clarify the goal, scope and content. Only then does it make sense to deal with design, development and deadlines.

Every step has a concrete decision, so the project does not drift forward on feelings alone.

Discovery

A shared understanding of goals, audience and project scope.

We go through goals, audience, competitors and existing materials. For an existing site we map out what works and what is hurting conversions. The outcome is a shared understanding of scope and priorities.

  • Goals and measurable signals (enquiries, orders, contact)
  • State of the current site or input materials
  • Scope estimate as a basis for the proposal

If content is missing, we agree who will deliver it and by when — an empty website on launch day helps no one.

Design

Approved structure and visual direction — before expensive coding starts.

Site structure, wireframes or a prototype, and the visual style. Approved before development to avoid costly changes in code and to make sure the result matches expectations.

  • Information architecture and content order
  • Prototype or wireframe to discuss
  • Visual direction aligned with your brand

For larger teams a single “owner” of feedback helps — otherwise the budget and schedule get derailed by conflicting requests.

Development

A working site on a staging URL — open for review at any time.

Implementation of the responsive interface, content and integrations. Focus on performance, sensible accessibility and clean, maintainable code. Continuous previews on the staging environment.

  • Staging environment instead of “you will see it on production”
  • Check of key pages on mobile and desktop
  • Technical groundwork for SEO and analytics

We test on common phones and viewport sizes — not only on the developer’s laptop.

Launch

Production launch, analytics, a short training and a clear handover.

Deployment to production, verification of analytics and SEO basics, a short content training and handover of operations documentation. After launch we stay in touch as agreed — the site keeps living together with your business.

  • HTTPS, forms and basic analytics
  • Handover of credentials and a short training
  • Agreement on maintenance or further work

The first weeks in production usually surface small issues — fixing them quickly is normal, as long as you have someone to do it.

Start

We can start with a short e-mail or a call.

Briefly describe what you are dealing with, send a link to your current site and tell us when it should be ready. I will come back with further questions and the next step.