Running Not Quite My Tempo as a service, AI Code Tools

Not Quite My Tempo Agency Implementation, Code Quality Retainers

Learn how to deliver automated code review as a recurring service to software development teams using Fletcher's line-by-line pull request feedback and severity flagging. This course covers client onboarding, .fletcher.json configuration per repository, credit management across multiple codebases, and pricing strategies for code quality retainers.

Open the decision record for Not Quite My Tempo

What does running Not Quite My Tempo for clients commit you to?

Published figures for this service. Blank fields are not published.

Monthly tool cost
Vendor cost basis: free tier of 5 reviews; paid plan with monthly credits (specific amounts not published in supplied data). Optional bring-your-own Gemini API key for unlimited reviews. Agency must model its own labor and client pricing.
Time to first value
Not published
Payback
Not modeled, client price, labor, usage, overhead, and expected volume are not supplied
Guided implementation
8 hours

Is Not Quite My Tempo worth running as a client service?

The evidence supports Fletcher as a low-friction, configurable automated PR review layer on GitHub, with a free starting tier and Gemini-based analysis teams can trial. What remains unknown is the paid plan's dollar cost, the credit-to-review ratio, and whether client-reviewed output justifies a specific managed-service fee.

An agency-fit judgement for reselling this service. It is separate from the tool description on the decision record.

Before you start

What has to be in place before the first client engagement.

Tools and subscriptions

  • GitHub account and repository access for the client codebases to be reviewed
  • Fletcher GitHub App installed on selected repositories
  • Google Gemini API key (optional, for unlimited reviews under bring-your-own-key)
  • Repository guideline files (AGENTS.md or CLAUDE.md) and dependency manifests for context-aware analysis
  • .fletcher.json configuration file per repository

People and inputs

  • A developer or DevOps owner to install and maintain the GitHub App and .fletcher.json per client repo
  • A review-triage process for Critical, warning, and suggestion severity flags
  • Documentation for retrying or re-running reviews via the /fletcher again comment
  • Budget tracking for Gemini credits or API-key usage across client repositories

Lessons in this course

7 lessons on running Not Quite My Tempo for clients.

  1. 01Why Not Quite My Tempo Is a Retainer Add-On, Not a Standalone Agency ProductStrategy
  2. 02Not Quite My Tempo Retainer Fit MatrixConcept
  3. 03Not Quite My Tempo Rule: Bill It Only Where the Client Owns the Gemini KeyEvaluation Rule
  4. 04Not Quite My Tempo: Buy vs Skip (Agency PR Review Add-On)Decision Framework
  5. 05The Not Quite My Tempo Retainer Trap: Billing Clients for Reviews Nobody ReadsFailure Pattern
  6. 06Not Quite My Tempo PR Review Retainer Setup (5-7 days)Implementation Blueprint
  7. 07Not Quite My Tempo Client Repo Onboarding (.fletcher.json Setup) (Onboarding)Operating Procedure

Included with the course

7 working documents for delivering this service.

  • Fletcher Client Onboarding Checklistchecklist
  • Repository Configuration Template (.fletcher.json)template
  • Code Review Retainer Pricing Worksheetworksheet
  • GitHub App Installation and Permissions SOPsop
  • Review Credit Allocation Guide for Multi-Repo Clientsguide
  • Severity Flag Interpretation and Client Communication Templatetemplate
  • Monthly Review Performance Report Templatetemplate

Listed by name. These documents are not yet published as individual downloads.