Unfamiliar, then inevitable

A sentence in. Software out.

The product work you'd ship if you had a developer. Now you do.

24h

scope on clear requests

1 week

review-ready deliverable

$100/mo

no retainer

WORK IN MOTIONSENTENCE IN. SCOPED WORK OUT.

Showing request slots 01 · 02 · 03

RSVP system with host check‑ins

Build an RSVP system with host check‑ins and different user types

  1. DB

    Shipped

    Guests, hosts, roles, check‑in events

  2. API

    In progress

    RSVP create, update, lookup

  3. Auth

    In progress

    Host access and guest permissions

  4. Frontend

    Scoped

    Guest form and host screen

:: Problem

Small requests are where products quietly rot.

They are too small for a rebuild, too visible to ignore, and too easy to postpone until the wrong thing ships again.

01

Requests pile up between bigger projects.

The work is real, but too small to justify the projects that get attention.

02

The context is scattered across five tools.

Links, notes, screenshots, customer proof, and rough ideas sit in texts, inboxes, and docs.

03

Small fixes wait for a perfect moment.

The request drifts. The system it should fix stays wrong.

:: Outcome

One request, scoped and shipped within the week for $100/mo.

Turning takes the work you would hire an agency for and turns it into a subscription. Send the stale system, broken flow, or copy change. Get a written scope, a preview, and a shipped update. No retainer. Cancel anytime.

Scope first

We turn the request into what will change, what will not, and what we still need before build starts.

Small enough to ship

One request stays in flight, kept small enough to ship within the week.

Reviewed before it ships

The Turning reviewer scopes each request and reviews the shipped change against the approved scope.

:: Workflow

How a request becomes shipped work.

01 :: Request

Send the request.

Tell us what needs to change: a system edit, workflow tweak, service detail, image swap, event post, copy pass, broken link, or polish request.

02 :: Scope

We review the request and write the scope.

We review current context, your materials, and the constraints around the work. You see what will change, what will not, and what we still need.

03 :: Approve

You approve before any build starts.

Edit the scope or approve it as written. Build starts only when the request is clear enough to change the right system without touching unrelated work.

04 :: Build

We build the approved change.

Agents draft the change, inspect adjacent systems, list risks, and prepare a preview for the Turning reviewer.

05 :: Ship

We review and ship it.

The Turning reviewer reviews the work against the approved scope, then ships it or sends it back for your sign-off. Approved requests ship within the week.

:: Example requests

Real systems shipping here soon.

We are polishing the first three systems Turning has shipped against. Names and live URLs land in the next update.

System #1

Shipped change coming.

System #2

Shipped change coming.

System #3

Shipped change coming.

Send the request. Tell us what good looks like.

We will scope it, build it, review it, and ship what you approve.