We manufacture furniture and had an order tracking system built. The contract said 3 months, it's been 6 and it's still not done. We've paid 70% of the money.
Every time I call, they say "it'll be done this week." Here's what happened to us: we saw two demos, both had the same missing features.
I don't know what to do now. Should I wait, go to a lawyer, or hand it over to another agency? Has anyone else been through this?
First off, I'm giving general info, not legal advice; I can't give specific recommendations without seeing your file.
The first thing to do in this situation is to turn verbal follow-ups into written ones. Saying "it'll be done this week" on the phone has no evidentiary value. Summarize every subsequent meeting via email: "in today's meeting, it was stated that delivery will be made on [date]."
The second step is to check what the contract stipulates for delays. If there's a penalty clause, you usually need to put them in default first, i.e., send a proper formal notice. The content and timeline of this notice are important, don't just download a template and send it.
The third step is to secure what you have: request the delivery of the existing code, database, and design files if any. This is the most common thing lost when disputes escalate; it's much easier to ask while the relationship is still good.
If you're thinking about handing it over, this third step is essential. If you don't have working code in hand, there's no handover, just a rebuild.
Let me speak from the agency side, I won't make excuses but I'll try to diagnose the issue.
1. In the vast majority of 3-month projects that take 6 months, the reason is the same: the agency took on more work than their capacity allows, and your project got pushed back because you're the least vocal client.
The phrase "it'll be done this week" is usually not a lie, but a wish. That week another client yells and the team shifts there.
3. The most effective thing you can do is ask for weekly visibility instead of just dates. A written progress report every Friday: what was finished this week, what will be finished next week, what are the blockers. If the same thing is written two weeks in a row, you have your answer.
4. Before handing it over, definitely get a technical review. Taking over a project that's 70% paid but only 20% done is more expensive than starting from scratch. Don't make a decision without knowing this.
I've been doing this for twenty years, and I've done many takeover reviews. Let me list what to look for, don't rush.
The first thing to check is whether the code is stored somewhere. Is version control being used, is there history? If not, that's the clearest sign the work isn't being managed properly.
Second, does it run? If the code doesn't launch on another machine when you get it, it hasn't been delivered.
Third, the database structure. Missing screens can be fixed. If the data model is wrong, you can't build on top of it, you have to tear it down.
Have someone who can assess these three things in a day look at it. A small cost for a very big decision.
Gökhan Bey, let me list what you should do step by step, you can handle this within this week:
Today: gather all correspondence from the last six months into a single folder, in chronological order. Put the contract next to it too.
Tomorrow: send a written email to the agency asking for three things — an up-to-date status report, a dated list of remaining tasks, and a copy of the current code and database. Be polite but clear.
If they reply: get the technical review Volkan Bey mentioned, then make your decision.
If they don't reply or try to brush you off: move to the formal notice stage Kemal Bey mentioned; at this point, you really need to work with a lawyer.
For some moral support: this situation is way more common than you think, and most cases get resolved without going to court. Stay calm, keep everything in writing, and take control of the process.
Thanks a lot, I sent the email asking for a written report yesterday, and they called today.
Here's what happened on our end: for the first time, they sent a real list, and it turned out most of the missing items were just waiting for our approval. So it's not entirely their fault, I'll be honest about that. Still, the fact that no one told us this for six months is a separate issue.
I'll also get the technical review done and post the results here.
The most overlooked point about delivery is this: Taking notes for two weeks yields better results than a six-month estimate.
This is my opinion, I'm not claiming it's absolute truth.
I partly agree, partly disagree. Payment schedules should be tied to project phases not calendar dates.
Hope this helps.
Doki · Infrastructure migration · 2026
For the record: the most common mistake in this area is relying on a single preventive measure. Go layer by layer — if one fails, the other stops it.
Let me clarify the technical side. The real issue isnt the number, but what its based on.
Everything goes well for the first three months; problems arise in the fourth.
The opposite happened to me, that's why I'm writing. Start with a small trial; don't commit to everything at once.
Hope this helps.