Discovery and scope
We define the business goal, audience, pages, content, and technical requirements.
I design information architecture, user flows and interfaces for corporate websites and digital services. UI/UX alone or design with development can be scoped; code, CMS, integrations and launch responsibilities are agreed separately in the brief.
Responsive interface design shaped around the brand, content and visitor journey, with modern web development included when agreed in the project scope.
A strong website should do more than look polished: it should help visitors find relevant information and move toward the right action. I treat information architecture, interface design and responsive behavior as one connected system. A UI/UX-only handoff includes editable design files, a prototype and implementation notes; production-ready front-end development, a CMS and integrations are separately approved proposal items.
Work with Onur Demircan on a UI/UX-only scope or a combined design and development project. Pages, content management, forms and integrations are scoped together. The designdmc case study presents his own work across web UI/UX, Next.js and CMS.
Questions, examples and project preparation (Turkish) ↗The four things worth knowing before asking for a quote. No figures here — only what the figures depend on.
We can discuss a new corporate website, a redesign or the user flows of a service platform. A UI/UX-only scope defines the page structure, key screens and design handoff. If development is required, content management, forms, integrations and launch responsibilities are scoped separately. Each portfolio project should be assessed against the role I actually performed.
KonutKonfor presents the design of service selection, booking and payment steps. Garantili Oto Servis presents vehicle details, package comparison and booking flows. The case study of my own website separately documents web design, Next.js development and CMS work. Use the preparation guide to clarify goals, content and delivery questions before starting.
A design handoff is defined through information architecture, wireframes, desktop/mobile screens, key states, a clickable prototype and developer notes. Form submission, a CMS, payments or booking integrations require working code; showing them in a design does not include their implementation. Responsibility for copy, imagery, domain, hosting, content entry, technical delivery and launch checks is stated separately in the proposal.
We define the business goal, audience, pages, content, and technical requirements.
The page structure, visual direction, and responsive behavior of key screens are designed.
Design files and handoff notes are prepared; when development is included, the build is reviewed with real content across target screen sizes.
Suitable for teams seeking a tailored, maintainable, and scalable portfolio, corporate, or service-focused web experience.
Development is not automatically included in every UI/UX project. Information architecture, interface design and responsive behavior belong to the design scope. Design handoff, front-end code, content management, integrations and launch responsibilities are separate proposal items; when commissioned together, they follow the same design system.
The design scope covers a sitemap, content hierarchy, user flows, desktop and mobile interfaces, plus the agreed prototype and developer notes. When development is included, responsive front-end delivery, content integration and technical SEO, accessibility and performance checks are added. A CMS and custom integrations are listed separately.
Discovery defines the goal, audience, pages, content and technical requirements. Page architecture, visual direction and responsive behavior are then designed. A design-only engagement ends with files and handoff notes; when development is also agreed, the approved design is implemented and checked with real content across screen sizes.
A web development scope includes baseline canonical, heading, accessibility and performance checks. A UI/UX-only handoff covers information hierarchy and accessible design decisions; technical implementation on the live site is not automatically included. Content planning, search-intent analysis and a comprehensive technical audit are separate SEO items.
Teams that need a brand-specific, manageable, and scalable web experience for a portfolio, company profile, or service story.
The timeline is set by page count, content readiness, and technical requirements; a content-ready landing site and a multi-page CMS build are different schedules. Scope is clarified during discovery, and the timeline is agreed there.
Pricing is per project, driven by the number of pages and screens, custom component needs, the scope of content integration, and technical requirements. After the brief is clear, a written proposal matches the agreed scope.
Page structure and visual direction are approved first, with feedback gathered in design files and the prototype. When development is included, the approved design is built and reviewed before launch with real content across screen sizes. New pages or integrations outside the agreed scope are considered separately.
Your current website, target visitors, priority services, required pages and features, available content and target date are enough to begin. You do not need to decide every technical detail in advance; the UI/UX and development scope is clarified from this information.
Let’s clarify the need, deliverables, and timing through a concise brief.
I reply to your message within 24 hours.
Onur Demircan Web Site 2026 | All Right Reserved