Shape the first version
Work out what the website needs to explain and which pages belong in the first useful version.
See examples
- Whether you need a website yet
- Landing page versus a full website
- Which pages should be included
- What visitors need to understand
- Calls to action
Choose useful features
Separate genuinely useful functionality from additions that can wait until the website proves it needs them.
See examples
- Forms and enquiry systems
- Booking links
- Email follow-up
- Chatbots and FAQ assistants
- Customer portals
Understand the tools
Talk through platforms and connected services in plain language, without assuming the biggest setup is best.
See examples
- Website builders versus custom code
- Basic SEO and analytics
- How AI may help with content or development
- Avoiding unnecessary platform lock-in
Plan a sensible next step
Get clearer on cost, developer conversations and how an existing website might be improved.
See examples
- What a website may cost
- What to ask a developer
- How to improve an existing website
- What to build now and what can wait
Build what you need first
The first version does not need to do everything
It needs to do the main job properly. A website can begin with the essential pages and features, then
grow as the business learns what customers actually need.
01 Build now
Do the main job properly
Include the pages, content and functionality required for a useful first version.
02 Add later
Grow from real feedback
Add useful features after the website is live and you know more about what customers need.
03 Leave out
Avoid early complexity
Skip features that add cost or maintenance without solving an immediate problem.
Not every website needs a blog, chatbot, booking system, automation or customer portal from the beginning.
What will you leave with?
A clearer idea of what makes sense next
This is primarily a conversation and advisory session, not a formal written strategy or detailed website
specification.
- The type of website that may suit your business
- What the first version should include
- Which features are important and what can wait
- Which tools or platforms may be suitable
- What questions to ask a developer
- What your practical next step should be
You should leave knowing more than you did when we started and, hopefully, with fewer tabs open.
A relaxed conversation
Bring the idea, the notes or the questions in your head
We will spend an hour making sense of them together. There is no complicated presentation and no need
to arrive with a polished brief.
- Bring notes, screenshots, links or a messy list of questions.
- You do not need to understand technical terminology.
- I may suggest a simpler option or explain why a simple-looking feature needs more work.
- If something needs more research, I will say so rather than pretend to know everything.
- There is no obligation to hire me for a website build afterward.
Why speak with me?
More than ten years of looking at the wider problem
My experience is not limited to making pages look good. I also think about what the business is trying
to achieve, what the customer needs to understand and what should happen after someone visits the website.
- Websites
- Applications
- Spreadsheets and data
- Business processes
- Accounting systems
- Internal tools
See what is not included
- Website design
- Website development
- A complete written website strategy
- Detailed SEO research
- Full copywriting
- Technical implementation
- Ongoing support after the call
There is no requirement to hire me for a website build after the call.
You can use what you learn to:
- Work with me
- Work with another developer
- Continue researching independently
- Decide not to build yet
How it works
Pay first, then choose a time or wait for my email
- 1
Pay through PayPal
Purchase the call securely through PayPal for USD 57.
- 2
Choose a suitable time
After payment, you can use the return page to request a time through Cal.com, or wait for me to contact you using the email connected to the payment.
- 3
Bring the questions
Share your website, business idea, links, notes or questions before the call where useful. No formal brief is required.
- 4
Talk it through
We spend one hour discussing the website, the available options and the clearest practical next step.
Is this only for new websites?
No. The call can also be used to discuss an existing website, possible improvements or whether a rebuild is necessary.
Do I need to prepare anything?
No formal brief is required. Links, notes, questions and examples are helpful but optional.
Will you build the website during the call?
No. This is a one-hour discussion and advisory session. Design and development are separate services.
Will I receive a written report?
A formal written strategy or report is not included. The value is in the live conversation, explanations and questions answered.
Do I have to hire you afterward?
No. There is no obligation to purchase another service.
Why is this offer in USD when other offers are in GBP?
This call is currently priced and processed in USD through PayPal. Larger website projects may be quoted separately in GBP.
What happens after I pay?
PayPal returns you to a page where you can request a suitable time through Cal.com. If you prefer not to schedule immediately, I will contact you using the email connected to the payment. Bookings are confirmed after they are matched with the payment.
What if my question is not only about websites?
The main focus is websites and the tools or processes directly connected to them. Related questions about forms, email automation, chatbots, AI, SEO, analytics or simple business systems may also be discussed where relevant.