Our Process


Once a customer starts discussing his requirements, the team gets into it, towards the preliminary requirement analysis. The first important thing is finding the targeted audience. Then, all the present hardware, software, people and data should be considered during the time of analysis. The team should be able to come up with the complete cost-benefit analysis and as the plan for the project will be an output of analysis, it should be realistic.


Preliminary specifications are drawn up by covering up each and every element of the requirement, eg. layout, site structure and dynamic parts. Larger projects will require further levels of consultation to assess additional business and technical requirements. After reviewing and approving the preliminary document, a written proposal is prepared, outlining the scope of the project including responsibilities, timelines and costs.


After building the specification, work on the web site is scheduled upon receipt of the signed proposal, a deposit, and any written content materials and graphics you wish to include. Here normally the layouts and navigation will be submitted as mockups via email, messenger programs… There can be a lot of suggestions and changes from the customer side, and all the changes should be completed before moving into the next phase.


Our clients are to supply the content being uploaded to their sites at this stage. Every change in content will be made effectively and efficiently.


It is time that programmers turning the design into a more vividly functional website. While the mocks are being designed, the programmers must recommend his technical knowledge to the designers so as to enhance the flexibility of the site and avoid further malfunctioned elements. The site will be sent to our clients in specified phases for preview and comments if any. The end-user documentation can also be prepared by the coding team, which can be used by a technical writer who can understand them, writes helps and manuals later.


Unlike software, web based applications need intensive testing, as the applications will always function as a multi-user system with bandwidth limitations. Some of the testing which should be done are, Integration, Loading speed, Resolution rationality and Cross-browsers compatibility


This phase is optional to our clients. Promotion needs preparation of meta tags, constant analysis and submitting the URL to the search engines and directories. The site promotion is normally an ongoing process as the strategies of search engine may change quite often. Submitting a site URLs once in 2 months can be an ideal submission policy. If the customer is willing, then paid click and paid submissions can also be done with additional cost.


Further updates and their corresponding quotes will be discussed and processed upon agreement after the site has been finished. Bug fixings can be done during the time of maintenance free of charge once they are our coding-rooted.

AHT;s process of web design and development

The above-mentioned steps alone are not strict to web application or web site development. Some steps may not applicable for certain tasks. It depends on the cost and time involved and the necessity. Sometimes if it is a intranet site, then there will be no site promotion. But even if you are a small development firm, if you adopt certain planning along with this web engineering steps in mind, it will definitely reflects in the Quality of the outcome.

ArrowHiTech Development process is based on SCRUM process!

AHTsolutions development process

Sprint detail

AHTsolutions\' sprint details

Our staff members are all well-trained and experienced enough to afford any kind and any level of projects. As a matter of fact that there is a rising demand for hiring developers for short-term in house tasks, we offer a flexible hiring policy in wide variety of skills and time. Contact us to receive list of candidates and select the right ones.

  • You receive written CVs of the developers
  • You interview them in person through phone, skype conference…
  • You describe the details of required tasks for the developer(s) or the project manager
  • You review the results on our local server or your server (if deployed there)
  • You assess the quality of work and submit feedback