10 Questions to Ask a Next.js Agency Before You Pay a Single Dollar | Aizecs

The most expensive mistake a non-technical founder makes is not hiring the wrong agency. It is hiring the wrong agency and not knowing it until month three — when the budget is half gone, the timeline has slipped twice, and the codebase looks nothing like what was described on the sales call.

You cannot read their code. You cannot evaluate their architecture decisions. You cannot tell from a GitHub profile whether the developer assigned to your project is genuinely senior or recently promoted themselves. And the agencies that are going to disappoint you know all of this which is why their sales calls are polished, their case studies are curated, and their proposals are long on process language and short on specific commitments.

What you can do is ask the right questions. Not the questions agencies expect — "what is your process?" and "do you have experience in our industry?" but the questions that reveal the gap between how an agency presents itself and how it actually operates.

These ten questions are the ones that separate agencies that ship from agencies that stall. Ask every single one of them before you pay anything.

Question 1: "Can you show me a live URL you built and deployed in the last 90 days?"

Not a case study. Not a PDF with screenshots. Not a Behance portfolio. A live URL you can open on your phone right now, navigate through, and experience as a real user.

This question has one purpose: to test whether the agency's output meets a production standard under real conditions. A live product that loads in under two seconds on mobile, handles user flows without breaking, and has been stable for months tells you more about an agency's capabilities than any proposal ever will.

The answer that should concern you is not "we can't share client work due to NDAs" — that is sometimes legitimate. The answer that should end the conversation is a long pause followed by a portfolio site with mockups and testimonials but no working URLs. Every legitimate Next.js agency that ships production-grade work has at least one product they can show you live.

When you get the URL — open it on your phone on a 4G connection. Run it through PageSpeed Insights. If the mobile score is below 70, you are looking at either old work that has not been maintained or a team that does not prioritise the performance metrics that determine your search rankings and your users' experience. Both are disqualifying.

Question 2: "How long after signing does a developer actually start writing code on my project?"

This question exposes the onboarding gap that burns the first month of most agency retainers.

The standard agency onboarding process looks like this: one week for contracts and paperwork, one week for a discovery session and requirements document, one week for the PRD review and approval, one week for "sprint zero" setup. By the time a developer writes the first line of production code, you have paid for four weeks and received a document.

The answer you are looking for is measured in hours, not weeks. An agency that has its process dialled in that has a brief template, a development environment ready, and developers who can orient themselves from a well-written brief should be able to start writing production code within 24–48 hours of a completed scoping call.

At Aizecs, the sequence is: contact form submission → 12-hour response → same-day scoping call → working prototype on a live staging URL within 24 hours of that call. Not a plan for a prototype. A clickable, deployed Next.js prototype you can open before the next morning.

Ask every agency you speak to: "If I sign today and give you everything you need — access, brief, design files — when will I see a working staging URL?" If the answer is more than 72 hours, ask why. The answer will tell you whether the delay is a process they have built deliberately or an inefficiency they have never thought to question.

Question 3: "What does your daily update look like — can you show me an example?"

Communication failure is the single most common reason agency relationships break down and it is entirely predictable and preventable if you know what to look for before you sign.

The agencies that fail on communication do not fail because they do not care. They fail because their communication standard is undefined, each developer communicates differently, each project manager has a different cadence, and "we'll keep you updated" means something different to every person on the team.

Ask for a specific example. A screenshot of a Slack update. A sample Loom link. A weekly report from a previous client engagement. If they cannot produce a concrete example of what client communication looks like in practice, they do not have a standard. They have a sales promise.

The update you should expect from a production-grade agency: a daily message that says what was built today, what the current staging URL shows, what question or decision is needed from you before tomorrow, and whether the sprint is on track for Friday delivery. Five sentences. Sent every working day. Not a weekly check-in, not a "just wanted to let you know we're making progress" — specific, actionable, reviewable.

This matters especially for non-technical founders because the daily update is your window into the build. You cannot read the code. But you can open the staging URL every morning and see whether the product is moving in the right direction. An agency that sends you a live staging URL update every single day is an agency you can hold accountable without technical knowledge.

Question 4: "What happens if I'm not happy with what you deliver at the end of the first sprint?"

This question separates agencies that are confident in their output from agencies that are banking on your reluctance to have a difficult conversation.

The answer you are looking for is simple and immediate: "We fix it. Tell us specifically what doesn't match the brief and we address it in the next sprint at no additional charge."

The answers that should concern you:

"We'll discuss scope at that point" — this means revision is a billing event and you will be negotiating against your own brief.

"That hasn't happened with our clients" — this is not an answer to the question. Every agency has delivered something a client was not happy with. The question is what they do when it happens.

