A developer who answered within the hour for three months and then stops replying is one of the most stressful things that can happen to an owner with a custom system. The build is half finished, or the system is live and something has broken, and the one person who understands it is not picking up the phone. The instinct is to send an angry message, stop paying, or start looking for someone to take over at once. Those are usually the wrong first moves.
This guide is for owners and managers of small and medium businesses whose custom system, web app or mobile app has stalled, whether mid-build, after launch, or because the developer has left the company. It sets out what to do in the first week, what to put in one calm message, what a new builder will need before they can help, and how to choose between waiting, moving on, repairing and rebuilding. It is general guidance. It is not legal advice about contracts, unpaid invoices or disputes, and it describes no takeover, rescue or audit service.
Two related questions are covered elsewhere and linked rather than repeated. What the law and your contract say about who owns the code is in who owns the source code of your custom software. Who should hold the Apple and Google developer accounts is in app store developer accounts. If the person who went quiet built your website rather than a system, read what to do when your web designer disappears.
Three kinds of quiet, and why the difference matters
Not every silence is an abandoned project. The right response depends on which of these you are in, but the first step is the same for all three: collect facts before you react.
- Slow. Replies arrive late and dates slip, but there is contact and visible progress. This is a management problem, handled with clearer milestones and a regular check-in.
- Stalled. A date has been missed, messages go unanswered for days or weeks, or the answers are vague. Work may still be happening, or it may not.
- Gone. Calls, WhatsApp and email all go unanswered, the company has closed, or the one person who knew the system has left. Nobody on their side can tell you what exists.
A short silence can have ordinary causes: illness, a family matter, a freelancer juggling clients, a small company whose only developer resigned. Assume nothing about motive. Your job in week one is not to decide who is at fault. It is to make sure you know what you have and can reach it.
Week one, step one: write down what exists
Before sending anything, spend an hour building one page, or one folder, that records the facts. It protects you whichever way things go, and any new builder will ask for exactly this. Keep it somewhere that is not the developer’s own system, such as your own email or company drive.
| Item | Where to look | Why it matters |
|---|---|---|
| The quote or contract | Email, signed PDFs, WhatsApp attachments | Shows what was agreed, the stages, and what you should receive at the end |
| Invoices and what you paid | Your accounts, bank statements, receipts | Shows what has been paid for and which stage it matches |
| Messages and calls | Email, WhatsApp, meeting notes | A dated record of what was promised and when you last had a real reply |
| The system address | Browser bookmarks, the login page, staff devices | You cannot ask for the handover of something you cannot name |
| Who holds the hosting | Invoices, welcome emails, renewal notices | This is the server where the system lives. How to find who hosts a site works for systems too |
| Who holds the domain | Registrar emails, a registrant look-up | The address staff and customers type. See who owns your domain name |
| App-store accounts, if there is a mobile app | Developer-account emails, the store listing | Decides who can update, transfer or remove the app |
| Other services the system uses | Emails from a payment gateway, SMS, email-sending or maps provider | Each has its own account, its own bill and its own renewal |
| Who in your business has a login | Your staff list | Tells you whose login still works today |
Beside the table, add two dates: when you last had a real reply, and when the next payment or milestone is due. Do not delete or edit any message. If the developer was ever sent your logins or documents by email, note that too.
Check the basics: is the system running, and is it backed up?
A quiet developer is an inconvenience. A system that silently stops working, or a hosting or domain renewal that lapses, is a business problem. In week one, check four things without changing anything.
- Does it work today? Log in with your own staff account and do a normal, read-only task such as opening a recent order or report. Do not test by typing fake records into a live system.
- When do hosting, the domain and any outside services renew? Find the dates and the email address or card that receives the reminders. A lapse during a quiet period is the most avoidable way to lose a system. If the reminders go only to the developer, that is the first thing to fix.
- Where are the backups? Work out what is copied (the database, uploaded files, settings and code), how often, where the copies are kept, and who can restore them. If the only copy sits in the developer’s account, it is not really your backup. The questions to ask are in security basics for a custom business system, and the idea for websites is in the website backup guide.
- Can you keep a copy of what you can already reach? Many systems let a normal user export lists or reports to a spreadsheet. A recent export of customers, orders and stock is a modest but real safety net. Check with your team that exporting is allowed, and store the files securely because they contain customer data.
Send one calm written message with a reply-by date
One clear message beats ten anxious ones. Write it so that someone reading it a year from now, perhaps a new builder or a lawyer, would think it was fair. The aims are to get a reply, to create a record, and to leave the door open.
- Short and factual. Name the project, say when you last heard back, and list the specific things you are waiting for.
- A reply-by date. Give a real date, often about a week away, and say in neutral terms what you will do next, such as asking another developer for a read-only review of what has been built.
- A second contact. Ask who else on their side can answer if the main person is unavailable.
- Sent where it will be kept. Use email as the main record and a short WhatsApp message that points to it. Keep copies.
- Free of accusations. Do not guess at reasons or call anyone unprofessional. Facts and dates only.
Here is a template in English, Bahasa Malaysia and Chinese. The names, company and dates are made up, so change them to fit your situation. It also asks, softly, for the key records to be confirmed, so that your business has them on file whatever happens next. You can split that part into a second message if you prefer.
Example in English (made-up names)
Subject: Stock and ordering system: status update needed by Tuesday 24 November 2026
Hi Aiman,
I am writing about the stock and ordering system you are building for Orchard Trading. We last spoke on Monday 2 November, and I have not had a reply to my messages of 9 and 12 November.
Could you please reply by Tuesday 24 November 2026 with: (1) the current status and what is still to be done; (2) the date of the next delivery or update; and (3) another person on your side we can contact if you are unavailable.
So that our business has the key records on file, please also confirm where the latest source code, the documentation and the system logins are kept, and where the backups are stored.
We would like to keep working with you and finish this properly. If we do not hear from you by 24 November, we will ask another developer for a read-only review of what has been built, so that we can plan the next steps.
Thank you,
Mei Ling Tan, Orchard Trading
Contoh dalam Bahasa Malaysia (nama rekaan)
Subjek: Sistem stok dan pesanan: mohon kemas kini status sebelum Selasa 24 November 2026
Salam Aiman,
Saya menulis berkenaan sistem stok dan pesanan yang sedang anda bangunkan untuk Orchard Trading. Kali terakhir kita berbincang ialah pada Isnin 2 November, dan saya belum menerima balasan kepada mesej saya pada 9 dan 12 November.
Boleh anda balas sebelum Selasa 24 November 2026 dengan: (1) status semasa dan kerja yang masih tinggal; (2) tarikh penyerahan atau kemas kini yang seterusnya; dan (3) seorang lagi wakil di pihak anda yang boleh kami hubungi jika anda tidak dapat dihubungi.
Supaya syarikat kami mempunyai rekod penting dalam simpanan, mohon sahkan juga di mana kod sumber terkini, dokumentasi dan log masuk sistem disimpan, serta di mana salinan sandaran disimpan.
Kami ingin terus bekerjasama dengan anda dan menyiapkan projek ini dengan baik. Jika kami tidak mendengar daripada anda sebelum 24 November, kami akan meminta pembangun lain membuat semakan baca sahaja ke atas apa yang telah dibina, supaya kami dapat merancang langkah seterusnya.
Terima kasih,
Mei Ling Tan, Orchard Trading
中文示例(人名和公司均为虚构)
主题:库存与订单系统:请在 2026年11月24日(星期二)前告知进度
Aiman 您好:
我想跟您谈谈您为 Orchard Trading 开发的库存与订单系统。我们上一次联系是 11 月 2 日(星期一),我在 11 月 9 日和 12 日发的消息还没有收到回复。
请您在 2026年11月24日(星期二)前回复:(1)目前的进度和尚未完成的部分;(2)下一次交付或更新的日期;(3)如果您不方便,我们还可以联系贵方的哪一位同事。
为了让公司留存关键资料,也请您确认最新的源代码、文档和系统登录信息存放在哪里,以及备份保存在哪里。
我们希望继续与您合作,把项目好好完成。如果 11 月 24 日前仍没有收到您的回复,我们会请另一位开发人员对已完成的部分做只读审阅,以便规划下一步。
谢谢,
Mei Ling Tan,Orchard Trading
What not to do: threats, and a rushed stop in payment
Frustration makes some owners reach for the strongest lever they have. Resist that in week one.
- Threats and public complaints. A threat to sue, or a post on social media, can end a conversation a calm message might have saved, and whatever you write can later be read by others. Keep to facts and dates.
- A sudden stop in payment. Check your contract, and ask a lawyer before withholding any payment, because the contract may set out what follows. This guide gives no legal advice about contracts, invoices or disputes.
- Changing passwords or removing the developer’s access without a plan. If the developer holds the only administrator login, locking them out blindly can break the system. Know what you hold first.
- Hiring a replacement in a hurry. A builder who starts coding before reviewing what exists may duplicate work or build on a weak base.
- Handing live logins to many people. Give a reviewer the minimum access they need, for as long as they need it.
Ask in writing for the source code, documentation and logins
If the reply-by date passes, or in the first message as in the template, ask in writing for the things a new builder would need. Asking is not the same as being owed. Whether you are entitled to the source code depends on your contract and the law, which is explained in the source code ownership guide and is not repeated here. Ask politely anyway: many developers hand things over when asked clearly, and the record is useful whatever happens.
| What to ask for | What it is | Ask for it as |
|---|---|---|
| Source code | The human-readable program, usually kept in a code repository | Access to the repository, or a complete export that includes its history |
| Documentation | Notes on how the system is set up, how it works and how it is published to the server | Whatever exists, even if it is incomplete |
| Logins | Administrator access to the system, the hosting control panel, the database and any outside services | Accounts moved to your business email, or new logins created in your name |
| Your data | Customers, orders, invoices and uploaded files | A full export in a form you can open |
| Backups | The latest copies, and the place they are stored | The location, the schedule and how to restore |
| Setup notes | Which server, which settings and which services the system connects to | A short written list |
| Mobile app access | Developer-account access and the signing details used to publish updates | See app store developer accounts |
Number the items, give a date, and ask the developer to confirm in writing what has been sent. If part of the reply is “that belongs to us”, note it and move to the next step instead of arguing by message. That is the moment to ask a lawyer, not to raise your tone.
What a new builder needs before they can help
Any developer you approach will want to see what exists before saying what to do. Expect them to propose a read-only review first: a short piece of work in which they look at the code, the running system and the documents without changing anything, then tell you in writing what they found. Prepare these so the review is quick:
- Your page of facts: the contract, invoices, messages and who holds each account.
- Read-only access: to the repository if you have it, to a test copy if one exists, and to the live system only through a normal staff login.
- A recent data export, and a description in your own words of what the system should do, with the tasks staff carry out in it.
- A list of connections: payment gateway, email, SMS, accounting software, e-invoicing, or anything else it talks to.
- Known faults and unfinished items, kept in one running list as described in software maintenance after launch.
A review should end in written findings and a recommendation, not an automatic quote for a rebuild. Ask what was reviewed, what was not, and what could not be confirmed. If you are also comparing proposals from several builders, how to compare custom software quotes applies equally to a quote to repair or continue the work. Then you choose between four paths.
Choosing a path: wait and nudge, move on, repair or rebuild
| Path | Fits when | You need first | Main risk |
|---|---|---|---|
| Wait and nudge | There is still contact, progress is visible and the delay has a believable reason | A dated list of what is overdue and one reply-by date | Waiting becomes the default and quietly costs weeks |
| Move to a new builder | The code and accounts are in your hands and the work so far is sound | Source code, logins and a read-only review | The new builder needs time to learn the system, so budget for it |
| Repair | The system is live and mostly works, with a few faults, or needs updates to stay safe to use | Code and server access, a list of faults, working backups | Repairs on a poorly documented base can be slow and uncertain |
| Rebuild | You do not have the code, the base is unsound, or your needs have changed a lot | Your data export, written requirements and the old system as a reference | The most work and time; the old system must keep running meanwhile |
Rebuilding is not a failure. If you have your data and a clear picture of what the system does, a rebuild can sometimes be a better choice than repairing code nobody understands, and it gives you a base you own from day one. Plan it like any new project: keep the first version small as in scoping a first app version, move the records carefully as in moving your data into a new system, and choose how to switch over with phased rollout or big-bang launch.

