A single point of contact
The most important thing you can do is designate a single person on your side who has authority to make decisions on behalf of your organisation. Projects where feedback has to be approved by committee move slowly and accumulate conflicting requirements.
Timely feedback
At the end of each sprint, you will receive a staging environment link and a list of what is ready for review. We need your feedback within three working days. Feedback that arrives after this window risks delaying the next sprint.
Feedback on staged work should be specific. "This is not quite right" is not actionable. "The table should show the last 30 days by default, not all time" is.
Content and assets
If the project requires content — copy, images, branding assets, product data — we need these before the sprint where they will be used. Waiting for content is one of the most common causes of project delays.
Access and credentials
We will need access to any systems the project integrates with. This means API credentials, sandbox accounts, or read access to production data for reference. Gather these before the kick-off call.
Decisions in a reasonable timeframe
We will occasionally ask questions that require a business decision — prioritisation choices, edge case handling, or scope clarifications. These should be resolved within one business day where possible. Delayed decisions are the most common cause of projects running over timeline.
What you do not need to do
You do not need technical knowledge. You do not need to review pull requests or understand the code. You do not need to manage the development process — that is our job. Your role is to ensure the project reflects your business needs, provide timely feedback on working software, and make decisions when we need them.