Process
Good projects need more than a good idea. This is how I move from an initial conversation to something useful, with clear decisions and visible progress along the way.
Working together
One direct relationship.From the first conversation to the details of the handover.
Tell me about your projectWe start with the business, the people using the product and the friction you want to remove. I review the existing experience and ask what a successful outcome would change, before deciding what needs to be built.
The work becomes a written scope with deliverables, an approach, review points and an agreed quote. We establish who supplies content, what access is needed and which decisions need to be made along the way.
I work through the structure, content and important journeys, then bring the visual direction into focus. For a website that includes the inner pages and mobile experience. For an AI tool it includes inputs, feedback, review and recovery.
You see working progress at agreed stages. I develop the interface and integrations, check the responsive behaviour and use feedback to resolve the details. Questions are addressed while the work is still easy to change.
Before launch, we review the key pages, links, forms and interactions, and check the content and setup. The handover explains how to use and manage the finished work, alongside any agreed support arrangements.
Once the work is in use, the questions become more specific. We can use analytics, feedback and operational experience to decide what to improve next, through a separate project or an agreed ongoing engagement.
A few working principles
The process should make the work easier to understand and easier to move forward.
Clear explanations of the options, the recommendation and what a decision means for your project.
Reviewable work at agreed checkpoints, with room for useful feedback before the finishing touches.
New ideas are welcome. If they affect the scope, timing or cost, we discuss that before adding the work.
Practical questions
No. A link to your current website, a few sentences about the issue and a sense of the outcome are enough to begin. If you already have a detailed brief, designs or technical requirements, those are useful too.
Yes. An audit, a specific page, a prototype or one workflow can be a useful starting point. It helps us understand the priorities and gives you a concrete result before committing to a larger build.
You work directly with me, Gokul. We agree how to communicate, when to review progress and what you need to provide at the start of the project.
Have something in mind?
Tell me what you are building, where it gets difficult, and what a better outcome looks like.