01 — Web development / 3 min
Why a $150 landing page can bring in more than a $1,000 site
How to skip features you don't need at the start and put the focus on generating leads.
A $150 landing page is one page, one offer, and one path to a request. Three days. A heavy multi-page site at $1,000 is a different job: a long hunt for copy, a menu, and a request that gets lost in that menu. Most local businesses do not need that much site.
The brief usually starts as a wish list. Home, about, services, gallery, blog, contacts. Then it turns out there is one service, one city, and nobody has written the about page. The extra pages still have to be filled. The request hides in a menu. Someone who clicked an ad is not hunting for your manifesto. They want to know what you do and where to tap.
I build the landing page around that tap. One promise. Who it is for. What happens after they leave a contact. The form lands in Telegram, not in an inbox that gets opened on Fridays. This is not a chopped-down site sold cheap. It is a format where filler has nowhere to sit.
Think about a local service: a mobile repair, a workshop, a clinic with one procedure, a salon, a lawyer who solves one kind of problem. The customer is already close to a decision. They do not need a sitemap. They need a first screen that says what you do, who it is for, and what happens when they write. Everything else is friction.
The $300 site earns its price when the extra pages are real. A service deserves its own page when people should be able to find that service on Google. Office cleaning and post-renovation window washing are different queries. One page blends them. Six empty pages do not blend them better. They show that the copy was never written. I do not add sections to make the quote look heavier.
Here is the test before you pay. Say the offer in one sentence. Name the one action the visitor should take. If you can do both, the landing page is enough. If you have several services and each one has its own search demand, take the site, up to six pages, and bring the copy for each page now. Not later.
A store is a different job. Catalog, cart, payment, $450, up to 10 business days. Until you have products and prices you are willing to say out loud, a store will not beat a landing page on requests. It will beat it on the work that lands on you after launch: photos, stock, delivery, returns.
Speed is not a line in a deck. I build the page on Next.js. It is a compiled app, not a theme with a pile of plugins hung on it. The bar I ship to is a mobile Lighthouse score of 95+ in all four categories: performance, SEO, accessibility, best practices. The main content has to show up in under 2 seconds. That number is LCP. A person on a phone does not wait for a loading animation. An empty first screen loses the request before anyone reads how attentive you are.
The 95+ on my own site is the bar I build to. On your project, ask for the report itself. Mobile. Before the final payment. A label without a report proves nothing. Not from me, and not from anyone else.
Before we start I need three things: the offer in one sentence, real photos, and a logo as a file. If those are missing, six pages do not fix the silence. They stretch it. Start with one action. Pages get added on the same Next.js build when you actually have the volume, without throwing the site away and starting over.