Home / Blog / Process

How we plan a web project before writing any code

Discovery, user journeys, modules, stack choices and milestones: what happens before development starts, and why it matters.

The most important work on a website or app happens before anyone writes code. A clear plan keeps a project on track, makes the finished product easy to use, and keeps it easy to extend later. This is how we plan every project, whatever its size.

Start with the problem, not the features

We begin with a discovery call about your business rather than your feature list. Who are your customers? What do they need to do on your site or app? What slows your team down today? A booking platform, a CRM and an online store can all start with “we need a website”, and the answers to these questions are what tell them apart.

Map the users and their journeys

Next we list everyone who will use the product and what each of them needs to get done. A typical online store has three very different users:

  • Customers who browse, search, pay and track orders.
  • Your team who add products, manage stock and handle orders.
  • Admins who manage users, settings and reports.

Walking through each journey step by step shows which screens are needed and where the tricky parts are, long before they turn into bugs.

Break the product into modules

We split the product into modules that can be designed, built and tested on their own. Each one gets a short written description of what it does and how it connects to the rest.

Module What it covers Depends on
Accounts Sign-up, login, roles and permissions None
Catalogue Products, categories, search and filters Accounts (for admin)
Checkout Cart, payment gateway, confirmations Catalogue
Orders & stock Order tracking, inventory, notifications Checkout
Reports Sales, customers and exports Orders

Modules make the work easy to follow. They also make it easy to launch the core first and add the rest in a second phase.

Write down what’s out of scope tooListing what a release will not include is as useful as listing what it will. It keeps everyone’s expectations the same.

Choose the right stack for the job

We pick technology to fit the project, not the other way round. A content-heavy business site is often best on WordPress, so your team can edit it easily. A fast brand or product site suits Next.js. Custom software such as a CRM or booking platform usually needs React with a Node.js backend and a proper database, and iOS and Android apps can share one React Native codebase.

The best stack is the one your business can run and grow without friction.

Set milestones you can see

The plan ends with milestones, each tied to something you can open and try: the designs, then the first working modules, then the full product on a test link. You see progress at every stage, and feedback lands while it is still easy to act on.

Once the product passes QA on real devices and browsers, we launch it on your hosting and stay on for post-launch support.

Why it’s worth the time

Planning takes a little longer at the start and saves far more later. You get a product that fits how your business works, a team that knows exactly what it is building, and code that is easy to extend when you are ready for the next step.