Before kickoff
- Name one decision-maker. One person who can say yes or no on behalf of the business. Five opinions with no final say is the most common cause of delays.
- Set up the accounts in your company's name. Repository, hosting, app store developer accounts, domain and any payment gateway. Some take days to approve, so start early. See who owns the code for why this matters.
- Collect real examples. Sample invoices, order forms, spreadsheets, reports: whatever your team uses today. They explain your workflow better than any description.
- Line up the people who'll use it. A short conversation with the staff or customers who'll use the system saves weeks of rework.
- Agree how you'll communicate. Which channel, which day for demos, and how quickly each side replies.
Every week during the build
- Join the demo. See working software, not a report. Ask questions; this is where misunderstandings get caught early.
- Answer questions within a day. A two-day wait for a decision can easily become a week of lost progress.
- Give feedback on the real thing. Click through what's been built and say what doesn't match how your business works.
- Keep priorities clear. If something becomes more urgent, say so before the next milestone is planned, not halfway through it.
- Write down new ideas, don't add them mid-sprint. Keep a list. Good ideas are easier to plan in than to squeeze in.
At each milestone
Test what's been delivered against the agreed acceptance criteria, report anything that doesn't work, and sign off when it does. Our guide to milestone payments explains how acceptance works.Before launch
- Content. Text, images, product data, email wording, help text. This is often the last thing ready.
- Legal pages. Privacy policy and terms, written or reviewed for your business.
- Data. If you're moving off spreadsheets or an old system, clean the data you're bringing across. Our data migration plan walks through it.
- Your team. Who trains staff, and who answers customer questions in the first week.
- A support plan. Agree how issues are reported and fixed after launch.
What slows projects down on the client side
- No single decision-maker, or one who's rarely available
- Accounts and access set up late
- Feedback held back until "it's finished"
- Content and data left until the last week
- New features added to the current milestone instead of the next one
How we work with clients
You get a weekly demo of working software, written updates between demos, and one named person who answers your questions. On the scoping call we agree your overlap hours, your decision-maker and the accounts to set up before kickoff, so the first week isn't spent waiting.FAQ
How much time will I need to spend on a software project?
Usually a weekly demo and a few quick replies on other days. Expect more at the start, while the scope is being agreed, and around launch.Do I need to be technical to manage a software agency?
No. You need to know your business and make decisions quickly. A good agency explains technical choices in plain language.What happens if I can't answer questions quickly?
The work waits, or the team makes an assumption that may need redoing. If you'll be unavailable, name someone who can decide in your place.Planning a build and want to know what it'll ask of you? Book a free scoping call.


