Intro: where does the cost of the wrong agency land?
Most software project failures are not about technical incompetence; they're about starting the journey with the wrong team. An agency may write code fast but make wrong decisions — the product launches in 6 months, then 18 months are spent rewriting and paying off maintenance debt.
This article lists 10 questions you must ask during the proposal phase. The answers reveal not just technical capacity but process maturity, contract transparency, and seriousness about long-term partnership.
1. Who is technically responsible for this project?
The answer should typically be two people: a named tech lead (architecture decisions) and a delivery / project manager (sprints, demos, reporting). "Our team handles it" is a red flag; diluted responsibility slows down decisions.
Get to know the tech lead. Years of experience? What similar products have they shipped? Will they be in the weekly demo, or only at kickoff?
Good answer: "Tech lead is Tolga, 8 years in SaaS and fintech. Joins every weekly demo. Architecture decisions don't change without their input."
2. How does your delivery rhythm work?
Sprint length, demo cadence, reporting format must be clear. "Demo every two weeks, written summary after demo, scope and risk list at the end of each sprint" is an answer. "We'll show you when it's done" is not.
Daily communication channel must be defined. Slack/Teams/email — which? How fast is response on a critical bug? If these aren't set before the contract, every urgent moment turns into a fight.
For remote teams especially, async + sync balance must be planned. Critical if you're in a different timezone from Turkey.
3. How are scope changes handled?
No project finishes with the original scope. A good agency accepts this upfront and writes the change request process into the contract: "New feature request → scope analysis → additional quote → approval → added to sprint".
Bad answer: "We'll see when we get there." That phrase produces two outcomes — surprise invoices, or quietly added unpaid work that drags down quality later.
Good answer: "We collect requests at the start of the sprint. Small changes go into the same sprint (free or low cost); larger features get a separate quote." Transparency builds trust.
4. What technologies do you use, and why?
The answer should be "fits this project", not "is on trend". Next.js + TypeScript + Postgres is a solid default for modern web; Flutter or React Native for mobile. But every project differs; the agency must justify their choice.
Ask: "Why Next.js and not Vue? Will this choice scale? How many people on your team know this stack?" Stacks dependent on a single senior carry bus-factor risk.
Also ask about vendor lock-in. If you stop working with this agency, can another team pick up the code? Standard stacks and open-source dependencies reduce this risk.
5. Do code and data ownership transfer to me with delivery?
The standard answer should be: yes, fully. Code lives in your GitHub/GitLab repository under your account; database in your hosting; domain in your name. If the agency says "hosted on our infra", vendor lock-in has begun.
IP transfer must be explicit in the contract. "All delivered source code, design files, and documentation are owned by the Client" — non-negotiable.
Check third-party library licenses too. If the agency uses GPL code in a way incompatible with your contract, you face the issue later.
6. How are KVKK, security, and backups handled?
For any application storing customer data, KVKK / GDPR compliance is not negotiable. The agency should have ready answers: TLS 1.2+ in transit, AES-256 / bcrypt at rest, password hashing, role-based access, audit logs, regular backups, disaster recovery plan.
Backup strategy must be specific: how often (daily? hourly?), where stored (different region?), restore tested? "Automatic" is not enough.
If your project is in healthcare, finance, or public sector, ask whether the agency has implemented relevant standards (HIPAA, PCI-DSS, ISO 27001).
7. What is the maintenance and next-phase model?
First delivery is not the end of the project. There must be a clear maintenance contract for post-launch bugs, small improvements, and new feature requests.
Ask: "What's the warranty period? (Typical: 30-60-90 days, critical bugs fixed free.) After that, what's the maintenance model? Monthly retainer, hourly, hybrid?"
A healthy structure: 60 days free warranty + hourly or retainer afterward. Be suspicious if maintenance is presented as free; real maintenance costs money — if hidden, it surfaces somewhere else.
8. Who delivered similar past projects — can you provide references?
Portfolio is not enough; ask for active references. Get the past customer's phone or email and talk directly. "What went well during the process, what went badly? Would you work with them again?"
Deeper question: "In a similar scale + sector, how many projects have you delivered in the past 12 months?" The reference quality matters, but so does the team's recent shipping cadence — how alive is the agency?
Negative signal: agency avoids sharing references, projects are 3+ years old, customer contact info is withheld. Alarms should ring.
9. What is the contract + billing model?
Three core models exist: fixed price (clear scope, lower client risk but agency bears risk), T&M / hourly (flexible but unclear budget), hybrid (core scope fixed + extras hourly).
Which is right for you? Clear scope → fixed price. Fast iteration and constant change → T&M. For most enterprise projects, hybrid is healthiest.
Other contract points: payment plan (deposit + 20-30-30-20 by milestone), late penalties, KVKK / GDPR clauses, cancellation rights and conditions, dispute resolution venue.
10. If you'd reject this project and refer it elsewhere, would you say so?
This question is the strongest filter. A good agency says yes. A team that can say "this isn't our specialty, I'd recommend you talk to firm X" is one you can trust.
An agency that says "we take every project" is likely mediocre on most of them. An expert agency stepping back from a poor fit is a positive signal.
Bottom line: choosing a software agency is a five-year business decision. The wrong pick locks your data into a foreign platform; the right one is infrastructure that grows with you. Ask these 10 questions before signing.
Conclusion
Few agencies will give clear answers to all 10 questions. Work with one that clarifies as many as possible and says "let's plan this together" for the rest. Transparency, speed, and long-term partnership start there.
At CreativeCode, we welcome you to test our proposal process — designed to answer these questions openly — through our project request page.
Related services
Related articles
Other articles that support the same decision
Mobile
How to Evaluate a Flutter Developer or Team
Choosing a Flutter developer is not just about coding skill — it's architecture, state management, performance, testing, and delivery discipline. A 7-criterion practical guide.
Proposal Process
How to Prepare a Project Before Requesting a Proposal
A 6-section preparation checklist for faster, more accurate proposals: goal, scope, references, budget, GDPR/KVKK, documentation. Good preparation doubles proposal quality.
Cost Analysis
Mobile App Cost in 2026: What Actually Sets the Price?
$10K or $200K? Mobile app cost is set by 7 line items: scope, backend, integrations, native need, testing+security, maintenance, phased approach. Concrete ranges per item.
Next step
If you are planning a similar project, we can clarify the scope and shape the right proposal flow together.
Start a project request