10 questions to ask before hiring an agency
These ten questions move the sales call from theatre to substance. If a Danish agency can't answer the first four on the spot, walk.
The ten questions
- What similar projects have you completed? Look for specific examples with measurable outcomes. Generic portfolio pieces aren't enough.
- Can you give us references from those projects? If an agency won't, that's a red flag. Always call the references.
- What's your process for requirements gathering? If they're ready to quote a fixed price after one meeting, they're guessing.
- How do you handle scope changes? Look for a written change-request process and transparent pricing per change.
- What happens if the project goes over budget or timeline? Understand who bears the cost. "We'll work it out" means you bear it.
- Who, by name, will actually work on my project? Senior salespeople aren't always the ones writing the code. Get the rate per role in writing.
- What's your approach to testing and QA? Testing should be in the process, not at the end. Ask for the test pyramid they actually run.
- How will you document the system? Documentation determines whether you're locked in. ADRs, runbooks, and architecture diagrams should be deliverables.
- What's included in post-launch support? Launch is the beginning, not the end. Get the warranty period and the SLA in writing.
- Why this technology stack for my project? Good answers reference your needs and constraints. Bad answers reference the agency's preferences.
What to listen for in the answers
The shape of a good answer is concrete and bounded. "We did a similar project for X, here is the architecture diagram, here is the launch metric, here is the contact you can call." The shape of a bad answer is generic and aspirational. "We follow agile best practices and partner closely with our clients." If you can't picture the deliverable from the answer, the answer is marketing.
Pay attention to who answers. If every question goes to the salesperson and never to a technical lead, you are buying a sales process, not engineering. Ask to speak with the developer who would actually build your system. Their candor will tell you more than the proposal will.
Want this kind of judgment on your project?
I read every email within one working day. Bring a project, a quote, or a system you're stuck on.
The consultancy playbook
How digital consultancies operate, how they price, and where Danish clients typically overpay.
How to evaluate agency proposals
A step-by-step framework for comparing proposals, identifying red flags, and making informed vendor decisions.
15 things every Contentful enterprise project gets wrong in the first 6 weeks
The 15 production gaps every enterprise Contentful + Next.js build hits in the first six weeks — and how to close each one without burning a sprint. A pre-kickoff checklist for technical leads on a Contentful enterprise starter.