Bangkok Web AgencyDiscuss a projectOur approach
The details vary between a company website, custom application and automation project, but the same principles apply: understand the requirement, agree the scope and review the work before release.
The first conversations establish what is happening now, who is affected and what the project needs to change. For an automation or application, this includes the real workflow and its exceptions. For a website, it includes the audience, content, enquiry path and current technical setup.
We set out the recommended approach, what the first phase will include and which ideas should wait. The scope also identifies important integrations, dependencies, responsibilities and review points so both sides know what is being agreed.
Before full development, we work through the parts that are expensive to misunderstand. That may mean page structures and visual designs for a website, or an interactive prototype for an application or internal workflow.
Development is delivered in stages so progress remains visible. We test the agreed devices, browsers, integrations and workflows throughout the build, then resolve issues before the release is prepared.
Once the work is approved, we prepare the production release and check the live result. Support after launch depends on the project and can include maintenance, monitoring, content changes and later development.
Working together
You will have a main point of contact, regular progress updates and agreed stages for review. Changes to the requirement, cost or schedule are discussed before they are made.
If new information changes our recommendation, we explain why. This includes saying when a smaller piece of work will solve the problem adequately.
How we make decisions
These working principles apply whether the deliverable is a website, an application or an automated process.
A page draft or working prototype reveals misunderstandings that are difficult to spot in a written specification alone.
Technical and design choices affect cost, delivery time and future maintenance. We explain those effects before asking for a decision.
The finished work is judged by whether customers or staff can complete the intended task, not by how impressive it sounds in a meeting.