What a Sprint Demo Should Show a Client
A sprint demo is a shared look at software that exists. If the only artifact is a slide, you had a status meeting. At Croncode we demo a TestFlight (or a staging URL) that a client can tap after the call. The point is not theater. The point is to agree what shipped, what failed, and what stays on the not-now list. Engineering sits in Istanbul. The LLC that can sign sits in Albuquerque.
A sprint demo should show a build the client can hold, the first job completed, one failed path, and what is not in the increment. A deck without a binary is a status meeting.
What is the minimum demo script?
- Name the build number and who can install it.
- Finish the first job once, live, on a small phone if you can.
- Trigger one error or empty state on purpose.
- Show the written not-now items you refused this week.
- Name the next increment in one sentence.
Design QA should already have a pass: design QA. Process choice lives outside the demo: fixed scope vs agile. Sequence: idea to App Store.
Which artifacts waste the hour?
| Artifact | Use | Skip |
|---|---|---|
| TestFlight | Always for iOS | Never if a binary exists |
| Figma | To compare a future increment | As a substitute for the build |
| Burn-down chart | If the contract is agile hours | If it hides a missing job |
| Competitor video | To name a job they fail | As a promise you will copy. Teardowns |
If the increment is a paywall, show StoreKit, not a picture: honest paywalls. If it is an AI path, show timeout and retry: fail-safe AI.
When should the client speak?
After the job, not during the first tap path. Ask: can a stranger finish this without us on the call. Ask: which not-now item they want to fight for. Do not take a new epic in the last five minutes without writing the cost. Feature creep: feature creep.
People on our side of the call: Goktug Unver, Yusufhan Sokur, Ozgur Ismet Ozkan. Dual-track weeks: products and client software.
How do consumer apps change the demo?
Show the job, not a studio reel. Closet: save a garment and build a look. Decision: structure one choice. Case: follow one clue. Journey: confirm one window. Those products: YourStyle, Numira, Spylie, Luviport. We do not demo fake rankings.
What we build: what Croncode builds. How we ship: Istanbul shipping.
What mistakes turn demos into theater?
- A recorded video of last week’s build: the live binary may have moved.
- No overlap hour: the client watches a ghost. Istanbul overlap.
- Hiding crashes until after the call: crash questions.
- Promising Android because the demo felt good: Android after iOS.
Quote the demo cadence in the packet: what to send. Commercial shape: fixed price vs retainer. Hire: hire. Custom: custom software. Contact: contact. Journal: /en/journel/.
What should happen in the twenty minutes after?
Send the build number, the not-now list, and the next increment in writing. If a stakeholder missed the call, they watch the binary, not a recap novel. Support and review owners should be named if you are close to store: support email, store account. Security topics stay off the screen share: security questions.
If the work is a marketing site increment, demo the deployed URL on the host you will keep: cPanel deploys.
Frequently asked questions
How long should the demo be?
Thirty to forty-five minutes is enough for one increment. If you need two hours, you are demoing two increments or a missing job.
Can we demo on the engineer’s phone only?
The engineer can drive. The client still needs an install or a TestFlight seat. A single hero device hides layout bugs.
What if the increment is backend only?
Show a user-visible consequence, even if it is an admin screen the operator will use. Invisible work still needs a proof.
Do you record every demo?
Only if the client asks and no secrets are on screen. Default is notes plus a build number.
Who runs the demo at Croncode?
The person who owns the increment. Names are public on the team pages. Start with Goktug Unver if you are booking the first one.
