Expanding Release Candidate Testing
Congratulations on Reaching This Point!
You’ve now successfully shared your release candidate with 6 users. This is an important milestone — it shows that the system is strong enough to be tested in real-world conditions. The feedback you’ve already received is valuable: some minor bugs, some user suggestions, and a chance to see how the app performs outside of your own environment.
Now you are ready to expand to the next step. This is where you shift from building to validating adoption.
The Plan Going Forward
- Continue with the First 6 Testers
- Every piece of feedback they give must be logged into the task management system.
- Bugs are fixed quickly. Feature requests are logged but saved for future releases.
- This shows discipline and maturity, which will impress clients.
- Expand to 20 New Testers
- Create a list of 20 members across different councils. This ensures diversity and broader feedback.
- They will receive a download link to install the APK file on their Android phones.
- The process will be tracked so you know: who received the email, who installed, who gave feedback, and what follow-ups are needed.
- Why This Matters
- The way you handle this stage will shape how testers perceive you. If you look organized, professional, and responsive, they will talk positively about you.
- Every communication and response builds trust. Every logged bug and tracked follow-up makes you look like a serious company.
How to Communicate with Testers
Your role is to set expectations, manage relationships, and look polished.
- Remind testers that this is a release candidate, not the final product.
- Explain that you are fixing bugs now and feature requests will be considered for future releases.
- Be consistent: always thank them, always acknowledge their input, always keep it logged.
- Log ALL reports regardless of size, remember, your goal is to look polished. If even the smallest item gets lost in the shuffle then you are not living up to your full potential as a software company.
Common Phrases You May Hear — And How to Respond
- “Can you add this feature right away?”
→ “Great idea. We’re logging all feature requests for future releases. Right now we’re focused on stability so everyone has a reliable experience.” - “This button doesn’t do what I expect.”
→ “Thanks for pointing that out. I’ll log it right now so we can check if it’s a bug or something to improve in the future.” - “Why doesn’t it have [X] like other apps?”
→ “That’s a helpful comparison. We’re building steadily and focusing on what councils need most first. We’ll log this for future consideration.” - “It crashed when I did this.”
→ “I appreciate you telling me. That’s exactly the type of feedback we need at this stage. We’ll prioritize fixing that.” - “I’d like to see reports for [X].”
→ “That’s a strong suggestion. We’ll capture it in our tracker and look at it for a later release.” - “I told you about this already.”
→ “Thanks for following up. We log everything so nothing gets lost, and sometimes it takes a little time to prioritize fixes.” - “Can you make it faster?”
→ “Performance is important. We’re gathering feedback like this to make sure speed improves in the right areas.” - “When is the next update coming?”
→ “We’re rolling out updates regularly for bugs. New features will be bundled into future releases as adoption grows.” - “It’s good, but it’s missing [X].”
→ “Thanks — that’s useful to know. Missing features are being tracked and considered carefully for roadmap planning.” - “I’m not sure how to use this part.”
→ “That’s helpful feedback. If multiple testers are unclear, we’ll adjust instructions or make improvements.” - “Can we get this for our whole council yet?”
→ “We’re still in testing mode, but we’ll expand steadily. Your feedback is preparing us for wider rollout.” - “Why can’t I get what I asked for right now?”
→ “We’re running this like a professional software company — stability first, new features tied to growth. That ensures quality and fairness for all councils.”
What to Expect in This Phase
- More feedback than before. That’s good — it shows people care.
- Some complaints. Don’t panic; complaints mean engagement.
- Pressure for new features. Stay consistent: log them, thank them, and explain the roadmap.
- Questions you can’t answer. That’s fine — say “Let me check with our team” rather than improvising.
Why This Execution Matters
- Testers will judge you not just on the app, but on how you respond.
- Professional communication builds credibility and positions you as a real company.
- If you can stay disciplined and consistent, you will look like a company that councils can trust.
Bottom Line
You’re entering a critical stage. The product works. Now you must prove that you can manage feedback, scale adoption, and present yourselves as professional and disciplined. If you do this right, the councils will see you as a company that’s reliable, serious, and worth investing their trust in.