Recruit
Invite five testers from the target list.
Use this page during live beta sessions. The goal is simple: help a new user reach one useful result quickly, then collect honest feedback.
Use this as the operating checklist before wider launch. Each session should prove that a new user can create one useful Qanat AI output and understand what to do next.
Invite five testers from the target list.
Watch them create one useful output without coaching.
Capture friction, paying interest, and testimonial permission.
Use the feedback center to choose the next product fix.
Complete five first-session tests before adding major features.
Each tester should generate or approve one useful result.
Collect three approved quotes after confirming wording.
Start every beta session here. If this path feels slow, confusing, or blocked, fix that before adding new features.
Tester signs up or signs in without help.
Tester enters the website they want Qanat AI to audit.
Tester starts the first audit and waits for the report.
Tester generates one social, content, report, or growth output.
Keep the session moving. Start with account creation, complete Brand Kit if needed, generate one real output, then record feedback immediately.
Use when a beta user is ready to create a free account.
Check whether the user can add logo, colors, voice, and audience.
Test the strongest visual output workflow first.
Save confusion points, useful output signal, and quote permission.
See whether the 5-user and 3-testimonial goals are moving.
Tester creates a free Qanat AI account.
Open RegisterTester selects user type, adds a website, and starts setup.
Open OnboardingTester runs the first SEO audit without coaching.
Continue SetupTester tries an AI fix, social package, competitor comparison, or growth plan.
Open DashboardTester shares confusion points, value, and testimonial permission.
Collect FeedbackKeep outreach simple. Ask for a short test session, make it clear that feedback is the goal, and only ask for a testimonial after they see a useful result.
Hi, I am testing Qanat AI with a few local businesses. It reviews your website, finds growth opportunities, and creates marketing actions like social content, reports, and growth plans. Would you be open to a 20-minute test session? I am looking for honest feedback, not a sales call.
I am running a small beta for Qanat AI, an AI marketing platform that turns audits, competitors, and business profile context into client-ready marketing outputs. I would love your feedback as a marketer. The goal is to see if it saves time and where the workflow still feels unclear.
I am testing Qanat AI for agency-style workflows: audits, competitor intelligence, content, social assets, reports, and approval before publishing. Would your team be open to testing one client-style workflow and sharing what would make it worth using?
Quick follow-up on testing Qanat AI. I am only looking for honest product feedback. If it is useful, great. If it is confusing, that is useful too. Would you be open to a 20-minute walkthrough this week?
Use this as the live session checklist. Fill it in during each tester call so the next product decision is based on real usage, not guesses.
| Tester | Type | First audit | Useful output | Confusion point | Paying interest | Quote permission |
|---|---|---|---|---|---|---|
| Tester 1 | Local business owner | Yes / No | What they made | Where they paused | Pro / Agency / No | Yes / No |
| Tester 2 | Second local business | Yes / No | What they made | Where they paused | Pro / Agency / No | Yes / No |
| Tester 3 | Marketing freelancer | Yes / No | What they made | Where they paused | Pro / Agency / No | Yes / No |
| Tester 4 | Small agency or consultant | Yes / No | What they made | Where they paused | Pro / Agency / No | Yes / No |
| Tester 5 | Friend with a website | Yes / No | What they made | Where they paused | Pro / Agency / No | Yes / No |
Use this checklist during each live test. The goal is not to show every feature. The goal is to see whether a real user can create, understand, and review one valuable Qanat AI output.
The tester reached an SEO report without manual help.
They generated a report, social package, email, ad plan, or growth plan.
They could tell what Qanat AI created and what to do with it next.
They understood that Qanat AI waits for approval before applying or publishing.
They shared confusion points, willingness to pay, and testimonial permission.
Use this after each live test. A good beta session is not just "they saw the dashboard." It means the tester reached value, understood the workflow, and showed whether Qanat AI is worth improving for their use case.
| Check | Strong signal | Needs work | Session note |
|---|---|---|---|
| Time to first audit | Under 60 seconds | Needs help or takes too long | Pass / Needs follow-up |
| Useful output created | Tester would use the output | Output feels generic or unclear | Pass / Needs follow-up |
| Next action understood | Tester knows what to do next | Tester asks what the product does now | Pass / Needs follow-up |
| Approval flow understood | Tester understands review before publish | Tester thinks Qanat AI may auto-publish | Pass / Needs follow-up |
| Willingness to pay | Pro or Agency feels plausible | Value is not clear enough yet | Pass / Needs follow-up |
Only ask after the tester reaches a useful output or clear value moment.
Send the final quote back before publishing it anywhere.
Use beta customer wording only when the quote is approved.
Write down where the tester paused, asked a question, or expected Qanat AI to do more.
Open FeedbackMark whether the tested agent created a real preview, approval step, and usable output.
Review AgentsIf the result was useful, ask permission to follow up for a short testimonial.
View Testimonials