Choosing an agency is a decision about how your project will be understood, built and maintained. A portfolio can show visual quality, but it cannot tell you everything about the working relationship. The most useful questions reveal how the team handles uncertainty and who will take responsibility for the details.
Look for relevant problems, not matching industries
Ask to see work with similar complexity: a publishing workflow, a customer portal, a booking journey or a product with several user roles. An agency does not need an identical project in its portfolio to understand yours, but it should explain how its experience applies.
Discuss one project in detail. What did the team actually deliver? Which decisions were difficult? What changed during the build? Clear answers tell you more than a list of client logos.
Meet the people who will do the work
Find out who handles discovery, design, development and testing. Ask who attends reviews and who has authority to make a decision. Team size alone does not establish quality; the important thing is whether the proposed team has the skills and capacity your project needs.
If specialists or delivery partners are involved, understand their role. You should know where feedback goes and who is accountable for bringing the pieces together.
Compare estimates on the same basis
An estimate is only meaningful alongside its assumptions. Check the number of page templates or workflows, content responsibilities, integrations, migration work, testing and handover. A lower figure may describe a smaller project.
Ask how new requests are assessed and agreed. A sensible process makes the effect on cost and timing visible before work begins. It should also give you a way to exchange lower-priority features for more valuable ones.
Ask how progress becomes reviewable
Agree on the evidence you will see: a prototype, a working journey in a staging environment or a tested integration. Regular reviews help you catch misunderstandings before they become expensive changes.
Provide feedback through one agreed owner. Separate a usability problem from a personal preference and explain the context. “Customers need to compare these plans” is more useful than prescribing a different button colour.
Agree the handover before signing
Confirm ownership and access for the code, design files, hosting and service accounts. Discuss documentation, deployment and what happens if another team takes over. These are ordinary delivery questions, not a sign of distrust.
Clarify the difference between fixing defects, maintaining dependencies and developing new features. Ask who monitors the live product and how support requests are handled. The right agency should make these arrangements understandable before you commit.