Not Quite My Tempo

Not Quite My Tempo reviews pull requests in about a minute with line-by-line comments and severity flags, which lets an agency attach automated review to an existing client development retainer instead of selling it cold. The economics only work when the agency already sits inside the client's GitHub workflow, because the tool runs on GitHub as its review surface and Gemini as its engine, leaving no white-label layer to resell. Pricing scales per workspace, so a shop with several client repos should model workspace count before quoting a fixed fee.

Not Quite My Tempo only earns its keep when an agency already sits inside a client's GitHub workflow. The matrix has two axes: whether the agency has delivery access to the client's repositories, and whether the client ships pull requests often enough to feel a one-minute review cycle. High access plus high PR volume is the retainer zone: install the GitHub App, write a .fletcher.json with severity thresholds and ignore globs, and run Gemini on the client's own key so review credits never touch your bill. Low access is the dead zone, because the tool posts comments under Fletcher branding and cannot be white-labeled, so there is nothing to resell. A typical engagement: a 16-hour setup billed at $1,800 for a single-repo dev shop, then a monthly line item for tuning severity rules as the codebase grows. Price the retainer against the client's Gemini usage, not a flat fee.

AI code tools compress the cost of producing a first working version, but they do not compress the cost of owning it. The Scaffold Versus Steward Split separates two jobs agencies have historically billed as one: scaffolding (generating a full-stack app, wiring auth and payments, standing up a prototype) and stewardship (architecture decisions, review, and keeping consumer code in sync when contracts change). Scaffolding is where the speed advantage lives. Stewardship is where retainer value and liability live. Verdent illustrates the first half, turning a plain-English description into a working product with authentication, payments, and an admin dashboard. Ripple illustrates the second, detecting a breaking API change and opening pull requests across every affected repository. Agencies that price both halves at the same rate give away the margin on scaffolding and undercharge for stewardship. Split the two in your statements of work, and staff them differently.

The Agent Output Liability Line is the boundary between code an agency can ship under its own name and code that still needs a human signature. Agentic tools now generate full-stack applications from prompts and auto-fix breaking API changes across repositories, which moves the liability question from 'did we write it' to 'who reviewed it.' Agencies that blur this line absorb client risk without pricing it. A practical test: if an agent opens a pull request at 2am and no human reads the diff before merge, that code sits above the line and belongs in a maintenance retainer, not a fixed-scope build. Tools like Agent Monitor and Agent Desk exist specifically to make that review boundary visible by surfacing per-file risk levels and session histories. The framework matters because delivery speed without a defined liability line converts margin into unpaid warranty work.

Sell Not Quite My Tempo as a configured add-on to an existing development retainer, and put the Gemini key in the client's account before the first pull request is reviewed.

Set a hard blast-radius limit per agent run, then require a named human reviewer before any change merges into a client branch.

IF your agency already runs client work inside GitHub and wants a per-pull-request review layer that posts line-by-line comments within about a minute, THEN Not Quite My Tempo is worth a sandbox trial on Fletcher Pro, where 200 review credits a month run on Fletcher's keys and reviews on your own Gemini key never consume credits. IF clients need white-labeled review output or a non-GitHub review surface, THEN skip it, because Fletcher branding stays visible in PR comments and the analysis engine is fixed to Google's Gemini API.

Agencies install and configure Not Quite My Tempo on a client's GitHub repository, tune .fletcher.json for severity and scope, and hand off a documented automated PR review workflow that runs on the client's own Gemini API key.