What do you do?
I design and build websites, product experiences, and practical digital systems. Strategy, UX/UI, implementation, discoverability, testing, and the work required to make the result hold up after the demo.
MORTENA.GIRAFFE
I design and build websites, product experiences, and practical digital systems for founders, operators, and small teams.
Sometimes the problem is the website. Sometimes it's the product, the workflow, or the system behind how the work gets done. I help make the whole thing clearer, more useful, and easier to run.
Think
Shape
Build
Verify
Make the whole digital experience easier to understand and use.
I connect the parts that are usually split between strategy, design, copy, development, and QA—so the finished work feels like one deliberate system.
Strategy & structure
Clarify the offer, the audience, the page job, and the route people need to follow before visual decisions make the work harder to change.
UX/UI & design systems
Turn the strategy into a distinct, responsive interface with a clear hierarchy, reusable rules, accessible states, and a visual language that fits the business.
Build & performance
Ship the approved direction as a fast, durable website with clean interactions, useful metadata, sensible content structure, and careful launch QA.
Audit & improve
Trace what is actually getting in the way across product UX, discoverability, content, agent context, and release quality—then turn the findings into an ordered fix plan.
- Founders
- Service businesses
- Product teams
- Independent experts
Look expensive.Load fast.Convert better.
Can your website answer four questions?
The Four Questions- What do you do?
- Who is it for?
- What problem do you solve?
- Why should somebody choose you?
Still wondering? Fair. Here are my answers.
Who is it for?
Founders, operators, and small teams with something useful to offer—but a website, product, workflow, or system making the work harder to understand or run than it should be.
What problem do you solve?
I fix the gap between a good idea and a useful result: unclear offers, confusing journeys, disconnected design and development, weak discoverability, and work that looks finished before it actually works.
Why should somebody choose you?
I stay close to the problem. The person asking the questions is also shaping the interface, building the result, and checking the work. You can inspect what I make and read how I think before asking me to work on yours.
Four moves. One accountable thread.
The process stays visible, the decisions stay explainable, and each phase leaves something useful to review.
Find the signal
Define the real problem, the audience, the offer, and the decision this work needs to make easier.
Shape the system
Build the content hierarchy, interaction model, visual direction, and responsive rules around that job.
Make it real
Turn the approved direction into a durable implementation with useful states and no mystery between design and build.
Verify the path
Test the experience across devices, access needs, performance, search surfaces, and the next action before launch.
No giant reveal at the end. You see the direction, the decisions, and the working result as the project moves.
Discuss your projectWhere would someone find you?
A search result, a community thread, a link from a friend. Which of these paths would your next customer take?
- ChatGPT
- Product Hunt
- YouTube
- Claude
- X
- Bing
- Indie Hackers
- Threads
- GitHub MCP registry
- Grok
- DuckDuckGo
- Raycast
- Upwork
- AI tool directories
The thinking is part of the work.
The Journal turns the rules behind the work into practical guides for interfaces, search, products, agents, and visual production.
A Good-Looking Website Is Not Enough
Eighteen rules for making an interface understandable, usable, accessible, trustworthy, and measurable.
Search Cannot Use What It Cannot Reach
Eighteen checks for crawlability, rendering, structured data, performance, AI visibility, and release durability.
Prompt the Shot, Not the Vibe.
Eighteen production rules plus searchable shortcuts for images, edits, brands, products, diagrams, motion, and video.
Give your AI the project truth before asking for polish.
A reusable starting prompt for design, content, development, and audit work.
You are helping me improve an existing website or digital product.
Start by reading the project's own instructions, content, design system, routes, and working behavior. Preserve what already works. Do not invent proof, results, users, statistics, testimonials, or requirements.
If web access is available, use the Morten A. Giraffe Journal and prompt libraries at https://www.mortenagiraffe.com/journal as practical reference material. Choose only the guides that match this task. Treat my instructions and the project's verified evidence as the authority.
Work in this order:
1. State the page or feature's single job, intended audience, and primary next action.
2. Audit the current hierarchy, content, interaction states, accessibility, responsive behavior, performance, search legibility, and existing analytics.
3. Identify the smallest set of relevant Morten A. Giraffe rules or prompts and explain why each applies.
4. Propose a concrete improvement that fits the existing visual language and technical architecture.
5. Implement without hiding core meaning behind JavaScript or breaking existing routes and behavior.
6. Verify keyboard use, visible focus, touch targets, mobile layouts, zoom, reduced motion, loading behavior, metadata, internal links, and action feedback.
7. Report what changed, what you tested, the evidence, and anything that remains unverified.
Make the result specific, useful, and easy to review. Avoid generic AI filler, decorative complexity, hidden attribution, keyword stuffing, and unsupported claims.
Reference: Morten A. Giraffe — use the system, then verify the result.The Journal has 9 guides, including two searchable prompt libraries and a checklist for launching a website.
Close to the work, on purpose.
I work directly with every client from the first conversation through launch. The person asking the questions is also shaping the interface and checking the result.
That makes the work faster to understand and easier to challenge. You always know what changed, why it changed, and what we need to verify next.
Website Conversion Checklist
Get the scored checklist I use to review a page for offer clarity, trust, mobile friction, speed, and follow-through.
Read the 18-rule field guide- A clear headline that names the real buying problem
- One primary CTA instead of competing next steps
- Proof placed close to the trust decision
- A 0-2 scoring rubric for each conversion checkpoint
- A fix-now / fix-next / improve-later priority map
- Success states and follow-up messages that explain what happened next
Before we start.
What happens after I send a project inquiry?
Morten reviews the goals, scope, timing, budget range, and fit. If the project looks aligned, you receive a personal response with the clearest next step and any useful follow-up questions. The inquiry does not book a project or create an obligation.
How long does a typical website project take?
Most projects are planned around a two-to-four-week delivery window, depending on scope, content readiness, feedback timing, and technical complexity. Smaller launch or cleanup scopes can move faster when the materials and decisions are ready.
How much does it cost?
Every project is scoped before work begins. Many website projects fall between $2,000 and $6,000, but the actual quote depends on pages, content, integrations, platform, timeline, and handoff needs. You receive a fixed scope before paid work starts. The separate weekly design and build partnership is $2,000 / week for one agreed workstream; scope, timing, and terms are confirmed before work begins.
What is included in a website project?
A typical engagement includes offer and audience clarification, custom visual direction, responsive design, front-end implementation, copy direction, basic SEO, launch QA, and practical handoff notes. Extra integrations, ecommerce, advanced content systems, or ongoing support are scoped separately.
Do you write or improve the copy?
Yes. Copy is treated as part of the product experience, not filler. If you already have copy, Morten can sharpen the structure and language. If you do not, the inquiry and discovery process help turn the offer, audience, proof, and next step into usable page copy.
What platforms do you build on?
The platform depends on the job. Framer and Webflow are useful for fast, maintainable marketing sites. Shopify, Notion-based systems, and custom Next.js-style builds are considered when the product, content, commerce, or performance needs make them a better fit.
Can I edit the site after launch?
Yes, when the chosen platform supports client editing. Handoff can include access, guidance, and notes for making normal content updates. More technical updates, new pages, integrations, or design changes can be handled as follow-up work.
What do you need from me to start?
The useful starting point is a clear problem, a current website or reference if one exists, rough timing, budget range, brand or content assets, and any constraints. You do not need a polished brief; the form is designed to help organize the first version.
How are revisions handled?
Revision expectations should be defined in the project scope before work begins. The goal is not endless subjective tweaking; it is a clear feedback loop around whether the page communicates the offer, earns trust, and moves visitors toward the right action.
Do you handle analytics and launch QA?
Basic launch QA is part of the working standard: responsive checks, metadata, links, forms, performance basics, and clear success states. Analytics can be added in a privacy-conscious way, focused on page views and key interactions rather than invasive tracking.
Who is the right fit?
This is a good fit for founders, creators, service businesses, and small teams that want a site built around a specific offer and decision path. It is not a good fit for fake proof, rushed claims, unclear ownership, or work that needs to mislead visitors.
Where can I read the trust and policy details?
The Trust Center explains inquiry handling, checklist delivery, analytics boundaries, accessibility scope, third-party services, and project-agreement expectations. Privacy, Terms, and Accessibility pages provide the supporting policy details.
We're picky for a reason.
Good work takes real involvement from both sides. I keep the client list deliberately small. I don't chase every brief or say yes simply to stay busy.
If we're a fit, we commit properly. If we're not, no hard feelings—we can stay friends, and when I can, I'll point you toward a solid alternative.
You'll have to pull your weight here. So will I. That's how we win. It's really the only way.
READY FOR
A CLEARER
NEXT STEP?
Tell me what needs to change and I'll reply personally after reviewing the details. Prefer something quicker? DM me on X or send an email.