FlunesUse case · Agencies & freelancers
Collect client feedback straight into GitHub
Clients send feedback over email, calls, and shared docs, and you retype it into GitHub. Flunes gives each client one link to report a bug or request; every submission becomes a clean GitHub issue, with no GitHub account for them and no per-client seat for you.
Clients report without GitHub
Each client gets a private magic link, no account, no login, nothing to install. They describe the problem in plain language; optional AI follow-up questions fill the gaps a developer would otherwise have to chase.
You get a clean, labeled issue
Every submission lands in the right repo as a structured GitHub issue, labeled by type and priority, with a link back to the original message and any screenshots.
No per-client pricing
Invite as many clients and stakeholders as you want, Flunes prices on flat tiers with unlimited collaborators, so cost never scales with how many people report.
Keep each client separate
Run several clients or projects at once without their feedback bleeding together. Connect each repository on its own, and every repo gets its own invite link and submission history, so a report from one client never lands in another client's project. When you onboard a new client, you hand them their link; when an engagement ends, that history stays attached to the right repo. You decide who reports where, and the client feedback to GitHub flow stays scoped per project instead of one shared inbox you have to sort by hand afterwards.
What the client actually sees
Reporters never touch GitHub. After sending feedback through their link, they can check a simple status page to see whether you have picked it up, and reply to your follow-up questions straight from email. When you close the issue in GitHub, they get a resolved notification without you writing a separate update. There is no annotation overlay, no website widget, and no dashboard to learn. Just a link to report and a clear answer on where things stand, which keeps non-technical clients comfortable and stops them from re-sending the same request because they assumed it was lost.
Cut the chase-up time
Most agency hours leak into clarifying vague reports and copying messages from email and calls into issues by hand. Flunes removes the retyping step, and optional AI follow-up questions gather the missing details up front, so a developer is not emailing the client to ask which page broke or what they expected. Fewer round trips means client feedback to GitHub arrives ready to work on. To be clear, Flunes does not prioritise or triage for you; it gets clean, answerable issues into the repo. The judgement on what to build stays with your team in GitHub.
FAQ
Do clients need a GitHub account?
No. Clients report through a private link with no GitHub account, no signup, and nothing to install.
Can I separate feedback per client or project?
Yes. Each connected repo has its own invite links and submission history, so client feedback stays scoped to the right project.