The accounts you should hold in your own business name
Stalled projects hurt most when the accounts sit in the developer’s name. Use this as a checklist today for your current system, and before you sign for the next one.
- Domain: your business is the registrant, and the registrar login uses an email you control.
- Hosting or server: the account is in your business name, the bill comes to you, and at least two people can log in.
- Code repository: it sits in an account owned by your business, or a complete copy is delivered to you at each stage.
- Outside services: the payment gateway, SMS, email-sending, maps and similar services are registered to your business.
- App-store accounts: the Apple and Google developer accounts are in your business name, with the builder added as a collaborator.
- The system’s own administrator login: at least one administrator on your side, not shared and not the developer’s.
- Backups: at least one copy stored somewhere you can reach without the developer.
- Documentation: a current copy of the notes on how the system works, held by you.
- Renewal reminders: sent to an address that reaches you, not only to the supplier.
A worked example (made up): the stock system that went quiet
Orchard Trading, a made-up wholesaler with two warehouses, had a stock and ordering system built by a freelancer. It went live in July. In October staff said the low-stock report was wrong. The owner, Mei Ling, messaged the developer three times and heard nothing. Here is how her first week could go.
| Day | What she does |
|---|---|
| Day 1 | Writes the one-page fact sheet. Finds the contract and two paid invoices. Sees that the hosting renewal emails go to the developer’s address, while the domain is registered in her own company’s name. |
| Day 2 | Logs in with her own staff account and checks that orders still work. Exports the customer and stock lists to a spreadsheet and saves it in the company drive with limited access. |
| Day 3 | Finds the hosting renewal is three weeks away. Asks the hosting company what proof it needs to add her email as a contact on the account. |
| Day 4 | Sends the calm message with a reply-by date one week away, copying the second email address printed on the invoice. |
| Days 5 and 6 | No reply. She asks a second developer whether a read-only review is possible. Without the code there is little to review, so she notes the gap. |
| Day 7 | The date passes. She sends a short follow-up that lists the missing items by number, rereads the contract’s sections on handover and ending the work, and books a lawyer before deciding anything about payments. |
Whatever happens next, Mei Ling now has a record, knows a renewal will not lapse unnoticed, holds a data export, and understands that the decision depends on whether the code can be obtained. If it can, a new builder can continue or repair. If it cannot, she can plan a rebuild using the export and the old system as a reference.
How to avoid this next time
Most of the damage in the example came from decisions made before the build, not during the silence. These are cheap to agree at the start and hard to add later.
- Pay by milestone, tied to something you can see. Each payment should match a delivered, testable piece rather than a large amount up front. Agree the stages in the quote, as in comparing custom software quotes and fixed price or hourly rate.
- Sign off each stage after testing. Use user acceptance testing before a milestone is accepted.
- Require a written handover at every stage. The code, documentation, logins, data and setup notes, in a form another developer could pick up, delivered at each milestone and not only at the very end.
- Own the accounts from day one. Register the domain, hosting, repository and store accounts in your business name, and add the builder as a collaborator.
- Agree a second contact. A named second person on the supplier’s side, and a named owner on yours. Ask what happens if the main developer is unavailable.
- Keep a backup you control, and ask for a restore test, as set out in the security basics guide.
- Settle who looks after the system after launch, in writing, using the maintenance guide.
- Choose the kind of builder knowingly. A single freelancer, an in-house hire and a software company fail in different ways. See freelancer, in-house developer or software company, and prepare well for the first meeting with what to prepare before you talk to a developer.
Common mistakes
- Reacting before collecting facts. An hour of writing things down changes every later decision.
- Many messages on many channels. None dated, none kept, and no clear request in any of them.
- Assuming bad faith, or assuming nothing is wrong. Either assumption leads to the wrong tone. Stick to facts.
- Locking the developer out before knowing what only they can reach. You may break the live system.
- Stopping payment on impulse. Check your contract and ask a lawyer first.
- Letting a renewal lapse during the silence. Hosting and domain dates do not pause.
- Starting a rebuild without a data export or a review. You may pay to rebuild something that could have been repaired.
- Waiting for months because the system “still works”. Software needs looking after, and problems arrive on their own schedule.
- Treating a copy of the code as proof you can run the system. Code without the server settings, outside accounts and data may not run on its own.
- Signing the next project on the same terms. The cheapest time to fix the handover is before you sign.
Where Gotka Technologies fits
Gotka’s App & System Development service builds mobile apps, web apps and business systems, and it is quoted in writing once your needs are scoped. This guide is general advice for any owner in this situation. It describes no takeover service, and nothing in it should be read as an offer to take over, repair or audit a system built by someone else. For mobile app builds, Gotka publishes the app under a developer account registered in the client’s own business name, with Gotka added as a collaborator for the work, and the store registration fees are paid directly by the business to Apple or Google. If you are planning a new engagement and want to talk it through, get in touch.
Key terms used in this guide
- Source code: the human-readable instructions that make up a program, which a developer edits to change how it works.
- Repository: the place where source code and its history are stored, usually on a code-hosting service.
- Hosting: the server space where a website or system runs and is reachable online.
- Registrant: the person or business listed as the holder of a domain name.
- Handover: the delivery of code, documentation, logins and data so that another party can run and maintain the system.
- Milestone: an agreed stage of the work with a deliverable you can check and, usually, a payment attached.
- Read-only review: an examination of code, system and documents that changes nothing, ending in written findings.
- Backup: a separate copy of data and files that lets you recover if the original is lost or damaged.
- Restore test: proving a backup works by restoring it to a separate copy and checking the result.
- Developer account: the Apple or Google account under which a mobile app is published in the store.
What should I do first when my software developer stops replying?
Do not react yet. Write down what exists: the quote or contract, invoices and payments, messages, the system address, and who holds the hosting, domain and app-store accounts. Check that the system still runs and where its backups are. Then send one calm written message with a reply-by date, and ask in writing for the source code, documentation and logins.
How long should I wait before moving on?
There is no fixed number that suits every project. Give one clear reply-by date, often about a week away, and say what you will do next, such as asking another developer for a read-only review. Check your contract for any notice or handover terms first. If the date passes with no reply, decide between waiting, a new builder, repair or rebuild.
Can I get the source code if my developer has disappeared?
Ask in writing first, because many developers hand it over when asked clearly. Whether you are entitled to it depends on your contract and the law, so check what you signed and consider asking a lawyer. Without the code you can still keep your data, hold the accounts and plan a rebuild, using the old system as a reference for what it should do.
Should I stop paying a developer who has gone quiet?
Do not stop on impulse. Check your contract and ask a lawyer before withholding any payment, because the contract may set out what follows. This guide gives no legal advice about contracts, invoices or disputes. Keep every invoice, receipt and message, and match each payment to the stage it covered, so the record is clear whatever you decide.
What does a new builder need to take over a stalled system?
Expect a read-only review first. Prepare your page of facts, read-only access to the code and any test copy, a recent export of your data, a plain description of what the system should do, a list of the services it connects to, and any known faults. The review should end in written findings and a recommendation to continue, repair or rebuild.
Which accounts should be in my own business name?
The domain, the hosting or server, the code repository, outside services such as payment, SMS and email sending, and the Apple and Google developer accounts. The builder can be added as a collaborator. Keep at least one administrator login on your side, one backup you can reach without the developer, and renewal reminders sent to an address that reaches you.
Freelancer, In-House Developer or Development Company: Who Should Build Your Business System?
Freelancer, in-house developer or development company? A decision guide to who should build your business system, what to ask each, and where each fits.
App DevelopmentSigns Your Business Has Outgrown Spreadsheets
Multiple people editing one spreadsheet, no single source of truth for stock or orders, and decisions made on stale numbers are signs it's time for a system.
App DevelopmentOff-the-Shelf Software vs a Custom System: How to Choose
Off-the-shelf software works for most growing businesses, but not all of them. A framework for choosing between buying, customising or building custom software.


