Founder of Goodspeed
The first meeting with a Codex agency sets the tone for everything that follows. Turn up unprepared and you spend the hour being pitched. Turn up prepared and you spend it working out whether this is the team that can actually build what you need. The difference is almost entirely in the preparation you do beforehand.
We are an AI engineering team that ships production software with coding agents like Codex and Claude Code, and we sit on both sides of these conversations. The clients who get the most out of a first meeting are not the ones with the most technical knowledge. They are the ones who arrive clear about the problem, honest about the constraints, and armed with the right questions.
This guide walks through exactly how to prepare, what to bring, what to ask, and the red flags to watch for while you are in the room.
Get clear on the problem before the solution
The single most useful thing you can do is arrive able to describe the problem, not the feature list. Agencies hear plenty of clients who lead with a solution they have half-designed in their head, and it narrows the conversation before it starts. What you actually want is a team that can hear the underlying problem and tell you the best way to solve it, which might not be what you first imagined.
Spend time before the meeting writing down what is genuinely broken or missing today, who feels that pain, and what would change if it were fixed. Keep it in plain business terms. A good agency will take that and translate it into an approach, and the quality of their translation is one of the strongest signals you will get about whether they think or just build.
Define what success actually looks like
Bring a clear picture of what a good outcome means for your business. Is it a specific process that gets faster, a manual job that disappears, revenue that becomes possible, or a product you can put in front of customers. The more concretely you can describe the result you want, the more useful the whole conversation becomes.
This matters more with agent-built software, because the speed of building can pull a project towards doing more rather than doing the right thing. If you and the agency agree early on what success looks like, you have a shared target to steer towards and to measure against later. Turning up without one means you are effectively asking them to decide what matters, which is not their job to guess.
Know your constraints and be honest about them
Constraints are not weaknesses to hide; they are essential information. Be ready to talk openly about budget, timeline, existing systems the software has to work with, security or compliance requirements, and who internally will be involved. Agencies that are worth hiring want these on the table early, because they shape what is realistic and how the work should be approached.
Being vague about budget in particular tends to waste everyone's time. You do not have to name an exact figure, but a range lets the agency tell you honestly whether your expectations and your budget line up, and what trade-offs might be needed. The same goes for deadlines and technical constraints. Honesty here leads to a realistic plan. Coyness leads to a proposal built on guesses that unravels later.
Bring the right materials
Come with anything that helps the agency understand your world quickly. That might be examples of the current process, screenshots or access to existing tools, relevant data samples where appropriate, notes on what you have tried before, and any documentation of requirements you already have. You do not need a formal brief, but concrete artefacts move the conversation faster than description alone.
If there are people in your organisation who understand the problem better than you do, consider whether they should be there or whether you should gather their input in advance. The goal is that the agency leaves the meeting with a genuine understanding of the problem, not a polite but shallow impression. Good raw material on your side makes their thinking sharper and their eventual proposal much more accurate.
Prepare your questions about how they build
This is where you learn whether they are a serious engineering team or a group riding the hype. Prepare to ask how they use Codex and other agents in their workflow, and listen for a grounded answer about where agents help and where human judgement takes over. Ask how they stop an agent shipping something wrong, and expect to hear about testing, review, and guardrails.
Ask to see production software they have built, not demos, and ask what happened after it launched. Ask who specifically will work on your project and how the work gets reviewed. These questions do more than gather information. They signal that you are a discerning buyer, which changes how the agency engages with you and tends to surface a more honest, less polished pitch.
Prepare questions about ownership and handover
Do not leave ownership to the contract stage. Ask in the first meeting who owns the code, the accounts, and the infrastructure, and what access you get. Ask what happens if the relationship ends and how handover works. You are listening for a clear, comfortable answer, because the good agencies have nothing to hide here and will state plainly that you own everything.
Hesitation or vagueness on ownership is one of the most useful early warning signs you can pick up. Software you cannot fully control is a long-term liability, and the first meeting is the cheapest possible moment to discover whether that risk exists. Raise it early, watch the reaction, and let the answer inform how much you trust everything else they tell you.
Think through post-launch from the start
Even in the first conversation, it is worth surfacing what happens after launch. Ask how they support software once it is live, how they monitor it, and how improvements get made over time. AI-built systems in particular benefit from ongoing attention as models, tools, and requirements change, and you want to know early whether the agency treats maintenance as core work or an afterthought.
Raising this in the first meeting also tells you something about how the agency thinks. Teams that build for the long term will engage readily, because they design with maintenance in mind. Teams focused only on getting to launch and moving on will give thin answers. You are not committing to anything by asking. You are finding out whether they build software meant to last or just to ship.
Decide who from your side should attend
The right people in the room make an enormous difference. You want whoever genuinely understands the problem and whoever has the authority to make decisions, because a meeting full of people who cannot commit to anything tends to stall. At the same time, avoid crowding it with observers who dilute the conversation without adding to it.
If the software touches a specific team's work, having someone from that team present gives the agency direct access to the reality of the problem, which sharpens their thinking. Just be clear beforehand about who is leading the conversation on your side, so the meeting has direction. A focused, well-chosen group gets far more from an hour than a large, uncertain one.
Red flags to watch for in the meeting
Pay attention to how the agency behaves, not just what they say. Be wary of anyone who sells the tool rather than the outcome, who cannot point to production software, or who talks around your questions about ownership and maintenance. Watch for a team that pushes their preferred solution before they have understood your problem, which suggests they build first and think second.
Other warning signs include overpromising on timeline and cost in a way that sounds too easy, vagueness about who will actually do the work, and any implication of official Codex credentials, which do not exist. None of these has to be disqualifying on its own, but each is a thread worth pulling. The first meeting is your best chance to notice them while it is still cheap to walk away.
Green flags that suggest a strong fit
Just as important is knowing what good looks like. Strong agencies ask you more questions than you ask them, because they are genuinely trying to understand the problem before proposing anything. They talk about outcomes and trade-offs rather than features and buzzwords, and they are relaxed and specific about ownership, testing, and what happens after launch.
You should also notice whether they push back. A team that challenges an assumption, or tells you honestly that part of what you want is a bad idea, is far more valuable than one that agrees with everything to win the work. Building with agents rewards clear thinking, and the agencies that think clearly will show it in how they interrogate your problem rather than how smoothly they pitch their answer.
Leave with a clear next step
A good first meeting ends with clarity about what happens next, not a vague promise to be in touch. You want to know what the agency will produce as a follow-up, whether that is a proposal, a scoped plan, or a recommendation, and roughly when. You should also leave with your own sense of whether the problem is understood and whether this is a team you would trust with it.
Take a moment afterwards to write down your honest impression while it is fresh. Did they grasp the problem, were the answers on rigour and ownership convincing, and did the conversation feel like genuine thinking or a rehearsed pitch. Those notes are worth more than any brochure, and they will guide the decision far better than the polish of the meeting itself.
Conclusion
Preparing for a first Codex agency meeting is mostly about clarity on your side and good questions for theirs. Arrive able to describe the problem, honest about your constraints, clear on what success looks like, and ready to probe how they build, who owns what, and what happens after launch. That preparation turns the meeting from a pitch you sit through into an assessment you control.
Do it well and you will leave knowing not just what the agency can do, but whether they actually understood your problem, which is the thing that matters most.
If you want a team that ships production software with AI coding agents, see our AI work, or book a free call with our AI engineering team.
Written By
Founder of Goodspeed