A fast website that looks right on a phone and gets visitors in touch with you. Design, content architecture, technical setup, mobile layout, baseline SEO and launch are handled in one production flow.
What determines the price and timeline of a website is not the page count but how many distinct screen types it has and which external systems it connects to. The platform decision comes down to one question: how often will you update the content yourself? A corporate site updated a few times a year is faster, safer and cheaper to maintain as a static build; a site publishing continuously needs a content management system.
Founders, creative teams, boutique brands, restaurants, clinics, portfolio owners and local businesses that need a trustworthy website.
Platform choice is the most debated part of a website project. In practice it turns on one question: how often will you update the content yourself?
The cost of the wrong choice does not show up at launch; it shows up months later. A CMS installed for a site updated three times a year is a permanent maintenance load: a queue of plugins waiting to be patched, mandatory backups and breakage risk on every update. Conversely, building a continuously publishing site as static turns every text change into technical work.
For a real example of this decision, see the Nest Worldwide case: a three-division company's corporate site was deliberately built static, because the content changed a few times a year.
A common misconception is that website price scales with the number of pages. But 40 product pages sharing a template are designed once; 5 genuinely different screens are designed five times.
The right question is: how many distinct screen types are there? Home, list, detail, form and dashboard are each separate design and development work. The second driver is external connections: payment, shipping, accounting, SMS, booking. Every integration means separate documentation, separate testing and separate failure modes.
I have written out all the items that determine price on the pricing page — without figures, by explaining what changes what.
The phrase gets used a lot and usually means nothing. Concretely it should mean:
/page/index.html redirected 301 to one address.Most of the gain in speed work sits in four places: converting images to WebP, preloading the large above-the-fold image, fixing images without declared dimensions, and moving third-party requests onto your own server. In one real setup the format change alone took an image folder from about 147 MB to roughly 10 MB.
The danger here is breaking what you are not measuring while improving what you are. A speed plugin deferring all JavaScript raises the score but can make the checkout page stop working on e-commerce sites. Details in the speed note.
Work runs in four steps: writing the scope down, setting the design direction, development, and launch. When scope is written, what will not be done is written too — the only practical way to stop projects growing silently.
The timeline is usually set not by development but by two external factors: content readiness and any bank or integration approvals. If the copy is unwritten and the photography untaken, the project finishes technically but cannot launch. So the content requirement is turned into a list at the start, naming who prepares what and by when.
Less by page count than by two things: how many distinct screen types there are (home, listing, detail, form, panel) and which external systems the site connects to (payments, booking, SMS). The scope is written first, then a fixed quote follows.
WordPress is strong when content will be edited often. Next.js is stronger for fast, custom and product-like sites that need more control.
Yes. Titles, meta descriptions, canonical tags, sitemap, robots, JSON-LD schema, image alt logic and internal links are included in the delivery scope.
No. I am based in Istanbul, but the whole process can run remotely; I also work with clients in Ankara, Izmir, Tekirdağ and abroad. Several of the projects in the case studies are outside Istanbul.
A corporate brochure site typically takes a few weeks. What stretches the timeline is usually not development but content readiness and any external approvals — for example a bank virtual POS application if you will take payments. With copy and imagery ready, the schedule shortens noticeably.
With a CMS, yes, from an admin panel. On a static build, content is updated in the source and the site is rebuilt and republished — for a corporate firm making a few updates a year this is not a problem, and you gain speed and security in return. Which model suits you becomes clear in the first conversation.
In most cases no. If the existing structure is sustainable, working on top of it is faster and cheaper, and you keep the history you have accumulated in search. A rebuild is advisable only when the current structure genuinely cannot be carried forward.
The maintenance model is agreed up front. Three common options: full handover of the system to you, support on demand, or regular maintenance (updates, backups, monitoring). For systems that take payments or hold personal data, regular maintenance is strongly recommended.