Small businesses and independent professionals
For presenting a business, professional profile, service, location, or clear way to make contact through one focused website or a small set of pages.
← All services
Static Business Website or Landing Page
A focused custom website, built without a CMS.
I design, build, test, and launch a custom static Next.js website around a clear business, professional, campaign, event, or service goal.
This service is best suited to one or a small number of pages whose content changes infrequently and can be maintained through occasional code updates.
Good fit
For a clear online presence that does not need day-to-day content editing.
The service is intended for businesses, independent professionals, campaigns, events, and focused offers that need a polished custom website without an editing dashboard or frequent publishing.
Campaigns, events, and focused offers
For a dedicated landing page built around one audience and action, such as explaining an offer, collecting an enquiry, supporting a launch, or presenting an event.
Replacing a limited existing website
For replacing an outdated or generic online presence when the new content can remain intentionally stable and future changes can be handled occasionally through code.
The public website matters more than an administration layer.
- The purpose, audience, and primary action are clearly defined
- The website needs one or a small number of pages
- The content changes rarely
- No internal editing or publishing workflow is required
- The available budget is better invested in the public website than in CMS functionality that would rarely be used
- The main interaction is informational or enquiry-based
If several people need to publish regularly, manage structured collections, or update content independently, the headless WordPress website service is likely the better fit.
Complete focused delivery
Everything needed for a polished static website, without an unnecessary administration layer.
A smaller scope does not mean using an off-the-shelf template or skipping the engineering, testing, and delivery work required for a dependable result.
Structure, content, and direction
The project starts with a structured questionnaire covering the goal, audience, available content, brand materials, desired action, and relevant constraints.
- Focused page and information architecture
- Relevant keyword and search-intent research
- Initial page copy based on supplied information
- Practical UX/UI developed alongside implementation
- Adaptation of existing brand materials or visual direction
Custom static frontend
The website is designed and implemented as a custom static Next.js frontend built around the agreed content and purpose.
- One landing page or a focused set of business pages
- Custom responsive layouts and reusable components
- Semantic and accessibility-conscious HTML
- Performance-conscious images, fonts, and assets
- Clear navigation and calls to action
Forms and focused integrations
Lightweight third-party functionality can be included when it supports the page goal and remains proportionate to the project.
- Contact or enquiry forms
- Anti-spam protection
- Maps and booking links
- Analytics and cookie-consent tooling
- Other agreed lightweight integrations
Search and launch foundations
The project includes the technical and on-page foundations required for a complete production launch, not ongoing marketing management.
- Titles, descriptions, and canonical URLs
- Open Graph and social-sharing metadata
- Relevant structured data
- Sitemap, crawler, and llms.txt configuration where appropriate
- Favicon, error page, and production details
Quality, infrastructure, and launch
The website is tested and delivered through client-owned infrastructure with an automated release workflow.
- Client-owned repository, domain, and hosting account
- Automated build and deployment configuration
- Manual responsive, browser, form, and link QA
- Focused automated checks where useful
- Production launch and 90-day stabilization
Client approval: I can structure and draft the initial content from the information supplied. The client approves business claims, prices, qualifications, legal statements, and regulated or industry-specific information before publication.
Architecture
Source-controlled content. Tested build. Static delivery.
Content and presentation are implemented together in the Next.js project, keeping the system focused when an editing interface or frequent publishing workflow is unnecessary.
- 01
Agree the content and design
We review the page structure, initial copy, visual direction, calls to action, and required integrations before implementing the approved content.
- 02
Build the custom frontend
Next.js generates the agreed pages from source containing only the layouts, styles, components, and behavior required for the website.
- 03
Validate the release
Changes pass through the configured build and delivery process, including the agreed content, browser, form, metadata, and release checks.
- 04
Deploy to static hosting
The generated website is served without a public CMS, database, PHP runtime, theme, or plugin stack producing every page request.
- 05
Make occasional updates through code
Future content, design, or functionality changes are implemented in the source and published through a new tested deployment.
The intentional trade-off
The client receives a custom website with fewer operational layers to host, update, and administer. There is no editing dashboard, so future changes require a code update and tested deployment.
During the included 90-day stabilization period, defects and minor adjustments within the original scope are covered. New content, design, functionality, and changes requested later are assessed and priced separately.
Delivery process
A focused path from project context to a live static website.
- 01
Project questionnaire
You provide the business or offer, audience, desired action, available content, brand materials, and timeframe.
- 02
Scope and direction
We define the pages, content responsibilities, integrations, visual direction, delivery responsibilities, and project boundaries.
- 03
Proposal and agreement
You receive the deliverables, price, and estimated timeline. Work begins after the proposal and project terms are accepted.
- 04
Content, structure, and design
I prepare the information architecture, relevant keyword research, initial copy, and practical UX/UI around the implemented experience.
- 05
Static frontend development
I build the responsive Next.js website, agreed form and integrations, metadata, production configuration, and delivery workflow.
- 06
Testing and client review
The website goes through the agreed manual and automated checks, followed by your review and in-scope adjustments.
- 07
Launch and stabilization
I validate the production release on the client-owned domain and hosting account, followed by 90 days of stabilization.
After launch
Your website and accounts remain under your control.
The project is delivered through client-owned accounts rather than being locked inside a proprietary platform or developer-controlled account.
Domain, hosting, and setup
The domain, hosting, repository, and required services are created in or transferred to your control. Suitable projects may use a free static-hosting tier.
If needed, a guided setup call of up to one hour can be used to register the domain, create accounts in your name, and grant the access required for configuration.
Project source and reuse rights
The delivered source stays in your repository and may be used, hosted, modified, maintained, or transferred by you. General methods, patterns, pre-existing tools, and non-client-specific components remain reusable in other work.
90-day stabilization
The included period covers defects, operational issues in the delivered website and workflow, minor adjustments within the original scope, and operational guidance.
It does not include new pages, campaigns, integrations, substantial additions, redesign, or new functionality.
Future changes
After stabilization, occasional changes can be assessed and quoted separately. You can request them from me or work with another developer who has access to your repository and accounts.
No continuing service is required to retain control of the website.
Scope boundaries
A focused scope keeps the static website efficient.
The service is designed for one landing page or a focused set of presentation and enquiry-oriented pages with intentionally stable content.
Content management
No CMS, dashboard, user roles, editorial workflow, or self-service publishing is included. Blogs, frequently changing catalogs, structured collections, and regular publishing are better suited to the headless WordPress service.
Functionality
The service does not target accounts, dashboards, memberships, SaaS functionality, complex e-commerce, sensitive transactions, or authenticated workflows. Focused links, maps, analytics, and enquiry forms may be included.
SEO and marketing
Launch foundations can include initial copy, keyword research, on-page SEO, metadata, structured data, and sitemap configuration. Ongoing SEO, analytics monitoring, A/B testing, advertising, backlinks, social media, and content production are not included.
Branding and visual materials
Clients normally provide their logo, brand materials, and photography. Limited launch-ready direction or AI-assisted assets may be prepared where appropriate, but do not replace professional branding, trademark review, or photography.
Accessibility, privacy, and legal
The implementation is responsive, semantic, usable, and accessibility-conscious. Formal conformance requires a defined scope. Legal text, regulatory interpretation, and confirmation of obligations remain with the client or an appropriate specialist.
Third-party services
Forms, analytics, maps, booking or payment links, fonts, and hosting remain subject to provider limits, policies, availability, and pricing. Provider migrations, recovery, legal review, and ongoing administration are not included.
Start with the goal
Tell me what the website needs to present and what visitors should do next.
Send a short written overview of the business, professional profile, campaign, event, or offer, together with the page goal and any existing website or materials.
I will review the information and reply by email if a static website appears to be the appropriate fit or if I need specific details before suggesting the next step.
Prefer email? Write directly to [email protected].