"It depends on what was agreed in the contract" — the contract will always be interpreted in their favour when there is ambiguity. What you need is a cultural commitment to quality, not a legal framework for disputes.

Ask a follow-up: "If the prototype you deliver in the first week looks nothing like what I briefed, what is the process?" An agency that answers this confidently — "show us specifically what doesn't match, we'll fix it before we charge for the next sprint" has a quality culture that protects you. An agency that hedges has a billing culture that protects itself.

Question 5: "Do you charge for meetings, calls, or Slack messages outside the sprint?"

Ask this question directly. Do not soften it. Do not frame it as a hypothetical. Ask it exactly as written and wait for the specific answer.

The agencies that charge for every interaction — $150 for a 30-minute call, $75 for a Slack thread that runs long, $200 for a button change that takes 20 minutes produce a specific and predictable client behaviour: founders stop communicating. They batch questions. They avoid feedback conversations. They let misalignments run for a week because raising them costs money.

The product that gets built in that environment is the product that would have been built if the founder had never given any feedback after the initial brief. It is the agency's interpretation of your idea, unmodified by the ongoing conversation that every good product requires.

When an agency says "all communication is included in the monthly retainer", verify it. Ask: "If I send 15 Slack messages in a day, is that included? If we have a 45-minute call to review the staging URL, is that included? If I ask for a layout change that takes 30 minutes, is that included?" Push on every scenario until the answer is unambiguous.

An agency that is genuinely confident in its value does not need to monetise the communication that produces it.

Question 6: "Who specifically will be working on my project — and can I speak to them before we start?"

Most agency sales calls are run by a founder, a business development lead, or a senior account manager. The person on the call is often not the person who will write your code. Ask explicitly: "Who will be the developer on my project?" and then: "Can I have a 20-minute technical call with them before we sign?"

This request does two things. First, it gives you a direct signal of seniority — a 20-minute conversation in which you ask the architecture question from our complete hiring guide tells you more about the developer's actual skill level than any credential the agency presents. Second, it tells you about the agency's confidence in their team. An agency that makes it easy to speak to the assigned developer is an agency that trusts their developer to represent them well.

An agency that deflects this request — "our developers are focused on delivery, we handle all client communication centrally" is an agency that does not want you to evaluate the developer directly. That is worth understanding before you sign.

Question 7: "What does your codebase handoff look like if we end the engagement?"

This question reveals something no agency talks about in sales calls: what happens to your product and your code when the relationship ends.

There are two types of agencies. Agencies that build on infrastructure you fully own, your GitHub repository, your Vercel account, your database, your domain and hand everything over cleanly when the engagement concludes. And agencies that build on their own infrastructure, their own accounts, and their own tooling creating a dependency that makes switching painful and sometimes nearly impossible.

The second type is not always acting in bad faith. Sometimes it is simply the path of least resistance, it is easier for the agency to manage everything centrally. But the effect for you is lock-in: you cannot leave easily, which means the agency has less incentive to continue earning your business.

Ask: "If we end this engagement tomorrow, what do I walk away with and how do I access it?" The complete answer is: full GitHub repository ownership under your account, Vercel project ownership transferred to your account, all environment variables and API keys documented and handed over, and no proprietary tooling that only works inside the agency's systems.

Anything less than this is a degree of lock-in. Know what degree you are accepting before you sign.

Question 8: "Can you show me a project where something went wrong and what did you do?"

This is the question most founders never ask. It is the most revealing question on this list.

Every agency has a project that went wrong. A timeline that slipped. A scope that was misjudged. A feature that had to be rebuilt after delivery. The agencies that have genuinely learned from these experiences can describe them specifically — what happened, why it happened, what they changed as a result. The agencies that have not learned from them either cannot remember a specific example or describe every past problem as the client's fault.

What you are not looking for is a perfect record. You are looking for self-awareness and accountability. A founder who hears "we had a project last year where we underestimated the complexity of a payment integration and delivered two days late, we now include a complexity buffer in every payment sprint estimate" should feel more confident, not less. That agency has encountered the real world and adapted to it.

The agency that has never had a project go wrong has either never taken on anything challenging enough to go wrong, or is not being honest with you.

Question 9: "What is the minimum contract length and what are the exit terms?"

The minimum contract length question is a direct test of agency confidence. An agency that requires a 6-month minimum contract before you have seen a single staging URL is an agency that knows the first month may not be impressive enough to earn a second month voluntarily.

An agency that offers a 30-day exit clause or better, a sprint-by-sprint model where each sprint is independently scoped and priced is an agency that is betting on the quality of the work to earn the continued relationship. That is the bet you want your agency to be making.

