Choosing a web agency feels a lot like choosing a contractor for a renovation. You pay and commit now, but you will only see the result weeks later. The cost of a mistake is not just money. A failed website means lost time, delayed advertising plans, and the search for a new team that will first have to untangle someone else’s code.
The good news is that most problems are visible before you sign anything, if you know where to look. Here is a practical checklist: the criteria for evaluating an agency, the questions to ask in the first conversation, and the promises that should make you politely walk away.
A web agency’s live portfolio: websites you can actually open
The portfolio is your first filter. But look at live websites, not screenshots in a slide deck. Ask for links to 5-7 recent projects and open each one in your browser.
- The site opens at all. If half of the links lead to dead domains, that is a bad sign. Either the projects shut down right after launch, or they never existed.
- Speed and the mobile version. Open the site on your phone. Slow loading and a broken layout on a smartphone mean your site will end up the same way.
- The forms work. Click the contact button, try adding a product to the cart. Broken forms on portfolio sites are more common than you would expect.
- Similar projects. If you need an online store, the portfolio should contain actual stores, not just landing pages and brochure sites. These are different skills and different pitfalls.
Also ask what exactly the agency did in each project. Sometimes a contractor shows a website where they only swapped banners, while the design and development were done by another team. An honest agency will calmly tell you where they built everything and where they only made improvements.
Look at the agency’s own website too. It should load quickly, open correctly on a phone, and look current rather than untouched for years. If the team did not take care of their own site, it is odd to expect a different attitude toward yours.
Reputation is easy to check through other people. Search for reviews outside the agency’s own site, on Google, Clutch, and social media. There you will find both happy clients and those who were unhappy about something, so the picture is more honest than a curated set of testimonials on the site itself. Better still, ask for the contacts of one or two former clients and call them. A direct conversation of a couple of minutes will tell you more about an agency than a page of case studies.
A clear process and a specific person to talk to
Behind every good website there is a sequence of stages:
- brief and task analysis;
- structure and prototype;
- design;
- coding and development;
- content and testing;
- launch.
Ask the agency to describe the process for your specific project. If the answer is a vague “do not worry, we will handle everything”, treat it as a warning.
The second thing worth clarifying is who you will be talking to. It could be a project manager, the head of the studio, or the developer themselves. The format matters less than the substance:
- you have a specific person, not a generic inbox “for all questions”;
- you have agreed how quickly they respond during working hours;
- you know where the communication happens, whether email, messenger, or calls;
- at every stage you see an intermediate result instead of waiting for one big reveal at the end.
Intermediate reviews are the key point. If the first time you see the website is the day before launch, every comment turns into a conflict. It is too late to redo things, and accepting the result as is feels wrong. A healthy process looks different. First you approve the structure, then the homepage design, then the inner pages, and only after that does development begin.
Contract, timelines, and what the price includes
Verbal agreements work right up until the first disagreement. Standard practice is a contract that fixes the scope of work, stages, deadlines, and the number of revision rounds. It protects both sides: you know what you will get and when, and the agency knows the task will not grow endlessly.
Discuss separately what is included in the price and what is not. Typical grey areas that later grow into conflicts:
- who writes the page copy, the agency, a copywriter, or you;
- where photos and illustrations come from and who pays for licenses;
- integrations with CRM, payments, and delivery services;
- hosting, domain, and business email setup;
- basic SEO setup such as meta tags, sitemap, and redirects.
For timelines, use realistic ranges as a benchmark:
| Project type | Approximate timeline |
|---|---|
| Landing page on a ready-made template | 1-2 weeks |
| Landing page with a unique design | 3-4 weeks |
| Corporate website on a template | 2-3 weeks |
| Corporate website with a unique design on WordPress | up to 2 months |
| Online store on a template | 2-4 weeks |
| Online store with a unique design | 2-3 months |
| Complex custom project on Laravel | up to 4 months |
If a proposal promises much shorter timelines, ask what exactly gets cut.
This article deliberately says nothing about budgets. Current price ranges are listed on our service pages, for example the e-commerce development page.
What happens after launch
Launch is not the finish line, it is the start of daily operation. Clarify three things before the work begins.
Warranty. Bugs found after launch should be fixed free of charge within an agreed period. The warranty term and what it covers should be written into the contract, not exist as a verbal promise.
Support. Someone has to update the CMS and plugins, make backups, and monitor uptime. It can be your own employee or a dedicated support service on the agency’s side. The point is that the question should not hang in the air. An unmaintained website gradually becomes slow and vulnerable.
Ownership. The domain is registered to you, the hosting is paid from your account, and you hold all the credentials — admin panel, FTP or SSH, database, email. The source code and project materials are handed over to you. If the website runs on an open CMS such as WordPress or OpenCart, any other developer can pick up the work. This is your insurance in case the cooperation with the agency ever ends.
Red flags: when it is better to keep looking
None of these signals alone is a verdict, but two or three together are a serious reason to stop.
- “A website in 3 days and the top of Google in a week”. In three days you can deploy a template with borrowed texts. Search rankings are never instant, they take months of systematic work, and no agency controls search engine algorithms.
- A price far below the market with no explanation. Sometimes a low price has an honest reason: a young studio building its portfolio. But if there is no explanation, you usually pay the difference later, in revisions, delays, or a full redo.
- A demand for full prepayment. A request to pay the entire sum upfront, or the absence of a staged payment schedule, should put you on guard. A healthy option is to split payments into stages tied to results — an advance, interim payments after approved milestones, and the balance after launch. That way both sides share the risk evenly.
- Refusal to show live projects. “Everything is under NDA” in response to a request to see at least one working site is a bad sign. Even agencies with corporate clients have projects they can show.
- “All inclusive” without an itemized scope. If the proposal is a single figure with no breakdown, you do not know what you are buying. Any additional task will later turn out to be “not included”.
- No one to sign a contract with. If the contractor avoids formal paperwork and works purely “on trust”, you have no legal protection. A proper agency operates as a legally registered business, a sole proprietor or a company, and and signs the contract in the name of that legal entity.
- The website stays on the agency’s accounts. The domain, hosting, and admin panel registered to the contractor is a classic client lock-in scheme. While things are fine, you will not notice it. Problems start the moment you want to change something.
Questions to ask a web agency and how to compare proposals
Questions worth asking before signing the contract
- Show me 5 live projects similar to mine. What exactly did you do in them?
- Can you share the contacts of a few clients I could talk to about working with you?
- What stages will the work consist of, and what will I see after each one?
- Who will be my contact person and how quickly do you respond?
- What is included in the price and what is billed separately?
- How is the payment schedule structured?
- How many revision rounds are included at the design stage?
- What are the deadlines, and what happens if they slip through the agency’s fault?
- Who will the domain and hosting be registered to?
- Do you hand over the source code and all credentials after launch?
- What about the warranty and post-launch support?
Compare proposals on more than price
Comparing the numbers in proposals is pointless until you bring them to the same scope. One offer may be cheaper because it does not include copy, integrations, or mobile adaptation. So:
- write one list of requirements and send it to every candidate;
- compare the scope of work, not just the total;
- factor in timelines, warranty, and support terms;
- assess the quality of communication during negotiations, from how quickly they reply to whether they ask clarifying questions about your business.
The last point is underrated. An agency that starts by asking about your customers, competitors, and the website’s goals will most likely build a useful tool. An agency that talks only about colors and buttons from day one will build a picture.
Conclusions
A reliable web agency is recognizable by simple signs: a live portfolio you can open and click through, a clear process with intermediate reviews, a contract with a fixed scope and deadlines, an honest answer to “what is not included in the price”, and a full handover of credentials after launch.
The red flags are just as simple: unrealistic deadlines and promised top search positions, an inexplicably low price, a demand for full prepayment, refusal to show real work, and a website kept on someone else’s accounts. Each of these signals on its own can still be explained, but a combination of them almost always means trouble ahead.
We at Amidcode, a web agency from Kyiv, have been working since 2012 and have delivered more than 300 projects in that time. So this checklist is not theory, behind every point there are real stories, including websites that came to us for rescue after an unfortunate choice of contractor. One such example is the 911 Balsam online store, where after a rebuild we reached fourfold growth in online sales.
If you are choosing a developer for your website right now, take a look at our live work on the portfolio page and read how we run projects on the service pages: corporate websites, online stores, and project support. And if it is easier to just talk, write to us, and we will tell you honestly whether your task is a fit.