Morten A. Giraffe

About / Morten A. Giraffe

A sharper website starts with a sharper read.

I work directly with clients to make the important parts of a website clearer: what is offered, why it matters, what proves it, and what a visitor should do next.

01Working Model

Fewer handoffs. Better reads.

The work stays cleaner when strategy, copy, design, implementation, and launch QA are not treated as separate conversations.

  1. 01

    Read the business before the layout.

    The first pass is about the offer, audience, proof, objections, and decision the visitor has to make. Layout follows that read.

  2. 02

    Build the page around a real next step.

    A good-looking site still fails if the call, form, booking path, or follow-up message is vague. The conversion path is part of the design.

  3. 03

    Keep proof visible and honest.

    Screenshots, case studies, routes, trust details, and live workflows do the convincing. Unsupported metrics and borrowed authority stay out.

  4. 04

    Ship with the boring details handled.

    Responsive QA, metadata, icons, forms, analytics boundaries, accessibility checks, and handoff notes are treated as launch work, not cleanup.

02Design Principles

Principles, not page furniture.

Each principle ties a design choice to public work, so the profile stays grounded in proof you can inspect.

Read the 18-rule field guide
  • D&L Garage DoorsStart with the decision the visitor has to make.

    A page is not finished because it looks expensive. It is finished when a specific visitor understands the offer, trusts the path, and knows what to do next.

    Proof example

    D&L Garage Doors uses service, location, booking, callback, and call paths for visitors arriving with urgent local intent.

    Read case study
  • GoalDNAMake complexity legible before adding polish.

    Most website problems get worse when every point gets equal weight. Stronger design starts by deciding what each page is responsible for.

    Proof example

    GoalDNA frames a multi-role club product around the week before matchday, then keeps beta and rollout status visible.

    Read case study
  • Chewb & SPAKOiUse proof people can inspect.

    Screenshots, routes, forms, policy pages, and live surfaces carry more weight than vague authority language. If a claim cannot be inspected or sourced, it should not carry the sale.

    Proof example

    Chewb & SPAKOi pairs a distinctive studio voice with service boundaries and a visible trust layer.

    Read case study
  • VARSELOStay honest about maturity.

    Launch work should create momentum without pretending a product is further along than it is. Clear status language protects trust.

    Proof example

    VARSELO uses a disciplined pre-launch surface and early-interest path instead of a fake storefront.

    Read case study
03Work You Can Inspect

Proof belongs in public.

Service business clarity

D&L Garage Doors

Urgent service visitors need fewer choices, clearer proof, and contact actions that stay within reach.

Inspect the work

Product story clarity

GoalDNA

A product story gets easier to trust when the site explains the operating problem before asking for adoption.

Inspect the work

Brand voice with boundaries

Chewb & SPAKOi

A memorable voice works harder when it is backed by plain service scope, trust information, and a clear next step.

Inspect the work
04Profile FAQ

Before you ask.

  • Is Morten a solo designer or a studio?

    Morten works as an independent designer and direct project partner. The public site intentionally avoids implying a large agency team, account layer, or anonymous production handoff.

  • What kind of work is the strongest fit?

    The best fit is a founder, professional, creator, service business, or small team with a real offer and a website that needs to make the visitor path clearer.

  • Does the work include copy direction?

    Yes. Copy is treated as part of the product experience. The goal is to turn the offer, audience, proof, and next step into page language that can actually guide a visitor.

  • How do you keep the work from feeling generic?

    The work starts with the offer, audience, proof, and next decision before layout polish. Reusable patterns are allowed, but the page has to earn its structure from the business in front of it.

  • Can Morten work with existing assets or an existing site?

    Yes, when the source material is real and usable. Existing copy, brand assets, screenshots, analytics context, and platform constraints can all shape a sharper scope.

  • What should I read before reaching out?

    Start with the selected work, the Trust Center, and the project inquiry form. Those three surfaces explain the kind of problems the site is built to solve and how a first conversation is handled.

Project fit check

Bring the site that needs to work harder.

Send the current surface, the offer, and the decision you need visitors to make. I will review the context and reply with the clearest next step.

Looking for the less formal version? Read the story behind how I think and work.