Lesson 4 of 6 · 25 min

Managing App Timelines and Change Requests

Keep projects on time and protect your margin when the client asks for more.

In this lesson1. Milestones your client can see2. A simple change request process3. When things slip4. Worked example: a change mid-build5. Common timeline mistakes

Milestones your client can see

Break the build into milestones the client understands: designs approved, first working screens, connections done, testing, launch. Share a short update every week in your brand, with what was done, what is next and anything you need from the client. Most delays come from waiting on the client for content, logins or decisions, so name those needs early.

A simple change request process

Changes are normal. Handle them with a written change request: what changes, why, the effect on time and cost, and the client's approval before work starts. Send each request to your build partner for an estimate first, then add your margin. Small changes can be bundled into a monthly batch so the project keeps moving.

Never absorb changes silently to keep a client happy. It erodes your margin and teaches the client that scope does not matter.

  • Describe the change and the reason
  • Estimate time and cost with your partner
  • Add your margin
  • Get written approval before work starts

When things slip

If a milestone slips, tell the client early with a new date and the reason. Agree with your partner what will be done to recover. Early, honest updates keep trust; late surprises lose it.

Worked example: a change mid-build

Halfway through a portal build, the client asked for a referral discount at checkout. The agency wrote a change request, sent it to the build partner for an estimate, added its margin and showed the client the cost and a one-week effect on the launch date. The client approved it in writing and the work was added to the plan.

Two smaller changes, a new field and a wording update, were bundled into the monthly batch without moving the date.

Common timeline mistakes

Timelines slip quietly unless someone watches them every week. A short update protects both the schedule and the relationship.

  • Absorbing changes for free
  • Not naming client inputs and their due dates
  • Reporting slips at the deadline instead of early
  • Skipping written approval for changes
Key takeaways
  • Use milestones the client understands and update weekly.
  • Name what you need from the client early.
  • Run every change through a written request with cost and time.
  • Report slips early with a new date.
Try it

Write a milestone plan for a sample app with five milestones and the client inputs each needs. Draft a change request template and fill it in for one realistic change.

Check your understanding

1. What causes many delays in client projects?

2. What must happen before a change is built?

3. How should a slipped milestone be handled?

← PreviousWhite-Label Agreements: NDA, IP and Non-SolicitationNext lesson →User Acceptance Testing: A Checklist Before Launch
XDQ Partner Network

Turn what you learn into monthly income

Resell AI agents and apps under your own brand. Up to 30% off credits, up to 30% recurring share, and apps built by XDQ Labs for your clients. Free to join.

Partner NetworkFor developer agenciesFor resellersFor consultantsWhite-label buildsDeal registration
Join the Partner Network free →
XDQ xAgents · AI lab for your company
While you sleep, your AI agents keep working.

From USD 49 or INR 2,999 a month. A person approves every step.

Start free, 14 days →See every agent300 credits · no card needed · prices include taxes🚀 Startup? Free landing page for 30 days →Need custom software or a security review? Send a brief →
Practise this lesson

Templates from our playbooks

Copy ready templates with when to use each one and why it works.

Playbook · Agency growthThe Agency LinkedIn Growth System: Positioning, a Weekly Content Engine, 10 Post Hooks and 40 Outreach MessagesFor software, AI and digital agencies. How to pick a niche, set up founder and team profiles, publish three posts a week, use hiring posts for reach, and start conversations with 40 messages for clients and partners.50 templates · 27 min readOpen the playbook →Playbook · Agency growthReach Beyond LinkedIn: A Channel by Channel Growth Plan for Agencies and ResellersGoogle Business Profile, WhatsApp Business, YouTube, Instagram, communities, directories, job platforms, partnerships, events, email and AI search. What each channel is good for, how to start, and 25 ready posts and captions.25 templates · 24 min readOpen the playbook →Playbook · Reselling software40 Sales Scripts for Software Resellers: Calls, WhatsApp, Demos, Objections and RenewalsFor people reselling software to small and mid sized businesses in India. Call openers, WhatsApp messages for warm leads, demo and no show scripts, objection replies, closing, onboarding and renewal scripts.40 templates · 25 min readOpen the playbook →