Web development
A website ready for advertising and search
We agree the structure, design key screens, build the mobile version and connect forms and analytics.
- 01 · task
- BRIEF
- 02 · structure
- FLOW
- 03 · interface
- UI
- 04 · launch
- SHIP
01 · Problem
When this service helps
A polished mockup still fails when the website is slow, weak on mobile, missing analytics, difficult to update or unprepared for search.
- You need a landing page or corporate website
- The current platform restricts your catalogue
- You need commerce, an account or an internal service
- The existing site blocks acquisition
02 · Diagnosis
How we find the cause
- 01
Define the business job and the visitor's primary action
- 02
Map structure and states before visual design
- 03
Confirm integration and content constraints
- 04
Plan mobile delivery, analytics and search foundations
In plain language
Three terms used in this service.
Core Web Vitals
In plain language: field metrics for loading, responsiveness and visual stability.
The term helps define the issue, agree the outcome and verify delivery.
Open in glossaryStructured data
It is a fact card for search engines that states whether the page represents an article, product, organisation or another entity.
Correct markup reduces ambiguity and gives search engines data for richer result presentation.
Open in glossaryTBT
It shows how long the page is busy with heavy work and cannot respond promptly to user input.
A high TBT helps identify JavaScript and other work that makes the interface feel frozen.
Open in glossary03 · Result
What changes and what you keep
- Working mobile version
- Connected forms and analytics
- Basic search preparation
- Source files and handover guide
- Structure and prototype
- Key-state designs
- Working website and repository
- Forms and analytics
- Handover guide
04 · Process
What we actually do
- 01
Business discovery
- 02
Information architecture and prototype
- 03
Original visual system
- 04
Responsive development, forms and integrations
- 05
Analytics and baseline SEO
- 06
Repository, backups, updates and handover
05 · Options
Scope, limit and price together
Start
One page for one service or offer.
LimitUp to 7 sections · 1 form
Individual estimateFull tier scope
- Structure
- Design
- Responsive build
- Analytics and basic SEO
Business
A clear set of pages for a service business.
LimitUp to 5 templates · 10 completed pages
Individual estimateFull tier scope
- Prototype
- Design
- Development
- Content management
Custom system
An account or internal tool scoped after a short brief.
LimitScope and schedule after a short brief
Individual estimateFull tier scope
- Requirements
- Prototype
- Development
- Support
06 · Timing and limits
What we clarify upfront
A landing page typically takes 5–7 weeks. Larger websites are estimated after a brief.
- Domain, hosting and paid services
- Content outside the scope
- Unspecified integrations
- Unlimited support
07 · Proof
Delivery can be accepted against evidence
- 01
We record the baseline and scope before work begins.
- 02
We hand over the completed changes and included materials.
- 03
We repeat applicable checks and state the remaining limits.
Nobody can promise a search position or number of sales in advance: demand, competitors, seasonality and the product all matter. We agree the work, timing and price upfront, then check everything again after the changes.
Result example
Development moves from the task to a working product that can be handed over
Each stage leaves a clear artefact and an acceptance criterion for the next part of the work.
Project handover map
An example scope without tying the work to a specific platform.
- Brief
- Task, audience, primary action and mandatory constraints
- Sitemap
- Pages, page roles and links between key journeys
- Prototype
- Content, states and form behaviour before visual design
- Design
- Components, key screens and responsive rules
- Development
- A working responsive version with agreed integrations
- Testing
- Scenarios, findings and resolution status
- Launch
- Agreed publishing order and checks for mandatory signals
- Handover
- Access, source files, guidance and support boundaries
Before → after
Preferences without acceptance criteria
- The visitor's primary action is undefined
- Layouts omit states and the mobile journey
- Ownership and support are unclear
A working product with handover
- Structure follows visitor tasks
- Key states are checked through scenarios
- Source files, access and support rules are handed over
Why this option
- A new interface is needed rather than a set of disconnected screens
- Forms, analytics and search foundations should enter one launch scope
- The project needs staged acceptance and a handover without dependency on one contractor
Why KILENI
- Structure and journeys are settled before visual polish
- Mobile states, forms and mandatory launch signals are tested
- Integrations, exclusions and handover contents are recorded in advance
This is a project framework example. Technology, screen count, integrations and timing are confirmed only after the task and source materials are agreed.
08 · Before ordering
11 answers for a buying decision
Scope, access, timing, acceptance and service boundaries — without hidden assumptions.
01What is wrong right now?
A polished mockup still fails when the website is slow, weak on mobile, missing analytics, difficult to update or unprepared for search.
02How will KILENI check it?
Define the business job and the visitor's primary action; Map structure and states before visual design; Confirm integration and content constraints; Plan mobile delivery, analytics and search foundations
03What exactly will be done?
Business discovery; Information architecture and prototype; Original visual system; Responsive development, forms and integrations; Analytics and baseline SEO; Repository, backups, updates and handover
04What will I receive?
Structure and prototype; Key-state designs; Working website and repository; Forms and analytics; Handover guide
05How do I accept the result?
Accept the result against the criteria agreed upfront: Working mobile version; Connected forms and analytics; Basic search preparation; Source files and handover guide.
06How long will it take?
A landing page typically takes 5–7 weeks. Larger websites are estimated after a brief.
07What does it cost?
Start — Individual estimate (Up to 7 sections · 1 form); Business — Individual estimate (Up to 5 templates · 10 completed pages); Maximum — Individual estimate (Up to 100 products · integrations separate); Custom system — Individual estimate (Scope and schedule after a short brief)
08What is not included?
Domain, hosting and paid services; Content outside the scope; Unspecified integrations; Unlimited support
09Why choose this option?
Start: One page for one service or offer. Business: A clear set of pages for a service business. Maximum: Catalogue, filters and cart for a product business. Custom system: An account or internal tool scoped after a short brief.
10Why KILENI?
Before starting, we record the baseline, scope, timing, price and acceptance criteria. For this service, the handover includes: Structure and prototype; Key-state designs; Working website and repository.
11What happens next?
Complete the short brief for “Web development”. If the option is unclear, choose “Not sure” and we will start by defining the task boundaries.
Questions about the service
Which technology do you use?
We select it after discovery and consider support, load and future integrations instead of forcing one CMS.
Can we begin with a prototype?
Yes. For complex products, discovery and prototyping can be a separate paid phase.
Is SEO included?
Technical foundations are included. Ongoing growth is a separate service.
Next step
Describe the task — get a sensible scope
Before work starts, we state scope, timing, price and exclusions.