© — 001.
A new site or service
There is no structure or logic yet. We build them from analysis of the niche and your customers, not from guesses.
(SW® — 01) Service
Logic and a clickable prototype first, design second. Changes cost less this way, and the site answers the customer’s questions.
Website planning: a structure that leads to an enquiry, not to the exit
(SW® — 02) Terms
- Price
- from $25/hour
- Timeline
- after the brief
- 210+ projects since 2016
- 2 weeks for a clickable prototype of a complex project
- 0 lines of code before the prototype is approved
(SW® — 03) Diagnosis
A site without planning does not sell when…
-
01
The designer draws “beautiful”, not “clear”.
The picture is lovely, but the visitor cannot find the main thing and does not know what to do next.
-
02
The structure was invented in a meeting, not from data.
Without analysing the niche, competitors and the customer’s objections, blocks sit in an order that suits the team, not the buyer.
-
03
The main action got lost among ten others.
When a page leads in every direction it leads nowhere. A landing page needs one main action.
-
04
Changes start after development.
Moving a screen in Figma is cheaper than rewriting a finished module. People remember that too late.
Design without planning is a pretty picture that does not sell.
(SW® — 05) What is included
What is included
- Price
- from $25/hour
- Timeline
- after the brief
(SW® — 04) Who it is for
Who it is for
© — 002.
A site that does not convert
Traffic but no enquiries. We rebuild the visitor’s path, because often the structure, not the design, delivers most of the growth.
© — 003.
A complex product or account area
Scenarios, roles, steps. A prototype you can show to the team, users and investors first, development second.
(SW® — 06) Comparison
Straight to design or planning first?
Straight to design
Planning by SWEB
Start
They start drawing screens
Analysis of the niche, competitors and the customer’s objections
Structure
Blocks in the order that suits the team
An order built around the customer’s path and one main action
Copy
Placeholders that never get replaced
The offer and first-screen headline, prompts for the copy
Changes
After the build, when it is expensive
On the prototype, when it is cheap
Search
Queries are remembered after launch
A structure built around search queries for multi-page sites
Result
A picture
A clickable prototype you can show to the team and investors
(SW® — 07) Formats
What we plan
We define the scope after a short brief, and it is free.
© — 01
Landing page structure and prototype
Block logic, the offer and a clickable prototype.
after the brief
Timeline: after the brief
- Niche and competitor analysis
- The objections the page must answer
- The offer and first-screen headline
- Block order built around the customer’s path
- A clickable Figma prototype
© — 02 Recommended
Multi-page site prototype
A page map, navigation and a structure built around queries.
from $25/hour
Timeline: after the brief
- A structure built around search queries
- A page map and navigation
- Visitor scenarios up to an enquiry
- A Figma prototype of the key pages
- Prompts for page content
- Handover to design and development
© — 03
Planning a service or account area
Roles, scenarios and screens of a complex product.
after the session
Timeline: prototype in up to 2 weeks
- A technical session and a description of features
- Roles, scenarios and edge cases
- A clickable prototype before development
- A basis for an accurate development estimate
- Something to show to users and investors
(SW® — 06) Related work
Related work
All projects
(SW® — 11)Client reviews
Client reviews
What the companies we have worked with have to say.
All reviewsWe sold dancewear through Instagram and were drowning in DM orders. The team built a store where the customer picks size and colour themselves, and orders finally stopped getting lost. Worth adding: we have run the catalogue ourselves ever since, without coming back for small changes.
(SW® — 09) Guarantees
What you get at the end
-
01
Approved logic before design
You approve the structure and prototype before anyone draws a design or writes code.
-
02
You can take the prototype and go
It is yours: hand it to your own designer or developer if you want to work without us.
-
03
A basis for an honest estimate
The scope is visible on the prototype, so the cost and timeline of development are calculated more accurately.
-
04
Fewer changes later
We agree the direction first, then the details. Changes on a prototype cost less than on a layout.
(SW® — 10) FAQ
Questions about planning
001. Why plan if we can go straight to design?
Because it is cheaper to move a screen in a prototype than to redo a finished layout or code. Planning answers “what to show, in what order and where to lead”, and design only dresses up the answer.
002. Can I order only the planning?
Yes. The prototype and structure are yours: hand them to your own designer or developer, or continue with us.
003. What do I get at the end?
A page structure, block logic, the first-screen offer and a clickable Figma prototype. For complex products also a description of scenarios and roles.
004. How much does planning cost?
Hourly work from $25/hour. We name the sum after a short brief, once it is clear what we are planning.
005. Why not generate a prototype with AI?
AI draws screens quickly, but it does not know your customers, their objections or their path to buying. A prototype without analysis is a pretty guess. We use AI as a tool, but we build the logic from data.
006. Do you work from our technical brief?
Yes. We will review the brief, tell you what is missing and help you complete it before we start.
(SW® — 12) Next step
Tell us about the task. We will say what to plan and where to start.
Describe the site or product and the goal. We will give you an honest estimate: whether planning is needed, how much, and what it costs.