// Digital products · by AMWARE

Playbooks from real client work.

Short, practical guides for founders and the engineers who work with them. Each one comes out of a real engagement.

Browse the libraryScore your contract free
Free checklist to startWritten by a working fractional CTO

01 · The library

Start with what you need this week.

Every guide comes out of an engagement. Pick by who you are. Courses live on their own page.

PDF guide · 16 pages

The 15-Minute Key Rotation Playbook

The Switch Clone method for rotating API keys and webhooks without taking production down. Eight provider runbooks included.

FoundersDevelopers
$12.00One-time
See the method

Checklist · 2 pages

Dev Shop Contract Red Flags

The seven clauses that cost non-technical founders money, time and sometimes their IP. Check them before you sign.

Founders
FreeEmail delivery
Score my contract

02 · The 15-Minute Key Rotation Playbook

Rotate a leaked key without breaking production.

The Switch Clone method runs the new key beside the old one, so nothing breaks while you switch. Here it is in three steps.

What's in the PDF · 16 pages

  • The Switch Clone method, step by step
  • Runbooks for eight providers
  • Architecture diagrams
  • Checklists you can copy into a ticket
$12.00One-time · PDF

03 · Free · Dev Shop Contract Red Flags

Score your dev-shop contract before you sign it.

Seven clauses, checked in order, about twenty minutes. Mark each one as it reads in your contract.

Your contract

0fails · 0 of 7 checked
Start with clause 1Mark each clause pass or fail. Nothing you mark here is saved or sent.

Get the full checklist

Two pages with the green-flag fix for each clause, free.

One email with the PDF. No newsletter unless you ask.

  1. 1
    Who owns the code?Look for "work made for hire" and an IP assignment, not a licence.
  2. 2
    What does "done" mean?If acceptance criteria are not written down, done is whatever the shop says.
  3. 3
    The hourly-overage trapdoorA "fixed price" that bills anything outside a vague spec by the hour.
  4. 4
    Who holds the keys?Repos, cloud accounts and domains that live under the shop's accounts.
  5. 5
    The maintenance handcuffAuto-renewing retainers, or a warranty void once anyone else touches the code.
  6. 6
    No exit planTerminate mid-build and they keep the money and the work in progress.
  7. 7
    The documentation black holeNo obligation to document means only they can maintain it.