Direct answer
The first conversation is useful when you can show the current constraint, the decision owner, and what must be true after launch.
This is a diagnosis and a working sequence, not a ranking promise and not a quote. Scope, fees, and dates stay in a written proposal.
The situation behind the search
People look up “prepare for website project” when a real constraint is already costing time: a site that cannot explain the offer, a backlog that does not move, or a launch date with no owner. Treat the search as a symptom.
If you cannot name the buyer, the constraint, and the decision owner, stop and write those down before you change the UI or the stack.
Before you change anything
Collect evidence that would change your mind. Screenshots of the broken path, the current URL, the analytics you actually have permission to use, and the last proposal or backlog are enough to start.
Do not start with a moodboard, a new CMS, or a hiring plan. Those are downstream of the job the software is supposed to finish.
A practical sequence
Work in this order. Skip a step only if you already have a dated artifact for it.
- Capture the current URL and what it fails to do
- Name the decision owner and other approvers
- List integrations, CMS, and legal reviews
- Share timing and investment context as scope, not a bid
- Collect examples of competitor sites you do and do not want
Mistakes that look like progress
These are common, expensive, and avoidable:
- Rewriting copy without naming the buyer and the outcome.
- Adding tools (chat widgets, overlays, extra analytics) on top of an unclear offer.
- Treating a slide metric as a contract. If you cannot source it, do not publish it.
What to send if you want a senior review
If this problem is now a delivery job — not a blog post — share the goal, the constraint, timing, and investment context on the project request. Related work at Kiwi: custom website design and development.
Submitting a request does not create an engagement. A senior practitioner replies within one business day. Kickoff is typically within five business days of an accepted written proposal. You own the source at the agreed handover.
Frequently asked questions
Is “prepare for website project” usually a design problem or a strategy problem?
It is usually both, but strategy leads. If the offer, buyer, and next step are unclear, visual polish will not create qualified demand. If those are clear, then templates, speed, and forms become the constraint.
Can a studio promise a ranking, lead volume, or conversion lift?
No. Honest studios set acceptance criteria (crawlable pages, Core Web Vitals budgets, WCAG 2.2 AA on the templates in scope) and measure after launch. They do not sell outcome promises.
What is the smallest useful next step?
Write the constraint and the decision owner, then either run the sequence above internally or send a project request with that context. You do not need a finished specification first.
Sources
- Nielsen Norman Group — Usability 101
- Nielsen Norman Group — Information architecture vs. navigation
- Nielsen Norman Group — Placeholders in form fields
Figures cited above are drawn from the linked publications and are the responsibility of their sources; we date and scope them rather than presenting them as universal guarantees.