The scope stays visible.
Every request starts with what will change, what will stay untouched, and what needs approval.
About Turning
A standing product workshop for one request at a time.
Send the request when something needs to change. We scope it, build it, review it with humans and agents, and ship the approved work within the week.
Why this exists
Small product requests deserve a steady lane.
Teams do not need a full rebuild every time a page, workflow, offer, message, or detail changes. They need a reliable way to move small, scoped product work from request to shipped without turning it into a project.
Turning is built for that loop: a narrow request, a visible scope, agent-assisted preparation, human review, and a shipped change that keeps the current product honest.
How we keep work moving
A tight loop from intake to shipped.
Every step is meant to keep one request understandable, bounded, and ready for review.
- 01
Send the request
Bring the context, links, assets, screenshots, and outcome that explain the change.
- 02
We scope the change
The request becomes a clear small piece of work with boundaries before build starts.
- 03
We review and ship
Agents help prepare the work, and a person owns judgment, QA, and the handoff.
Who is behind it
Human accountability stays at the center.
Turning is run by founder Jake Harris. Humans stay accountable for judgment, taste, and final review. Agents help inspect inputs, draft work, compare the result to the approved scope, and catch details that need another pass, but a person owns the handoff.
The loop stays small.
One request moves at a time so the workshop does not turn into an unbounded backlog.
The handoff stays human.
Agents can draft and inspect, but a person remains accountable for taste, judgment, and final review.
Keep one request moving.