Home / Blog App Development

Keeping a Custom Software Build on Track: A Weekly Check-In Routine for Non-Technical Owners

By Gotka Technologies ·

A smartphone home screen full of apps
What should I ask my developer for every week?

Ask for three things: a working demo of what changed, shown on a test copy; a short list of the decisions you owe, each with a needed-by date; and a running list of requested changes kept apart from the agreed scope. Add a brief note of risks and of what each side still owes in content, data and access. Ask for a short written summary the same day.

How long should a weekly check-in take?

For a small or medium build, about thirty minutes is common: a demo first, then decisions, the change list and risks. There is no fixed rule, so agree a rhythm with your builder in writing. A very small project may need only a written update every fortnight, and a busy final stretch may need short calls more often.

What slows a custom software project most?

Very often it is waiting on the client side: late decisions, late content such as text and photos, late data such as customer and stock lists, missing logins, slow feedback and testers who are not free. The builder cannot invent these. Listing each owed item with a name and a date makes the delay visible and easier to fix.

How do I tell a change request from something already in scope?

Check the written scope. If it already covers the item, it is part of the agreed work. If it is new, it is a change request, and it goes on the list with who asked, what it is, and its effect on time and cost. Something that does not work as agreed is a bug, not a change.

What are the warning signs that a build is drifting?

Demos replaced by status messages, the same item almost done for weeks, a go-live date that moves without a reason, changes agreed in conversation with no cost stated, a growing list of decisions waiting on you, and no mention of risks. Each is a prompt to ask a question, not proof of a problem.

What if my builder will not show a working demo?

Ask politely for a short demo on a test copy at the next check-in, and say that you want to see what changed. If none can be shown for several weeks, ask in writing what remains, in steps. If replies also slow down, follow the first-week steps for a stalled developer and consider legal advice about your contract.

WhatsApp
Get in touch

Send us a message

A real person from our team will get back to you.