diff --git a/CMakeLists.txt b/CMakeLists.txt
index 95fb084..55aad93 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -22,7 +22,7 @@ set(PACKAGE "sai")
set(CPACK_PACKAGE_NAME "${PACKAGE}")
set(CPACK_PACKAGE_VERSION_MAJOR "0")
set(CPACK_PACKAGE_VERSION_MINOR "2")
-set(CPACK_PACKAGE_VERSION_PATCH "0")
+set(CPACK_PACKAGE_VERSION_PATCH "99")
set(CPACK_PACKAGE_RELEASE 1)
if (WIN32 OR MSVC)
set(CPACK_GENERATOR "7Z")
diff --git a/README.md b/README.md
index 76e2aa4..db359ff 100644
--- a/README.md
+++ b/README.md
@@ -1,13 +1,13 @@

-`Sai` (pronouced like 'sigh', "Trial" in Japanese) is a very lightweight
-network-aware distributed CI builder and coordinating server. It knows how to
-use `systemd-nspawn` and `overlayfs` to build remote git repos on a variety of
-distro versions very cheaply.
+[](https://warmcat.com/git/sai)
-On small targets, it can also build on the host rootfs directly, and can also
-run on an RPi3-class 'buddy' to flash and collect results (eg, over serial, or
-gpio) from even smaller targets.
+`Sai` (pronouced like 'sigh', "Trial" in Japanese) is a very lightweight
+network-aware distributed CI builder and coordinating server. You can run the
+sai-builder daemon on any number of devices to offer builds for that platform...
+builders can run on native boxes, inside systemd-nspawn contexts, inside VMs
+(eg, via qemu) for non-native arches, or on connected embedded devices which can
+be flashed and run the built results, controlled by gpio and serial.
A self-assembling constellation of Sai Builder clients make their own
connections to one or more Sai Servers, who then receive hook notifications,