Ask specifically: "If after the first sprint the work doesn't meet the standard we agreed on, what is my exit? What have I paid for and what do I owe?" The answer should be: you pay for the sprint that was delivered, you own everything that was built, and you owe nothing further.

Anything that makes this exit more complicated — a retainer that does not refund for undelivered work, a minimum term that continues regardless of quality, a proprietary system that makes the code difficult to transfer is a contractual risk that should be understood explicitly before signing.

Question 10: "What is the one thing most clients get wrong when briefing you and how do I avoid it?"

This is the question that tells you whether the agency is a vendor or a partner.

A vendor answers this question generically or not at all: "Just make sure you have all your requirements ready." A partner answers it specifically and honestly — because they have seen the same briefing mistakes across enough client engagements to know exactly what goes wrong and exactly what to do about it.

The honest answer to this question, from our experience across 40+ Next.js builds, is this: most founders brief the solution rather than the problem. They describe the feature they want — "I need a dashboard with three charts and a filter" rather than the user outcome they need — "a user needs to understand their pipeline health in under 30 seconds without asking the sales team."

When you brief the solution, the developer builds exactly what you described and if what you described was not quite right, you discover it after delivery. When you brief the outcome, the developer can tell you if your proposed solution is the best way to get there or if there is a simpler, faster, cheaper approach that achieves the same result.

An agency that tells you this before you sign that coaches you toward better briefing before the project starts is an agency that is optimising for your outcome, not for minimising revision scope.

Answers That Should End the Conversation Immediately

After ten conversations with ten different agencies, you will have a matrix of answers. Some will be strong across all ten questions. Most will be strong on the questions they anticipated and weak on the ones they did not.

The answers that are individually disqualifying — regardless of how strong the agency is elsewhere:

No live URL available — non-negotiable. An agency that cannot show you a live production product has not built one recently or has not built one well.

Developer starts in 2+ weeks — process inefficiency that will compound across every sprint.

Revision is a billing event — a billing model that penalises the communication your product requires.

No access to the assigned developer — an agency hiding its execution layer from its clients.

6-month minimum contract before first delivery — confidence deficit disguised as a contract term.

Any one of these answers means the risk of the engagement is being transferred from the agency to you. A good agency absorbs the risk of its own quality. A bad one distributes it to clients through contracts, billing models, and process barriers that make it expensive to hold them accountable.

How Aizecs Answers All Ten Questions

We are going to answer our own questions directly because if we are asking you to hold other agencies to this standard, you should be able to hold us to it too.

Live URL in the last 90 days: Yes — ask us on the call and we will share three.

Time to first working code: 24 hours from scoping call to live staging prototype. Not a plan. A URL.

Daily update example: Loom video or written standup, sent every working day. Ask us for a sample from a recent engagement on the call.

Unhappy with first sprint delivery: We fix it before the next sprint bill. Tell us specifically what does not match the brief.

Charges for meetings and Slack: No. Monthly retainer covers all communication, all calls, all small changes.

Access to assigned developer: Yes. We encourage a 20-minute technical call with your developer before sprint one begins.

Codebase handoff: Full GitHub repository ownership under your account from Day 1. Vercel project under your account. Full documentation on exit. No lock-in.

A project that went wrong: Yes, we will describe one specifically on the call. Ask us.

Minimum contract length: No minimum. Sprint-by-sprint model. 30-day exit clause on dedicated engagements. You pay for what was delivered and nothing more.

What clients get wrong: Briefing the solution instead of the outcome. We include a brief template with every engagement that corrects this before the first sprint starts.

These are not marketing answers. They are operational commitments we make to every client and hold ourselves to across every engagement. If any of them are not true in your experience with us, that is the conversation we need to have.

Founder Who Asks These Questions Hires Better

The reason most non-technical founders hire the wrong agency is not that they are bad at evaluating people. It is that they walk into agency calls without a framework for what to look for and the agency's well-practised sales process fills the vacuum.

The founder who walks in with these ten questions controls the conversation. They are evaluating the agency, not being sold by it. And they discover within 45 minutes whether the agency in front of them is the kind of partner who will ship their product or the kind who will spend three months explaining why it is taking longer than expected.

The question that matters most — the one that contains all the others is this: "Does this agency make it easy to hold them accountable?"

A live URL. A 24-hour prototype. Daily updates. No hidden billing. Sprint-by-sprint exit. Full code ownership.

If all ten of those answers are yes, you have found an agency worth trusting with your product.

Want to hear our answers to all ten questions in real time?

Book a call. We will answer every question on this list before you decide anything and we will show you a live staging prototype within 24 hours of that call.

→ Start at aizecs.com/contact