MORTENA.GIRAFFE

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.