A good portfolio is a minimum requirement, not a distinguishing factor: nearly every agency can show a few nice projects. The questions that reveal the difference are about ownership, process and what happens when the project is finished.
1. Will I own the code and the design?
With some agencies you remain dependent on their platform or licence, even after delivery. Ask explicitly whether you become the full owner of code, design and content when the project is done, without a licence that ties you to that agency.
2. Who actually works on my project?
At larger agencies you often talk to an account manager who passes the work on to a separate team, or even to another agency. Ask who the actual builders are, and whether you have direct contact with them during the project.
3. What happens after launch?
A website or app is never really "finished". Ask about the maintenance model: who keeps the site secure and up to date, and at what cost? An agency that is vague about this often leaves you out in the cold after delivery.
4 and 5. Price and timeline in writing
A fixed price upfront, instead of an estimate that "will probably be about right", prevents unpleasant surprises. Also ask for a realistic timeline with milestones along the way, not just a delivery date at the end.
6. How transparent is communication during the project?
Ask in the introductory call what communication looks like once the project is running: do you get access to a working interim version, or do you only see something at delivery? An agency willing to let you look along gives you the chance to adjust before something is "finished". An agency that brushes it off with "you will see it at delivery" does not.
7. What happens when things go wrong?
Not every project runs perfectly, and an agency that is honest about that is more reliable than one that only tells success stories. Ask how an agency handles a missed deadline, a bug after launch, or a change you want to make halfway. The answer says more about the collaboration than any portfolio.
A short checklist for the first call
Take these seven questions literally to a first call: ownership of code and design, who actually builds, what happens after launch, a fixed price, a realistic timeline with milestones, how communication works during the project, and how setbacks are handled. An agency that gives a clear, concrete answer to all seven without dodging deserves serious consideration. Vagueness on more than one of them is a reason to ask further, not to let it slide.
Warning signs to take seriously
A few concrete warning signs from practice. A quote much lower than all others without a clear reason: often parts are missing that come back later as extra work. An agency unwilling to share a single reference or contact from previous clients: a healthy agency has clients willing to answer a few questions. Pressure to sign quickly, with an "offer that expires tomorrow": a well-founded quote still stands in two weeks.
None of these automatically means an agency is unreliable, but they are reasons to ask extra questions before you sign. An agency that responds confidently and transparently to critical questions gives you more confidence than one that gets defensive.
Small agency or large agency: what suits you
Large agencies have more capacity and can pick up bigger, more complex projects in parallel, but often have a layer of account management between you and the actual builders. Small agencies and independent teams usually work more directly, with shorter lines and more personal involvement in each project, but have limited capacity for several large projects at once.
Neither is better across the board: a large, complex project involving several departments is sometimes better off with a larger agency. A clear-cut project where speed, direct communication and personal involvement matter most often fits a smaller team better. Know which of the two weighs heaviest for you before you choose.
What references really tell you
Do not just ask whether an agency has references; actually call or email a few. The most useful questions: did communication go as promised, was the deadline met, and perhaps most importantly, how did the agency handle something that did not go right straight away? Every project hits a bump sometimes; how it is handled says more about an agency’s reliability than a smooth first impression in the sales conversation.
Why TechGents starts with these questions
We are a small team ourselves: no account managers, no layers in between. From the first call you speak with the people who actually build your project. That is not a marketing line; it is why we like to answer the questions above before a potential client asks them: ownership of code and design is standard, a fixed price always follows an introductory call, and maintenance after launch is a choice, not an obligation.
The sales conversation versus the actual project
Almost every agency is at its best in the first conversation: enthusiastic, responsive, full of good ideas. It is wiser to judge how an agency behaves after the quote is signed than in the sales conversation before. So ask explicitly: what does contact look like once we have a deal, who do I communicate with, and how quickly can I expect an answer to a question halfway through? An agency that can answer concretely has clearly thought about it before. One that stays vague leaves you guessing what changes after the signature.
The role of a written quote
A verbal promise is no substitute for a detailed written quote. Everything discussed, from scope to price to timeline, should be in writing before the project starts. It protects both sides: you know exactly what you are entitled to, and the agency knows exactly what is expected. In a disagreement halfway through, a clear quote is the first thing both parties fall back on, and an agency that handles it carefully prevents most discussions before they start.