Turner
From clicked options to a plan somebody can run.
An offer builder that turns chosen options into priced phases, and an accepted offer into a project with sprints, steps and a clock on each of them.
- steps — in every sprint, always the same eight
- 8steps in every sprint, always the same eight
- levels — phase, sprint, step — each with its own clock
- 3levels phase, sprint, step — each with its own clock
- shared secrets — at either end of a connection
- 0shared secrets at either end of a connection
- Role
- Product, architecture, build
- Period
- 2026 — now
- Stack
- Laravel Blade Tailwind CSS OAuth Webhooks SQLite
The problem
A quotation and a plan are usually two documents that stop agreeing the moment work starts. The quote is written to win the job and the plan afterwards to do it, with nothing carrying the promise from one to the other — so the phase priced at four days is never the phase whose hours anybody counts. What is missing is not a better estimate. It is one structure that is both the offer and the plan, so that what gets measured is what was sold.
How it works
Choose the options — the size, the kind of project, the complexity, the functional blocks — and the offer assembles itself: the run-up first, then the blocks ordered by risk and dependency, folded into as many phases as the size justifies, each with a deliverable and acceptance criteria. Accept it and those same phases become the project, cut into sprints of one to three weeks that each run the same eight steps. Every step carries its own clock, and what those clocks measure is held against the estimate the client was given.
What is in it
A phase is something you can use
Design, building and testing are steps inside every sprint, never phases of their own. A phase that hands over a back end nobody can open is a phase that invoices for something the client cannot take into use. So phases follow what the software does rather than who was doing it, and each ends in a finished, working product.
Invoiceable is three events, in order
The work is finished, then the client accepts it against criteria written into the offer, then it is invoiced — and only then does the warranty start. A sprint carries no price at all: it closes on the day it was due whether or not everything is done, leftovers move on, and a phase that needs another sprint grows in duration while the price stays where it was quoted.
A clock on every step
Each of the eight steps starts and stops on its own, in a fullscreen session that keeps ticking and asks what is being worked on. Work nobody clocked can be booked afterwards — a call, a meeting, a step somebody forgot — and it hangs on the sprint rather than being pushed onto the nearest step, because that would corrupt the only figures there are to check an estimate against.
What the clock does to the invoice
Decided per project. Where the work is billed by the hour the timers are the invoice. Where a price was fixed they are a signal instead: the hours are still valued at a rate, so a phase that took half or double what it was quoted at gets noticed before it is billed rather than after.
The client fills in the parts only they know
Who does what, the software already in the building, and what security has to hold are asked as forms behind one link per project — no account and no login. Only the roles a project actually needs are asked: a website is asked for an editor, an application is not. Several people per role, each marked first choice or stand-in, so there is somewhere to turn when the first does not answer.
Nothing shares a secret
Another application connects by holding a private key and signing a short assertion for a token that lives fifteen minutes; Turner keeps only the public half, so there is no shared secret to leak at either end. Every call and every refusal is recorded for ninety days — a key that still works cannot tell you it has been refused two hundred times since Tuesday.
The trade-off
Turner proposes and a person decides. When the hours on a fixed-price phase drift far enough from the quote to matter — past a share and an amount, so small phases do not nag and large ones do not stay quiet — it offers a second completion button at an adjusted figure, and never presses it. The quoted price is never rewritten either, only the amount actually invoiced: what the client was promised has to stay readable beside what they were billed, or the record is merely the last thing somebody thought.
Something like this on your list?
The projects differ, the way of working does not. Tell me what you are trying to solve.
Taking on new work