# Kosuke Use Cases: AI Website Changes for Non-Developers > How agency owners, ops leads, marketing managers, founders and consultants use Kosuke previews and automated QA to check AI-made changes safely. Source: https://learn.ynteractive.com/content/blog/kosuke-use-cases-by-role · Updated 2026-10-20 · Free from Stepthrough (https://learn.ynteractive.com) Quick answer Kosuke fits any office role that owns a website or internal tool, uses an AI coding agent to change it, and needs to check the result without reading code: agency owners approving client changes, operations leads testing an internal app, marketing managers updating a site, founders running their own store, and consultants handing work to a client's developer. The workflow is the same for each, taught in two free lessons, [preview changes before your client does](https://learn.ynteractive.com/content/kosuke-preview-website-changes-before-client-sees) and [automated QA](https://learn.ynteractive.com/content/kosuke-automated-qa-test-ai-changes): ask in plain words, check the live Preview on desktop and phone, run `/kosuke:automated-qa`, share a link, and hand off a [pull request](https://learn.ynteractive.com/content/glossary/pull-request) with proof. Last updated October 20, 2026 [Take the free module →](https://learn.ynteractive.com/courses/ai-apps-worth-knowing/23)Module 23 of the free [AI Apps Worth Knowing](https://learn.ynteractive.com/courses/ai-apps-worth-knowing) course, about 15 minutes. No account needed. By [Robert Breen](https://learn.ynteractive.com/content/about) · Published October 20, 2026 · Updated October 20, 2026 · 5 min read Kosuke · AI coding · Use cases What changes by role is who reviews, what "done" looks like, and how much testing a change needs. ## What does every role get from the same workflow? | Step | What you do | What you get | | --- | --- | --- | | Ask | **New Session**, describe the change | A branch and sandbox, live site untouched | | Check | Click through the **Preview**, phone size on | Bugs found by you, not a client | | Test | `/kosuke:automated-qa` | A QA Report with a video per section | | Show | **Share preview** | A link anyone can open, no account | | Hand off | **Open PR** | A pull request with a `qa:` label and links | ## How do agency owners use it? This is the preview lesson's case. Jordan runs Harbor Lane Studio, a made-up agency with 12 client websites. Each change used to mean a staging copy, screenshots, emails and waiting, about 1.5 hours a change, and last month a booking button did nothing on phones for four days before the client noticed. With Kosuke, Jordan describes the change, checks it at phone size, runs QA and sends the client a share link before anything goes live. In the lesson's example numbers, that's about 20 minutes a change. - **Watch:** share links have no password or expiry. Revoke them after sign-off. ## How do operations leads use it? This is the QA lesson's case. Sam Alvarez runs operations at Acme, a made-up online store, and used to hand-test every change by opening test orders in every status, about 2 hours a change. A change to the orders page once showed shipped orders the wrong delivery window, and 38 customers emailed before anyone noticed. In the lesson, QA catches that same bug as a FAILED item, `--fix` repairs it, and a BLOCKED item is unblocked by adding a processing test order. - **Watch:** BLOCKED isn't a bug. Give the tester the [test data](https://learn.ynteractive.com/content/glossary/test-data) it needs, then name the item in the next run. ## Try it free, step by step **Kosuke: Let the AI Test Its Own Changes with Automated QA**. A business case for small teams that use an AI coding agent: price what hand-testing every change costs, then let Kosuke's automated QA test the change in a real browser, record video, fix what… You do every step yourself in a practice copy of Kosuke, it checks your work as you go, and “Do it for me” finishes any step you get stuck on. Free, and nothing touches your real accounts. [Start the free lesson](https://learn.ynteractive.com/modules/kosuke-automated-qa) [Or read the full step-by-step guide](https://learn.ynteractive.com/content/kosuke-automated-qa-test-ai-changes) ## How do marketing managers use it? A marketing manager who owns the company site asks for a new pricing section, a banner or a form change in plain words. The Preview shows the real page, not a mock-up, and the responsive toggle shows it at phone size, where most visitors will see it. The pull request goes to whoever maintains the site. - **Change:** set **Agent replies** to **Not-tech** so the agent explains what it did in plain language. - **Watch:** a passed report is evidence, not a guarantee. Read the page copy yourself. ## How do founders and small business owners use it? A founder running a store or booking site, with an [AI agent](https://learn.ynteractive.com/content/glossary/ai-agent) doing the code, uses Kosuke as the review step they never had. The Trial gives $10 of sandbox credit, granted once per person, with sandbox time billed by the second while it runs; the [AI model](https://learn.ynteractive.com/content/glossary/ai-model) runs on your own Anthropic or OpenAI account. - **Change:** give Kosuke access to only the one repository. - **Watch:** the live site changes only when a pull request is merged. Merge on GitHub when you're happy. ## How do consultants and freelancers use it? A consultant who makes changes in a client's repository can hand over a pull request that already carries the `qa: passed` label and a comment linking the QA Report, the Testing Checklist and each section's video. The client's developer reviews and merges as usual. - **Watch:** the Project QA Guide, saved in project settings under Advanced, should name the environment variable for a password, never the password. ## How do product and customer-facing teams use it? Anyone who signs off on changes others asked for, such as a product owner or a customer success lead, can open the share link, try the flow and read the QA Report, all without a Kosuke account or the code. The report lists failed and blocked sections first, and each item plays its video. - **Watch:** sharing a link wakes a paused sandbox, and that time counts toward usage. ## Which role should start with which lesson? Start with the preview lesson if your main job is approving changes for others, and the QA lesson if your main job is testing. Both share the same safety model: every change on its own [branch](https://learn.ynteractive.com/content/glossary/git-branch) and [sandbox](https://learn.ynteractive.com/content/glossary/sandbox-environment), merged only through a [pull request](https://learn.ynteractive.com/content/glossary/pull-request). For pitfalls see [Kosuke mistakes](https://learn.ynteractive.com/content/blog/kosuke-sensei-mistakes); for quick answers see the [Kosuke FAQ](https://learn.ynteractive.com/content/blog/kosuke-faq); for settings see the [preview cheat sheet](https://learn.ynteractive.com/content/cheat-sheets). Kosuke is listed in the [AI tools directory](https://learn.ynteractive.com/content/ai-tools/coding-developer#tool-kosuke). ## Key takeaways - One workflow fits every role: ask, check on phone, test, share, hand off. - Agencies gain client sign-off before go-live; ops gains recorded tests. - Non-developers stay in plain language with Not-tech replies. - Nobody's review is replaced: a person still clicks through and merges. ## Frequently asked questions **Which role saves the most time?** The lessons' examples: an agency at 20 changes a month, and an ops lead at 12 changes a month. Use your own numbers. **Can a client approve without a Kosuke account?** Yes. The share link opens the running site with no account. **Does Kosuke merge the change?** No. You or your developer merge the pull request on GitHub. **Is it only for websites?** The lessons use a client website and a store's orders page; the lessons describe it for websites and internal tools. ## Build it yourself, free **Preview Every Website Change Before Your Client Sees It using Kosuke**. A business case for agencies and small businesses that use an AI coding agent: price what an unchecked website change costs, then use Kosuke to give every change a live preview, check it on a phone… You do every step yourself in a practice copy of Kosuke, it checks your work as you go, and “Do it for me” finishes any step you get stuck on. Free, and nothing touches your real accounts. [Start the free lesson](https://learn.ynteractive.com/modules/kosuke-preview-changes) [Or read the full step-by-step guide](https://learn.ynteractive.com/content/kosuke-preview-website-changes-before-client-sees) ## Free lessons in this post - [Preview Every Website Change Before Your Client Sees It using Kosuke](https://learn.ynteractive.com/content/kosuke-preview-website-changes-before-client-sees): A business case for agencies and small businesses that use an AI coding agent: price what an unchecked website change costs, then use Kosuke to give every change a live… - [Kosuke: Let the AI Test Its Own Changes with Automated QA](https://learn.ynteractive.com/content/kosuke-automated-qa-test-ai-changes): A business case for small teams that use an AI coding agent: price what hand-testing every change costs, then let Kosuke's automated QA test the change in a real… ## Related terms Plain-English definitions, each with an example from a free lesson. [Pull request (PR)](https://learn.ynteractive.com/content/glossary/pull-request) · [AI agent](https://learn.ynteractive.com/content/glossary/ai-agent) · [AI model](https://learn.ynteractive.com/content/glossary/ai-model) · [Git branch](https://learn.ynteractive.com/content/glossary/git-branch) · [Preview deployment](https://learn.ynteractive.com/content/glossary/preview-deployment) · [Regression testing](https://learn.ynteractive.com/content/glossary/regression-testing) · [Sandbox environment](https://learn.ynteractive.com/content/glossary/sandbox-environment) · [Acceptance testing](https://learn.ynteractive.com/content/glossary/acceptance-testing) [The full AI glossary](https://learn.ynteractive.com/content/glossary) ## Keep reading - [Kosuke FAQ: Previews, Automated QA, Costs and Safety](https://learn.ynteractive.com/content/blog/kosuke-faq): Plain answers about Kosuke for non-developers: what it does, how previews and automated QA work, share links, pull requests and what the Trial covers. - [Kosuke Mistakes: 9 Ways to Misread AI Website Changes](https://learn.ynteractive.com/content/blog/kosuke-sensei-mistakes): Common Kosuke mistakes for agencies and ops teams: skipping the phone check, treating BLOCKED like FAILED, open share links, and trusting a pass blindly. - [AI Automation for HR Teams: 12 Questions Answered](https://learn.ynteractive.com/content/blog/ai-automation-for-hr-teams-faq): How HR teams use AI for a handbook agent, leave replies that don't overpromise and a team AI policy, with the guardrails each one needs. [All blog posts](https://learn.ynteractive.com/content/blog) · [All free tutorials](https://learn.ynteractive.com/content)