Product
Settle feasibility before the meeting ends.
Get an answer grounded in the code, turn the idea into a plan, and open a working version without taking an engineer out of focus time.
Product · Design · QA · Engineering
Give product managers, designers, testers, and engineers one shared AI workspace to plan, design, test, and build in your real product—with working previews and evidence everyone can review.
“Let couriers choose when they work, and only offer routes to couriers available that day.”
The bottleneck moved
More changes now reach the slowest part of the process: understanding the request, getting the app running, checking the real flow, and giving a reviewer enough context to decide. Gently changes what shows up for review.
One thread, start to finish
Stop after the answer, approve the plan, or carry the work all the way to a reviewable change. Gentlybot meets you where you are.
Ask how something works, whether an idea is feasible, or request a change in plain language.
Gently reads the real product and turns the request into a plan your team can review.
The work runs in an isolated copy of your app at a URL the whole team can open.
A browser walkthrough, checks, and a pull request arrive together—ready for judgment.
Design in the thread
Product and design can explore the flow together before anyone commits to an implementation.
Design prompt“Sketch two simple ways for couriers to set which days they are available to work.”
One constraint, three teams
Gently keeps the request, the running product, and the proof in one place—so each team can focus on the decision only they can make.
Product
Get an answer grounded in the code, turn the idea into a plan, and open a working version without taking an engineer out of focus time.
Engineering
Receive the change with its environment, checks, browser evidence, and context already attached.
QA
Turn a test plan into a real browser journey and keep the recording beside the work.
Test the real flow
QA can ask Gently to exercise the running product, follow both success and failure paths, and check what customers actually receive.
Testing prompt“Test that a courier can accept a route, deliver an order, and mark another delivery as failed. Check the customer emails too.”
What arrives at review
Gently opens the changed flow in a real browser, reads the app’s own errors and logs, and fixes what it finds before asking your team to review the work.
Built for trust
Gently gives more people a useful way to contribute without changing who controls production.
Experiments run apart from production and everyone else’s work.
Gently proposes the change. Your team reviews and decides what ships.
Prompts, files, checks, previews, and recordings remain together in one thread.
Yes. You don’t need a team to use Gently. Connect your own app, ask how it works, request a change, and review it in a running preview. Free is for one builder, and Starter is designed for solo builders and two-person teams. Explore Gently for founders
Yes. Connect the repositories and services that make up your app. Gently gets that product running in an isolated environment, rather than building a disconnected prototype.
No. Teammates work in Gently or ask from Slack, then open the running preview in their browser. Project setup is saved once for the team.
No. Gently works in a separate environment and opens a pull request. Your existing review and release process remains the production gate.
No. Teams also use it to answer product questions, investigate bugs, assess feasibility, draft plans, and run tests. Many useful threads do not change code at all.
Start with a question your team asks every week, or the small feature that keeps slipping down the backlog.