rapidlaunchcode.app
Enterprise StarterAdvisoryEngineeringProductsWritingAbout
Book a call
rapidlaunchcode.app

Independent technology advisory and engineering. København, Denmark.

Njalsgade 21F, 2. sal, København

CVR 45 44 13 93

Nicklas@rapidlaunchcode.app

WhatsApp +45 31 33 25 99

Work

  • Enterprise Starter
  • Advisory
  • Engineering
  • Products
  • Contact

Resources

  • Writing
  • Guides
  • Free tools
  • About

Elsewhere

  • HourIQ
  • Translately
  • NomadWorld
  • Privacy

© 2026 Rapid Launch Code ApS. All rights reserved.

Built in København with Next.js, Contentful, and zero consultancy bullshit.

Back to guides
3 min · HIRING & VETTING

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.

On this page
  • The ten questions
  • What to listen for in the answers
Updated 2026-04
TL;DR
  • Specific examples beat generic portfolio pieces. Ask for them.
  • Process questions reveal whether an estimate is real or invented.
  • Always ask who, by name, will write the code, and what their rate is.
  • Documentation and handover plans determine whether you're locked in.
  • If the agency can't articulate the trade-offs, they don't understand them.

The ten questions

  1. What similar projects have you completed? Look for specific examples with measurable outcomes. Generic portfolio pieces aren't enough.
  2. Can you give us references from those projects? If an agency won't, that's a red flag. Always call the references.
  3. What's your process for requirements gathering? If they're ready to quote a fixed price after one meeting, they're guessing.
  4. How do you handle scope changes? Look for a written change-request process and transparent pricing per change.
  5. What happens if the project goes over budget or timeline? Understand who bears the cost. "We'll work it out" means you bear it.
  6. 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.
  7. 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.
  8. How will you document the system? Documentation determines whether you're locked in. ADRs, runbooks, and architecture diagrams should be deliverables.
  9. What's included in post-launch support? Launch is the beginning, not the end. Get the warranty period and the SLA in writing.
  10. 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.

What to actually do
  • Send the ten questions in writing the day before the call. The good shops answer them in the meeting; the rest stall.
  • Insist on naming the people who will work on the project, with a CV per role.
  • Get the change-order process and the warranty period in the contract, not the email thread.
  • If the agency refuses to put references on the call, you don't have references.
  • The answer to "why this stack?" should mention your constraints, not their CVs.

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.

Book a 30-min callSee the Enterprise Starter
Related guides
  • 3 min

    The consultancy playbook

    How digital consultancies operate, how they price, and where Danish clients typically overpay.

  • 4 min

    How to evaluate agency proposals

    A step-by-step framework for comparing proposals, identifying red flags, and making informed vendor decisions.

  • 9 min

    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.