Websites and software
Website development
We design and build business websites, landing pages and redesigns. Audience and content structure come first; technology follows the real editing and expansion needs.
Discuss a websiteWhat are you actually buying?
Not a page count and not only a polished visual. You are buying a clear information structure, practical editing, a dependable technical foundation and an agreed way to verify launch readiness.
When this is a good fit
- The current website no longer represents the offer or is difficult to edit.
- You need a new sales or information channel with a clear enquiry path.
- A redesign must preserve useful URLs, content and measurement.
- The site will later expand with languages, services or integrations.
When a smaller step may be enough
- A dedicated landing page may be enough to test one offer.
- If one journey is broken, improve that journey or form first.
- If content is not ready, start with structure and ownership—not visual design.
What a comparable proposal should cover
Proposals are comparable only when included work, customer responsibilities and post-launch ownership are explicit.
| Area | What we define | What must be agreed |
|---|---|---|
| Content and structure | Audience journeys, page tree and core messages | Who writes, approves and enters final content |
| Design and interface | Key screens, components and mobile behaviour | Iterations, states and decision owners |
| Engineering | Content management, forms, integrations and browser support | Third-party accounts, licences and data ownership |
| SEO migration | Metadata, indexing foundations and URL inventory | Which old URLs remain and who verifies redirects |
| Launch | Acceptance checks, analytics and handover | Who owns the domain, content and future changes |
How we would work
- 01
Understand
Agree on the audience, business task, content readiness and technical constraints.
- 02
Shape
Create the structure, key page logic and a scope that can be estimated.
- 03
Build
Design and engineering move in testable stages rather than disappearing until launch.
- 04
Verify and hand over
Check agreed criteria, important URLs, forms, editing and post-launch responsibilities.
What changes cost and timing most
- Content volume and who prepares it
- Custom design and component scope
- Languages, roles and editing workflow
- Forms, payments, CRM or other integrations
- Migration, URL preservation and testing scope
Useful answers before the first conversation
- 01What should a visitor do on the website?
- 02Who edits content now and who will own it later?
- 03Which existing pages or URLs already matter?
- 04Which systems must exchange data with the website?
- 05What would be a clear, verifiable launch result?
We can start with one clearly defined problem.
Send the current website address or a short description of the new project. If a full redesign is not necessary, we will say so.